The Currency That Tells You Nothing
Six independent countries share the Eastern Caribbean dollar and charge four different rates of VAT. Every instinct a finance system has says they are one market — no conversion, no revaluation, one price list — and the safeguard that stops it adding unlike currencies is exactly what hides six separate tax positions.
Currency is the most visible fact about a foreign market and one of the least informative. It decides whether you need conversion, revaluation and a translation policy — real problems, all of them — and it tells you almost nothing about what you owe. The Eastern Caribbean is where that gap is widest, because six independent countries share one currency and charge four different rates of the same tax.
| Country | Currency | Standard VAT rate |
|---|---|---|
| Antigua & Barbuda | East Caribbean dollar | 17% |
| St Kitts & Nevis | East Caribbean dollar | 17% |
| St Vincent & the Grenadines | East Caribbean dollar | 16% |
| Dominica | East Caribbean dollar | 15% |
| Grenada | East Caribbean dollar | 15% |
| Saint Lucia | East Caribbean dollar | 12.5% |
Those are the six independent states on our table that use this currency, and the spread across them is four and a half points. Saint Lucia and Antigua & Barbuda are a short flight apart, quote in the same money, and differ by more than the entire standard rate of several countries elsewhere in the world.
No conversion, no revaluation, no translation policy, one price list — and six tax authorities, six registrations, six returns.
Why this is a systems problem and not a trivia question
Finance systems key an enormous amount of behaviour off currency, and they are right to. A second currency is the thing that forces a rate table, a revaluation run, a gain-and-loss account and a decision about what your reports are denominated in. It is the loudest signal a system gets that it has left home.
So a group trading across all six of these markets receives none of the signals. Nothing prompts a conversion policy. No revaluation appears. Every report adds up cleanly. The system is behaving perfectly and is telling you, in the only vocabulary it has, that this is one place.
The safeguard that becomes the blind spot
This is the part we did not expect to find and the reason this post exists. We have written before about a report that summed unlike currencies into a single meaningless total, and about the discipline that fixed it: never convert, never add across currencies, group by currency and disclose. That discipline is correct and we would defend it anywhere.
Here is what it does in the Eastern Caribbean. The helper that assembles a multi-currency total folds every amount sharing a currency code into one bucket and adds it. That is exactly right — two amounts in the same currency are addable. And it means that receivables from six countries with six tax positions arrive as one clean line, correctly totalled, correctly labelled, and completely silent about the fact that it spans six tax jurisdictions.
The uncomfortable version
The mechanism that protects you from a wrong number is the same mechanism that conceals a real difference. It is not a bug and there is no version of it that is simply better — grouping by currency is the correct defence against the error it was built for. What it cannot do is know that currency was never the question.
The inverse case, which is more familiar
Europe runs the same mismatch the other way round and nobody finds it surprising. Member states use several different currencies and operate one harmonised VAT framework — shared concepts, shared mechanisms, a common set of rules for cross-border supply. Rates still differ country by country; what is shared is the machinery.
So one region has a common currency and independent tax systems, and the other has independent currencies and common tax machinery. Neither is unusual. Put together they say something simple that software rarely encodes: currency and tax jurisdiction are two unrelated facts about a market, and knowing one predicts nothing about the other.
-
How many tax registrations do we hold, and can the system name them?
The count is the first thing worth writing down, because it is the number the currency is hiding. If the system holds one default rate for the whole operation, that is the honest state of things and it is better known than assumed.
-
Can a report be scoped to one country rather than one currency?
This is the practical version of the whole post. If the only available grouping is currency, then six markets are one row and there is no drill-down that separates them. Ask to see the six as six.
-
What happens when one of them moves its rate?
Nothing about the currency changes, so nothing that watches currency will notice. A rate move inside a currency union is invisible to every FX control you have, and it is the ordinary way these figures change.
-
Are we sure the standard rate is the rate?
Not in Saint Lucia, where two tourism rates sit below it and the boundary is drawn by counting bedrooms. The table above gives six standard rates and a standard rate is not always the one you charge.
What our own system does
The honest version, read on the day this was written.
What AWRA OpsHub does today
- Multi-currency totals that never convert and never add across currencies. Amounts are grouped by their own currency, the largest exposure leads, and the rest are disclosed rather than folded in. This is a genuine strength and it is why the aging report stopped lying.
- A per-line tax rate stored on the document, so a document raised in one market keeps its own rate regardless of what the organisation default becomes later.
- A country reference table with a rate and a provenance record per country, so the six figures above exist as six separate verified facts rather than as one regional guess.
What it does not do
- Any grouping of money by tax jurisdiction. The multi-currency total sees a currency code and nothing else, so six countries on one currency are one bucket. There is no country dimension alongside the currency one.
- More than one default tax rate per organisation, per tax type. An operation spanning these six markets has one default, so five of the six are being handled by whoever is raising the document.
- Any link between the country reference table and what an organisation is actually charged. The reference table knows all six rates. It is read once at provisioning, and after that the organisation's own default is the only figure in play.
- Any alert when a rate moves inside a currency you already trade in. Nothing watches for it, and no currency-based control could see it if it did.
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 tax on the purchase side, a rate that follows the class of supply, 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.
The unit a rate is measured in, and the direction it travels
Two builds cover most of what this region exposes. A rate that follows the class of supply rather than only the jurisdiction, for markets where one tax has several rates and a country-keyed default is correct and useless at the same time. And tax recorded on the purchase side — a rate and an amount held out of cost, attributable to a supplier and a period — for businesses whose returns are claims rather than payments. Both are data-model changes rather than settings, and we would quote them as such.
Banks, payments and supplier obligations with dates on them
Statement feeds and local payment rails wired into the Payments Register, alongside supplier qualification that carries a per-supplier expiry and acts when it passes — the latter already runs, and reporting against a local content or preference regime is the buildable part on top of it.
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
A local payroll engine with income tax tables and social security contributions computed on live employee records, producing returns in the layout your authority expects rather than rebuilt each month.
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 integratedThe second and third items compound in a specific way worth naming. Our reference table holds all six of these figures, correctly, with sources — and an organisation set up in one of these countries gets one of them written into its settings as a default, after which the other five are just facts in a file nobody reads. Knowing the right answer and not being able to use it is a different failure from not knowing it, and it is the one we have.
The general version
Shared currencies are common — West and Central Africa each have one, the euro area is the largest, and the Eastern Caribbean is among the oldest. In every one of them the same assumption is available to be made, and it is the assumption that a currency boundary and a tax boundary are the same line. They are not, and the places where they diverge are precisely the places where nothing in your software will tell you.
The check is one sentence long. Count your tax registrations, not your currencies, and then ask whether any report you rely on can show you that number.
Frequently asked questions
Do the Eastern Caribbean countries charge the same VAT?
No. The six independent states on our table that use the East Caribbean dollar charge four different standard rates: 17% in Antigua & Barbuda and St Kitts & Nevis, 16% in St Vincent & the Grenadines, 15% in Dominica and Grenada, and 12.5% in Saint Lucia. They share a currency and set their tax rates nationally. Each of those figures is verified against a source and dated in our own provenance records.
Why does a shared currency make this harder rather than easier?
Because currency is the signal most finance systems use to notice that a second market exists. A second currency forces a conversion policy, a revaluation and a decision about reporting. When six markets share one currency, none of those prompts fire — everything adds up, every report looks clean, and nothing indicates that six separate tax positions are involved.
Is grouping by currency wrong, then?
No, and that is the awkward part. Grouping by currency is the correct defence against adding unlike currencies into a meaningless total, which is a real and common defect we have written about and fixed. The point is not that the safeguard is wrong but that it answers a different question from the one a multi-country operation is asking. Both groupings are needed and we only have one.
What should I do if I trade across several of these markets?
Start by counting your tax registrations rather than your currencies, and check whether any report you use can separate the markets that share a currency. If it cannot, that separation is being done by people, and it is worth knowing that explicitly rather than discovering it at a filing deadline. We would rather say that plainly than describe a country dimension we have not built.
