Troubleshooting
Penalties & invoice rejections
When invoices fail validation, teams need fast, practical answers. This guide covers common rejection causes and clears up myths about penalties — it is not legal advice.
The legal position
What the law actually says
Failure to comply with Pakistan’s digital invoicing requirements is dealt with under section 33 of the Sales Tax Act 1990, and more than one entry in that section can be relevant. They carry very different amounts, and FBR’s own digital invoicing FAQ refers only to “section 33” without naming an entry.
Section 33, serial 25A
Serial 25A of the section 33 table covers a person required to integrate under section 23 who fails to integrate, or who fails to issue electronic invoices after integration. It provides for penalties of Rs 500,000 for a first default, Rs 1 million for a second, Rs 2 million for a third and Rs 3 million for a fourth, and provides that business premises are liable to be sealed.
Section 33, serial 25
A separate serial 25, substituted by the Finance Act 2026 with effect from 1 July 2026, covers failure to integrate for monitoring, tracking, reporting or recording of sales and production. It provides for a penalty of up to Rs 1 million, a further penalty of up to Rs 5 million if the default continues beyond one month, and sealing of business premises.
Which one applies to you
Because these entries overlap in wording and carry different amounts, and because FBR has not settled in a published clarification which applies to a given default, confirm your own exposure with a qualified tax adviser rather than relying on a single figure.
A rejected invoice is not the same thing as a penalty. Rejections are usually data problems you fix and resubmit; exposure under section 33 is about failing to integrate or failing to issue electronic invoices at all.
Position stated as at 12 August 2026. References to the Sales Tax Act 1990 and the Sales Tax Rules 2006 are to FBR’s published consolidated texts, which are convenience consolidations; the gazetted text prevails.
Myths vs facts
What teams get wrong about penalties
Clear these up in finance meetings before fear or complacency drives bad process.
One rejected invoice always means a penalty.
Rejections are often technical. Fix the data and resubmit. Penalties depend on the nature and pattern of non-compliance — not every failed attempt.
Software guarantees zero rejections.
Good software reduces errors, but buyer data quality and tax treatment still need human judgment. Sandbox testing catches most issues before go-live.
You can ignore rejections and fix them at return time.
FBR digital invoicing expects timely submission around the point of supply. Unresolved rejections create gaps between billed and reported amounts — address them promptly.
Problem → fix
Common rejection causes and fixes
Start with the rejection message — it usually names the field that failed.
Buyer data errors
- Invalid or inactive NTN — verify before billing
- CNIC format mismatch — check digits and separators
- Buyer name does not match registration records
Tax & line items
- Wrong sales tax rate for the supply type
- Further tax not applied where required
- HS code or description missing or inconsistent
Operational fixes
- Use NTN/CNIC lookup before submitting
- Test edge-case invoices in sandbox first
- Assign someone to monitor daily rejections
- Keep rejection logs for advisor review
FAQ
Frequently Asked Questions
Why was my invoice rejected by FBR?
Common causes include invalid buyer NTN/CNIC, incorrect tax treatment, missing mandatory fields, or connectivity issues. Read the rejection message carefully — it usually points to the field that failed — then correct and resubmit.
Can I resubmit a rejected invoice?
Usually yes — after correcting the error. Keep a record of the original attempt and the corrected version for audit purposes. Your software should retain both the rejection payload and the successful confirmation.
What penalties apply for non-compliance?
Penalties sit in section 33 of the Sales Tax Act 1990, and more than one entry in that section can be relevant to a digital invoicing default. Serial 25A provides for Rs 500,000 for a first default rising to Rs 3 million for a fourth, with premises liable to be sealed. A separate serial 25, substituted by the Finance Act 2026 from 1 July 2026, provides for up to Rs 1 million, a further penalty of up to Rs 5 million if the default continues beyond a month, and sealing. FBR has not published a clarification saying which applies to a given default, so confirm your own exposure with a qualified tax adviser.
How do we reduce rejections before go-live?
Clean buyer master data, map tax codes carefully, and run representative sandbox cases — including deliberate failures. Assign a daily owner for rejections once you are live.
Continue
Prevent problems before they start
Deadlines & notifications
Which notification set which date, and what replaced what.
Read moreSandbox to go-live
Test representative invoices before live traffic.
Read moreFBR digital invoicing
Understand the basics of near real-time submission.
Read moreIRIS registration
Make sure portal access is set up correctly.
Read morePCT and HS codes explained
The single most common cause of a rejected line, in detail.
Read moreReady to simplify your FBR digital invoicing?
Join 2000+ businesses using eInvoicePro for real-time FBR integration and automated tax compliance.