The Rate Decided By A Bedroom Count
Saint Lucia charges 12.5%, 10% or 7% depending on what is being sold and who is selling it — and "who" is settled by counting bedrooms. Five or more and you are a hotel. Four and you are not, on the same street, selling the same night.
We have written before that the unit of a tax rate is often not a country — that asking "what is the rate in Jamaica" has no single answer. Saint Lucia takes the same idea somewhere smaller and stranger. Here the rate depends on what you are selling, and on whether the business selling it has five bedrooms.
That is not a rule of thumb or a registration test. It is the statutory definition, and it means two guesthouses on the same street, selling the same room on the same night, can owe different amounts of tax because one of them has an extra bedroom.
Three rates, and the standard one is the exception
Section 10(1) of the Value Added Tax Act sets the standard rate at 12.5% of the value of taxable goods or services imported into Saint Lucia, or of the value of taxable supplies. Section 10(2) then lets the Minister set a separate rate for hotels and other tourism providers, and the Value Added Tax (Rate of Tax) (Tourism Sector Goods and Services) Order does exactly that.
| Rate | What it applies to | Set by |
|---|---|---|
| 12.5% | Taxable supplies and imports generally | Section 10(1) of the Act |
| 7% | A supply of tourism accommodation service | The Tourism Sector Order, section 3 |
| 10% | Restaurant food and beverages including alcohol; water sports; tours conducted by land, air or sea within Saint Lucia; admission to heritage sites and other touristic attractions | The same order, same section |
Read the third row again as an operations problem rather than a tax one. It is a closed statutory list, not a description of a sector — and one detail inside it decides a surprising number of invoices: transport supplied directly as part of a tour package is in, and transport arranged indirectly is not.
A hotel selling a guest a room, dinner and a souvenir is running three tax rates down one folio, and only one of them is the country's rate.
That is the shape of an ordinary night in Saint Lucia. Room at 7%, dinner at 10%, a bottle from the gift shop at 12.5%. One customer, one stay, one document, three rates — and none of this is unusual or aggressive. It is what the law says, applied to a normal business doing normal things.
Five bedrooms
The tourism rates belong to hotels and tourism providers, so everything turns on what a hotel is. Section 10(5) answers it: five bedrooms or more, let for reward.
A definition that plain is easy to admire and hard to hold in software, because of what kind of fact it is. It is not a tax attribute, not a licence, not a registration and not a sector code. It is a count of a physical thing, and it changes when somebody converts a store room.
-
A guesthouse adds a fifth bedroom
Nothing about the business changes except the building. The rate on every night it sells changes with it, from a date that is a matter of fact rather than of filing. There is no event in any finance system that corresponds to this — no renewal, no notification, no field that would even be edited.
-
Two competitors quote the same price
One has four bedrooms and one has five. Their guests pay different tax on the identical stay, and the guest sees only a total. This is not a loophole; it is a threshold, and thresholds always have somebody sitting just below them.
-
A hotel runs a restaurant open to the public
Restaurant food and drink is on the 10% line by name. A guest's dinner and a walk-in's dinner are the same supply on the same list, and the difference between the two documents is not the rate — it is that one of them also has a room on it at 7%.
-
The same hotel sells something ordinary
Sun cream from the shop is not accommodation and is not on the closed 10% list, so it is a standard-rated supply at 12.5% sold by a business most of whose output is not. The rate is not a property of the seller. It is a property of the line.
The opposite of the neighbouring case
It is worth putting Saint Lucia beside Jamaica, because the two are structurally identical and point in opposite directions. Both run a standard rate with sector rates beside it. In Jamaica the notable sector rate is above the standard rate — telephone services and handsets are charged higher than ordinary goods. In Saint Lucia both sector rates are below it.
So a system that defaults every line to the country's standard rate is wrong in both places, in opposite directions: it under-collects in Jamaica and it over-charges a hotel's guests in Saint Lucia. One of those produces a liability nobody notices and the other produces a complaint from the customer. Neither produces an error message. We have written about the Jamaican half separately, as One Country, Three Rates.
What our own system does with a folio like that
The honest version. This is the same mechanism the Irish rates post describes, meeting a different law and failing the same way, and it was re-read on the day this was written rather than taken from that post.
What AWRA OpsHub does today
- A tax treatment stored per invoice line, so a document genuinely can carry different treatments on different lines rather than one rate for the whole invoice.
- Three treatments that resolve correctly: standard, zero-rated and exempt. The last two resolve to nothing charged, which is right, and they are stored on the line rather than recomputed later.
- One default rate per organisation, per tax type, applied to standard lines — which is the correct answer for the 12.5% and for every ordinary supply.
- A per-customer exemption, read when the document is priced, for the case where the buyer rather than the supply carries the relief.
What it does not do
- Any third positive rate. The resolver has exactly two outcomes: the organisation default, or zero. There is no path that produces a rate which is neither the default nor nothing, so 7% and 10% cannot be reached at all on a line.
- A safe failure when you ask for one. This is the part worth stating plainly rather than politely: a treatment the resolver does not recognise falls through to the organisation default. Set a line to a reduced treatment and it is charged at the standard rate, saved, and printed. There is no warning, no validation error and nothing on the document to show it happened.
- Any rate that depends on a property of the selling business. Nothing in the tax path reads anything about the organisation except its default rate, so "this business is a hotel because it has five bedrooms" has nowhere to live and nothing to change if it were stored.
- Any notion of a closed statutory list of supplies. Whether a tour is direct or indirect transport is exactly the kind of determination the 10% line turns on, and there is no structure that would hold the distinction, let alone apply it.
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 item is the one to act on if you operate here. The failure is silent and it is in the over-charging direction for a hotel, which means the people who find it are your guests rather than your accountant. Until a line can carry a third rate, a Saint Lucian tourism business using our system is doing this arithmetic outside it.
Where these figures came from, and why that needs saying
The Inland Revenue Department's website has served "Down for maintenance" continuously since we began looking, so none of this came from the authority. It was read in the Revised Laws of Saint Lucia, published by the Attorney General's Chambers — which is not a .gov domain, and would ordinarily be a reason to keep looking. What makes it usable is that the Customs & Excise Department links to it from its own legislation page as the place to read the law.
We publish that reasoning rather than the rate alone because the alternative is worse. A figure with no stated source reads as more confident than one that names an imperfect source and says why it was accepted, and it is the second kind you can actually check.
The general version
Every finance system asks what country you are in, and better ones ask what you sell. Almost none can ask a question about the premises — and yet that is what a threshold expressed in bedrooms, seats, square metres or vehicles actually is. Saint Lucia is not exotic in this. It is unusually clear about it.
The instruction is one question to ask before you decide a country is configured: what does this rate depend on, and could my system store that thing at all? A rate you can type in is never the hard part. A rate that depends on a count of rooms is a different kind of problem, and finding that out at configuration time is much cheaper than finding it out from a guest.
Frequently asked questions
What is the VAT rate in Saint Lucia?
The standard rate is 12.5% under section 10(1) of the Value Added Tax Act. Two further rates apply in the tourism sector under an order made by the Minister: 7% on a supply of tourism accommodation service, and 10% on restaurant food and beverages including alcohol, water sports, tours conducted by land, air or sea within Saint Lucia, and admission to heritage sites and other touristic attractions. Which of the three applies depends on both what is supplied and who supplies it.
Why does the number of bedrooms matter?
Because the tourism rates apply to hotels and other tourism providers, and the Act defines a hotel at section 10(5) as premises with five bedrooms or more let for reward. That makes the boundary a count of rooms rather than a licence or a registration, so it can change when a building changes. Whether any particular business meets the definition is a determination for that business and its adviser, not something to infer from this post.
Can AWRA OpsHub charge 7% on one line and 12.5% on another?
No. Our line-level tax resolution has two outcomes — the organisation default rate, or nothing at all for zero-rated and exempt lines. There is no path to a third positive rate. Worse, asking for one is not refused: an unrecognised treatment falls back to the organisation default, so the line is charged at the standard rate and saved with no warning. If you operate in Saint Lucia's tourism sector this is a manual matter today and we would rather say so than describe a plan.
Is this the same thing as the Irish rates problem you wrote about?
The same mechanism in our product, meeting a different law. Ireland runs several rates assigned to categories of goods and services, so the question there is which rung a product sits on. Saint Lucia's rates turn partly on the seller — whether the business is a hotel — which is a kind of question our tax path cannot ask at all. The consequence in our system is identical because the fallback is the same one.
