Liberia · West Africa

On the first of January, Liberia's 13% becomes 18% — and the tax stops being a cost.

Almost every summary of this change reports five percentage points. That is the smallest thing about it. Today's Goods and Services Tax is single-stage with no right of deduction, so it sticks to every business it touches and compounds down the chain; the VAT that replaces it is deductible, so it sticks only to the final buyer. The headline rate goes up and the tax a business cannot recover goes down. Below: the same supply chain taxed both ways, and an honest account of which half of the change our system is ready for.

The change: 1 January 2027. An 18% VAT replaces the 13% Goods and Services Tax. The rate is the headline and the mechanism is the story: today's tax cannot be deducted and the new one can.
Why it matters: A tax you cannot reclaim is charged on prices that already contain it. In the chain below, 13% takes 28.33% of the value added and 18% takes 18.00%.
What we get right: Your history is safe. The rate is stored on each invoice line when the document is raised, so a December 2026 invoice will still read 13% in 2030.
The limit: We hold no tax on the purchase side, and our two date columns are read by nothing. Both are named below with the column names, because the first is the whole point of a VAT and the second is the whole point of a dated change.

See the chain taxed both ways Talk to us about Liberia

Five points up, ten points down

The same chain, taxed both ways

Three registered businesses in a line. Each adds 100 of value. Under the GST every sale is taxed and nobody may deduct what they paid, so the tax charged at each step is charged on the tax already in the price. Under the VAT each business hands over tax on its own value added and no more.

Stage	Value added	Today · GST 13%, not deductible			From 1 January 2027 · VAT 18%, deductible
Stage	Value added	Taxed on	Tax charged	Price out	Net	Tax charged	Deducted	Handed over
Importer	100.00	100.00	13.00	113.00	100.00	18.00	—	18.00
Wholesaler	100.00	213.00	27.69	240.69	200.00	36.00	18.00	18.00
Retailer	100.00	340.69	44.29	384.98	300.00	54.00	36.00	18.00
Value actually added		300.00			300.00
Total tax collected		84.98			54.00
Tax as a share of value added		28.33%			18.00%
What the last buyer pays		384.98			354.00

A 13% tax took 28.33% of the value added. An 18% tax takes 18.00%. Nothing was avoided and nobody was cheated — the difference is entirely the 30.98 of tax-on-tax that the GST charges and the VAT does not.

An illustration of a mechanism, not Liberian price data: three registered businesses, 100 of value added at each, every supply standard-rated, no exemptions and no zero-rating anywhere in the chain. Real chains are longer, shorter and more mixed than this. The point is the shape, not the figures. One figure does need naming, though: 13% is the general rate and Liberia charges two. Telecommunications services stay at 15% GST under the same Act that raised the general rate from 12%, so a telecoms business taking 13% from this table charges two points too little and carries the shortfall itself. If that is your sector, set your own rate rather than taking this one.

This is why the change is worth preparing for rather than absorbing. The business in the middle of that chain is currently carrying tax it can never reclaim, priced into its cost of goods and invisible in its accounts as tax. From January that same amount becomes a recoverable balance — but only if it is recorded as one, which means recording tax on the purchase side. Which brings us to what we do not do.

Our own limitation, stated

The columns for this already exist. Nothing reads them.

A tax change with a known future date is exactly the case for storing a rate against the date it starts. We have those columns. They have been in the per-organization tax rate table since February 2026, next to a region and a city column, and every one of them is dead weight — which we would rather write down here than let you discover in January.

What the record can hold

A rate can be given a start date.

A rate can be given an end date.

Two optional dates on the record that holds your organization's own tax rates. Everything a scheduled rate change needs — and nothing on either side of them that acts on it.

Four things are true about those two dates, all of them measured

Nothing reads them

Both of the ways a rate gets resolved for a document pick the rate marked as the default and stop there. No date is consulted, and nothing runs on a schedule to bring a future rate into force.

A rate with a start date of 1 January 2027 will not start on 1 January 2027.

Provisioning never writes them

When your organization is first given a tax rate from the country reference, both columns are left null.

The default state of every rate we create is "no date", so there is nothing for a future fix to migrate from.

The API writes them, and it changes nothing

The tax settings API accepts both dates and stores them faithfully. Marking a rate as the default also demotes the previous one — immediately, without consulting either date.

Enter next year's rate and mark it default and it applies today. Leave it undefaulted and it never applies at all. There is no third outcome.

The rate you submit is discarded

Both the create and update paths overwrite whatever rate you send with the current value from the country reference for that country and tax type.

You could not pre-enter 18% today even if the dates worked, because the field is validated and then thrown away.

This is our gap, and it is the one that matters most here

Put plainly: there is exactly one tax rate per organization per tax type, it is always the country reference's current value, and the two date columns beside it are decoration. For a market with no scheduled change that is an unremarkable simplification. For Liberia in August 2026 it is the specific thing you would want, five months before you need it, and we do not have it. Nor do we hold tax on the purchase side at all — there is no tax column on a purchase order anywhere in the schema, which is adequate for a GST you can never reclaim and inadequate for a VAT you can.

Both are commissionable and neither is a small change, so we are not going to imply a date. What we will do is state the position precisely enough that you can hold us to it: the dates are dead, the purchase side has no tax, and there is a test in the repository pinning both so that fixing them has to be deliberate. Ask the other vendors on your list what their system will do on the second of January. The useful question is not whether they support VAT — everyone will say yes — but whether an invoice raised on 31 December and credited on 5 January gets 13% or 18%.

What the cutover costs

Four problems, and none of them are the rate

Every one of these exists whichever system you use. They are here so that the questions you put to us — and to everyone else on your list — are the ones that will matter in February rather than the ones that demonstrate well in August.

Tax you are carrying and cannot see

Under a cascading GST the tax on your purchases is not tax in your accounts — it is part of what the goods cost. It does not appear on a tax line, it is not recoverable, and it is not visible as a number anyone could tell you. The first thing the VAT does is turn that invisible amount into a balance, and the second thing it does is ask you where the records are.

A cutover with documents on both sides of it

An order placed in December and delivered in January. An invoice raised at 13% and credited at 18%. A recurring schedule that runs straight through the change. None of these are unusual; all of them need the system to know which side of a date a document belongs on, and most systems know only what today's rate is.

Two currencies in ordinary circulation

The Liberian dollar and the US dollar both circulate, so a single business routinely holds costs in one and prices in the other. That is a reporting problem before it is a treasury problem: the question "what did this actually cost us" has two answers and a date.

Advice that is priced for a bigger market

A regime change is precisely when a business wants an adviser, and the bench that can walk a mid-sized Monrovia distributor through a VAT cutover is small and about to be very busy. Whatever your system does not do for you in January, somebody will be doing by hand at exactly the moment they are hardest to hire.

Operations in Liberia

The rains arrive every year and the tax mechanism changes once. Only one of those is an annual operating problem.

The switch above is real, it is dated, and it is worth understanding before it happens. It is also a single event. The recurring operational facts here are that upcountry roads close for months, that fuel and plant leak through custody rather than through theft anyone can name, and that a great deal of the spending is somebody else's money with rules attached. Those are the problems that repeat.

Inventory

Stock placed before the rains, not ordered during them

When a road is impassable for months, a reorder point is the wrong instrument — the decision is how much has to be upcountry before the season closes it off. Replenishment suggestions run off consumption against a lead time you set per location, so the plan is made against the calendar rather than against the bin.

Assets

Generators, vehicles and plant with a named custodian

The classic leak here is fuel and running hours, and it is a custody problem rather than a theft problem: nobody is quite responsible, so nobody is answerable. Every asset carries a custodian, a location, a movement history and a service record, and a change of hands is a recorded event.

Procurement

Thresholds set by whoever is funding the purchase

Donor and concession spending comes with its own approval thresholds and quotation requirements. Requisition, threshold approval, RFQ, quotation comparison, purchase order, receipt and three-way match — with the quotes and the approval attached to the order, which is what the audit actually asks to see.

