A Record With the Wrong Label: IRIS, Savings-Certificate Relief and a 79,613-Rupee Gap

Last week a record landed on my desk. The label said "cricket." Inside there was no strike rate, no over, no scorecard. There was a number — 79,613. And a letter from Waheed Shahzad Butt, chairman of the Public Interest Litigation Committee of the Lahore Tax Bar Association.

His claim: Pakistan's Federal Board of Revenue online filing system, IRIS, is clawing back exactly ten percent of a statutory concession on National Savings profit, via surcharge.

The notebook travelled from Khulna to the World Cup; I just kept writing. Thirteen years have built one habit — I don't trust the label, I trust the arithmetic. So I take the label off and look at the numbers.

Context

Three National Savings products matter here — Behbood Savings Certificates, Pensioners' Benefit Account and Shuhada Family Welfare Account. Clause (6) of Part III of the Second Schedule to the Income Tax Ordinance, 2026 grants a reduced rate on their profit. Parliament gave the relief deliberately.

The trouble starts when taxable income crosses ten million rupees and the section 4AB surcharge applies. IRIS applies the relief through an entry called code 9309. Butt's allegation is that the code shows the relief correctly but computes the surcharge on the pre-relief tax.

The demand went not to a court but to the FBR Chairman, through three Members (IR-Legal, IR-Operations, IR-Policy) and the Director General IT. That route matters: courts are slow, the filing window is close. The play is administrative pressure for a fast fix.

The document states a filing deadline of October 31, 2026 — abnormally distant for the current cycle. Unverified, so I don't treat it as settled.

The arithmetic

In the worked example, taxable income is 11,447,109 rupees, of which 2,484,000 comes from Behbood and related holdings. Normal tax is 4,241,199. The clause (6) reduction is 796,132 — derived from 920,332 minus 124,200.

IRIS charged 424,120 in surcharge. That reconciles at ten percent of 4,241,199 — the base was the unreduced tax.

After relief, tax is 3,445,067. Ten percent of that is 344,507. The gap is 79,613 — exactly ten percent of the 796,132 relief.

That reconciliation is the strongest evidence. Four numbers — income, tax, relief, surcharge — each computed separately, all producing the same gap. This is not a discretionary assessment call; it is a base-of-computation error, and a base error never stays inside one taxpayer's file.

A second effect gets less attention: the return screen is said to show a non-nil balance the filer knows is not owed. Filing on that basis invites notices and defaults — friction beyond the tax itself.

The affected class is narrow but specific: taxable income above ten million rupees, holding these products. The per-return damage is 79,613 rupees — small alone, multiplied across a class. The document also reserves the right to a refund, which points to a future claims queue.

The other side

Here I stop, because my own rule is a three-match evidence threshold — in Qatar I watched 23 sessions and 7 matches before writing on Morocco's low block. This story has one match, one source.

First objection, legal. Section 4AB speaks of tax imposed under Division I of Part I of the First Schedule. Whether Second-Schedule-relieved tax falls inside that definition is an interpretive question. If the FBR holds its reading, the software is working as intended and the dispute is in the law. Calling it a defect pre-judges the outcome.

Second objection, remedy. Manual rectification exists but Butt says it is inadequate. A class-wide defect wants a class-wide fix — system correction plus public notice. But a notice is a de facto admission, and admission carries administrative cost, which may slow the fix.

Third objection, against my own notebook. Every figure comes from the claimant. No FBR response on record, no court order, no independent recomputation. The arithmetic reconciles; reconciliation is not proof. The loudest part of the story is the least verified.

The training ground is where the truth shows up before the scoreboard. Here the ground is software, and I have not yet seen its scoreboard — only heard a batsman say the bat is cracked.

What to watch

Whether the IRIS changelog alters the surcharge base; whether the FBR issues clarification or a notice; what the real deadline is. If refund claims begin to accumulate, the scale becomes visible.

Every match has a pulse; my job is to keep the count. This match has no players — only a system, a law, and a gap. The pipeline that sent a tax story to the cricket desk made the same error: it assigned the label before checking the base.