Seven Mistakes People Keep Making When Filing in Pakistan

Almost nobody gets an FBR query because they tried to hide something. Most queries trace back to small, recurring gaps that a bit of record-keeping through the year would have closed. These are the ones that come up again and again.

1. Numbers on the return that don't match the bank statement

Banks report certain data to FBR directly. When the income or withholding figures on your return don't line up with what your own bank statement shows, that's one of the easiest mismatches for an automated check to catch — even when the gap is a genuine oversight, not anything deliberate.

2. A remittance that never made it onto the return

Money from abroad, sent through proper banking channels, usually gets favorable tax treatment — but it still has to be declared as remittance, not skipped or folded silently into some other income line. A remittance sitting in your bank account but nowhere on your return is an obvious gap the moment your wealth statement gets reconciled.

3. Confusing gross income with taxable income

Mostly a business and freelance filer problem: taxable income is receipts minus allowable expenses, not the raw amount that hit your account. Skip legitimate deductions and you overpay; ignore gross receipts entirely and you've made the riskier mistake in the other direction.

4. Missing wealth statement gap

Our wealth statement guide covers this in depth, but it earns a repeat mention here because it's one of the single biggest sources of post-filing queries. Declared assets need to reconcile with income, expenses, and tax paid — a gap doesn't automatically mean something was hidden, but it does mean you'll probably be asked to explain it.

5. Treating Zakat and donations as the same mechanism

Zakat is generally a straight deduction; approved donations are generally a tax credit, calculated on an entirely different formula. Apply the Zakat logic to a donation and the estimate comes out wrong — see our Zakat and donations guide for the distinction.

6. Filing in the last possible hour

IRIS gets slower and glitchier as deadline traffic spikes. File in the last hour and there's no room left to fix an error, chase a missing document, or wait out a portal outage. A week's buffer costs nothing and saves a genuine headache.

7. Not keeping records as the year goes

The root cause behind most of the above. Reconstructing a full year of income, expenses, remittances, and asset changes from memory and scattered statements in the final weeks is exactly where small errors creep in — not through carelessness, but because memory was never a substitute for a ledger.

The thread running through all seven: almost none of them are about intent. They're what happens when incomplete or reconstructed records meet a system built to check for consistency. The fix is the same one, every time — track through the year, not at the end of it.