If your invoices are being rejected by FBR's digital invoicing system, you are not alone. Rejection is the most common problem Pakistani businesses face when they first connect to FBR's PRAL gateway — and in most cases, it comes down to a small number of predictable errors. This article covers the top reasons FBR rejects invoices and exactly what to do about each one.
This is the single most common rejection reason. FBR's PRAL specification maps every HS code to a specific allowed Unit of Measure. If you submit an invoice with HS code 8517.1211 (mobile phones) but use "KG" as the UoM instead of "NOS" (numbers), FBR rejects the invoice immediately.
The fix: every HS code has a pre-approved UoM in the PRAL Technical Specification V1.12. You need software that has this mapping built in and auto-fills the correct UoM when you select the HS code. Panther FBR Enterprise V10.1 has all 8,521 HS codes pre-loaded with their correct UoMs — you cannot enter a wrong combination.
FBR defines 28 invoicing scenarios covering different combinations of buyer type, tax treatment, and transaction type. Choosing the wrong scenario — for example, using a B2B scenario for a B2C transaction — results in rejection even if every other field is correct.
The fix: map your transaction types to the correct FBR scenario before you start invoicing. Your software should make this selection clear and prevent invalid scenario-buyer type combinations. In Panther FBR, scenarios are labelled in plain language so you can identify the right one without referring to FBR documentation every time.
When issuing a B2B invoice to a registered buyer, FBR validates the buyer's NTN against its own database. If the NTN is entered incorrectly — a transposed digit, a missing dash, or an inactive NTN — the invoice is rejected.
The fix: verify buyer NTNs through FBR's Active Taxpayer List (ATL) before adding them to your buyer database. Panther FBR Enterprise allows you to import your buyer list and flag any NTNs that fail validation before they cause a rejection at submission time.
FBR's system recalculates the invoice total from the line items and compares it to the declared total. Any discrepancy — even a one-rupee rounding difference — causes rejection.
The fix: never manually enter the invoice total. Use software that calculates it from the line items automatically and applies FBR's prescribed rounding rules. Manual calculation is the cause of this error in almost every case.
FBR's gateway rejects any invoice with an invoice number that has already been submitted under your NTN, even if the previous submission was rejected. Many businesses make the mistake of resubmitting a rejected invoice with the same number after fixing the error.
The fix: when an invoice is rejected, generate a new invoice number for the corrected version. Do not reuse the rejected invoice number. Proper invoicing software manages invoice sequencing automatically and prevents duplicate number submissions.
FBR requires that invoices be submitted within a defined time window of when they were generated. Invoices submitted with timestamps that are too old or that appear inconsistent with the submission time are rejected.
The fix: submit invoices promptly after generation. If your business generates invoices offline during a connectivity outage, submit them as soon as connectivity is restored — do not queue them for days. Panther FBR Enterprise timestamps invoices at generation and flags any that are approaching the submission window limit.
FBR issues API tokens for connecting to the PRAL gateway. These tokens expire. If your token has expired or was entered incorrectly, every submission attempt is rejected at the authentication layer — before FBR even looks at the invoice content.
The fix: check your API token validity regularly in your software settings. In Panther FBR Enterprise, the Settings screen has a one-click connection test that tells you immediately whether your credentials are valid and your connection to FBR's gateway is working.
The common thread across all these errors is that they are preventable — if your software validates the invoice before it reaches FBR. Panther FBR Enterprise V10.1 runs a local validation pass against all PRAL V1.12 rules before every submission. If there is an error, you see a plain-language explanation of what is wrong and what to fix — before FBR ever sees the invoice.
Download the 7-day free trial at fbr.pecsglobal.com and run your first validated invoice against FBR's sandbox gateway. If you are currently getting rejections and want a diagnosis, WhatsApp us at +92 307 3812493 with your error code and we will tell you exactly what is causing it.