Budgets

Restricted funds walled off at the point of entry

Grant and budget lines tagged when the transaction is entered rather than allocated afterwards, with live burn against each. Reconstructing which fund paid for something is the expensive way, and it is the way most of the sector still does it.

Offline operations

Field capture that does not need a connection

Stock transfers, inventory check-out and check-in, and asset movements captured on mobile offline at a camp or a depot and synced when there is signal. Built for exactly this constraint rather than adapted to it.

Documents

The audit file assembled as the work happens

Quotations, delivery notes, waybills and approvals attached to the transaction they belong to, with retention that runs. The alternative is the panic week, and the panic week is where the exceptions get discovered by somebody else.

The qualification. Liberian payroll is not built — no local income tax tables and no NASSCORP contribution calculation — so labour cost attribution to projects and cost centres is what exists, and it is not payroll. It is on the commissionable list above with Kenya as the precedent. Nothing in this section depends on the tax change either way, which is the point of putting it on the same page.

Scope, in three parts rather than two

What runs today, what we would build, and where we stop on purpose

Three columns, because "no" means two entirely different things and one list hides which is which. The middle column is work that has not been done and has a price. The right-hand column is work we would decline from a paying customer — and it is the one worth demanding from every other vendor you talk to, because a page without it has not told you where its edges are.

Scope in Liberia, including the two dead columns

Running in the product today

The tax rate stored on each invoice line, so documents raised before a change keep the rate they were raised at without a lookup and without drift.
Multi-currency documents and reporting, which in a dual-currency economy is an everyday requirement rather than an export feature.
Landed cost open after receipt, so late freight and duty invoices still reach the goods and move the unit cost.
Purchase orders, receipts and three-way matching, with variances surfaced rather than quietly absorbed.
Branch, site, project and cost-centre attribution, across inventory, purchasing and revenue.

More we can add — and commissionable now

A tax on the purchase side. A purchase order in our product has nowhere to record tax. For a GST that can never be reclaimed this is defensible, because the tax genuinely is part of what the goods cost. From 1 January 2027 it stops being defensible, because deductible input tax has to be recorded as tax before it can be claimed as tax. This is the single largest item on this page and it is a change to how purchase records are structured rather than a screen.
Scheduled rate changes that the resolver actually consults. A start date and an end date can both be entered against your organization's rate today, and both are stored; the resolver reads neither. Making a rate start on a date is the build, and we would rather write that down than let the presence of the fields imply otherwise.
One rate per organization per tax type. Liberia's telecommunications rate sits above the standard rate, and our country reference holds a single headline figure per country. A business straddling two sector rates keeps the second one outside the system — see the Jamaica page, where this is the whole subject.
A filing output for the Revenue Authority, in both regimes. We produce no return in any format the LRA accepts, today under GST or after January under VAT. The VAT invoice specification has not been published yet; once it is, this is buildable against it and against a real filing calendar.
A Liberian payroll engine. Income tax tables, NASSCORP calculation and filing. We attribute labour cost to branches, sites and projects, which is the reporting half rather than the calculation half. Our maintained statutory payroll engine covers Kenya only — which is both the honest limit and the evidence that a second one can be built.

What we would decline, and would rather say now

We will not tell you how to treat stock on hand at the cutover. Transitional credit for goods bought under GST and sold under VAT is the question every business in this chain will have, and it is a question for your tax adviser and the Authority's transitional rules, not for a software vendor. We can record whatever treatment you are advised to take. We will not be the source of the advice.
We will not say we will be ready on a date. The VAT invoice specification has not been published, and a vendor promising readiness against a specification nobody has read is promising something they cannot know. When the specification exists we will quote against it.
We do not do currency strategy. Which of two circulating currencies to price in, hold in or bank in is a commercial and treasury decision with real consequences, and no software choice improves it. We will report accurately in both. See the Malawi page for why we hold this line firmly.
We will not act as your agent with the Revenue Authority. We do not file, we do not correspond, and we do not hold a practising credential. What we can do is produce the underlying data in a form your adviser can work from.

