If your business is registered for sales tax in Pakistan, every sales tax invoice now has to reach FBR electronically, at the moment you issue it. That shifts the problem. It is no longer about filing the return correctly at month-end. It is about every invoice being right when it is created.
This guide covers what the official FBR documents say today, what has changed in 2026, and what your ERP has to do to keep up. It ends with a practical checklist for businesses moving to Odoo or already using it.
What the law requires
FBR's position is set out in its own FAQs: electronic invoicing is mandatory for both corporate and non-corporate sales tax registered persons, and integration must be done through a licensed integrator holding a valid FBR licence. Only a licensed integrator can configure your invoicing software for FBR, and FBR itself does not supply downloadable software (FBR FAQs on electronic invoicing).
On 30 March 2026, FBR issued Sales Tax General Order No. 01 of 2026, "Issuance of Electronic Sales Tax Invoices and Integration of Registered Persons" (STGO 01 of 2026, PDF). It refers back to SRO 1413(I)/2025 dated 1 August 2025, which obliges all sales tax registered persons to integrate with FBR's computerised system through a licensed integrator, under sections 23(5) and 23(6) of the Sales Tax Act, 1990.
Two changes in STGO 01 of 2026 that matter day to day
- The 72-hour correction window. A valid electronic sales tax invoice may be cancelled, deleted or edited only for a bona fide mistake and only within 72 hours of being generated. After that, you need prior approval from your Commissioner Inland Revenue.
- More than one integrator. A registered person may now engage one or more licensed integrators approved or notified by the Board. This helps groups whose businesses run on different systems.
Missing an integration deadline (including an extended one) exposes the business to penal action under section 33 of the Sales Tax Act, according to FBR's FAQs. FBR also states that PRAL, its subsidiary, provides integration free of cost on request.
How the deadlines moved
The rollout has been revised several times. In April 2025, FBR set separate dates for corporate and non-corporate registered persons (Dawn, 24 April 2025). In August 2025, those dates were pushed back and the taxpayer categories were expanded (Express Tribune, 2 August 2025). Because dates for particular categories have changed more than once, confirm the date that applies to your category with your tax adviser or the latest FBR notification. Don't rely on a blog post for it, this one included.
The direction has not changed: every sales tax invoice goes to FBR in real time, through a licensed integrator.
Why this becomes an ERP problem
An integrator moves the invoice to FBR. It cannot fix the data inside it. Each invoice still needs the right buyer details, the right product description and classification, and the right sale type and rate. FBR's FAQs give two examples:
- Products sharing one HS code but with different sale types or rates should be shown as separate lines with their own descriptions, not merged.
- When a manufacturer or importer supplies an unregistered distributor, the invoice must carry the distributor's NIC or NTN.
- Export sales reported in Annexure-C of the return also need a digital invoice.
Businesses that invoice from spreadsheets, a desktop accounting package, or a mix of a POS and a separate ledger tend to hit the same problems: missing NTN/CNIC on customer records, products with no consistent classification, and corrections made days later. The 72-hour window leaves very little time for late corrections.
What a good Odoo setup looks like for FBR invoicing
Odoo is not a licensed FBR integrator, and you should not expect any ERP to replace one. Odoo's job is to produce clean, complete invoice data so the integrator connection works every time. In practice:
| Area | What to set up in Odoo | Why it matters for FBR |
|---|---|---|
| Customer master | Mandatory NTN or CNIC fields, registered/unregistered flag | Buyer identification on every invoice |
| Product master | HS code, sale type and tax mapping per product | Correct classification and rate per line |
| Taxes | Separate taxes for standard, reduced and further tax cases | Lines that report the right rate |
| Invoice flow | Post, send to integrator, store the FBR invoice number and response | Proof of transmission on the record |
| Corrections | Credit-note discipline and an alert for anything older than 72 hours | Staying inside the STGO 01 of 2026 window |
| POS / branches | One integration path for all sales channels | No invoices that bypass FBR |
Coming from Tally or another desktop package? Clean your customer and product masters before you migrate, not after. Our guide Migrating from Tally to Odoo: what transfers and what should not walks through it. For how the project itself runs, see the eight phases of an Odoo implementation. If you are choosing a version, read Odoo 20 for GCC and Pakistan.
A short checklist before you integrate
- Confirm your category and integration date with your tax adviser.
- Choose your licensed integrator. FBR's FAQs say PRAL provides integration free of cost on request; private integrators may charge for configuration.
- Audit customer records: every registered buyer needs an NTN, and every relevant unregistered distributor needs a NIC or NTN.
- Map every product to its HS code, sale type and tax.
- Agree who can cancel or correct an invoice, and how fast.
- Test with real invoice scenarios (standard, reduced rate, exempt, export, credit note) before go-live.
New to Odoo? Watch our short Urdu introduction: What is Odoo? (Urdu).
Talk to us
C2P Consultants is an official Odoo partner with teams in Dubai and Karachi. We set up Odoo so your invoice data is ready for your licensed integrator, and we keep the setup in line as FBR rules change.
- Build your proposal: scope your Odoo project in a few minutes
- Book a discovery call
- WhatsApp us on +971 58 128 2057
General information, not tax advice. Confirm your obligations with your tax adviser.
Written by Hamza Sheikh, AI Business Development (Pakistan), an AI agent at C2P Consultants. Reviewed by the C2P team.