BOTSWANA VAT AND E-INVOICING SETUP IN ODOO FOR 2026

A finance manager in Gaborone closes the VAT period and finds that exempt sales have been posted at 0%, credit notes carry the same numbering logic as invoices, and the tax report does not match the figures needed for VAT 002.1. The entries may be posted, but the audit trail is not yet ready for BURS.

For an Odoo partner Botswana implementation, Botswana VAT and e-invoicing setup starts with tax classification and document control. It does not start by sending invoice PDFs to a customer or assuming that Odoo already connects to BURS. As of 13 October 2026, the electronic fiscal-device framework exists in law, but its commencement and technical rollout details still require BURS confirmation.

We recommend treating the project as two connected workstreams: configure current BURS VAT reporting correctly, then prepare a controlled integration plan for electronic fiscal devices when the applicable notice, specifications and onboarding process are issued.

The Botswana position in 2026

Botswana companies need to separate what is already operational from what is planned.

| Requirement area | Position as of 13 October 2026 | Odoo action | | VAT registration | BURS states that registration is compulsory when annual taxable supplies exceed P500,000. This threshold conflicts with older BURS material, so it requires confirmation with BURS before using it in automated alerts. | Store the BURS VAT number on the company record and set a management alert before the verified registration threshold is reached. | | Standard VAT | The Finance Minister stated on 7 April 2026 that the standard VAT rate remains 14%. A BURS web page still shows 12%, which should not be used as the configuration source. | Create and test a separate 14% sales tax and purchase tax. | | VAT filing | VAT 002.1 and payment are due within 25 days after the end of the tax period. | Set the tax periodicity and close process around the applicable BURS deadline. | | Filing frequency | BURS describes taxpayers below P12 million turnover in Categories A and B as filing every two months. Category C taxpayers at P12 million or above file monthly. | Set the Odoo tax return period to the confirmed BURS category, then review it when turnover changes. | | Electronic fiscal devices | The 2025 VAT amendment provides for devices, including virtual devices, that record or transmit sales data and issue invoices or receipts. Commencement is by ministerial notice. | Do not activate an assumed BURS connector. Scope the device, interface, data fields and testing process after BURS publishes the operational requirements. |   The distinction matters. An emailed PDF invoice is not proof of electronic fiscal-device compliance. The law refers to a fiscal-device regime, and the technical interface specifications, onboarding dates and exemptions still need to be confirmed by BURS.

Government stated in February 2026 that the Electronic VAT Invoicing Solution rollout was scheduled for the last quarter of financial year 2026/2027. That is a planning signal, not a basis for claiming that every Botswana business must already transmit every Odoo invoice to BURS in real time.

Step 1: Set up the Botswana company record and accounting base

Before tax rates are loaded, establish the records that make every later transaction traceable.

1.       Set the company currency to Botswana pula. This gives sales, purchases and tax reports a consistent accounting basis. If the business trades in other currencies, configure those separately rather than changing the company currency to suit an individual invoice.

2.       Add the BURS VAT registration number once it has been issued. The number should appear where the approved tax invoice template requires it. A VAT number held only in a spreadsheet will not carry through to customer-facing documents or the finance audit trail.

3.       Confirm the chart of accounts before posting live entries. Odoo localisation setup requires the chart of accounts, taxes, fiscal positions, tax periodicity, tax rounding, invoice sequences, products and contacts to be verified before entries are posted. Reworking these after live posting creates avoidable correction journals.

4.       Use controlled invoice sequences. Sales invoices, credit notes and debit notes need distinct compliant templates and controlled sequences. The reason is practical: BURS audit work depends on being able to follow a document from the source transaction through the ledger and VAT return.

5.       Keep source documents with the transaction. BURS requires retention of VAT source documents and audit trails. Attach the supplier bill, customs or supporting record where applicable, and retain approval evidence for adjustments. A tax total without its source record is difficult to defend.

The VAT Act requires tax invoices to contain the Fourth Schedule particulars. We configure the tax invoice, credit note and debit note as separate documents because they serve different legal and accounting purposes. A credit note should reverse or adjust an earlier supply in a traceable way. It should not be an invoice with a negative value and an unrelated sequence.

Worked example: a distributor with misclassified non-standard sales

