FBR Digital Invoicing in Pakistan: Who Must Comply and How to Get Started

Every sales tax registered business in Pakistan is now expected to send its invoices to FBR electronically, in real time. This guide explains what that means, who it applies to, and the practical steps to go live without disrupting your billing.

What is FBR Digital Invoicing?

Under FBR's Digital Invoicing (also called e-invoicing) system, each sales tax invoice is sent electronically to FBR at the moment it is issued, through the Digital Invoicing API run by PRAL (Pakistan Revenue Automation Limited). FBR checks the invoice and returns a unique FBR invoice number, which is printed on the invoice together with a QR code. Your buyer, and FBR, can then match the invoice with what you declare in your sales tax return.

In short: the invoice you post in your accounting or ERP system must be the same invoice FBR receives — no re-typing into a portal at the end of the month.

Who has to comply?

FBR is rolling the requirement out to sales tax registered persons in phases. Under SRO 1852(I)/2025, the schedule was:

Before each start date, businesses had to register and finish integration testing. FBR announced that penalties for businesses that missed their deadline would start from January 2026.

Your two options

1. Use PRAL's own solution — suitable for very small businesses with a handful of invoices, but it sits outside your accounts, so stock, customer ledgers and tax accounts still need separate entry.
2. Connect your ERP or billing software to the Digital Invoicing API — invoices are submitted straight from the system where you already create them, and every accepted invoice also updates stock, the customer's ledger and your sales tax payable automatically.

Getting started: a 6-step checklist

1. Register for Digital Invoicing with FBR/PRAL and get your sandbox security token.
2. Clean your customer master. For registered buyers you need a valid NTN; for unregistered buyers, a CNIC where required. Record each buyer's province.
3. Clean your item master. Every item needs the correct HS code, unit of measure and sales tax rate (and the SRO / schedule reference where a reduced or exempt rate applies).
4. Run the sandbox scenarios. PRAL provides test scenarios for the types of sale your business makes. Pass all the scenarios that apply to you.
5. Switch to production once FBR approves your testing, using your production token.
6. Train your billing staff on what to do when an invoice is rejected (see below), so that billing never stops.

The most common reasons invoices are rejected

• Buyer NTN or CNIC missing or in the wrong format
• HS code that does not match the item or the tax rate charged
• Unit of measure not in FBR's accepted list for that HS code
• Tax amount that does not equal value × rate (usually a rounding difference)
• Wrong sale type, e.g. a reduced-rate item sent as a standard-rate sale
• Re-sending an invoice that FBR has already accepted

Almost all of these come from master data, not from the invoice itself. An hour spent cleaning customers and items before go-live saves days of rejected invoices afterwards.

How BarkahSuite handles it

In BarkahSuite, each company enters its own PRAL token, NTN and business details once in Company Settings. From then on, sales invoices in Sales & Distribution and receipts in POS are submitted to FBR from the same screen your team already uses. The FBR invoice number and QR code are printed on the document, and the FBR status is saved with it, so a rejected invoice can be corrected and sent again. You can test everything in sandbox mode before going live. See how FBR integration works in BarkahSuite →

Related

← All blog posts