Two of those five are dated obsolescence rather than scope: purchase-side tax and scheduled rates are both things this product will need, and Liberia is simply the first market that makes the need legible. Both are commissionable now, on the same terms as everything else here — a written specification, a timeline and a price, before any money moves. The evidence that this is a real offer rather than a sales line is Kenya, where the eTIMS transmission and the maintained statutory payroll engine were both built exactly this way. We will not name a date on this page, and we will name one in a quote.

The five months are yours, not ours. If our answer on purchase-side tax is not good enough for your January, the right conclusion is a different system, and this page exists so you can reach it in August rather than in February.

How this starts

Three moves, and the first one needs no vendor at all

Add up the tax you cannot currently reclaim

Take one month of purchase invoices and total the GST on them. Under today's rules that figure is part of your cost of goods and appears nowhere as tax. From January the same figure is a recoverable balance. It is usually the first number that makes the change concrete, and almost nobody has it to hand.

Ask what happens to a December invoice credited in January

Not what the rate is — what the system does. Ask your current vendor, ask us, and ask anyone else on your list. The answers separate systems that store a rate on the document from systems that look one up, and the difference will be visible within a fortnight of the change.

Find out where purchase tax would be recorded

In whatever you use today, find the field that holds tax on a purchase. If there is not one, you have found the same gap we have named on this page, and you now have a question to put to every vendor rather than a feature list to read.

Read before you shortlist

Guides for this market

Accounting Insights

When The Rate Goes Up And The Tax Goes Down

A cascading tax charges tax on tax. A credit-invoice tax does not. Liberia switches from one to the other on 1 January 2027, and the five percentage points are the least interesting part of it.

Dec 14, 2025 · 11 min Read

Accounting Insights

Fields, Features, and How We Tell Them Apart

A field that saves without error is not by itself evidence of a working feature. The one-afternoon test that separates the two, run on our own tax rate table first — and worth running on any vendor you are evaluating.

Dec 16, 2025 · 9 min Read

Implementation & Rollout

Buying Operations Software in Liberia: A Straight Guide

Ask every vendor where tax on a purchase is recorded, and what happens to a December invoice credited in January. We publish our own answers, and the first one is that the field does not exist.

Dec 25, 2025 · 12 min Read

Point of Sale

Two Mandates in One Law

Nigeria clears a business-to-business invoice before it reaches the buyer and reports a till receipt after it is issued. Those are two machines, not two settings — and only one of them can stand in front of a queue on a Saturday afternoon.

Jul 8, 2026 · 14 min Read

Assets & Equipment

Register First, Depreciation Next

This product tracks where every asset is, who holds it and what happened to it — a register built for custody. A depreciation ledger is the companion system, and we can add schedules, methods and period postings alongside it.

Jun 11, 2026 · 11 min Read

Helpdesk & Support

Smart Assignment: Deciding Who Should Own a Ticket

When a ticket breaches, this product tells the agent, then their manager, then the department. Assignment rules that decide who should own the ticket in the first place — before the deadline rather than after — are something we can add to your helpdesk.

Jun 9, 2026 · 12 min Read

Questions we are asked here

Straight answers, starting with the cutover

Will your system handle Liberian VAT on 1 January 2027?

Not as it stands today, and the honest answer has two parts. What already works: the rate on each invoice line is stored on the line, so documents raised under GST keep 13% permanently and nothing rewrites your history when the rate changes. What does not: we hold no tax on the purchase side at all, and deductible input tax is the entire point of a VAT. Recording output tax at 18% is a configuration change; recording and claiming input tax is a data-model change, and we would be misleading you to describe the second as a setting. On the roadmap and commissionable now — a written specification, a timeline and a price, with Kenya's eTIMS transmission and payroll engine as the evidence that we build this way rather than talk about it. We will not name a date on a public page, because there is no published VAT invoice specification to build against yet.

Can I enter the 18% rate now so it switches over automatically?