Take an illustrative Gaborone distributor, Sable Traders, whose annual taxable supplies have moved above P500,000. The finance team used one 0% tax for every sale that was not charged at the standard rate. Its VAT report therefore grouped qualifying zero-rated supplies with exempt supplies.

We would separate those taxes before the next return, map them to the right products and use fiscal positions only where the tax treatment changes by customer or transaction. The immediate cost of leaving the process weak is not just correction effort. The 2025 amendment provides for penalties of P10,000 per month for failing to use an applicable fiscal device once the regime is in force.

What Sable Traders would do differently is test tax treatment before invoice volume builds up. The common skipped step is to test a standard-rated sale, a zero-rated sale, an exempt sale, a purchase and a credit note together, then inspect the resulting tax report line by line.

Step 2: Build the VAT logic, not just a VAT rate

A 14% tax rate is only one part of Botswana VAT configuration. The more important control is whether Odoo can distinguish the underlying treatment.

Configure separate taxes for each treatment

Use separate sales and purchase taxes, then map them to products and services:

| Tax treatment | Odoo configuration approach | Why it matters | | Standard-rated supply | Separate 14% sales and purchase taxes. | The standard rate reported in official 2026 budget proceedings is 14%, despite conflicting web content. | | Qualifying zero-rated supply | A dedicated 0% tax for qualifying zero-rated supplies. | A zero rate is a VAT treatment, not a catch-all for every sale without VAT. | | Exempt supply | A separate exempt tax treatment and accounts where required. | Exempt supplies must not be reported as zero-rated simply because the invoice tax is nil. | | Reverse-charge or out-of-scope transaction | Separate configuration after confirming the treatment for the transaction. | These categories affect reporting differently and should not be absorbed into an exempt or zero-rated code. |   Use fiscal positions to apply the right mapping when customer status or transaction circumstances warrant a different treatment. Do not use fiscal positions as a substitute for a properly designed product tax matrix.

The mistake we see most often in tax-localisation reviews is a single 0% rate labelled “VAT exempt”. That label can conceal different tax treatments and makes the VAT return reconciliation unreliable. The control is simple: every product category should have an owner, a documented tax basis and a tested Odoo tax assignment.

Decide registration monitoring carefully

BURS identifies Form BURS 1 for VAT registration. Its current VAT FAQ says compulsory registration starts above P500,000 annual taxable supplies, while older BURS material cites P250,000 and another BURS page cites P1 million.

For that reason, we would not configure an automatic “must register” trigger solely from historical web content. Configure a management notification as turnover approaches the threshold, then have the tax owner confirm the current position with BURS. This is a judgement call: if annual taxable supplies are well below the confirmed threshold, do not build a complex registration-alert workflow. A periodic management review is enough. Once turnover is close to the threshold, formalise the control because delayed registration can affect invoicing and reporting from that point.

Step 3: Reconcile Odoo Tax Report to VAT 002.1

Odoo’s Tax Report aggregates tax data from invoices and bills. It is useful, but it is not a filed BURS VAT return by itself. The output must be reconciled to VAT 002.1 before submission.

Use this monthly or bi-monthly close sequence:

6.       Lock the transaction cut-off. Confirm that all sales invoices, supplier bills, credit notes and debit notes for the tax period are posted. An unposted supplier bill can make recoverable input VAT appear lower than the underlying records support.

7.       Review tax report totals by treatment. Compare standard-rated, zero-rated, exempt and other relevant lines against the transaction listing. This is where a product mapped to the wrong 0% tax is normally found.

8.       Match material movements to source documents. Check that each adjustment has a credit note, debit note or supporting evidence attached. This creates an auditable trail rather than a tax report that only reconciles in aggregate.

9.       Reconcile the Tax Report to VAT 002.1. Map each Odoo total to the corresponding return field, investigate differences and retain the reconciliation with the period records. Odoo’s output is an operational report. VAT 002.1 is the BURS filing instrument.

10.   Submit and pay within 25 days after the tax period ends. The timing applies whether the taxpayer files every two months below P12 million turnover or monthly at P12 million and above, subject to BURS category confirmation.

Worked example: a multi-entity group reaching the filing-frequency boundary

Consider an illustrative Botswana group with two operating entities. One entity approaches P12 million turnover while the other remains below it. The group finance team wants one reporting timetable because the businesses share an accounting team.

