Buying Operations Software in Jamaica: A Straight Guide
Write down every rate you actually charge before you look at a single system. If that list has more than one entry, most tax configuration screens do not have a shape for your business.
Most software evaluations in Jamaica go wrong in the same quiet place: the tax setup. Not because anybody gets the rate wrong, but because the system asks which country you are in when the question that matters is what you sell. The General Consumption Tax is 15% as standard, 25% on telephone services, phone cards and handsets, and a reduced effective rate in tourism — and a configuration screen with one box for a rate has already lost two of those.
This guide is written by a vendor and our own answer to the central question is a manual workaround, which we would rather tell you now than have you find in month three.
The one piece of preparation worth doing
Before any demonstration, write down every rate your business charges and roughly what proportion of revenue sits behind each. It takes twenty minutes. If the answer is one rate, you can skip most of this guide and evaluate on ordinary grounds — stock, invoicing, reporting, support. If it is two or three, that piece of paper is now the most useful document in the process, and you should put it in front of every vendor at the start rather than the end.
A wrong rate is a maintenance problem. A right rate in the wrong unit cannot be fixed by looking anything up, because there is no single value that would be correct.
The questions worth asking
Seven questions, and the first three do most of the work
Where does a non-standard rate live — on the item, the customer, the line, or a rule?
What you will hear
One of those four.
How to read it
Only "on the item" or "a rule" survives staff turnover. Ours is the line, set by whoever raises the document, and we will not describe that as sector support.
What rate will you set us up with on day one?
What you will hear
A figure from a country reference.
How to read it
If that is 15% and you are a telecoms dealer, your configuration is wrong from the first document. Ask what prompts anyone to change it — usually nothing does.
If I enable two tax types, what happens to the total?
What you will hear
Separate lines, or a sum.
How to read it
Worth knowing before you configure a second rate as a second tax type. Ours sums them, so 15 and 25 would present as 40 — which is why we would decline that configuration rather than ship it.
Can an item carry its own tax treatment?
What you will hear
Often yes, in some form.
How to read it
This is the closest most mid-market systems come to a sector rate, and it is genuinely useful. Ask whether it overrides the organization default automatically or only offers a suggestion.
The tourism rate is announced to move in April 2027. What does the system do?
What you will hear
A date field, usually.
How to read it
Ask what reads it. A stored date that nothing consults is a common gap — we have two such columns and publish the fact.
What happens to a quotation issued at one rate and accepted after a change?
What you will hear
Frequently nothing at all.
How to read it
Most systems convert it carrying the rate it was issued at, with no flag. That is sometimes correct and it should be a decision rather than an accident.
Can we invoice guests in one currency and pay staff in another, and report across both?
What you will hear
Most credible systems: yes.
How to read it
Ordinary for tourism operators. If multi-currency sits in an upgrade tier, price it in now.
What good looks like, given nobody is perfect here
You are unlikely to find a mid-market system that models a rate per class of supply properly, so the realistic question is which compromise you can live with. In rough order of preference: a rule that derives the rate from what is being sold; a tax treatment carried on the item; a rate defaulted per customer where your sectors map cleanly onto customer types; and last, a rate set by hand on each line. The last one works — every document can be correct — and its weakness is entirely about people rather than software.
Whichever you end up with, the thing to insist on is that the rate is stored on the document line once set, rather than resolved when the document is displayed. That is what stops a future rate change from rewriting invoices you raised years ago, and it is the one part of this that most systems, including ours, get right.
Our own answer, so the question is fair
Our country reference holds Jamaica at 15%, which is correct, and that is the rate we would provision you with. Your organization's own rate can be varied by country, by region and by city — three kinds of geography, and nothing about what is being supplied — and you hold one default rate per tax type. So for telecoms or tourism the default is wrong and the correct rate is set per line by a person. Items can carry a tax treatment, which helps. None of that adds up to sector support and we do not describe it as such. Published on our Jamaica page in the same words.
One missing dimension, and it is not a Jamaican special case.
"Not built in" describes what ships in the standard product rather than the limit of what AWRA OpsHub can do. Kenya's eTIMS integration and its maintained statutory payroll engine were both commissioned by clients who needed them. The same door is open here. The item at the top of this list is worth understanding as one piece of work rather than four: the same missing dimension is what sub-national rates would need for a United States or Canadian page, so it gets built once and serves several markets. Tell us which of these decides your evaluation and we will scope it — written specification, timeline and price, before anything starts.
A rate that follows the class of supply
A dimension on a tax rate that is not geography, so 25% reaches a handset without anybody remembering. The whole subject of the Jamaica page, and the same build that sub-national rates need elsewhere.
Rates that start on a date
For April 2027 and every announced change after it. The columns exist on our rate table and nothing reads them, which we publish rather than hide.
A prompt when a rate moves under an open document
A quotation issued before a change and accepted after it, flagged rather than silently converted. Small, once dated rates exist underneath it.
A GCT return for the Authority
Produced from records the system already holds, against a published specification. Honestly not the first thing we would build here — invoices are not cleared in Jamaica, so this is convenience rather than a blocker.
A Jamaican payroll engine
Income tax tables, NIS and NHT on live employee records. A maintenance commitment rather than a project with an end date, and we would quote it as one.
Absent from that list, and present on the equivalent lists for our Francophone and Gulf pages: language. English is Jamaica's official language, so there is nothing to disclose and we will not pad the list to look thorough.
The short version
Write your rate list down first. If it has one entry, evaluate on ordinary grounds. If it has more, you have a requirement that most tax configuration screens cannot express, and the honest question to every vendor is not "do you support 25%" — everything supports 25% — but "where does the 25% live, and what happens when the person who knows is on leave". Our answer is the line, and a person. It is a real workaround and it is not a feature.
