When FBR rejects an invoice, the response is often technical. This guide maps common FBR invoice validation errors to fixes finance teams can apply before resubmitting. Always confirm details against current FBR notices and your tax adviser.
Wrong environment (sandbox vs production)
Sandbox tokens must not post to production endpoints and vice versa. Symptom: auth failures or unexpected empty responses. Fix: match token type in IRIS with the environment selected in software settings.
Buyer NTN, registration type, or province
Registered vs unregistered buyers, STRN, and province fields must match FBR’s expected format. Fix: update the buyer library entry and re-validate line items.
HS code, UOM, or scenario mismatch
Each line must fit the invoice scenario you selected. Symptom: item-level error codes in the API response. Fix: pick the correct scenario, refresh HS/UOM from FBR lists, and run sandbox tests for that scenario set.
Token expired or revoked
Regenerate the bearer token in IRIS and paste the new value. Retest with validate before submit.