Electronic invoice in Taiwan
A comprehensive guide to Taiwan’s unique e-invoicing landscape: navigating the MOF Platform, strict MIG 4.1 reporting deadlines, and the newly separated Peppol layer without a universal mandate.
Taiwan operates a mature state system of electronic uniform invoices — the standardised tax invoice — run by the Ministry of Finance (MOF). But the electronic form remains one of several lawful ways of issuing a uniform invoice, alongside paper. There is no nationwide mandate requiring all companies to use electronic invoices in B2B, or all government suppliers in B2G.
The one real mandate is narrow and outward-facing: foreign suppliers of electronic services to Taiwanese consumers above the threshold must register for business tax and issue Taiwanese cloud invoices. For cross-border B2B the model is different again — the foreign supplier generally issues nothing Taiwanese, and the buyer accounts for the tax itself.
Taiwan has been building this since 2000 without ever making it universal. The recent movement is technical — and, from 2025, institutional.
The B2B pilot began on 1 December 2000; the central platform has run since December 2006, with B2C functionality from the same year and the cloud invoice developing actively from 2009. The B2G pilot started in January 2008.
From 1 May 2017 foreign B2C e-service suppliers with annual Taiwan sales above NT$600,000 had to register for business tax; from 1 January 2019 they must issue cloud invoices.
A dedicated penalty provision now backs the duty to transmit e-invoice data on time and accurately. See Transmission deadlines.
The Ministry of Digital Affairs (MoDA) became Peppol Authority on 18 September 2025, and the agreement with OpenPeppol was signed on 27 November 2025. This is a parallel cross-border layer — see Peppol in Taiwan.
The official Turnkey process moved to MIG 4.1. Current testing documentation specifies MIG 4.1 and requires that a single XML file contain the data of only one invoice.
No date for a general B2B mandate has been published in the MOF or MoDA material reviewed. The legislation treats paper and electronic uniform invoices as alternative lawful forms, and the tax administration confirms that a business which voluntarily stops using e-invoices is not compelled to resume. Nothing in the "still ahead" column, therefore — which is itself the most useful fact about Taiwan.
The system centres on the MOF E-Invoice Platform (電子發票整合服務平台), which stores electronic uniform invoice data, invoice numbers, amendments, cancellations, returns and allowances. A company can operate in one of four ways:
Taiwan is not a classic clearance model. An invoice needs no prior approval or clearance code before it goes to the buyer; the legal ability to issue does not depend on a response from the MOF Platform; and the data is transmitted after issue, within the prescribed window. Nor is it a Peppol four- or five-corner arrangement — the MOF Platform and Peppol are currently separate infrastructure layers.
The accurate description is a centralised, CTC-like reporting and evidence-deposit model with deferred transmission — not pre-clearance.
For a Turnkey integration the platform does validate: it checks message structure and business rules and returns a success or error status, an erroneous file must be corrected and resubmitted, and permission for production upload follows successful testing. That is technical control — not tax approval of each transaction before the invoice reaches the buyer.
Since 1 January 2025 the duty to transmit e-invoice data promptly and accurately has been backed by its own penalty provision. The deadlines are short but they are not real time:
There is no statutory real-time reporting obligation on the seller — two or seven days is not clearance. The nuance is on the provider side: an accredited Value-Added Service Center must forward the data it receives to the MOF Platform immediately. That binds the provider's operation; it does not turn the national system into pre-clearance.
Electronic invoices are supported and have been since the B2G pilot in January 2008, with suppliers progressively connected to the MOF Platform for invoicing and payment. But there is no nationwide mandatory B2G requirement, and no dedicated government network of the kind some countries build around Peppol.
A specific agency or procurement contract may nonetheless require an electronic format. So the practical step for a supplier is to check the tender terms and the contract: whether the agency is connected, which identifiers or budget references it needs, the required issuing method, and how confirmation and payment work. The MOF rules place business entities, government agencies and other organisations in the same chapter — platform, Value-Added Service Center or own integration.
Where a seller uses e-invoicing for consumer sales, Taiwan's distinctive carrier mechanism applies — the invoice is held against an identifier the consumer chooses rather than handed over on paper.
That last point is worth building into a point-of-sale design rather than treating as an option: refusing a common carrier is not a permitted configuration.
The Taiwanese system is not based on EN 16931, UBL 2.1 or UN/CEFACT CII. The mandatory structured format for integration with the MOF Platform is the local XML standard MIG — Message Implementation Guideline (電子發票資料交換標準訊息建置指引).
MIG covers the full document family: B2B invoice issue, acknowledgement of receipt, cancellation, rejection or return, allowance and discount documents, transmission of an invoice purely for platform storage, receipt of incoming invoices, and the allocation and accounting of official invoice numbers.
Peppol BIS Billing 3.0 is an application of EN 16931 using UBL 2.1. A foreign Access Point can therefore convert Peppol BIS or UBL into MIG — but transmitting UBL over Peppol does not by itself discharge the Taiwanese duty to send invoice data to the MOF Platform.
An ordinary PDF emailed to the buyer does not meet the definition of a Taiwanese electronic uniform invoice: the tax e-invoice must have structured data and a corresponding record on the MOF Platform.
What is permitted is generating and printing an Electronic Invoice Certification Copy. A buyer who needs a paper process can use it as a primary accounting document, and a buyer unable to receive a structured invoice can obtain it from the seller. The certification copy accompanies the process — it does not replace the MIG XML and the platform record.
Peppol arrived in Taiwan in 2025 as a separate strategic infrastructure for cross-border document exchange. The Ministry of Digital Affairs became Peppol Authority on 18 September 2025 and signed the agreement with OpenPeppol on 27 November 2025.
It does not replace the MOF E-Invoice Platform and is not the principal tax channel. Treating a Taiwanese Peppol connection as tax compliance would be a straightforward error.
Several things are not yet published, and we flag rather than guess. The Taiwan Peppol Authority Specific Requirements, the approved Electronic Address Schemes, the rules for registering participant IDs, the terms on which foreign Access Points are recognised, and any local security and audit requirements had not been confirmed in the official material reviewed. Anyone planning a Taiwanese Peppol offering should treat these as open items to obtain from MoDA rather than assumptions.
This is the one genuine obligation on foreign suppliers. Where annual Taiwan sales exceed NT$600,000, the supplier registers for business tax, issues cloud invoices, may use the dedicated cross-border e-commerce email carrier, and declares and pays Taiwanese business tax.
The opposite applies. For cross-border electronic services the foreign supplier is not required to issue a Taiwanese cloud invoice; the Taiwanese buyer self-assesses business tax under Article 36 of the Business Tax Act. Where the buyer is on the general VAT model and the service is used exclusively for taxable business, an exemption from actual payment may apply, and dual-status entities calculate a proportion. For imported goods the tax is normally collected by Customs — and a foreign commercial invoice plus customs documents does not become a Taiwanese electronic uniform invoice.
There is no special mandatory e-invoice channel for exports. Exported goods and qualifying export services may be zero-rated, supported by export, customs, banking and other documents depending on the transaction. On a supply into a bonded zone, the electronic invoice can be signed by the buyer on the MOF Platform, in its own system or in a Value-Added Service Center's system, and used as evidence of the seller's entitlement to the zero rate.
A direct supply from a Taiwanese company to a European buyer is not an intra-EU transaction, because the supplier sits outside the EU. ViDA can reach the transaction only on the European side — through an EU-established subsidiary or fixed establishment of a Taiwanese group, an intra-Community supply or acquisition, or a party with its own EU VAT obligations. The 1 July 2030 requirements create no duty to send Taiwanese MIG invoices into any European reporting system.
Taiwan in 2026 should be approached as a two-layer market, and conflating the layers is what makes projects fail.
You can already offer Peppol BIS Billing 3.0, UBL 2.1, cross-border document exchange, conversion from EN 16931, and delivery and status services. What you must wait for or obtain from MoDA is the Taiwan PASR, the approved EAS, participant ID registration rules, the terms for recognising foreign Access Points, and the local security and audit requirements.
A full domestic e-invoice service needs MIG 4.1, official invoice numbers, a MOF Platform connection, test and production approval, local certificates, compliance with the two and seven-day deadlines, and either Value-Added Service Center status or integration through such a provider.
An EU Peppol certification does not substitute for national MOF accreditation. The most realistic starting model for a foreign provider is: foreign Peppol Access Point + EN 16931/UBL-to-MIG conversion + a local Taiwanese MOF Value-Added Service Center.
Going direct without a local partner would require local tax registration, passing MOF testing, ISO 27001 with the correct scope, and obtaining your own Value-Added Service Center permission. No separate official electronic mailbox requirement was found.
Electronic invoices must be archived securely and remain accessible for a minimum of five years under the Taiwanese tax rules. Because the MOF Platform holds the data too, the temptation is to treat that as the archive — which is the mistake to avoid.
The law also makes the archive a condition of the deduction: if the required documents are missing or not retained as required, input tax deduction is prohibited.
Taiwan separates the penalty for how you report from the penalty for whether you invoiced at all — a distinction worth keeping straight when assessing exposure.
Note what the second row is not: it penalises the absence of a required uniform invoice altogether, not the choice of paper over electronic where no e-invoicing mandate applies.
An electronic invoice is not the only basis for deducting input business tax. Article 33 of the Business Tax Act admits a uniform invoice showing the business tax paid, a self-issued uniform invoice in the cases the law provides for, and other documents showing the tax amount and approved by the MOF.
Nowhere does the law say the uniform invoice must be electronic — a paper uniform invoice remains a lawful basis where the requirements are met. What the document must do is relate to a real purchase, carry the buyer's name, address and BAN, and be received and retained properly.
The electronic uniform invoice is not the sole lawful basis for deduction — but a correctly formed electronic invoice, or the accounting record or certification copy the law provides for, performs that function. Where the required documents are absent or not retained as required, deduction is prohibited outright.
Taiwan is a conversion-and-partnership market rather than a direct one. What the work looks like:
Taiwan has one of the oldest electronic invoicing systems in Asia and still no general mandate. Paper and electronic uniform invoices remain alternative lawful forms, no date for universal adoption has been published, and a business that stops using e-invoices is not compelled to resume. The obligations that do bite are the transmission deadlines — two days for consumers, seven for businesses — and the narrow rule for foreign B2C e-service suppliers.
Technically the country is entirely local: MIG 4.1 XML into the MOF Platform, with MIG 4.0 discontinued at the start of 2026. EN 16931, UBL and CII have no standing in the tax system, and reporting happens after issue rather than before delivery.
The 2025 arrival of a Peppol Authority makes Taiwan a two-layer market rather than a Peppol market. You can build cross-border interoperability now; you cannot yet build a domestic tax service on it, and several of the Peppol ground rules — PASR, EAS, participant IDs, recognition of foreign Access Points — are still unpublished. Plan for a MIG conversion and a local Value-Added Service Center partner, and revisit the Peppol layer when MoDA publishes.