No, and this is worth understanding precisely because the screen suggests otherwise. Your organization's rate can be given a start date and an end date, and both will be accepted and stored. Neither is ever read. Marking a future rate as your default applies it immediately, because the only thing the rate lookup asks is which rate is the default; leaving it undefaulted means it never activates. And the rate you submit is discarded and replaced with the current value from our country reference, so the figure would come back as 13% regardless. A backlog item, not a boundary — scheduled rates are commissionable and are named in the middle column above. In the meantime, the reliable answer is to change the rate on the day, which is one field.

Is the tax really going down when the rate is going up?

For businesses in the middle of a supply chain, yes, and the table above shows why. A cascading tax is charged on a price that already contains tax, so a 13% rate collected three times over collects 28.33% of the value actually added. A VAT collects 18% once, because each business deducts what it was charged. The final buyer in that illustration pays 384.98 under the GST and 354.00 under the VAT. That is a model with stated assumptions rather than a forecast for your business, and your own chain will differ — but the direction is a property of the mechanism, not of the numbers we picked.

What happens to stock we bought under GST and sell under VAT?

That is the right question and it is not ours to answer. Transitional relief for stock on hand at the cutover is a matter for the Authority's transitional rules and for your tax adviser, and a software vendor offering a view on it would be doing something we think is genuinely wrong. A boundary rather than a backlog, and the reason it protects you is straightforward: our incentive is to make our software look sufficient, which is exactly the wrong incentive to have when the answer determines a real liability. What we will do is record whatever treatment you are advised to take, and produce the stock and purchase history your adviser needs to work it out.

We invoice in both Liberian and US dollars. Is that a problem?

Not for the system. Documents can be raised and held in more than one currency and reported across them, which in an economy where both circulate is an everyday requirement rather than an export feature. What we will not do is advise you on which to price in, hold or bank in — that is a treasury and commercial decision with real consequences, and no software choice improves it. We hold that line everywhere for the same reason; the Malawi page explains it at length.

Do you file our returns with the Liberia Revenue Authority?

No, and we produce no return in any format the Authority accepts — that is true today under GST and it will be true in January under VAT until somebody builds it. Two halves, and they have different answers. The data half is a backlog item: producing a return from records the system already holds is buildable against a published specification, and none exists for the new regime yet. The filing half is a boundary: we do not correspond with the Authority on your behalf and we hold no practising credential, so an intermediary who does is not a gap in our product but a person you should have.

Is English-language software a limitation here?

No. English is Liberia's official language and the language of business and administration, so the interface being English-only — a real constraint we raise on our Francophone and Arabic-market pages — is not a constraint here. We mention it only because we would rather answer the question than have you wonder whether we quietly avoided it.

We are donor-funded and our accountant handles the tax change. What is left for us?

The part that repeats every year, which is more of the product than the part that changes once. Stock placed upcountry before the roads close, planned against a lead time per location rather than a reorder point. Generators, vehicles and plant with a named custodian and a movement history, because the leak here is fuel and running hours and it is a custody problem rather than a theft anyone can name. Procurement with the approval thresholds your funder set, and the quotations and the approval attached to the order rather than in an inbox. Restricted funds tagged at the point of entry with live burn against each budget line, instead of reconstructed at report time. Field capture that works at a camp with no signal. None of that changes on the first of January, which is the reason it shares a page with something that does.

Why should we buy from a vendor in Nairobi rather than a local firm?

Quite possibly you should not, and if a Monrovia implementer knows your industry and will answer the phone, that is worth more than anything on this page. We are further away, in a different time zone — though a workable one, unlike our Pacific pages — with no office and no local partner. What we offer instead is checkability. This page names two specific gaps in our own schema with the column names, states that the largest one is dated obsolescence rather than a missing feature, and there is a test in the repository pinning both so a fix has to be deliberate. Ask every other vendor on your list what their system does with tax on a purchase order. The ones who understand why you are asking are the ones worth talking to.

One month of purchase invoices

Total the GST on them. That figure is invisible in your accounts today and becomes a recoverable balance in January. Bring it and we will tell you honestly which part of the change we are ready for and which part we are not.

Talk to us about Liberia See plans & pricing