Compliance
FBR digital invoicing, explained.
What the law asks of you, what software can genuinely do about it, and what happens on the day FBR's systems are unavailable. Written for a business owner rather than for an auditor.
This page explains how our software works. It is not tax advice, and your specific obligations depend on your registration and your sector — check those with your tax adviser.
What digital invoicing requires
- 01
Invoices must be transmitted to FBR
A registered person within scope has to send sales-tax invoice data to FBR electronically, rather than only keeping it in their own books. The invoice becomes valid once FBR has received and accepted it.
- 02
Each invoice comes back with a reference and a QR code
FBR returns an invoice reference number (the IRN) and a QR code. Both have to appear on the invoice document you issue to the buyer, so the buyer can verify it against FBR independently.
- 03
The data has to be right the first time
Buyer NTN, HS codes, tax rates and any SRO exemption you are claiming all have to be correct and internally consistent. An invoice with the wrong HS code is not a formatting problem — it is a wrong filing.
- 04
Records have to be retained
You keep the invoice, and the evidence of what was sent and accepted, for the retention period Pakistani tax law sets. A screenshot is not a record.
What Quick Safa does about it
It posts. That is the short version, and the reason to say it plainly is that plenty of software claims FBR “support” and means an invoice template with the right boxes on it.
- Validate before anything is sent
- The invoice is checked against FBR’s rules while it is still yours to fix. Errors show on your screen, not in a rejection you find out about at filing time.
- Post, and record what comes back
- The invoice is transmitted and the IRN and QR that FBR returns are stored against it and printed on the document, on your own template.
- Keep the whole exchange
- What was sent and what came back is retained against the invoice, rejections included. If FBR ever queries a document, you have the exchange rather than a status icon.
- Lock what has been accepted
- Once FBR has accepted an invoice, Quick Safa stops you editing it. An invoice in your books that no longer matches what FBR holds is worse than no invoice at all.
- Maintain the reference data
- HS codes, SRO chain and NTN lookup are maintained inside the product, so the values on an invoice come from a maintained list rather than from memory.
When FBR is down.
It happens. A national tax API has outages, and a plant cannot stop dispatching because of one.
You keep working
Raising and saving an invoice in Quick Safa does not depend on FBR being reachable. Posting is a separate step from creating.
The invoice stays honestly unposted
It sits in an unposted state with the error recorded against it. Nothing is marked as accepted unless FBR actually accepted it — a false green tick is the one outcome that would genuinely put you at risk.
You post when it returns
Unposted invoices are listed together so you can see exactly what is outstanding and clear the queue once the service is back. Nothing is silently dropped.
Getting compliant
The FBR Integration Portal does digital invoicing on its own from Rs 20,000/year. If you make corrugated boxes, it is included in the Manufacturer Suite at no extra cost and you should not buy it separately.