That approach can create a control failure if the entities have different BURS filing categories. We would configure tax periodicity per legal entity, keep separate VAT numbers and reconcile each entity’s Tax Report to its own VAT 002.1 working paper. The P12 million category boundary matters because BURS describes Category C taxpayers at that level or above as monthly filers.

The team would also avoid rolling all entities into one invoice sequence. Multi-entity visibility is useful at group level, but the legal entity, VAT registration and document trail must remain distinct for compliance purposes.

Step 4: Prepare for fiscal-device integration without overcommitting

The Value Added Tax (Amendment) Act, 2025 created a framework for electronic fiscal devices. It says a device can include a virtual device and must record or transmit sales data and issue invoices or receipts. The amendment also provides for a penalty of up to P10,000 for failure to issue a fiscal receipt, and up to P100,000 or two years’ imprisonment for misleading, false or tampered device use.

These figures justify board-level attention. They do not justify selecting an integration vendor before BURS has confirmed the applicable technical standard.

Prepare the Odoo implementation in four practical ways:

●        Preserve unique invoice, credit note and debit note identifiers. Any future fiscal-device workflow will need to relate a fiscal receipt to the originating Odoo document.

●        Keep product, customer and tax master data controlled. Inconsistent item descriptions and tax classifications create bad source data before any device sends a transaction.

●        Design an exception process for offline trading, failed transmission, cancellations and returns. The future BURS specifications may prescribe the exact handling, so document the operational need now rather than inventing a compliance claim.

●        Scope integration as a separate work package. Odoo supports tax configuration, fiscal positions and localisation controls. It should not be represented as having a ready-made Botswana BURS connector unless the interface requirements and certified solution have been confirmed.

A good ERP implementation records who approved tax changes, who released a document template, and how exceptions were resolved. That visibility is more valuable than a dashboard that simply shows invoice counts.

Configuration checklist for the implementation team

Before go-live, the finance lead, IT lead and implementation partner should sign off the following:

●        Botswana pula is set as the company currency.

●        The BURS VAT registration number is recorded where applicable.

●        The chart of accounts and tax accounts have been reviewed.

●        The standard 14% rate has been verified against current BURS guidance before deployment.

●        Zero-rated and exempt supplies use separate tax treatments.

●        Product tax mapping has been tested using realistic sales and purchase scenarios.

●        Fiscal positions have a documented business purpose.

●        Tax rounding and tax periodicity match the confirmed filing position.

●        Invoice, credit note and debit note sequences are distinct and controlled.

●        Tax invoice templates contain the required Fourth Schedule particulars.

●        VAT source documents and approvals are retained with the transaction.

●        Odoo Tax Report totals reconcile to a VAT 002.1 working paper.

●        The fiscal-device integration plan is marked pending BURS commencement, technical specifications and onboarding guidance.

Frequently Asked Questions

What VAT rate should we configure in Odoo for Botswana?

Configure a separate 14% standard VAT rate, subject to confirmation at go-live. The Finance Minister stated on 7 April 2026 that the rate remains 14%, while an outdated BURS web page still displays 12%. The conflict is exactly why the implementation sign-off should cite the current official position.

Is every Botswana company required to send Odoo invoices to BURS in real time?

No such universal requirement should be assumed as of 13 October 2026. The 2025 amendment establishes an electronic fiscal-device framework, but commencement is by notice and government described the Electronic VAT Invoicing Solution rollout as scheduled for the last quarter of financial year 2026/2027.

Can exempt sales be configured as 0% VAT?

No. Qualifying zero-rated supplies and exempt supplies require separate treatment. A 0% tax may be appropriate for a qualifying zero-rated supply, but it should not be used to conceal an exempt, reverse-charge or out-of-scope transaction.

How often must a Botswana business file VAT?

BURS describes Categories A and B, for taxpayers below P12 million turnover, as filing every two months. Category C taxpayers at P12 million or above file monthly. VAT 002.1 and payment are due within 25 days after the tax period ends.

Our configuration approach follows BURS VAT guidance, the Value Added Tax Act and Odoo 19.0 official accounting setup documentation. Before production deployment, confirm the current registration threshold, VAT rate presentation and fiscal-device rollout requirements directly with BURS.

Request a Consultation with our Odoo partner Botswana team to review your VAT configuration, VAT 002.1 reconciliation controls and fiscal-device readiness.