The Tax You Do Not Get Back
Two Taiwanese businesses can pay identical tax on identical invoices and be required to account for it in opposite ways — and nothing about that is a percentage.
Almost every conversation about tax in software is a conversation about rates. What is the percentage, where is it configured, what happens when it changes. Taiwan is a useful place to notice that rates are the easy part, because its Business Tax Act runs two different mechanisms simultaneously and the difference between them is not a number at all.
One statute, two ways of being taxed
Most Taiwanese businesses sit on the value-added regime: tax paid to a supplier is deducted from tax charged to a customer, so what you paid is a receivable — money the state will effectively return to you. Financial businesses sit under a different article of the same Act on the non-value-added regime, taxed on gross receipts with no input credit at all. For them the identical payment is a cost, part of what the purchase was worth, and it never comes back.
That is not a variation in severity. It is a different question having a different answer, and it lands in a different place in the accounts. A retailer and a bank on the same street can receive the same invoice, pay the same tax, and be required to record it in ways that do not resemble each other.
Why this is not the usual "no VAT here" story
Plenty of countries levy a single-stage tax with no input credit — the same fact is true of Eritrea and of San Marino, and we have written about both. What makes Taiwan different is that BOTH mechanisms operate inside one country at the same time, decided by what kind of business you are. It is not a national fact and cannot be stored as one.
What a system has to hold for this to work
Less than you would think, and more than most systems hold. You do not need two tax engines. You need, against each amount of tax paid on a purchase, one more piece of information: is this recoverable? That single classification is what decides whether the figure is an asset or an expense, and everything downstream follows from it.
Our own system records the tax amount on an expense and does not record that classification. There is no flag for "receivable" and none for "cost", because in the overwhelming majority of markets and businesses the answer is always the same and the question never comes up. Taiwan is where it comes up, inside one country, and our records for the retailer and the bank are identical. We wrote about what that absence actually is separately, because it turns out to be a general shape rather than a Taiwanese one.
What goes wrong, in each direction
| If the system assumes | And you are on the other regime | The symptom |
|---|---|---|
| Recoverable | Under article 11, so it is not | A receivable accumulates that no filing will ever recover. It reconciles perfectly against itself. |
| A cost | On the value-added regime, so it is recoverable | Cost is overstated and recoverable tax is understated. Margins look worse than they are. |
A footnote about the rate, which is genuinely odd
Taiwan's business tax rate is 5%, and the Act does not say so. Article 10 sets a band — no less than 5% and no more than 10% — and leaves the operative figure to the executive, which has left it at the bottom of the band since the tax was reformed in 1988. It is worth knowing for one practical reason: anybody who "checks the rate at the primary source" will find no number there at all, and may conclude the reference data is wrong when it is not.
It is also a small argument for the main point of this post. The rate is the part everybody checks and it is the part that has not moved in nearly forty years. The mechanism is the part nobody asks about, and it is the part that decides what your accounts say.
The question to take to any vendor
Ask whether tax mechanism is a property of the country or of the business. Most systems answer "country", because most countries only have one, and the answer is usually correct. Taiwan is where that assumption produces two businesses with identical records and opposite accounts — and the vendor will not know it, because nothing in their system has ever failed.
