Why FBR digital invoices get rejected: 10 checks before you post
Most failed FBR invoices come down to a small set of data problems. Run through these ten checks before you validate and you will catch the majority of them.
1. The buyer's NTN or CNIC
A missing digit, a dropped leading zero or a stray space is the classic cause. Keep NTN and CNIC as text, never as numbers, so leading zeros survive. This matters most when you copy data from a spreadsheet.
2. The buyer registration type
Registered, Unregistered, Consumer and AOP are treated differently. Make sure the type matches the details you supply. A buyer marked Registered needs a valid NTN or registration number.
3. The buyer's province
The province must be filled in and spelled the way the form expects, such as Punjab, Sindh, KPK, Balochistan, ICT, AJK, GB or FATA. Choose it from a list instead of typing it.
4. The HS code
An HS code that is wrong, incomplete or unrelated to the description can fail validation. Use the full code for the item and keep it consistent between invoices.
5. The unit of measure
The unit has to suit the HS code. If you sell by the carton but the code expects kilograms or pieces, the item can be rejected. On the Realtime screen the portal looks up the unit from the HS code to help avoid this.
6. The tax rate and the sale type
The rate must make sense for what you are selling, and the sale type has to agree with it. A zero rate on a line marked as standard rate goods is a common mismatch.
7. The sales tax amount
Sales tax should equal the taxable value times the rate. Small rounding differences between your billing system and the amount you send can trigger errors. The portal calculates the amount for you, so avoid overriding it.
8. SRO details
If a reduced or zero rate depends on a specific SRO, you need both the SRO or schedule number and the item serial number. Leave both blank when no SRO applies.
9. The scenario ID
In the sandbox the scenario has to fit the kind of sale you are testing. In production, leave the scenario ID blank.
10. Invoice details
Check the invoice date, make sure each invoice number is used once, and give every Debit Note the reference number of the invoice it relates to.
Reading the error message
When FBR rejects an invoice, the portal shows the item number, the FBR error code and the message together. Start with the first error, fix it, validate again and repeat. Fixing one issue sometimes clears several.
New to the two steps? Read validate vs post. Preparing a spreadsheet? See the Excel upload checklist. FBR's rules can change, so confirm details against FBR's current instructions.