Choosing a Government E-Invoicing Provider in Taiwan: ECPay, ezPay, and the Big Platforms

If you run an online store in Taiwan, government e-invoicing is homework you can't skip. Most e-commerce operators don't apply to the Ministry of Finance to become a direct issuer and build their own Turnkey system — the cost is too high — and instead issue through a value-added service provider. There are plenty of options: ECPay, ezPay (the NewebPay family), Trade-Van, plus plans bundled with POS systems or storefront platforms. We use ECPay ourselves, issuing, voiding, and reissuing real invoices every day — but this article aims to stay neutral about what you should actually compare when choosing. The conclusion up front: fee differences aren't really the point. What matters is integration cost and exception handling.

Understand what you're buying first

An e-invoicing service provider delivers three core services. First, invoice-number track management — applying to the tax authority for number allocations, warning before you run out, handling period transitions. Second, issuance and transmission — turning your transaction data into legal invoices, uploading to the government platform, handling carrier registration and lottery-win notifications. Third, amendments — voiding, credit notes, cancellation — the piece most consistently underestimated. When picking a provider, everyone can do the first two; the difference lives in the third: how complete the API is, and how good the admin panel is at fixing things.

The four dimensions genuinely worth comparing

1. Integration with your payment gateway

If your payments and invoicing come from the same vendor (both ECPay, say, or both within the NewebPay family), the payment-completed-triggers-invoice wiring goes much more smoothly, and transaction IDs naturally line up at reconciliation. Two separate vendors can work, but you're maintaining two sets of API credentials, two admin panels, two reconciliation reports. Honestly, integration was the biggest reason we chose ECPay — the payment notification arrives, the same order number issues the invoice, and one less translation layer is one less way to fail.

2. API quality and documentation

Look at three things: whether the docs spell out the failure scenarios (what does a duplicate issuance return? what error code when the number track runs out?), whether the sandbox is complete (can you run the full issue → void → reissue cycle in test?), and how well the SDKs are maintained. We recommend running the void-and-reissue flow in the sandbox before signing — when an order amount changes, the invoice must be voided and reissued, and if the API makes that path awkward, you'll hurt for a long time. We've written up the detailed scenarios in the full lifecycle of automated e-invoice issuance — use it as an acceptance checklist.

3. Fee structure

Common pricing models: per-invoice (the market runs roughly from under NT$1 to a bit over NT$1 per invoice), flat monthly plans, or bundled into the payment-processing rate. Exact numbers vary by vendor and change with plans — always go by each provider's official published pricing. Note that a void-and-reissue consumes an extra invoice, and lottery-win notification SMS may be billed separately. Merchants with low monthly volume are almost always better off per-invoice; negotiate a plan once volume grows. Invoicing fees are a tiny share of total e-commerce cost — not worth sacrificing integration quality over a few cents per invoice.

4. The admin panel's rescue capabilities

However well your API integration works, a day will come when a human must intervene: support edited an order, month-end reveals an invoice with the wrong tax ID, a credit note was issued for the wrong amount. Whether the admin panel lets you manually search, void, and reissue determines whether that's a five-minute fix or a phone call to a support queue. During your trial, deliberately create one bad invoice and see whether you can rescue it yourself.

Choosing an invoicing provider isn't choosing the cheapest — it's choosing the one where, on the day something breaks, you can fix it yourself fastest.

Pitfalls people step in

• No warning when invoice numbers run out. A big sales event spikes volume, the number allocation runs dry, and no invoices can be issued. Confirm the provider has usage alerts — and monitor it yourself too.
• Business-tax-ID invoices have different carrier logic. B2B invoices can't be stored in personal carriers and require buyer information, so your checkout flow must branch.
• Think through the issuance timing. Issue at payment? At shipment? What about cash on delivery? That's your business decision, not the provider's — but the API has to support whichever path you choose.
• Every refund needs a credit note. Refund the money without issuing a credit note and your month-end business-tax filing won't reconcile — your accountant will come looking for you.

Our recommendation

If you already have a payment gateway you're committed to, evaluate that vendor's invoicing service first — lowest integration cost. Storefront-platform users should generally just use the platform's built-in option and not complicate things. Self-hosted stores with real volume are the ones who should seriously compare APIs and rates. For infrastructure like invoicing, stability and recoverability always rank ahead of cheap. If you're planning a self-hosted store and want payments and invoicing wired up right the first time, our e-commerce development service runs this exact chain on our own store every day — happy to talk.