Buying Operations Software in Trinidad and Tobago: A Straight Guide
If your last return was a claim rather than a payment, you are buying against a requirement most systems were not built for — and one question settles most of the evaluation.
Start by working out which kind of business you are, because it changes the entire evaluation. If you charge 12.5% on your sales and pay it on your purchases, your VAT return is a payment and almost any competent system will serve you. If you export, or what you sell is zero-rated, your return is a claim — and the number it turns on is not what you charged but what you were charged, which is the number most accounting systems never record as tax at all.
This guide is written by a vendor whose product does not hold that number. We have put our own answer next to every question rather than leaving you to discover it, because on this particular requirement the gap is large enough that you may reasonably conclude we are the wrong choice.
Why the claim side is structurally different
Zero-rating here is broad — basic foods, crude oil, natural gas and exports among others — so a substantial share of registered businesses are in a standing credit position rather than a paying one. For those businesses the VAT balance is a receivable, frequently among the larger current assets on the balance sheet, and commonly the only material asset assembled by hand from paper every second month.
The structural fact worth stating, and we will not go past it: a business in a credit position is financing its own input tax from the moment it pays a supplier until the moment its claim settles. How long that takes and why is not a software question and not one we will offer a view on. What is a software question is whether the evidence behind the claim accumulates continuously or is reconstructed six times a year.
The questions worth asking
Seven questions, and the first one eliminates most systems
Show me, on a purchase document, the field holding the tax I was charged.
What you will hear
A field, a report, or a redirection to landed cost.
How to read it
Only the field counts. Ours does not exist. A tax rate appears in three tables in our schema and all three are sales-side. Ask this before anything else.
What is my input tax total for the last period, and where does the number come from?
What you will hear
A screen, or an export and a formula.
How to read it
If the provenance is an export, the system is storing cost and a person is deriving tax. That person is your control.
Does landed cost hold the VAT separately from the goods cost?
What you will hear
Usually not, and usually not by design.
How to read it
Landed cost exists to fold tax into unit cost so margins are honest. That is the opposite of what a claim needs, and a good landed-cost implementation makes reclaiming harder rather than easier.
How do you apportion input tax between zero-rated and standard-rated activity?
What you will hear
A method, or an admission.
How to read it
This becomes urgent the day a domestic trader wins an export contract, which is exactly when a manual method stops scaling.
A supplier invoice arrives three weeks after the period closes. Which period is its input tax in?
What you will hear
A rule about document dates.
How to read it
Late supplier invoices are the normal case. A system with no answer produces claims that quietly disagree with the ledger.
Can I see, per supplier, what I have claimed and what is outstanding?
What you will hear
Rarely, in mid-market software.
How to read it
A nice-to-have that becomes a necessity once the receivable is material. Worth asking even if you expect a no.
Can I report on a two-month period?
What you will hear
Almost always yes.
How to read it
Genuinely not a problem anywhere — reporting cuts to arbitrary dates in most systems including ours. Do not let a vendor sell you a "bi-monthly VAT module"; the period is not the hard part.
A distinction worth keeping straight
The two-month filing period sounds like it should be a software problem and it is not. Reporting in most systems, ours included, can be cut to whatever dates you specify. We have no concept of a statutory filing period because we do not file — which is a boundary rather than a limitation, and a different thing from the genuine period problems that exist elsewhere. Our Papua New Guinea page describes one of those: a fortnightly pay cycle that a unique key in the database actively refuses. This is not that, and we would rather not borrow the drama.
Our own answer, so the question is fair
We hold no tax on the purchase side — no rate, no amount, no flag, on any purchase document. So we cannot total your input tax, cannot show your credit position, and cannot produce a return. What we do carry is the discipline the claim rests on: purchase orders matched to receipts and supplier invoices with variances surfaced, supplier records with the documents attached, and output tax stored per sales line so zero-rated and standard-rated supplies live in one ledger. If you export heavily, weigh that honestly — the sales half is well served and the half where your money is, is not. Published on our Trinidad and Tobago page, and it is the same missing column our Liberia page describes for a different reason.
One column underneath three of these, and it is already on the list for another market.
"Not built in" describes the standard product rather than the limit of what AWRA OpsHub can do. Kenya's eTIMS integration and its maintained statutory payroll engine both exist because clients commissioned them. The same door is open. What is worth knowing here is that the first item is not a Trinidadian special case: our Liberia page needs the identical build because a VAT arrives there in January, so it is one piece of work serving two markets. Tell us whether it decides your evaluation and we will scope it — written specification, timeline and price, agreed first.
Tax on the purchase side
A rate and an amount on purchase documents, held out of cost, attributable to a supplier and a period. Everything else on this list depends on it and no reporting can substitute for it.
A credit position you can see
Input tax against output tax, per period, with what it nets to. Small once the column above exists and impossible before it.
Apportionment between zero-rated and standard-rated activity
For businesses that are partly both, which is most of them eventually. Genuinely commissionable, and the second thing we would build rather than the first.
A VAT return for the Board
Produced from records the system holds, against a published specification. Note that filing itself stays with you or your adviser — that part is a boundary rather than a backlog.
A Trinidadian payroll engine
Income tax tables and NIS on live employee records. A maintenance commitment rather than a project with an end date, quoted as one.
Two things deliberately absent. Language: English is the official language here, so there is nothing to disclose. And foreign exchange, which is a real feature of operating in this market and not a software problem — we will report accurately in whatever currencies you transact in and will not advise on sourcing or timing. Our Malawi page sets out why we hold that line rather than making a feature of it.
The short version
Take your last return. If the bottom line was a claim, the entire evaluation reduces to one question — where, on a purchase, is the tax recorded — and it is answerable in a sentence by anybody who knows their own product. Ask it of every vendor including us. Our answer is that the field does not exist, that it is the largest gap on our Trinidad and Tobago page, and that it is commissionable. A vendor who answers less specifically has probably not been asked before.
