Getting integrated with FBR is only half the job. The other half is keeping every invoice flowing to FBR without rejections.
When an invoice fails, the effect is immediate. Billing stops, customers wait at the counter, and invoices that never reach FBR become a compliance risk. The good news is that most FBR integration errors come from a small set of causes, and almost all of them can be fixed permanently once you know where they come from.
This guide covers the most common FBR digital invoicing and POS integration errors, what causes each one, and how to fix it.
How FBR Errors Work
When your POS or ERP sends an invoice, FBR's system (through PRAL's API) validates it and returns a response. A valid invoice gets an FBR invoice number and QR code. An invalid one gets an error code and message explaining what failed.
Most errors fall into five groups:
Connection and authentication: your system can't reach FBR or isn't recognised
Customer or business data: wrong NTN, CNIC, registration type or province
Product data: wrong HS code, unit of measure or sale type
Tax calculation: your tax amounts don't match what FBR expects
Operational: offline invoices, disconnected branches, outdated software
Identify the group first, and the fix usually becomes obvious.
1. Authentication Failed / Unauthorized (401)
What you see: "Unauthorized", "Access denied" or "Invalid token".
Common causes:
The API token was entered incorrectly or has been changed on IRIS
A sandbox token is being used in production (or the other way round)
The token belongs to a different NTN than the one on the invoice
How to fix:
Log in to IRIS and confirm the token for the correct NTN and environment
Keep separate settings for sandbox and production, and label them clearly
Store the token securely in your software rather than in spreadsheets or chats
2. Requests Rejected in Production (IP Not Whitelisted)
What you see: everything worked in sandbox, but production calls fail or time out.
Cause: FBR whitelists your server's IP address before issuing the production token. If you move to a new server, change hosting provider or your IP changes, requests from the new IP are blocked.
How to fix:
Use a static IP for the server that sends invoices
Update the whitelisted IP through IRIS or your licensed integrator before changing servers
With cloud hosting, confirm your provider gives you a fixed outbound IP
3. Error 0052: HS Code Does Not Match Sale Type
This is one of the most frequently reported FBR digital invoicing errors.
What you see: "HS Code does not match with provided sale type."
Cause: the product's HS code isn't valid for the sale type on the invoice. For example, you've marked an item as reduced-rate or Third Schedule goods, but its HS code isn't listed under that category in FBR's reference data.
How to fix:
Check the HS code against FBR's reference API for the sale type you're using
Correct the sale type if the item was classified wrongly
Fix it in the item master, not on the individual invoice, so every future invoice is correct automatically
4. Invalid Buyer NTN, CNIC or Registration Details
What you see: errors about the buyer's registration number, registration type or province.
Common causes:
NTN or CNIC typed with extra characters, spaces or missing digits
A buyer marked as "registered" when they're unregistered, or the reverse
A wrong or missing province for the buyer or seller
How to fix:
Clean up your customer master: correct NTN/CNIC formats and registration status
Make these fields mandatory when creating new customers
Recheck a customer's status if their registration has changed
5. Tax Calculation Mismatch
What you see: errors saying the sales tax, extra tax, further tax or total value doesn't match the expected calculation.
Common causes:
Rounding differences: your software rounds per line while FBR expects a different method, or the reverse
The wrong tax rate on an item (for example, standard rate applied to a reduced-rate item)
Extra tax or further tax added where it doesn't apply
Discounts applied in a way that changes the tax base incorrectly.
How to fix:
Set tax rates in the item and tax templates, not manually on invoices
Align your rounding method with FBR's technical documentation
Test each tax type (standard, reduced rate, Third Schedule, exempt) separately in sandbox
6. Unit of Measure (UOM) Mismatch
What you see: line-level errors about the unit of measure or quantity.
Cause: the unit in your system (for example "Pcs", "Box", "Carton") doesn't match the unit FBR expects for that HS code, or quantities are rounded differently.
How to fix: map your internal units to FBR's accepted UOM codes once, in your item setup, so every invoice sends the correct unit.
7. Invalid Format / Missing Mandatory Fields
What you see: schema validation or "invalid data" errors.
Common causes: missing required fields, wrong date format, empty values or text where numbers are expected.
How to fix:
Make FBR-required fields mandatory in your software
Validate invoice data before sending it
If you're using custom-built software, compare your payload against FBR's latest technical documentation
8. Sandbox Scenarios Failing
Before going live, FBR requires your system to pass testing for the scenarios that apply to your business (standard-rate sales, reduced rate, Third Schedule and so on).
Common causes of failure: the errors above (HS code, tax calculation, UOM) showing up in specific scenarios, or testing scenarios that don't match your business type.
How to fix: clear one scenario at a time, fix the root cause in your master data, and retest. Don't hard-code values just to pass a scenario. Whatever you hard-code will fail on real invoices later.
9. Invoices Stuck Offline or Not Syncing
What you see: invoices issued during an internet outage or FBR downtime never receive an FBR number, or sit in a "pending" state.
How to fix:
Use software that queues failed invoices and retries automatically
Check the pending queue every day, not at month-end
Keep a backup internet connection at busy outlets
10. POS Branch Shows "Disconnected"
For Tier-1 retailers, this is one of the most serious problems, because a disconnected branch is treated like a non-integrated one. FBR's own data in 2026 showed that most registered Tier-1 branches were marked as disconnected.
Common causes: the sync service isn't running, credentials changed, the network is down, or a new counter was added without being registered.
How to fix:
Monitor the connection status of every branch every day
Register every new branch and counter on IRIS before it starts selling
Set up alerts for failed or delayed submissions
(For the full POS setup process, see our step-by-step FBR POS integration guide.)
11. QR Code Missing or Not Scanning
What you see: receipts printing without a QR code, or customers unable to verify the invoice in the Tax Asaan app.
Why it matters: an invoice without a valid FBR number and QR code can be treated as bypassing the system, which carries heavy penalties.
How to fix:
Check that the invoice print format includes the FBR invoice number and QR code fields
Test with your actual thermal printer, since small or low-resolution printing can make QR codes unreadable
Never hand out a manual receipt when the system is down. Let the invoice queue and sync instead.
12. Outdated API Version
What you see: an integration that used to work suddenly starts failing after an FBR update.
Cause: FBR updates its API and validation rules through new versions and SROs. Software still sending data in an old format gets rejected.
How to fix: choose a vendor or partner who maintains the integration and updates it when FBR releases changes, and check that this is included in your support agreement.
13. Correcting an Invoice That's Already Been Reported
Mistakes happen, but corrections now have a time limit. Under the latest rules, a digital invoice can be cancelled or edited within 72 hours for genuine errors. After that, you need approval from the relevant Commissioner.
How to fix: review rejected and incorrect invoices daily so corrections are made within the window.
Quick Troubleshooting Checklist
When an invoice fails, work through these in order:
Read the error code and message. Which group does it belong to?
Connection: is the token correct for this NTN and environment? Is the server IP whitelisted?
Customer data: are the NTN/CNIC, registration type and province correct?
Product data: do the HS code, sale type and UOM match FBR's reference data?
Tax: are the rate, extra tax and rounding correct?
Fix the master data, not just the invoice, then resubmit.
How to Prevent FBR Errors in the First Place
Most FBR errors are master data problems, not software bugs. Businesses that rarely see rejections usually do these five things:
Clean item master data: correct HS codes, sale types, tax rates and units for every product
Clean customer master data: verified NTN/CNIC and registration status
Tax templates instead of manual entry: cashiers and accountants shouldn't type tax amounts
Daily monitoring: failed, pending and disconnected items checked every day
Maintained software: an integration that's updated whenever FBR changes its API or rules
An ERP with built-in FBR integration helps with all five, because product, customer, tax and invoice data live in one system instead of being copied between tools.
How Bizloom ERP Can Help
Bizloom ERP implements and supports ERPNext with FBR digital invoicing and POS integration for businesses across Pakistan. If your invoices are getting rejected, or you're setting up integration for the first time, we can:
Diagnose and fix recurring FBR errors at the source
Clean up HS codes, sale types, units and tax templates
Complete sandbox scenarios and go-live correctly
Set up automatic retry, failed-invoice alerts and branch monitoring
Keep your integration updated when FBR changes its API or rules
Book a demo session to see how FBR-integrated ERPNext handles invoicing without the errors.
Related reading: