FBR Digital Invoicing, explained for distributors
What FBR’s Digital Invoicing system is, who has to integrate, how integration works end to end, and what you need before you start — in plain language, without the document jargon.
What FBR Digital Invoicing is
Digital Invoicing is FBR’s system for reporting sales-tax invoices electronically, at the moment they are issued, through PRAL’s Digital Invoicing API. Instead of printing an invoice and reporting totals later, each invoice is transmitted to FBR as it is created.
FBR validates the invoice, assigns it a reference number, and returns a QR code. That code is printed on the customer’s copy, linking the paper document back to the electronic record FBR now holds. An invoice that fails validation is rejected with a numeric error code against the field or line at fault — those are catalogued in the error-code reference.
Who must integrate
FBR has been bringing businesses onto Digital Invoicing in phases, widening the net over time by turnover and by category of taxpayer. Larger and corporate taxpayers were drawn in first, with thresholds broadening as the programme matures.
Because the phasing and thresholds change, the practical posture for a distributor is simple: if you are sales-tax registered, assume you are either in scope now or will be soon, and treat integration as something to prepare for rather than react to. Confirm your own current obligation and timeline against FBR’s latest notifications or with your tax adviser, since those specifics move.
How integration works, end to end
From registration to your first live invoice, integration moves through six stages:
- 1
IRIS registration
Register on FBR's IRIS portal and enrol for Digital Invoicing under the sales-tax profile of the entity that will issue invoices.
- 2
Licensed integrator
Connect through a PRAL-licensed integration — either building directly against the API or using software that is already an approved integrator.
- 3
IP whitelisting
Register the static IP address your production traffic originates from. FBR only accepts production submissions from a whitelisted address.
- 4
Sandbox scenario testing
Pass the sandbox test scenarios that apply to your registered business nature and sector. These prove your payloads are correct before any live data is involved.
- 5
Production token
Once your scenarios pass, obtain a production access token bound to your registration number. The token authorises submissions for that number only.
- 6
Live submission
Submit real invoices in real time. Each accepted invoice returns an FBR reference and a QR code that ties the printed document to the electronic record.
What you need before you start
Sales-tax registration
An active sales-tax registration (STRN / NTN) in the name of the entity that will issue the invoices.
A static IP address
A static IP for production submission, because FBR whitelists the address your calls come from. Shared or rotating IPs will not work.
HS codes for your catalogue
Correct HS codes and tax classifications for the items you sell. Most rejections trace back to classification, so getting this right up front saves the most time.
Resources
Deeper references for building and debugging your integration.
Error codes
Every FBR rejection code — what it means and how to fix it.
Open referenceScenarios
The sandbox test scenarios that gate your production token, explained one by one.
Browse scenariosScenario finder
Get the exact scenario checklist for your business activity and sector.
Open finderTools
Coming soonValidators and helpers for building correct payloads.
Let Ordyoo handle FBR submission
Start free and issue FBR-compliant invoices without wiring up the API yourself.
