The Process of Implementation | The Applying and Testing of Turnkey Transmission | The Applying and Downloading of Alphanumeric Letters | Reference Material and Examples |
---|---|---|---|
1. The solution to Implementing of E-Invoice for Cross-border E-commerce Suppliers 2. Select Upload Method of E-Invoice | 3. Apply for Turnkey Transmission 4. Download and Install Turnkey 5. Apply online for Transmission Certificate 6. Apply for Turnkey online Test | 7. Apply for Alphanumeric Numbers 8. Download Alphanumeric Numbers | 9. Reference material and Information 10. MIG format Examples |
According to the Article 7-1-2 of the Regulations Governing the Use of Uniform Invoices issued by Ministry of Finance on July 16, 2018, the business entity (prescribed in Subparagraph 4, Article 6 of the Act) shall issue cloud invoices to purchasers".
(1)The process of E-Invoice for Cross-border E-commerce (Chinese Version) (English Version)
(2)In response to the requirements, Cross-border E-commerce Suppliers add accordingly the “Invoice Period” and “Invoice No.” to current consumer transaction information, and choose to add “promotional text of E-Invoice carrier consolidation”.
Reference Material and Information
The Cross-border E-commerce suppliers can choose to upload E-Invoices(include cloud invoices) by value-adding centers or by themselves using Turnkey, the transmission software of Ministry of Finance.
(1) For value-adding centers to upload the E-Invoice(include cloud invoices), please go to "search for value adding locations" on the E-Invoice Platform (the Platform) to search for the value adding locations nearby.
(2) To upload E-Invoice(include cloud invoices) by themselves, please download Turnkey and test it on the Integrated Service Platform in order to receive Notice of Approval for online. The testing process basically includes “apply for Turnkey transmission”, “download and install Turnkey”, “apply online for transmission certificate” and “Turnkey online test”. The process descriptions are as follows:
Fill out online the form of "Application Form for of E-Invoice Platform (for the use of Cross-border E-commerce Suppliers Only)". After the application was submitted successfully, the Platform will send out a Notice of Approval for Turnkey of E-Invoice Platform via email address provided on the application in 14 days basically. Please fill out a new application online if there is a change of IP or email address. Please go to: "eTax Portal, Ministry of Fincnce/Tax on Cross-border Electronic commerce/Cloud Invoice/Apply for Turnkey Transmission/Cross-border electronic commerce Business Entity Function Menu/Basic Functions/Application Form for E-Invoice Integrated Service Platform
(1) The Description of the Application Form for E-Invoice Integrated Service Platform (for the use of Cross-border E-commerce Suppliers only)
(2)Email The Example for Notice of Approval on Turnkey of E-Invoice Platform:
To transmit E-Invoice by Turnkey, the transmission must be signed electronically through certificate to ensure the identity of transmitter is undeniable. Please go to the Mixed Organization Certification Authority (XCA) and apply online for the 「Non-IC Card Certificate for Organization and Group」, then import the Certificate to Turnkey and register it with the Platform.
(1).The process of application and registration of transmission certificate:
(2) Registration of Transmission Certificate
(1) The transmission and exchange of E-Invoice information must comply with the "Message Implementation Guideline For E-Invoice Data Exchange(MIG) ver.3.2".(Chinese Version)(English Version)
(2) Before using Turnkey to transmit information, you must complete Turnkey Online Test in order to ensure the accuracy of the transmission. For detail, please refer to "E-Invoice Self-Test before Turnkey Goes Online(v4.4)"﹝Chinese Version﹞﹝English Version ﹞.
(3) Go to the Platform (testing environment) and register the Certificate (CER)
Path: "eTax Portal, Ministry of Finance /Tax on Cross-border Electronic commerce/Cloud Invoice/Apply for Turnkey Online Test/Cross-border Electronic commerce Business Entity Function Menu/Basic Functions/Software Certificate Registration".
(4) Complete the test according to "E-Invoice Self-Test before Turnkey Goes Online(v4.4)". When finished, upload the E-Invoice(include cloud invoices) to the Platform (testing environment), then go to the Platform and fill out the forms for testing. Written paper will need to be transformed to PDF files and uploaded to the Platform for review. On receipt of the files, the technical customer service of E-Invoice will provide feedback in about 2-3 days (the responding time may vary depending on how many cases they received). After that, the Platform will send out a Notice of Approval to those who pass the test and provide them with formal environment for E-Invoice(include cloud invoices) uploading.
1. Path: eTax Portal, Ministry of Finance /Tax on Cross-border Electronic commerce/Cloud Invoice/Apply for Turnkey Online Test
2. Please refer to "E-Invoice Self-Test before Turnkey Goes Online(v4.4)" for instructions of filling out the forms on the Platform.
(5) Testing Items for Turnkey Online Test:
Reminder:Do not send real personal and business data to test.
Please go to "eTax Portal, Ministry of Finance" to apply online for E-Invoice Alphanumeric Numbers. Basically, it takes 7 days for local branch or office of National Taxation Bureau to review and approve.
Path: eTax Portal, Ministry of Finance /Tax on Cross-border Electronic commerce/Cloud Invoice/Apply for Alphanumeric Numbers online"
(1) You may go online to apply for the alphanumeric numbers and have the value adding location to download them for you at the same time.
(2) Use Turnkey to download E-Invoice alphanumeric numbers by yourself
(1) Message Implementation Guideline For E-Invoice Data Exchange (MIG) ver3.2 ﹝Chinese Version﹞﹝English Version﹞
(2) The manual of Turnkey for E-Invoice Platform (ver. 2.7) ﹝Chinese Version﹞﹝English Version﹞
(3) Download the Transmission Software Turnkey of Ministry of Finance ﹝Chinese Version﹞﹝English Version﹞
(4) E-Invoice Self-Test before Turnkey Goes Online(v4.4) ﹝Chinese Version﹞﹝English Version﹞
(1) The Description of B2C invoice format example (example download)
Element name | XML Schema syntax | Data length | Necessity | Remark |
RoleDescriptionType | <xsd:group name="RoleDescriptionType"> | M |
Element name | XML Schema syntax | Data length | Necessity | Remark |
Identifier | type="BAN" | M | ||
Name | xsd:string xsd:minLength value="1" xsd:maxLength value="60" | 60 | M | Seller: Tax registration name of business entity Buyer: personal identifier that allows a business entity to inform consumers (for public auditing). It contains 4 ASCII characters or 2 full-width Chinese characters.The name of consumer or a consumer identifier developed by business entity (e.g.: the last 4 digit of the membership carrier; the last 4 digits of the member’s birth date; those who have not had one are advised to provide a random identifier that is different from the random identifier as the personal identifier) is acceptable. |
Address | xsd:string xsd:maxLength value="100" | 100 | O | |
PersonInCharge | xsd:string xsd:maxLength value="30" | 30 | O | |
TelephoneNumber | xsd:string xsd:maxLength value="260" | 26 | O | |
FacsimileNumber | xsd:string xsd:maxLength value="26" | 26 | O |
(2)Specifications of element “MessageTypeEnum”
Element name | XML Schema syntax | Data length | Necessity | Remark |
MessageTypeEnum | xsd:string xsd:minLength value="5" xsd:maxLength value="5" | 5 | M | A0101, A0102, A0201, A0202, A0301, A0302, A0401, A0501, A0601, B0101, B0102, B0201, B0202, B0401, B0501, C0401, C0501, C0701, D0401, D0501, E0401, E0402, E0501 |
(3) Specifications of element “InvoiceTypeEnum”
Element name | XML Schema syntax | Data length | Necessity | Remark |
InvoiceTypeEnum | xsd:string xsd:minLength value="2" xsd:maxLength value="2" xsd:pattern value="0[1-8]" | 2 | 07: electronic uniform invoice for general tax calculation 08: electronic uniform invoice for special tax calculation |
(4) Specifications of element “AllowanceNumberType”
Element name | XML Schema syntax | Data length | Necessity | Remark |
AllowanceNumberType | xsd:string xsd:minLength value="1" xsd:maxLength value="16" | 16 | The allowance form numbers are required not to be repeated even carried over from the previous year, or they will be rejected by the system. |
(5) Specifications of element “AllowanceTypeEnum”
Element name | XML Schema syntax | Data length | Necessity | Remark |
AllowanceTypeEnum | xsd:string xsd:minLength value="1" xsd:maxLength value="1" xsd:pattern value="[1-2]" | 1 | 1: allowance certificate issued by buyer 2: allowance certificate issued by seller For Cross-border E-commerce Suppliers who issue notice of allowance certificate, please enter 2. |
(6)Specifications of element “BAN”
Element name | XML Schema syntax | Data length | Necessity | Remark |
BAN | xsd:string xsd:minLength value="0" xsd:maxLength value="10" | 10 | Cross-border E-commerce supplier: |
(7)Specifications of element “BuyerRemarkEnum”
Element name | XML Schema syntax | Data length | Necessity | Remark |
BuyerRemarkEnum | xsd:string xsd:minLength value="1" xsd:maxLength value="1" xsd:pattern value="[1-4]" | 1 | 1: goods purchased and expenses that are deductable 2: fixed assets that are deductable 3: goods purchased and expenses that are not deductable 4: fixed assets that are not deductable |
(8) Specifications of element “InvoiceNumberType”
Element name | XML Schema syntax | Data length | Necessity | Remark |
InvoiceNumberType | xsd:string xsd:minLength value="10" xsd:maxLength value="10" < xsd:pattern value="[A-Z]{2}\d{8}/> | 10 | Alphabetic letters included For example: QQ12345678 |
(9) Specifications of element “DonateMarkEnum”
Element name | XML Schema syntax | Data length | Necessity | Remark |
DonateMarkEnum | xsd:string xsd:minLength value="1" xsd:maxLength value="1" xsd:pattern value="[0-1]" | 1 | 0: uniform invoices not donated 1: uniform invoices donated |
(10) Specifications of element “TaxTypeEnum”
Element name | XML Schema syntax | Data length | Necessity | Remark |
TaxTypeEnum | xsd:string xsd:minLength value="1" xsd:maxLength value="1" xsd:pattern value="[1,2,3,4,9]" | 1 | 1: taxable 2: zero tax rate 3: tax-free 4: taxable (special tax rates apply) 9: mixture of taxable and tax-free or zero-tax-rate items (for message C0401 only) |
(11) Specifications of element “CarrierTypeEnum”
Element name | XML Schema syntax | Data length | Necessity | Remark |
CarrierTypeEnum | xsd:string xsd:maxLength value="6" | 6 | Carrier type is 6 code. Cross-border E-commerce supplier: ●According to Article7-1-2 of Regulations Governing the Use of Uniform Invoices "The business entity prescribed in Subparagraph 4, Article 6 of the Act shall issue cloud invoices to the purchaser". ●Purchaser use carrier approved by Ministry of Finance for Cross-border E-commerce E-Invoice (i.e. consumer’s E-mail address) to request E-Invoices issued by Cross-border E-commerce Suppliers. The code of carrier type, 5G0001, should be entered. |
(12) Specifications of element “CurrencyCodeEnum”
Element name | XML Schema syntax | Data length | Necessity | Remark |
CurrencyCodeEnum | xsd:string xsd:minLength value="3" xsd:maxLength value="3" | 3 | AED:United Arab Emirates, Dirhams AFN:Afghanistan, Afghanis ALL:Albania, Leke AMD:Armenia, Drams ANG:Netherlands Antilles, Guilders (also called Florins) AOA:Angola, Kwanza ARS:Argentina, Pesos AUD:Australia, Dollars AWG:Aruba, Guilders (also called Florins) AZN:Azerbaijan, New Manats BAM:Bosnia and Herzegovina, Convertible Marka BBD:Barbados, Dollars BDT:Bangladesh, Taka BGN:Bulgaria, Leva BHD:Bahrain, Dinars BIF:Burundi, Francs BMD:Bermuda, Dollars BND:Brunei Darussalam, Dollars BOB:Bolivia, Bolivianos BRL:Brazil, Brazil Real BSD:Bahamas, Dollars BTN:Bhutan, Ngultrum BWP:Botswana, Pulas BYR:Belarus, Rubles BZD:Belize, Dollars CAD:Canada, Dollars CDF:Congo/Kinshasa, Congolese Francs CHF:Switzerland, Francs CLP:Chile, Pesos CNY:China, Yuan Renminbi COP:Colombia, Pesos CRC:Costa Rica, Colones CUP:Cuba, Pesos CVE:Cape Verde, Escudos CYP:Cyprus, Pounds (expires 2008-Jan-31) CZK:Czech Republic, Koruny DJF:Djibouti, Francs DKK:Denmark, Kroner DOP:Dominican Republic, Pesos DZD:Algeria, Algeria Dinars EGP:Egypt, Pounds ERN:Eritrea, Nakfa ETB:Ethiopia, Birr EUR:Euro Member Countries, Euro FJD:Fiji, Dollars FKP:Falkland Islands (Malvinas), Pounds GBP:United Kingdom, Pounds GEL:Georgia, Lari GGP:Guernsey, Pounds GHS:Ghana, Cedis GIP:Gibraltar, Pounds GMD:Gambia, Dalasi GNF:Guinea, Francs GTQ:Guatemala, Quetzales GYD:Guyana, Dollars HKD:Hong Kong, Dollars HNL:Honduras, Lempiras HRK:Croatia, Kuna HTG:Haiti, Gourdes HUF:Hungary, Forint IDR:Indonesia, Rupiahs ILS:Israel, New Shekels IMP:Isle of Man, Pounds INR:India, Rupees IQD:Iraq, Dinars IRR:Iran, Rials ISK:Iceland, Kronur JEP:Jersey, Pounds JMD:Jamaica, Dollars JOD:Jordan, Dinars JPY:Japan, Yen KES:Kenya, Shillings KGS:Kyrgyzstan, Soms KHR:Cambodia, Riels KMF:Comoros, Francs KPW:Korea (North), Won KRW:Korea (South), Won KWD:Kuwait, Dinars KYD:Cayman Islands, Dollars KZT:Kazakhstan, Tenge LAK:Laos, Kips LBP:Lebanon, Pounds LKR:Sri Lanka, Rupees LRD:Liberia, Dollars LSL:Lesotho, Maloti LTL:Lithuania, Litai LVL:Latvia, Lati LYD:Libya, Dinars MAD:Morocco, Dirhams MDL:Moldova, Lei MGA:Madagascar, Ariary MKD:Macedonia, Denars MMK:Myanmar (Burma), Kyats MNT:Mongolia, Tugriks MOP:Macau, Patacas MRO:Mauritania, Ouguiyas MTL:Malta, Liri (expires 2008-Jan-31) MUR:Mauritius, Rupees MVR:Maldives (Maldive Islands), Rufiyaa MWK:Malawi, Kwachas MXN:Mexico, Pesos MYR:Malaysia, Ringgits MZN:Mozambique, Meticais NAD:Namibia, Dollars NGN:Nigeria, Nairas NIO:Nicaragua, Cordobas NOK:Norway, Krone NPR:Nepal, Nepal Rupees NZD:New Zealand, Dollars OMR:Oman, Rials PAB:Panama, Balboa PEN:Peru, Nuevos Soles PGK:Papua New Guinea, Kina PHP:Philippines, Pesos PKR:Pakistan, Rupees PLN:Poland, Zlotych PYG:Paraguay, Guarani QAR:Qatar, Rials RON:Romania, New Lei RSD:Serbia, Dinars RUB:Russia, Rubles RWF:Rwanda, Rwanda Francs SAR:Saudi Arabia, Riyals SBD:Solomon Islands, Dollars SCR:Seychelles, Rupees SDG:Sudan, Pounds SEK:Sweden, Kronor SGD:Singapore, Dollars SHP:Saint Helena, Pounds SLL:Sierra Leone, Leones SOS:Somalia, Shillings SPL:Seborga, Luigini SRD:Suriname, Dollars STD:Sao Tome and Principe, Dobras SVC:El Salvador, Colones SYP:Syria, Pounds SZL:Swaziland, Emalangeni THB:Thailand, Baht TJS:Tajikistan, Somoni TMM:Turkmenistan, Manats TND:Tunisia, Dinars TOP:Tonga, Pa'anga TRY:Turkey, New Lira TTD:Trinidad and Tobago, Dollars TVD:Tuvalu, Tuvalu Dollars TWD:Taiwan, New Dollars TZS:Tanzania, Shillings UAH:Ukraine, Hryvnia UGX:Uganda, Shillings USD:United States of America, Dollars UYU:Uruguay, Pesos UZS:Uzbekistan, Sums VEB:Venezuela, Bolivares (expires 2008-Jun-30) VEF:Venezuela, Bolivares Fuertes VND:Viet Nam, Dong VUV:Vanuatu, Vatu WST:Samoa, Tala XAF:Communaute Financiere Africaine BEAC, Francs XAG:Silver, Ounces XAU:Gold, Ounces XCD:East Caribbean Dollars XDR:International Monetary Fund (IMF) Special Drawing Rights XOF:Communaute Financiere Africaine BCEAO, Francs XPD:Palladium Ounces XPF:Comptoirs Francais du Pacifique Francs XPT:Platinum, Ounces YER:Yemen, Rials ZAR:South Africa, Rand ZMK:Zambia, Kwacha ZWD:Zimbabwe, Zimbabwe Dollars |
(13) Specifications of aggregate “DateType”
Element name | XML Schema syntax | Data length | Necessity | Remark |
DateType | xsd:string xsd:minLength value="8" xsd:maxLength value="8" xsd:pattern value="[0-9][0-9][0-9][0-9] ((0[1-9]|1[0-2]))((0[1-9]|[1-2][0-9])|(3[0-1]))" | Taiwan time zone UTC+8 Supports only AD dates, for example: 20170101 |
(14) Specifications of aggregate “DateType”
Element name | XML Schema syntax | Data length | Necessity | Remark |
TimeType | xsd:time | Taiwan time zone UTC+8 |
(1)Specifications of aggregate “Invoice”
Element name | XML Schema syntax | Data length | Necessity | Remark |
Main | <xsd:element name="Main" type="Main"/> | M | ||
Details | <xsd:element name="Details " type="Details"/> | M | ||
Amount | <xsd:element name="Amount" type="Amount"/> | M |
(2)Specifications of element “Invoice/Main”
Element name | XML Schema syntax | Data length | Necessity | Remark |
InvoiceNumber | type="InvoiceNumberType" | M | See the specifications of element “InvoiceNumberType” for definition and example. | |
InvoiceDate | type="DateType" | M | See the specifications of element “DateType” for definition and example. | |
InvoiceTime | type="TimeType" | M | See the specifications of element “TimeType” for definition and example. | |
Seller | xsd:group ref="RoleDescriptionType" | M | See the specifications of element “RoleDescriptionType” for definition. | |
Buyer | xsd:group ref="RoleDescriptionType" | M | See the specifications of element “RoleDescriptionType” for definition. | |
CheckNumber | xsd:string xsd:maxLength value="1" | 1 | O | This field is not transmitted if the buyer is provided with the certificate of an electronic uniform invoice. Enter “P” if a physical uniform invoice, not an electronic one, is provided. The Cross-border E-commerce suppliers do not need to submit the information of this field. |
BuyerRemark | type="BuyerRemarkEnum" | O | See the specifications of element “BuyerRemarkEnum” for definition. | |
MainRemark | xsd:string xsd:maxLength value="200" | 200 | O | Matters required by tax law or other applicable rules shall be provided in this field. |
InvoiceType | type="InvoiceTypeEnum" | M | See the specifications of element “InvoiceTypeEnum” for definition. | |
GroupMark | xsd:string xsd:length value="1" | 1 | O | Separate with “*” |
Donate Mark | type="DonateMarkEnum" | M | See the specifications of element “DonateMarkEnum” for definition. The NPOBAN shall not be left blank if DonateMark is 1 | |
CarrierType | type="CarrierTypeEnum" | O | See the specifications of element “CarrierTypeEnum” for definition and example. The fields is required for Cross-border E-commerce supplier. Purchaser use carrier approved by Ministry of Finance for Cross-border E-commerce E-Invoice (i.e. consumer’s E-mail address) to request E-Invoices issued by Cross-border E-commerce Suppliers. The code of carrier type, 5G0001, should be entered. | |
CarrierId1 | xsd:string xsd:maxLength value="64" | 64 | O | Accorded CarrierType to fill corresponding CarrierId. 1. Cellphone barcode : is an 8-digit code starting with a slash “/” 2. Citizen Digital Certificate barcode : is a code consisting of 2 alphabets in capital case + 14 numeral digits of sequence number. 3. The E-Invoice carrier for Cross-border E-commerce Suppliers (The code of carrier type is 5G0001): Please enter consumer’s email address without any full- or half-with? space in a head or on behind. |
CarrierId2 | xsd:string xsd:maxLength value="64" | 64 | O | Accorded CarrierType to fill corresponding CarrierId. 1. Cellphone barcode : is an 8-digit code starting with a slash “/” 2. Citizen Digital Certificate barcode : is a code consisting of 2 alphabets in capital case + 14 numeral digits of sequence number. 3. The E-Invoice carrier for Cross-border E-commerce Suppliers (The code of carrier type is 5G0001): Please enter consumer’s email address without any full- or half-with? space in a head or on behind. |
PrintMark | xsd:string xsd:minLength value="1 " xsd:maxLength value="1" xsd:pattern value="[Y,N]" | 1 | M | Enter N if you are Cross-border E-commerce supplier. |
NPOBAN | type="BAN" | O | See the specifications of element “BAN” for definition and example. Please provide the “complete” donated code, which is a number containing 3 to 7 digits. | |
RandomNumber | xsd:string xsd:minLength value="4" xsd:maxLength value="4" xsd:pattern value="[0-9,A] [0-9,A] [0-9,A] [0-9,A]" | 4 | M | It will be generated randomly on transaction. Only two duplicated numbers are accepted at most among every one thousand numbers. The number has 4 digits. The number less than 4 digits will be kicked off. |
(3) Specifications of aggregate “Invoice/Details”
Element name | XML Schema syntax | Data length | Necessity | Remark |
ProductItem | <xsd:element name="ProductItem" maxOccurs="999"> | M |
(4)Specifications of element “Invoice/Details/ProductItem”
Element name | XML Schema syntax | Data length | Necessity | Remark |
Description | xsd:string maxLength value="256" | 256 | M | |
Quantity | xsd:decimal | M | ||
Unit | xsd:string maxLength value="6" | 6 | O | |
UnitPrice | xsd:decimal | M | Cross-border E-Commerce Suppliers see note 2 for how to fill out this field | |
Amount | xsd:decimal | M | Cross-border E-Commerce Suppliers see note 2 for how to fill out this field | |
SequenceNumber | xsd:string maxLength value="3" | 3 | M | Used by system |
Remark | xsd:string maxLength value="40" | 40 | O | Enter “health surcharge” in this field if it is as such. |
RelateNumber | xsd:string maxLength value="20" | 20 | O | 1. To enter the product barcode: {number type code and product code}, the number type codes are: |
(5) Specifications of element “Invoice/Amount”
Element name | XML Schema syntax | Data length | Necessity | Remark |
SalesAmount | xsd:decimal | M | 1.Integer (rounded off after decimal point). See note 1 and 2 for how to fill out this field. | |
FreeTaxSalesAmount | xsd:decimal | M | 1.It should be a Integer (rounded off after decimal point) if it’s calculated in New Taiwan Dollars.; | |
ZeroTaxSalesAmount | xsd:decimal | M | 1.It should be a Integer (rounded off after decimal point) if it’s calculated in New Taiwan Dollars. | |
TaxType | type="TaxTypeEnum" | M | See the specifications of element “TaxTypeEnum” for definition and example. | |
TaxRate | xsd:decimal | M | Example: enter 0.05 for tax rate of 5% | |
TaxAmount | xsd:decimal | M | It should be a Integer (rounded off after decimal point) if it’s calculated in New Taiwan Dollars.See note 1 and 2 for how to fill out this field. | |
TotalAmount | xsd:decimal | M | 1.Integer, See note 1 and 2 for how to fill out this field. | |
Currency | type="CurrencyCodeEnum" | 3 | O | 1.For remark by business entity; for definition in detail, see the specifications of element “CurrencyCodeEnum.” 2.This is required for Cross-border E-Commerce Suppliers. See note for how to fill out this field. If UnitPrice, Amount, TotalAmount caculated in New Taiwan Dollar, enter TWD; If they are caculated in foregin currency, enter CurrencyCode. (See the specifications of element “CurrencyCodeEnum” for definition and example.) |
Note 1 : Accorded Article 32 of the Value-added and Non-value-added Business Tax Act specifies “Where a business entity calculates the output tax pursuant to Article 14, if the purchaser is a business entity, the output tax and the sales amount shall be stated separately on the uniform invoice; if the purchaser is not a business entity, the uniform invoice shall be issued at the list price.” The contents of invoice uploaded to the E-Invoice Platform shall be consistent with those of the invoices issued. Note:2
(1) Specifications of element “CancelInvoice”
Element name | XML Schema syntax | Data length | Necessity | Remark |
CancelInvoiceNumber | type="InvoiceNumberType" | M | See the specifications of element “InvoiceNumberType” for definition and example. | |
InvoiceDate | type="DateType" | M | See the specifications of element “DateType” for definition and example. | |
BuyerId | type="BAN" | M | See the specifications of element “See the specifications of element “BAN” for definition and example. | |
SellerId | type="BAN" | M | See the specifications of element “BAN” for definition and example. | |
CancelDate | type="DateType" | M | See the specifications of element “DateType” for definition and example. | |
CancelTime | type="TimeType" | M | See the specifications of element “TimeType” for definition and example. | |
CancelReason | xsd:string xsd:maxLength value="20" | 20 | M | Length as least 1 |
Remark | xsd:string xsd:maxLength value="200" | 200 | O |
(1) Specifications of element “VoidInvoice”
Element name | XML Schema syntax | Data length | Necessity | Remark |
VoidInvoiceNumber | type="InvoiceNumberType" | M | See the specifications of element “InvoiceNumberType” for definition and example. | |
InvoiceDate | type="DateType" | M | See the specifications of element “DateType” for definition and example. | |
BuyerId | type="BAN" | M | See the specifications of element “BAN” for definition and example. | |
SellerId | type="BAN" | M | See the specifications of element “BAN” for definition and example. | |
VoidDate | type="DateType" | M | See the specifications of element “DateType” for definition and example. | |
VoidTime | type="TimeType" | M | See the specifications of element “TimeType” for definition and example. | |
VoidReason | xsd:string xsd:maxLength value="20" | 20 | M | Length at least 1 |
Remark | xsd:string xsd:maxLength value="200" | 200 | O |
(1)Specifications of aggregate “Allowance”
Element name | XML Schema syntax | Data length | Necessity | Remark | ||
Main | <xsd:element name="Main" type="Main"/> | M | ||||
Details | <xsd:element name="Details" type="Details"/> | M | ||||
Amount | <xsd:element name="Amount" type="Amount "/> | M |
(2) Specifications of element “Allowance/Main”
Element name | XML Schema syntax | Data length | Necessity | Remark |
AllowanceNumber | type="AllowanceNumberType" | M | Used by the issuer’s system; | |
AllowanceDate | type="DateType" | M | See the specifications of element “DateType” for definition and example. | |
Seller | xsd:group ref="RoleDescriptionType" | M | See the specifications of element “RoleDescriptionType” for definition. | |
Buyer | xsd:group ref="RoleDescriptionType" | M | See the specifications of element “RoleDescriptionType” for definition. | |
AllowanceType | type="AllowanceType" | M | See the specifications of element “AllowanceType” for definition. |
(3)Specifications of aggregate “Allowance/Details”
Element name | XML Schema syntax | Data length | Necessity | Remark |
ProductItem | <xsd:element name="ProductItem" maxOccurs="999"> | M |
(4)Specifications of element “Allowance/Details/ProductItem”
Element name | XML Schema syntax | Data length | Necessity | Remark |
OriginalInvoiceDate | type="DateType" | M | See the specifications of element “DateType” for definition and example | |
OriginalInvoiceNumber | type="InvoiceNumberType" | M | See the specifications of element “InvoiceNumberType” for definition and example. | |
OriginalSequenceNumber | xsd:string xsd:maxLength value="3" | 3 | O | Corresponds to the sequence number field in the details of original invoice |
OriginalDescription | xsd:string xsd:maxLength value="256" | 256 | M | |
Quantity | xsd:decimal | M | ||
Unit | xsd:string xsd:maxLength value="6" | 6 | O | |
UnitPrice | xsd:decimal | M | Cross-border E-Commerce Suppliers see note for how to fill out this field. | |
Amount | xsd:decimal | M | 1. Domestic suppliers fill amount of purchase without tax, should be Integer(rounded off after decimal point). | |
Tax | xsd:decimal | M | 1. Integer (rounded off after decimal point). See note for how to fill out this. | |
AllowanceSequenceNumber | xsd:string xsd:maxLength value="3" | 3 | M | Used by the system; the sequence number for the details of the allowance certificate. |
TaxType | type="TaxType" | M | See the specifications of element “TaxTypeEnum” for definition. |
Note:
(5) Specifications of element “Allowance/Amount”
Element name | XML Schema syntax | Data length | Necessity | Remark |
TaxAmount | xsd:decimal | M | 1. Integer | |
TotalAmount | xsd:decimal | M | 1. Domestic suppliers fill amount of purchase without tax, should be Integer(rounded off after decimal point). |
(1) Specifications of element “CancelAllowance”
Element name | XML Schema syntax | Data length | Necessity | Remark |
CancelAllowanceNumber | type="AllowanceNumberType" | M | See the specifications of element “AllowanceNumberType” for definition. | |
AllowanceDate | type="DateType" | M | See the specifications of element “DateType” for definition and example. | |
BuyerId | type="BAN" | M | See the specifications of element “BAN” for definition and example. | |
SellerId | type="BAN" | M | See the specifications of element “BAN” for definition and example. | |
CancelDate | type="DateType" | M | See the specifications of element “DateType” for definition and example. | |
CancelTime | type="TimeType" | M | See the specifications of element “TimeType” for definition and example. | |
CancelReason | xsd:string xsd:maxLength value="20" | 20 | M | Length at least 1 |
Remark | xsd:string xsd:maxLength value="200" | 200 | O |
(1) Specifications of aggregate “BranchTrackBlank”
Element name | XML Schema syntax | Data length | Necessity | Remark |
Main | <xsd:element name="Main" type="Main"/> | M | ||
Details | <xsd:element name="Details " type="Details"/> | M |
(2) Specifications of element “BranchTrackBlank/Main”
Element name | XML Schema syntax | Data length | Necessity | Remark |
HeadBan | type="BAN" | M | See the specifications of element “BAN” for definition and example. | |
BranchBan | type="BAN" | M | See the specifications of element “BAN” for definition and example. | |
InvoiceType | type="InvoiceTypeEnum" | M | See the specifications of element “InvoiceTypeEnum” for definition and example. | |
YearMonth | xsd:string xsd:minLength value="5" xsd:maxLength value="5" xsd:pattern value="\d{3}0[2|4|6|8]|\d{3}1[0|2]" | 5 | M | Even-number months only, for example: |
InvoiceTrack | xsd:string xsd:minLength value="2" xsd:maxLength value="2" xsd:pattern value="[A-Z]{2}" | 2 | M | 2 alphabets (in upper case) |
(3) Specifications of aggregate “BranchTrackBlank/Details”
Element name | XML Schema syntax | Data length | Necessity | Remark |
BranchTrackItem | <xsd:element name=" BranchTrackBlankItem" maxOccurs="10000" | M |
(1)Specifications of element “InvoiceAssignNo”
Element name | XML Schema syntax | Data length | Necessity | Remark |
Ban | type="BAN" | M | See the specifications of element “BAN” for definition and example | |
InvoiceType | type="InvoiceTypeEnum" | M | See the specifications of element “InvoiceTypeEnum” for definition and example. | |
YearMonth | xsd:string xsd:minLength value="5" xsd:maxLength value="5" xsd:pattern value="\d{3}0[2|4|6|8]|\d{3}1[0|2]" | 5 | M | Even-number months only, for example: |
InvoiceTrack | xsd:string xsd:minLength value="2" xsd:maxLength value="2" xsd:pattern value="[A-Z]{2}" | 2 | M | 2 alphabets (in upper case) |
InvoiceBeginNo | xsd:string xsd:minLength value="8" xsd:maxLength value="8" xsd:pattern value="\d{8}" | 8 | M | 8-digit number |
InvoiceEndNo | xsd:string xsd:minLength value="8" xsd:maxLength value="8" xsd:pattern value="\d{8}" | 8 | M | 8-digit number |
InvoiceBooklet | xsd: long xsd:totalDigits value="10" xsd:minInclusive value="0" | M |