Ask AwraIQ about features, pricing, onboarding, login, integrations, security, demos, mobile apps, automation, reports, or support.
Jamaica · Caribbean
The rate we hold for Jamaica is 15%, and it is correct. It is also the wrong answer for a telecoms dealer, who charges 25%, and for a hotel, which charges a reduced effective rate. That is not a stale number that somebody can go and refresh — the value is right and the **unit** is wrong. Our table can tell Kingston from Montego Bay, which does not matter here, and cannot tell a handset from a hotel room, which does. Below: the three rates, and precisely where a system that assumes one rate per country stops being useful.
Administered by Tax Administration Jamaica
All three are the General Consumption Tax. None of them is a different tax with a different name — it is the same instrument charged at a different rate depending on what is being supplied, which is why "what is the GCT rate in Jamaica" is a question with no single answer.
Most goods and services
15%
This is the figure our country reference holds and the one we provision.
Telephone services, phone cards and handsets
25%
Ten points above the rate we would give you as a default, on every document, from the day you start.
Hotels and the tourism sector
about 10%, effective
Effective, approximateFive points below our default, in the sector most likely to be invoicing in a second currency as well.
A fourth thing to know, and it is dated: the reduced tourism rate has been announced to move to the standard rate from April 2027. Announced, not yet in force. A hotel choosing a system this year is choosing one that has to survive a rate change in that one, which is the same problem the Liberia page is about and a much smaller version of it.
The reduced tourism figure is an effective rate and is written here as an approximation on purpose. The other two are exact. A page arguing that a system should be precise about rates does not get to round one of its own.
Our own limitation, stated
Here is everything your organization's own tax rate can be varied by — not the country reference, but the record you control, which is where a rate that differs from the national default would have to live.
Everything a rate can be varied by
A rate can be set for a country.
A rate can be set for a region within that country.
A rate can be set for a city within that region.
Country, region, city. A rate can change as you move across a map — which is the right shape for Canada or the United States, and no help at all in Jamaica, where the rate changes as you move across a price list.
One default per organization, per tax type
The rate lookup selects the single row marked as your default. A second rate for a second sector has nowhere to be the default from.
A business selling handsets and accessories has one correct rate and one incorrect one, whichever way it configures.
The country reference holds one headline figure
Jamaica appears once, at 15%. That is the right figure to provision a new organization with and it is what we provision.
A telecoms dealer is set up ten points light on day one unless somebody notices and overrides it.
Where the rate genuinely lives is the invoice line
Each invoice line stores its own rate as a figure, so a correct document can always be produced by setting the rate on the line.
This is a real workaround and it is manual. It is a person remembering, on every document, and we will not describe it as sector support.
Totals across enabled taxes are added, not composed
Where more than one tax type is switched on, the rates are summed into one blended figure.
Anyone tempted to model a second sector as a second tax type should know that the totals will add the two together.
We would rather put this plainly than let it be discovered. Our Jamaica row says 15% and 15% is correct. If you sell most things, the number we give you is the number you need and there is nothing on this page for you to worry about. If you sell telephone services or handsets, the number we give you is wrong by ten points, and the reason is not that we have not looked it up — it is that this file has one row per country and there is nowhere to put the second answer. If you are a hotel, the same thing happens in the other direction, and then again in April 2027 when the reduced rate is due to end.
The honest scope of the workaround: the rate on each invoice line is stored per line, so every document you raise can be correct, and none of your history will be rewritten when a rate moves. What is missing is the system knowing which rate to reach for without being told. That is a dimension this data model does not have, it is commissionable, and it is the same shape of gap as the sub-national rates a United States page would need — which is why it is on the roadmap as one piece of work rather than as a Jamaican special case.
What this costs
None of these produce an error. A document at the wrong rate is internally consistent, formats correctly and prints beautifully, which is why the discovery usually happens at a return rather than at a desk.
Systems provision a tax rate from a country. If your rate is not your country's headline rate, the setup is wrong from the first document and stays wrong quietly, because nothing about a correctly-formatted invoice at the wrong rate looks unusual. It is found at a return, or later.
A dealer selling handsets and accessories, a hotel with a retail arm, an operator billing both tourism services and ordinary ones. The mixed business is not an edge case here, it is the normal shape of a Jamaican trading company, and it is the case a one-rate configuration handles worst.
The reduced tourism rate has been announced to end in April 2027. Any system chosen now has to cross that date with documents on both sides of it — quotations issued before, invoices raised after, credits against either.
Jamaica has capable accounting practices and a small pool of people who implement mid-market systems. When configuration has to be right at the sector level and the system will not do it for you, that scarce person becomes the control — and their notes become the documentation.
What we are actually for
Everything below is running today. A sector dimension on a tax rate is not on this list, and the scope section immediately after it is more specific about that than a vendor normally would be.
Each line keeps the rate it was raised at as a stored figure rather than a lookup. That is what makes a correct 25% document possible today, and what stops any future rate change from rewriting the ones you have already raised.
Items carry their own tax treatment, so the goods themselves — rather than a person's memory at the moment of invoicing — can be the thing that decides how a line is taxed. This is the closest the product comes today to a sector rate, and the page above is honest about the distance remaining.
Raise, hold and report across more than one currency. Tourism businesses routinely price in a currency they do not bank in, and the reporting question that follows is an everyday one rather than a year-end one.
Retail sale lines carry their own tax figures and post to the same accounts as everything else, so a shop, a counter and a contract sale are one set of books rather than three that get reconciled monthly.
Every branch, store and holding location keeps its own position, transfers confirm on receipt rather than despatch, and stock in transit is a state rather than a gap.
Revenue and cost attributed to the part of the business that produced them, which for a mixed-sector trader is the reporting cut that actually answers questions.
Scope, in three parts rather than two
Three columns, because "no" means two entirely different things and one list hides which is which. The middle column has a price. The right-hand column is work we would decline from a paying customer, and it is the one to demand from every other vendor on your list.
Running in the product today
Not built yet — and commissionable
What we would decline, and would rather say now
The sector dimension is one piece of work, not a Jamaican special case — the same missing column is what a United States or Canadian page would need for sub-national rates, and building it once serves all three. It is commissionable now on the usual terms: a written specification, a timeline and a price agreed before anything starts. Kenya's eTIMS transmission and its maintained payroll engine were both built exactly that way, which is the reason to believe this is an offer rather than a deflection. No dates on a public page.
If most of what you sell is standard-rated, none of this affects you and the page has been more alarming than your situation warrants. If you are in telecoms or tourism, it is the first thing you should ask any vendor about, including us.
How this starts
List what you sell and the GCT rate each line attracts. If that list has more than one rate on it, you have a configuration question rather than a software question, and it should be the first thing you raise in any demonstration rather than the thing you discover in month two.
Not whether the system supports 25% — everything supports 25%. Ask where the 25% lives: on the item, on the customer, on the line, or in the head of the person raising the invoice. The answer tells you what happens on the day that person is on leave.
The tourism rate is announced to move. Ask any vendor how a system holds a rate that changes on a known future date, and whether a quotation issued before it and accepted after it re-prices. Ours does not, and says so on the Liberia page in more detail than most vendors will offer.
Read before you shortlist
Jamaica charges 15%, 25% and a reduced tourism rate under a single tax. Configuration screens ask which country you are in, which for a great many businesses is the wrong question entirely.
A field that saves without error is not evidence of a feature. We have two date columns on our own tax rate table that accept writes and change nothing, and the pattern is common enough to test any vendor with.
Write down every rate you actually charge before you look at a system. If the list has more than one entry, most tax configuration screens have no shape for your business — including ours.
Questions we are asked here
On the documents, yes — every invoice line stores its own rate, so a correct mixed invoice can be raised today and will stay correct permanently. In the configuration, no. Your organization holds one default rate per tax type, and the rate table can express a country, a region and a city but nothing about what is being supplied, so there is no rule that reaches for 25% because a line is telecoms. It is a person setting the rate. **On the roadmap and commissionable** — the missing sector dimension is the same piece of work that sub-national rates need elsewhere, so it gets built once and serves several markets; a written specification, a timeline and a price, with Kenya's eTIMS work as the evidence we build this way. We will not call the workaround a feature.
15%, because that is Jamaica's standard rate and what our country reference holds. If you are standard-rated, that is correct and there is nothing to do. If you are a telecoms dealer it is ten points light, and if you are a hotel it is above your effective rate — in both cases you would need to override it, and nothing in the system will prompt you to. We would rather you knew that before signing than found it at your first return.
It has been announced as a budget measure to move to the standard rate from April 2027, with the deferral intended to give operators time to adjust pricing and contracts. Announced is not the same as in force, and we would not build a business case on any tax measure that has not commenced. What is worth doing now is asking whichever system you are choosing what it does with a quotation issued at one rate and accepted at another, because that question has the same answer in April 2027 as it does at any other rate change, and most systems answer it badly.
Please do not, and we would decline to configure it that way. Where more than one tax type is enabled, the system adds their default rates together and reports one blended figure — so 15 and 25 would present as 40 on a total. It is not that the workaround is inelegant; it produces a number that is wrong and that nobody can explain from the screen. **A boundary rather than a backlog**, and the thing it protects you from is a configuration that appears to work for months. The supported answer today is the rate on the line.
No, and we produce no return in a format the Authority accepts. **Two halves, and they have different answers.** The data half is a backlog item — the underlying figures are in the system and a return is buildable against a published specification. The filing half is a boundary: we do not correspond with the Authority on your behalf and hold no practising credential. Worth saying plainly that invoices are not cleared in Jamaica, so unlike some markets we write about, nothing about your day-to-day invoicing waits on a government system.
Yes. Documents can be raised and held in more than one currency and reported across them, which for a tourism business is an operating requirement rather than a year-end convenience. What we will not do is advise you on which currency to price, hold or bank in — that is a commercial and treasury decision and no software choice improves it.
No. English is Jamaica's official language and the language of business and administration, so the English-only interface — a genuine constraint we raise on our Francophone and Arabic-market pages — is not one here. We answer it because it is a fair question to ask a vendor from another region, not because there is a problem hiding in it.
If a Kingston implementer knows your sector and will pick up the phone, that is worth a great deal and we would not pretend otherwise. We have no office on the island and no local partner, so configuration work happens remotely with you. The time zone is the one thing that genuinely favours us over our own Pacific pages — a Kingston morning overlaps a Nairobi afternoon, so there is a shared working window every day. What we offer beyond that is checkability: this page names the exact column that is missing, admits the default we would give you is wrong for two sectors, and there is a test in the repository pinning the claim. Ask every vendor on your list where a 25% rate is stored. The answers will differ more than you expect.
If it has more than one rate on it, we will show you exactly where each one would live in our system and which of them a person has to remember. That conversation takes twenty minutes and it is more useful than a demonstration.