FBR digital invoicing: the complete guide for Pakistani businesses
What FBR digital invoicing is, who must comply, what an invoice must show, the QR code, sandbox vs production, PRAL tokens and how to fix rejections.
On this page
Reviewed by [PLACEHOLDER: tax practitioner name, credentials]
FBR digital invoicing is the system under which a sales tax registered business sends every sales invoice to the Federal Board of Revenue (FBR) electronically, at the moment it is issued. Your invoicing software submits the invoice to FBR’s Digital Invoicing API, run by PRAL. FBR checks it, returns a unique FBR invoice number, and that number is printed on the invoice together with a QR code that anyone can scan to verify it. [VERIFY: SRO/rule reference]
This guide explains, in plain language, who has to comply, what an FBR digital invoice must contain, how the QR code works, the difference between the sandbox and production, how to get your tokens, and how to fix the rejections that trip most businesses up. It is written for business owners, accountants and billing staff. It is general information, not tax advice: always confirm your own position with a tax practitioner.
What FBR digital invoicing is, and why it exists
For years, a sales tax invoice was something you printed or wrote, kept in a file and summarised in your monthly return. FBR only saw the totals. Digital invoicing changes that: each invoice is reported individually, in a standard electronic format, when it is issued. [VERIFY: SRO/rule reference]
That gives FBR a near-real-time picture of sales and makes it much harder for an invoice to be issued without being declared. For compliant businesses there are benefits too: your buyers can claim input tax against invoices FBR has already seen, disputes about whether an invoice exists become rare, and your monthly return can be prepared from data that is already clean. [VERIFY: SRO/rule reference]
In practice, three things change for a business that comes under the system:
- Invoices are issued from software that is connected to FBR. A bill book, a Word template or an Excel sheet is not enough on its own.
- Each invoice is submitted to FBR when it is issued, not collected and uploaded at month-end.
- Each accepted invoice carries an FBR invoice number and QR code.
Who must comply
FBR brings businesses into digital invoicing in phases, by notification under the Sales Tax Act, 1990 and the Sales Tax Rules. Each phase names categories of sales tax registered persons and a date from which they must integrate. [VERIFY: SRO/rule reference]
Because those categories and dates change, we don’t list them here as fact. Instead, check these points with your tax advisor:
- Are you registered for sales tax? Digital invoicing applies to sales tax registered persons in the notified categories. [VERIFY: SRO/rule reference]
- Which category are you in? For example manufacturer, importer, distributor, wholesaler, retailer or service provider. Different categories have been notified at different times. [VERIFY: SRO/rule reference]
- Are you a Tier-1 retailer? Tier-1 retailers, a category defined in the sales tax law, have their own point-of-sale integration requirements. [VERIFY: SRO/rule reference]
- What is your deadline? Notifications set dates, and FBR has extended some of them in the past. [VERIFY: SRO/rule reference]
If you are not sure, read who must integrate with FBR digital invoicing and confirm with a practitioner before your deadline, not after.
How an invoice reaches FBR
Whatever software you use, the path an invoice takes is broadly the same:
- You create the invoice in your invoicing software: the buyer, the items, quantities and prices.
- The software works out the tax for each line, using each product’s sale type, rate and SRO and the buyer’s registration status.
- The software submits the invoice to FBR’s Digital Invoicing API using a token issued to your business. [VERIFY: SRO/rule reference]
- FBR validates it. If everything is in order, FBR accepts the invoice and returns an FBR invoice number. If not, it returns an error code and message.
- The invoice is printed or shared with the FBR invoice number and QR code on it.
In BillKul this is a single click: Save and submit. Before that, an optional Check with FBR runs a dry run that tests the invoice against FBR’s rules without filing anything. You can read how it works on the FBR digital invoicing feature page.
What an FBR digital invoice must contain
The exact fields depend on your registration, the buyer and the goods or services, and FBR publishes the technical specification for the API. Treat the list below as a typical picture and confirm the details for your category. [VERIFY: SRO/rule reference]
About you (the seller)
Comes from: your business profile
- Business name and address
- NTN and sales tax registration number (STRN)
About the buyer
Comes from: the customer’s tax profile
- Name, and whether they are registered, unregistered or a walk-in customer
- For registered buyers: NTN or CNIC, STRN and province
- Buyer type where it affects tax, for example distributor or retailer
About the invoice
Comes from: the invoice header
- Your invoice number and date
- Invoice type, for example sale, debit note or credit note
- Province of supply and other header fields in the specification
About each line
Comes from: each product’s record
- Description and HS code (the standard code that classifies the goods)
- Quantity and unit of measure as FBR expects it
- Value excluding tax, sales tax rate and amount
- Sale type and any SRO or schedule reference that applies, such as 3rd Schedule goods taxed on the printed retail price
- Further tax, extra tax, Federal Excise Duty or withholding amounts where they apply
After acceptance
Comes from: FBR, once it accepts the invoice
- The FBR invoice number and QR code
Most of this should come from your records, not be typed at the till. If each product stores its HS code, unit, sale type, rate and SRO, and each customer stores their tax profile, the invoice fills itself in correctly. That is the idea behind BillKul’s product FBR checklist and customer tax profiles. For the tax side, see how sales tax, Further Tax and advance tax are calculated.
The FBR invoice number and QR code
When FBR accepts an invoice it returns a unique FBR invoice number. This is separate from your own invoice number, and both appear on the invoice. The QR code printed next to it encodes a link to FBR’s record of that invoice. [VERIFY: SRO/rule reference]
Three practical points:
- No acceptance, no number. An invoice that was never accepted by FBR has no valid FBR number or QR code. If your printout lacks them, the invoice has not been accepted yet.
- Don’t make the QR yourself. It must come from the FBR submission, which is why it should be generated by your software. [VERIFY: SRO/rule reference]
- Buyers can check it. A buyer scans the QR with a phone to confirm the invoice exists at FBR. [PLACEHOLDER: name the official FBR app or page buyers use to verify]
More on this: the FBR invoice QR code explained.
Sandbox vs production
FBR gives each integrated business two environments:
| Sandbox | Production | |
|---|---|---|
| Purpose | Testing and training | Real invoices |
| Tax effect | None | Live: invoices are reported to FBR |
| Token | Sandbox token | Production token |
| When to use | Before go-live, and to test changes | Every real sale after go-live |
Use the sandbox to make sure every product, buyer type and invoice type works before you go live: a standard-rate sale to a registered buyer, a sale to an unregistered buyer, a 3rd Schedule item, a credit note. FBR may also require certain test scenarios to be passed before production access is granted. [VERIFY: SRO/rule reference]
In BillKul, sandbox invoices are free and never count against your plan, and switching is one click: Switch to Production.
Getting your PRAL / IRIS tokens
To submit invoices, your software needs a token issued to your business. The broad steps are: [VERIFY: SRO/rule reference]
- Make sure your registration is in order in IRIS: NTN, STRN, business details and the category you trade in.
- Apply for digital invoicing integration through IRIS, choosing to integrate through a software provider or your own system. [PLACEHOLDER: confirm the current IRIS menu path and form]
- Receive your sandbox token, add it to your invoicing software and complete your testing.
- Receive your production token once testing is done, add it to your software and switch to production.
Keep tokens private. In BillKul, FBR tokens are visible only to the account owner; staff accounts can create invoices but cannot see or change the tokens.
Common rejection reasons and how to fix them
Rejections are normal while you are setting up. FBR returns an error code and message; good software translates that into plain language. In BillKul it appears under What FBR said, with Change to draft & fix to correct and resubmit. These are the usual causes: [VERIFY: SRO/rule reference]
| Problem | Typical cause | How to fix it |
|---|---|---|
| HS code rejected | The code doesn’t exist, is outdated or doesn’t match the goods | Correct the HS code on the product; check with your customs agent or advisor if unsure |
| Unit of measure rejected | The unit isn’t one FBR accepts for that HS code | Set the FBR unit on the product; use package sizes if you sell by carton |
| Rate or SRO mismatch | The rate, schedule or SRO doesn’t fit the sale type | Review the product’s sale type, rate and SRO together |
| Buyer NTN or STRN invalid | Typing error or an unregistered buyer marked as registered | Verify the buyer’s registration and fix their profile |
| Province mismatch | Buyer or supply province wrong | Correct the province on the customer or invoice |
| Missing or invalid field | A required header or line field left blank | Complete the field; check the product and customer set-up |
Two habits prevent most rejections: clear every product’s FBR details before you invoice it, and verify buyer registration when you add a customer. Then run a dry run before filing important invoices.
When FBR doesn’t answer: timeouts and duplicates
Sometimes FBR’s system is slow. If your software sends an invoice and gets no reply, you can’t tell whether FBR received it. Sending it again blindly risks filing the same sale twice. [VERIFY: SRO/rule reference]
The safe approach is to check IRIS for the invoice first. If FBR received it, record the FBR number; if not, submit again. BillKul marks such invoices FBR unconfirmed, asks you to check IRIS before re-filing, and lists them in their own tab until they are settled.
Correcting an invoice: credit and debit notes
Once FBR has accepted an invoice, you should not edit or delete it. If goods are returned or the price was too high, issue a credit note; if you under-charged, issue a debit note. Each must refer to the original invoice and is itself reported to FBR. Time limits and conditions apply. [VERIFY: SRO/rule reference]
From invoices to the monthly sales tax return
Digital invoicing doesn’t replace the monthly sales tax return; it feeds it. Your sales appear in Annex-C and your purchases (input tax) in Annex-A. Because FBR already holds your invoices, any difference between your return and the invoices FBR received will stand out. [VERIFY: SRO/rule reference]
Before filing, make sure every invoice for the month has been accepted, and that input tax is within the limits the rules allow. BillKul’s sales tax return helper shows output tax, input tax and the estimated payable, warns about unfiled invoices and exports Annex-C and Annex-A for IRIS.
A go-live checklist
- Confirm with your tax advisor that you must integrate, and by when.
- Check your NTN, STRN, business details and province in IRIS.
- Apply for integration and get your sandbox token.
- Set up every product with HS code, FBR unit, sale type, rate and SRO.
- Set up customers with their tax profile and verify registrations.
- Test every kind of invoice you issue in the sandbox, including a credit note.
- Train billing staff on what to do when an invoice is rejected or unconfirmed.
- Get your production token and switch to production.
- Check failed, unconfirmed and unfiled invoices every day for the first weeks.
The How it works page shows the same steps in BillKul.
Glossary
- FBR: Federal Board of Revenue, Pakistan’s tax authority.
- PRAL: Pakistan Revenue Automation (Pvt) Ltd, which runs FBR’s IT systems, including the Digital Invoicing API.
- IRIS: FBR’s online portal for registration, returns and other filings.
- NTN: National Tax Number. STRN: Sales Tax Registration Number.
- FBR invoice number: the unique number FBR returns when it accepts an invoice.
- HS code: the Harmonized System code that classifies goods.
- SRO: Statutory Regulatory Order, a notification that sets rates, exemptions or procedures. [VERIFY: SRO/rule reference]
- 3rd Schedule goods: goods on which sales tax is charged on the printed retail price. [VERIFY: SRO/rule reference]
- Further Tax: additional sales tax on supplies to unregistered buyers. [VERIFY: SRO/rule reference]
- ATL: Active Taxpayers List, which decides filer or non-filer status for advance tax.
- Annex-C / Annex-A: the sales and purchase annexures of the monthly sales tax return.
What is FBR digital invoicing?
It is the system under which a sales tax registered business sends each sales invoice to FBR electronically, through the Digital Invoicing API run by PRAL, at the time of sale. FBR checks it, returns an FBR invoice number, and the invoice carries that number and a QR code. [VERIFY: SRO/rule reference]
Who must use FBR digital invoicing?
Categories of sales tax registered persons notified by FBR under the Sales Tax Act, 1990 and the related SROs. The categories and dates change, so confirm your position with your tax advisor or the latest FBR notification. [VERIFY: SRO/rule reference]
Is entering invoices in IRIS the same as digital invoicing?
No. Digital invoicing means your invoicing software submits each invoice to FBR’s API in real time. IRIS is FBR’s portal for returns and registration; you may use it to check a submitted invoice or file your return, but not as a substitute for real-time submission. [VERIFY: SRO/rule reference]
Where do I get my FBR digital invoicing token?
Tokens for the sandbox and production environments are issued to your business through PRAL/IRIS after you apply for digital invoicing integration. The exact menu path changes from time to time; your tax advisor or software provider can guide you. [VERIFY: SRO/rule reference]
What is the difference between sandbox and production?
The sandbox is FBR’s test environment: invoices sent there are practice and have no tax effect. Production is the live system for real invoices. You test in the sandbox first, then switch to production. [VERIFY: SRO/rule reference]
Why was my invoice rejected by FBR?
The most common reasons are a wrong HS code or unit of measure, a tax rate or SRO that doesn’t fit the product’s sale type, and wrong buyer details such as NTN, registration status or province. Fix the detail and submit again. [VERIFY: SRO/rule reference]
Can I edit an invoice after FBR accepts it?
No. An accepted invoice should not be changed. Corrections are made with a credit note or debit note that refers to the original invoice, within the conditions the rules allow. [VERIFY: SRO/rule reference]
What does the QR code on an FBR invoice do?
It links to FBR’s record of the invoice, so a buyer or officer can scan it with a phone and confirm the invoice was reported. [VERIFY: SRO/rule reference]
BillKul is a software provider. This content is for general information and is not tax or legal advice. Please consult your tax advisor.
