Three Ways to Have No Sales Tax
Nauru, the Federated States of Micronesia and Solomon Islands all put nothing on the invoice line. A system configured identically for the three would be wrong in two of them, and the reasons are operational rather than academic.
Ask a finance system what tax to charge in three Pacific countries and you get the same answer three times: nothing. Ask what that means for how the system should be set up, and the answer is different in every one — because "no sales tax" is not a fact about a rate. It is a fact about why there is no rate, and the why decides what your configuration has to do instead.
This came out of researching tax profiles for eight Pacific markets. Three of them charge nothing on an invoice, and it would have been easy to file all three as zero and move on. They are not the same case at all. One has no such tax in its statute book. One has no national tax and four state governments that each levy their own. One has two taxes and no VAT, so a services business charges 10% while a goods business charges nothing and pays real tax upstream that will never appear on a sales document.
Configure a system the same way for all three and you will be wrong in two.
The three positions, stated properly
Nauru has no consumption tax at all. Not a reduced one, not a suspended one — the statute book does not contain the instrument. The complete set of Nauruan tax statutes is a business tax, an employment and services tax, a tax on telecommunications services and a departure tax. Nothing there is charged on a sale. This is the cleanest decided zero we have found anywhere, and it is worth being precise about what the evidence is: it is an absence. There is no article to quote, because there is no article.
The Federated States of Micronesia has no national consumption tax, and four state governments that do. Title 54 of the FSM Code — the taxation and customs title — has chapters on wages, salaries and gross revenues, on duties and customs, on revenue administration and on penalties. There is no VAT or sales tax chapter in it. What the national government levies instead is a tax on the business: a flat annual charge on gross revenues up to a threshold and a percentage on the excess, with the smallest businesses exempt. Chuuk, Kosrae, Pohnpei and Yap each legislate their own sales taxes. So the rate a Micronesian business charges depends on which state it is trading in, and no national figure can hold that. A zero here is not a small answer. It is the wrong shape of answer.
Solomon Islands has two taxes and neither of them is a VAT. The Sales Tax Act charges a closed schedule of twenty-two named goods and services. Every percentage entry in it is 10%, and the list is heavily weighted toward services — accounting, legal and security services, professional services, real estate agency, vehicle and plant hire, computer hire, vessel and aircraft leasing, laundry, tyre and electronic repair. There is no residual "everything else" line, so anything not named is simply not charged. Separately, the Goods Tax Act taxes the wholesale value of goods once — imported goods at 15%, prescribed local manufactures at 10%, rice at 5% — with no credit mechanism at all. That second tax is real money and it never appears on an invoice.
| Nauru | Micronesia | Solomon Islands | |
|---|---|---|---|
| What is on the invoice line | Nothing | Nothing nationally | 10% on named services, nothing on goods |
| Why | The tax does not exist | The tax is a state matter | Goods are taxed once further up the chain |
| Is there tax to account for at all | Not on sales | Yes — at state level, and on gross revenue | Yes — 15%/10%/5% at wholesale, unrecoverable |
| What a finance system needs | Nothing special | A rate that varies by location inside one country | A per-item rule, and the upstream tax in cost |
Why the difference is operational
The distinction would be pedantry if all three ended in the same setup. They do not.
Nauru genuinely needs nothing, and the only trap is a system that will not let you say so. Plenty of finance software treats a tax type as mandatory and quietly assigns a zero from a placeholder rather than because anybody decided on one. A deliberate zero and an unresolved lookup have to be distinguishable, or the first time the software learns something new about your country, it will not update — because it already has an answer.
Micronesia needs something almost no product has: a rate that varies by location inside one country. Not a country per organisation — a rate per state, resolved by where the supply happens. Very few operations systems can do that, and the ones that can usually acquired it for the United States and Canada rather than for the Pacific.
Solomon Islands needs two unrelated things. On the sales side, a rule that charges 10% on the listed services and nothing on everything else — which is a per-item property, not a per-organisation rate. On the purchase side, the goods tax paid at wholesale has to reach the cost of the goods, because it is not reclaimable and will never be visible anywhere else. If it does not reach cost, every margin figure in the business is overstated by the tax.
A tax you cannot reclaim is not a tax question. It is a costing question, and it gets answered in the wrong module or not at all.
What our own system does with each of these
The honest version, because a post that describes a problem and then implies it is solved is worse than one that never raised it.
One default rate per organisation, per tax type. That is the whole of our rate resolution. When an invoice, a quotation or a point-of-sale line asks what the tax is, we look up the rate row flagged as the default for that tax type and use it. Nauru is therefore trivial — enable nothing, or enable a tax type whose configured rate is a real zero rather than a fallback, and every document comes out untaxed.
We have the columns for Micronesia and we do not have the behaviour. Our per-organisation rate table carries a country, a region and a city on every row. They are stored, they are shown, and nothing reads them to choose a rate — resolution looks only for the row marked default. So you can record that a rate belongs to Pohnpei; you cannot make a document in Pohnpei pick it up. In practice that means one organisation per state, which is a workaround with real costs — separate customer lists, separate numbering, no consolidated view without exporting. We would rather name that than describe the columns as support.
Solomon Islands is the one where we do better than expected on one half. Items carry a tax treatment, and an invoice line resolves its rate from it: standard takes the organisation rate, zero-rated and exempt take nothing. So a schedule of twenty-two taxable services against everything else untaxed is genuinely expressible — set the organisation rate to 10% and mark everything off the schedule as exempt. One limitation to know: zero-rated and exempt both come out as 0.00 and we do not distinguish them anywhere in the totals, which matters if you ever have to report them separately.
The other half of Solomon Islands is the gap. Our purchase orders carry no tax columns at all — the rate lives on sales documents and nowhere else. The only place an unrecoverable input tax can be captured is a landed cost line on the purchase order, which does work and does allocate: you define your own cost types, put an amount on the order, and it is spread across the batches received against it by value or by quantity. But you type the amount. Nothing computes 15% of the wholesale value for you, and nothing will tell you that you forgot.
The three positions against what we actually do
| What the market needs | Nauru | Micronesia | Solomon Islands |
|---|---|---|---|
| No tax on the invoice line | Yes | Yes | Yes |
| A rate that varies by location inside the country | No | No | No |
| Per-item taxable / not taxable, on the invoice line | Yes | Yes | Yes |
| Unrecoverable input tax reaching the cost of goods | Yes | Yes | Partly — configurable by you |
| A rate computed on the purchase side | No | No | No |
Built and maintained Configurable by you, not maintained by us Not built
Landed cost is marked as configurable rather than built because the mechanism allocates properly and the amount is typed by a person — nothing derives it from a rate. The location row is not a Pacific gap: our rate table has the region and city columns and no code path reads them.
What to ask a vendor, in this order
-
Can you store a rate of zero as a decision rather than as a default?
The failure mode is specific and common: a system cannot find a rate for your country, falls through to a placeholder of zero, saves it, and never looks again. It behaves identically to a correct zero until the day the software learns something and yours does not change. Ask how the two are distinguished in the data, not on the screen.
-
Can two locations in the same country charge different rates?
For Micronesia this is the whole question. Beware a demonstration that shows a region field on a rate record — storing a region and resolving by one are different things, and the field is the easy half. Ask to see a document raised in one location pick up a different rate from a document raised in another.
-
Is taxability a property of the item or of the organisation?
Where the taxed supplies are a closed list, the rate is not the interesting part — the list is. A system with one organisation-wide rate and no per-item override cannot express a twenty-two line schedule at all, and the workaround people reach for is editing the tax on each document, which is exactly how a schedule stops being applied consistently.
-
Where does an unrecoverable purchase tax end up?
If the answer is "in an expense account", your inventory is undervalued and your margins are overstated by the tax, permanently. It has to reach the cost of the goods. Ask specifically whether it lands on the batch, and whether the allocation is by value or by quantity — the two give different answers on a mixed shipment and only one of them is right for your goods.
The general point, which is not about the Pacific
Every system with a country list has a field that holds a percentage, and that field silently encodes an assumption: that the country is the unit at which the question is decided. Three Pacific markets break that assumption in three separate places — one where there is no question, one where the unit is the state and not the country, and one where the unit is the item and the real tax is not on the sale at all.
None of that is exotic. The same three shapes turn up in the United States, in India, in Nigeria and in every federal system with a devolved consumption tax, and in every jurisdiction that taxes goods once at import rather than at each supply. The Pacific is just where all three sit close enough together that you cannot pretend one setting covers them.
There is a fourth shape, and it belongs to the same family: a country where the tax exists and is not being charged yet. That is the Marshall Islands, in the same region and the subject of a tax that has not started yet — where the question is not whether a rate exists but which date it belongs to.
What AWRA OpsHub does today
- One default rate per organisation per tax type, resolved on every invoice, quotation and point-of-sale line from the row flagged as default.
- A real zero that is distinguishable from a failed lookup — a country that genuinely levies nothing is recorded as such rather than falling through to a placeholder.
- Per-item tax treatment — standard, zero-rated or exempt — resolved and stored per invoice line, which is what makes a closed schedule of taxable supplies expressible.
- Per-customer tax exemption, read from the customer record at the point the document is priced.
- Landed cost with your own cost types, allocated across received batches by value or by quantity, so an unrecoverable import charge can reach the cost of the goods.
- Tax presets for 186 countries, each with a named instrument and a dated source behind it, as a starting point you then own.
What it does not do
- No rate that varies by location inside a country. The region and city columns exist on the rate record, are stored and are displayed; no code path reads them to choose a rate.
- No per-customer rate override. The field is stored and deliberately not applied — exemption is wired, an override is not.
- No tax on the purchase side. Purchase orders carry no tax columns; an unrecoverable input tax is a landed cost line whose amount you type.
- No distinction between zero-rated and exempt in the totals. Both resolve to 0.00 on the line and are not reported separately.
- No rate history. One rate per country, with no date attached — the subject of the companion piece linked above.
- Nothing computes a tax from a wholesale or customs value. Where the tax base is not your invoice value, the figure is entered rather than derived.
What is not built for your market today can still be built for you
Anything described above as not built is a statement about what ships in the standard product today — not a limit on what AWRA OpsHub can do in your market. Kenya's eTIMS integration and its maintained payroll engine exist because Kenyan clients needed them and commissioned them; neither appeared by itself. The same door is open here. If a local payroll engine, a rate with a date on it, a bank or mobile money feed, a statutory return format, a rule your own operation needs that the standard one does not have, or a link to a system you already run is what stands between you and a decision, tell us and we will scope it as a build — written spec, timeline and price — before you commit to anything.
Dated rates and the periods your obligations actually use
Effective-dated tax rates, so a document raised about a past period is computed against the rate that applied then rather than the rate that applies now, and a credit note that carries the tax split of the supply it reverses. Where a jurisdiction operates a sales-monitoring or fiscalisation scheme, data produced in the published format alongside the approved equipment rather than in place of it.
Banks, payments and pay periods that are not months
Bank statement feeds and local payment rails wired into the Payments Register, and a payroll period that matches your statutory pay cycle rather than the calendar month our schema assumes today. The second is a data-model change and we would quote it as one.
The operational work, which is what most commissions actually are
An extra approval stage in a chain that does not match the standard one, a custom field set on employees or assets that only your sector needs, an expiry that has to block an order rather than send an email, a report your board asks for in a shape nothing produces, or a scanner or weighbridge feeding the goods-in door. These are the commissions we are asked for most often and the smallest ones we quote — and unlike a revenue-authority pipeline, none of them waits on a regulator.
Payroll and statutory returns
Income tax, superannuation or provident fund contributions computed on live employee records against your own pay cycle, with the returns produced in the layout your authority expects.
Systems you already run
The accounting package, CRM, online store or custom database you intend to keep — connected through our API so a fact is entered once and appears everywhere it is needed.
How it works: you describe the requirement, we return a written scope, timeline and cost, and once agreed it is built into your environment and maintained as part of the product. No roadmap slide, and no pretending in a demo that something exists when it does not.
Tell us what you need integratedIf you operate in any of the three, the practical summary is short. Nauru needs nothing and you should check that "nothing" is a decision your system recorded rather than a lookup it lost. Micronesia needs a per-state answer and almost nobody has one, so plan the workaround deliberately. Solomon Islands needs the schedule on the items and the goods tax in the cost — and of those two, the one that will quietly distort your accounts for years is the second.
Frequently asked questions
Do Nauru, Micronesia and Solomon Islands really have no sales tax?
None of the three adds a general consumption tax to an invoice line, and that is where the similarity ends. Nauru has no such tax in its statute book at all. The Federated States of Micronesia has none nationally, and Chuuk, Kosrae, Pohnpei and Yap each levy their own. Solomon Islands charges 10% on a closed schedule of twenty-two named goods and services and taxes goods separately at wholesale, once, with no credit. All three tax businesses in other ways — none of them is a low-tax jurisdiction, they are jurisdictions that do not tax the sale.
What rate should we configure for Solomon Islands?
10% is what a Solomon Islands business adds to an invoice when it adds anything, so that is the figure we ship. It only applies to supplies named in the Sales Tax Act's schedule, which is why per-item taxability matters more here than the rate does: set 10% as the organisation rate and mark everything off the schedule as exempt. Separately, the goods tax paid at wholesale — 15% on imports, 10% on prescribed local manufactures — is not an invoice line and not reclaimable, so it belongs in the cost of the goods and nowhere else.
Can we set a different rate for each state in Micronesia?
Not in our system today. Our per-organisation rate table has region and city columns and they are stored and displayed, but nothing reads them when a document resolves its rate — resolution finds the one row marked as the default for that tax type. The practical workaround is a separate organisation per state, which works and has real costs: separate customer lists, separate document numbering and no consolidated view without exporting. We would rather say that than let the presence of the columns imply the behaviour.
Where does an import tax we cannot reclaim end up?
It should end up in the cost of the goods, and in our system the way to get it there is a landed cost line on the purchase order. You define the cost type, enter the amount, and it is allocated across the batches received against that order either by value or by quantity. What we do not do is calculate it — nothing derives the charge from a wholesale value or a rate, and nothing warns you if the line is missing. If instead it is posted to an expense account, your stock is undervalued and your gross margin is overstated by the tax for as long as the goods are held.
Why does a zero rate need explaining at all?
Because two zeroes that look identical on screen mean different things in the data. One is a country that levies nothing and was recorded as such. The other is a lookup that failed, fell through to a placeholder and saved it — and that second one is permanent, because the system already has an answer and will not ask again. The first behaves correctly forever; the second is a defect waiting for the day your circumstances or the rate change.
