FBR Digital Invoicing · Guide

Pakistan E-Invoicing Mandate (2026): Scope, Deadlines, Format and Penalties Explained

Pakistan runs a real-time clearance e-invoicing model under Rule 150Q of the Sales Tax Rules. A one-page compliance overview: who is in scope, the SRO timeline, the JSON invoice format with IRN and QR, and the 2026 penalty regime.


A clearance model, not post-audit reporting

Pakistan's mandate is a continuous transaction control (CTC) clearance system: a sales tax registered person must transmit each invoice electronically to the Federal Board of Revenue's computerised system in real time, before issuing it to the buyer. FBR validates the invoice and returns a unique Invoice Reference Number (IRN) and QR data within seconds; only then does a legally valid tax invoice exist. Both B2B and B2C sales by registered sellers are covered, and any buyer can verify an invoice by scanning its QR code, using the Tax Asaan app, or texting the invoice number to short-code 9966.

The legal basis is Rule 150Q and Chapter XIV of the Sales Tax Rules 2006. The platform is operated by PRAL (Pakistan Revenue Automation Ltd), FBR's IT arm, and businesses connect either through PRAL directly — free of charge, including sandbox testing — or through private licensed integrators whose fees are reported as capped around Rs 10 per invoice or fixed retainers. Since STGO No. 01 of 2026 a registered person may engage more than one integrator at the same time.

Who must comply, and by when

The rollout came in waves of SROs. SRO 709(I)/2025 (April 2025) mandated integration for the first corporate and non-corporate groups — importers, manufacturers and FMCG wholesalers/distributors leading. SRO 1413(I)/2025 (August 2025) introduced a turnover-based phase calendar, and SRO 1852(I)/2025 (24 September 2025) — the current governing notification — superseded both and brought every sales tax registered person into scope on a phased schedule, with the final group required to be live by 31 December 2025.

In 2026 the widely reported consolidation dates are 1 June for corporate and 1 July for non-corporate registered persons, and enforcement is visibly active: from July 2026 non-integrated importers face penalty proceedings, suspension of sales tax registration and removal from the customs green channel. Services remain the moving edge — draft SRO 288(I)/2026 proposes extending online integration to named service and retail sectors, but it takes effect only on final notification and the provincial revenue authorities have formally objected, so service businesses should confirm their position with both FBR and their province.

Invoice format and technical requirements

Technically, an e-invoice is a single JSON document posted to FBR's Digital Invoicing API (v1.12): a header carrying invoice type, date, seller and buyer NTN/CNIC, provinces, addresses and buyer registration type, plus an items array with HS code, rate, unit of measure, quantity, value excluding sales tax and the tax fields. Before production, the business must pass sandbox test scenarios (SN001–SN028) matching its sector; sandbox and production tokens are each valid five years. The printed invoice must show the FBR invoice number, a Version 2.0 (25×25) QR code at 1.0 × 1.0 inch, and the official Digital Invoicing logo — the QR encodes the invoice number so anyone can verify it.

Corrections are tightly controlled: an issued e-invoice can be amended or cancelled through the system only within 72 hours (STGO 01/2026); after that, changes need Commissioner Inland Revenue approval, and later adjustments run through debit notes within 180 days of the original invoice. There is no auto-retry — if a transmission fails mid-post, the seller must resubmit, which is why save-then-post software workflows matter in practice.

Penalties and enforcement in 2026

Non-compliance is enforced from both directions. Under Section 33 of the Sales Tax Act 1990, issuing invoices outside the system carries a reported per-invoice penalty of Rs 50,000 or 2% of the tax involved (whichever is higher), with default penalties escalating from Rs 500,000 up to Rs 3,000,000 for repeat default. The Finance Act 2026 added a penalty of up to Rs 1,000,000 for failing to complete digital integration on time (up to Rs 5,000,000 more for repeat violations), powers to suspend registration or blacklist non-integrated businesses, a penalty equal to the full value of a fake invoice, and a public register of simulated invoice issuers.

The commercial enforcement is quieter but sharper: an invoice without a valid IRN is ineligible for input tax adjustment, so registered buyers increasingly refuse non-integrated suppliers. For most businesses the practical decision is not whether to comply but how — building the API directly takes weeks to months, while a ready PRAL-certified platform such as Digi Invoice reaches a first compliant, QR-stamped invoice the same day.

Frequently asked questions

Is Pakistan's e-invoicing a clearance or post-audit model?

Clearance. The invoice is transmitted to FBR's system in real time and validated before issuance — FBR returns the Invoice Reference Number (IRN) and QR data within seconds, and only an invoice carrying that IRN is a valid tax invoice eligible for input tax adjustment.

Does the mandate cover B2C sales?

Yes. A registered seller posts consumer sales with buyer registration type 'Unregistered'. Sales to unregistered buyers commonly attract further tax on top of standard sales tax, which the invoice must calculate correctly to pass validation.

Can a business comply without building the API itself?

Yes — that is how most SMEs comply. The choices are a direct API build (weeks to months of development plus sandbox scenario testing), or a ready licensed platform. Digi Invoice is PRAL-certified and handles tokens, validation, posting, QR printing and records, typically reaching the first compliant invoice the same day.

Start issuing FBR-compliant invoices today

Digi Invoice validates, posts and QR-stamps your sales tax invoices through FBR's Digital Invoicing API — no development required.