Zambia's turnover tax is not VAT and implementers coming from a VAT-return background keep tripping over that distinction. It is a presumptive tax charged on gross turnover for small businesses below the VAT registration threshold set by the Zambia Revenue Authority (ZRA), and if your Acumatica tenant is registered under it, the tax engine configuration looks nothing like a standard multi-rate VAT setup.
Turnover tax vs VAT in Acumatica
Turnover tax is charged as a flat percentage of gross sales, with no input tax credit mechanism — a business does not reclaim tax on its purchases the way a VAT-registered business does. In Acumatica terms, that means you are not configuring a chain of tax categories with reclaimable input/output legs on Tax Zones (TX206000) and Tax Categories (TX205500). Instead, you typically configure a single non-recoverable output tax applied at the sales-document level, similar to how a US sales-and-use tax is modeled: it hits revenue, not a VAT control account pair.
The most common mistake is reusing a VAT-style tax schedule and leaving the "reclaimable on purchase" flag active out of habit. For a turnover-tax taxpayer that overstates recoverable input tax that ZRA will not honour, and it usually surfaces months later during a compliance review rather than at go-live.
Threshold monitoring and registration status
Turnover tax applies below a registration threshold; cross it, and the business must register for standard VAT instead. That is a business-process problem more than a technical one, but Acumatica can help by tracking rolling 12-month turnover against the threshold. A lightweight approach: a scheduled generic inquiry against the AR Invoice and AR Cash Sale registers, summed by fiscal period, surfaced on a dashboard with a warning tile as the business approaches the threshold — so finance has months of runway to plan the VAT registration and tax engine cutover rather than discovering it retroactively.
Moving from turnover tax to VAT mid-year means the sales documents before and after the cutover date are taxed under fundamentally different rules. Do not just switch the tax schedule on the customer or item — issue a clear cutover date, close out the turnover-tax period cleanly, and start VAT registration on a new tax zone rather than mutating the existing one.
Configuring the tax category
Set up a dedicated Tax ID on Tax Zones and Tax Categories with the rate ZRA publishes for turnover tax (historically around 4% on gross turnover, though implementers should always confirm the current published rate rather than trust a prior project's number). Mark it non-reclaimable, tie it to the correct GL tax payable account, and scope it to the branch or company that operates under turnover-tax registration if you run a multi-branch tenant where only some entities qualify.
Tax Zone: ZM-TURNOVER
Tax Category: TURNOVER-TAX
Tax ID: ZM-TT
Calculation: Percent of taxable amount
Reclaimable: No (non-recoverable)
Applies to: AR Invoice, AR Cash Sale
Exclude from: AP Bill input tax recovery
Reporting to ZRA
Because there is no input tax netting, the turnover tax return is simpler than a VAT return — largely a summary of taxable gross turnover for the period and the tax due, filed through ZRA's e-services portal (Tax Online). Build the return as a generic inquiry or SSRS report summarising taxable sales by period from the AR tax transaction tables, reconciled against the GL tax payable account balance before filing. That reconciliation step catches manual journal entries or credit memos that bypassed the tax engine.
Wrapping up
The work here is less about Acumatica mechanics and more about getting the tax classification right at the source — reclaimable versus non-reclaimable, which entities are in scope, and where the registration threshold sits. Get that model right once and the reporting falls out of the transactional data cleanly. If you are stuck on something specific, reach out or keep reading through the rest of the Acumatica blog.
Independent software engineer in Nairobi specialising in Acumatica customisations, Laravel backends, and tax fiscalisation integrations across East and Southern Africa.