Ask AwraIQ about features, pricing, onboarding, login, integrations, security, demos, mobile apps, automation, reports, or support.
Guyana · Caribbean
Guyana's VAT is 14% and there is nothing interesting to say about it. The obligation that actually shapes how a business here buys is the Local Content Act: suppliers to petroleum operations register with the Local Content Secretariat and hold a Certificate of Registration, and that certificate renews **on the anniversary of its issuance**. Not at year end, not on a common date — on each supplier's own. A hundred suppliers is a hundred dates. This is the one page on this site whose central problem we can honestly say is already solved in the product, and the honesty section below is about where that stops.
A calendar with no season
An illustration of the shape rather than anybody's real supplier list. Each certificate was issued on a different day, so each falls due on a different one, and they will keep falling due on those days for as long as each supplier stays on your list.
| Supplier | Certificate issued | J | F | M | A | M | J | J | A | S | O | N | D |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Marine logistics contractor | 14 February 2026 | Due | |||||||||||
| Catering and camp services | 3 May 2026 | Due | |||||||||||
| Fabrication workshop | 22 June 2026 | Due | |||||||||||
| Freight and customs agent | 9 September 2026 | Due | |||||||||||
| Safety equipment supplier | 30 October 2026 | Due | |||||||||||
| Waste management | 7 December 2026 | Due |
Six suppliers produce six renewal months. Add a seventh and it is very likely a seventh month; add a hundred and effectively every working week contains somebody's anniversary.
Which is why the common approaches fail in a predictable way. An annual review catches everyone once and leaves eleven months of drift. A quarterly review is late by up to three months for whoever renewed just after it. A spreadsheet with dates works exactly as well as the attention of the person who maintains it, and the failure is silent: nothing happens when a certificate lapses, which is precisely the problem.
What is already there, stated
Supplier prequalification was built as general-purpose functionality, not for Guyana and not for this Act. It happens to have exactly the shape this obligation needs, and we would rather say that than pretend at foresight.
What the record holds today
Every approved supplier carries its own qualification expiry date.
Each organization sets the validity period that expiry is calculated from — twelve months unless you change it.
A date per supplier, and a validity period per organization that decides how that date is set. Twelve months by default, which is the anniversary model, and settable to anything from one month to ten years for obligations that are not annual.
A date per supplier, not a shared one
Each approved supplier carries its own expiry date, derived from when it was approved rather than from a calendar the buyer keeps.
The anniversary model is the default behaviour rather than something to be configured around.
An expiring-soon window you can ask about
Suppliers can be listed by how close they are to lapsing, so the question "who renews in the next sixty days" is answerable from the record.
The review can be continuous instead of quarterly, which is the only cadence that fits rolling dates.
A scheduled job that actually does something
A command runs on a schedule, lapses qualifications past their date, and deactivates the linked vendor record.
A lapsed certificate stops being a note somebody should have read and becomes a state the system is in.
The application and its documents are kept together
The certificate and supporting documents are attached to the application that was approved, with the review history alongside them.
When you are asked to show why a supplier was on the list in March, the answer is retrievable rather than reconstructed.
Everything above is a diary with consequences attached, and that is genuinely useful. It is not the same thing as knowing a certificate is real. We do not check anything with the Local Content Secretariat. We store the document your supplier gave you, we hold the date they told you it runs to, we count down to it, and we deactivate the vendor when it passes. If the certificate was withdrawn last month, or was never valid, our system will go on treating that supplier as qualified until its date arrives — because the only thing we know is what was typed in.
We are saying this on the page where we finally get to say yes, because that is exactly where the overclaim would be easiest and most damaging. If a register ever exposes a way to confirm a certificate programmatically, that is buildable and we would want to build it. Until then the honest description is: the system will not let a date slip past you, and it cannot tell you the document is true. Those are different promises and only one of them is ours.
What this costs today
Nothing happens when a certificate expires. That is the whole difficulty — there is no error, no interruption and no signal, so the list looks identical on the day after as on the day before.
Nothing happens when a certificate expires. No email arrives, no screen turns red, and the supplier keeps invoicing. The list looks exactly the same on the day after as on the day before, which is why lapses are usually found during a review of something else entirely.
Where eligibility lives in a spreadsheet and purchasing lives in a system, nothing connects the two. A purchase order can be raised against a supplier whose status lapsed in March, and the system that raised it had no way of knowing.
Showing why a particular supplier was eligible at the time you engaged them means finding the certificate that was current then, not the one on file now. If documents are replaced rather than kept in sequence, that history is gone.
Documents arrive as attachments, get reviewed in an inbox, and the decision lives in somebody's sent folder. It works until the person leaves, and then the basis for every approval on the list is unavailable.
What we are actually for
Everything below is running today. Secretariat reporting and certificate verification are not on this list, and the scope section immediately after it says so plainly.
Suppliers apply through a form you publish, upload their documents, and are reviewed in a structured workflow with information requests, approval and rejection recorded against the application rather than in an inbox.
Approval sets a qualified-until date from your own validity period, so every supplier carries its own expiry. Twelve months by default, and configurable where an obligation runs to a different clock.
A scheduled process lapses qualifications that pass their date and deactivates the linked vendor, so an expired certificate becomes a state of the system rather than a note nobody read.
The certificate and its supporting documents stay attached to the application that was approved, alongside the review history, so the basis for an approval is retrievable later.
Order, receipt and invoice reconciled with variances surfaced, so the buying record behind a qualified supplier is as disciplined as the qualification itself.
What you bought, from whom, against which project. Any report on procurement composition starts from this, whoever it is eventually for.
Scope, in three parts rather than two
Three columns, because "no" means two entirely different things and one list hides which is which. This is the one page in this wave with a long left-hand column, which makes the right-hand one more important rather than less.
Running in the product today
Not built yet — and commissionable
What we would decline, and would rather say now
The reporting gap is the obvious one and it is genuinely commissionable: the underlying spend data exists, and turning it into whatever a submission requires is specification work rather than invention. The same is true of a hard stop at ordering and of versioned certificate history. Usual terms — a written specification, a timeline and a price agreed before anything starts. Kenya is the evidence that this is real: eTIMS transmission and a maintained statutory payroll engine were both built to specification for one market and are now part of the product. No dates on a public page.
It is worth repeating that none of the built column was written for Guyana. It is general supplier prequalification that happens to match this obligation closely, which is a piece of luck rather than foresight, and we would rather describe it that way.
How this starts
Take your approved suppliers and note which month each certificate falls due. If the answer is most of the months in the year, a periodic review cannot work and you already know what you need — the question is only whether your system does it or a person does.
Not whether the system stores an expiry date — everything stores dates. Ask what the system *does* when the date passes. If the answer is "it shows in a report", that report is only as good as whoever opens it.
Pick a supplier and a purchase order from six months ago and establish, from your records as they stand, that the supplier was certified on the day the order was raised. Whatever that takes is what an assurance request will take, on a deadline.
Read before you shortlist
When every supplier certificate renews on its own anniversary, no review interval works and the failure is silent. What a system can do about it, and the difference between a countdown and a check.
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.
The hard compliance question here is procurement, not tax. Ask what the system does on the day a supplier certificate expires, and whether anybody verifies it — the plain no is the good answer.
Questions we are asked here
No, and this is the most important sentence on the page. We store the certificate your supplier gave you and the date you recorded, we count down to that date, and when it passes we lapse the qualification and deactivate the vendor. Every part of that is a diary. If the certificate was never valid, or was withdrawn after you filed it, our system has no way of knowing and will keep treating the supplier as qualified until the date arrives. **A boundary rather than a backlog** — and the reason it protects you is that a vendor claiming to verify would be inviting you to stop checking. If a register ever offers a programmatic way to confirm a certificate, that is buildable and we would want to build it.
No. It is general supplier prequalification, built because approving suppliers through email and a spreadsheet fails the same way everywhere. It fits this obligation unusually well because the obligation is a per-supplier dated certificate and that is exactly the shape the module has. We would rather tell you that than imply we designed for a statute we had not read at the time.
Not today, and it is a fair thing to want. What happens now is that the qualification expires on its date and the linked vendor is deactivated, which removes the supplier from ordinary use rather than hard-blocking a specific action. A true stop at the point of ordering — with an override and a recorded reason, because there are legitimate reasons to proceed — does not exist. **On the roadmap and commissionable now**: it is a small piece of work against a clear specification, priced and scheduled in writing before anything starts, and Kenya's eTIMS transmission is the evidence we deliver commissioned work rather than talk about it.
No. We can tell you what you bought, from whom, in what category and against which project, which is the data any such report is built from. We do not compute anything against the Act's prescribed categories and we emit nothing in a form the Secretariat expects, because we have not built against a reporting specification. **On the roadmap and commissionable** — this is specification work rather than invention, and it is the item we would expect to be asked for first here. No date on a public page, and a real one in a quote.
Partly answerable and we would rather be precise about which part. The approved application, its documents and the review history are retained, so the basis on which a supplier was approved is retrievable. What is missing is a versioned chain of certificates with the period each one covered — if a replacement document was attached over the top, the record of the earlier one is weaker than you would want for that question. Commissionable, and worth raising with us before you have a hundred suppliers rather than after.
Almost certainly not, and it is the least interesting thing about operating here. VAT is 14%, administered by the Guyana Revenue Authority, with zero-rating for exports among others. The rate is stored per invoice line, so mixed zero-rated and standard-rated invoicing is ordinary. Worth knowing that we hold no tax on the purchase side, which matters a great deal for a business in a standing credit position — our Trinidad and Tobago page sets out exactly why, and if you export heavily it is worth reading before you talk to us.
No. English is Guyana's official language, so the English-only interface — a real constraint we raise on our Francophone and Arabic-market pages — is not one here.
The honest comparison is not flattering in every direction and you should make it. A North American vendor will be closer to the operators' own systems and will cost accordingly. A local implementer will know the Secretariat and the people, which is worth more than most software features. We are remote, in a time zone that gives a workable daily overlap with Georgetown but not a shared morning, with no partner on the ground. What we bring is that the specific thing this market makes hard — a hundred certificates with a hundred different dates and a consequence when one passes — is already running rather than on a slide, and this page says exactly where it stops. Ask every vendor what their system does on the day a certificate expires. "It appears in a report" is a different answer from "the vendor is deactivated", and the difference is the whole problem.
We will show you what the expiring-soon view would look like with your own renewal months in it, and tell you plainly which parts of your local content obligation the system carries and which parts stay with you.