When the Scoreboard Itself Is Wrong: The Tax Credit Trapped Inside FBR's IRIS

Hook At first glance, this is not a sports story. No stadium, no ball, no player. The Public Interest Litigation Committee of the Lahore Tax Bar Association has written to Pakistan’s Federal Board of Revenue (FBR) about a software defect in the IRIS income tax return system. But anyone who works with systems — a cricket scorer or a tax calculator — knows that the most dangerous errors hide in classification, not in the big numbers. This is a scoreboard showing four runs for a ball that actually yielded two, except the ledger cannot see the difference. Context IRIS is FBR’s online platform for filing and processing income tax returns — the place where the government’s arithmetic and the taxpayer’s arithmetic are supposed to meet. The committee says the software is not allowing credit for advance adjustable tax deducted on profits from Behbood Savings Certificates, Pensioners’ Benefit Account and Shuhada Family Welfare Account. These are government saving schemes designed for senior citizens, pensioners and families of martyrs. Under the Income Tax Ordinance 2026, the deduction at source is not final tax; it should be adjusted when the return is processed. The committee’s letter, with Waheed Shahzad Butt named on it, argues that IRIS is stopping that adjustment. Core Based on my years of reading score sheets and data feeds, I can say this: when software stops giving credit, it changes the direction of the whole game, not just one number. It is as if a batter scored a fifty at 118 in the 14th over and the scorer recorded 32. The comparison is not exact, but the principle is identical: what is not recorded does not count. I build ledgers the way other people build excuses: from tiny, stubborn details. That is why I read this letter twice. The core issue here is not double taxation alone. It is trust. When an elderly certificate holder files a return and the system says the advance tax is not there, he starts searching for papers from three or five years ago. That burden is carried in silence, not in stadium noise. And silence carries a cost that never appears in highlight reels. The most important stat in this story is the one nobody has a column for: how many returns are affected, how much money is stuck, and since which tax year the fault has existed. Without those three numbers, we know the symptom, not the disease. Contrarian The awkward angle is that the letter’s arithmetic is clear, but its verification is incomplete. An advocacy committee’s letter, however detailed, is not an official FBR response. Without the revenue board’s processing log, we cannot know whether this is a systemic failure or a defect limited to certain old assessment years. Treating the letter as a verdict would be like judging an entire innings from one over. This is a hypothesis with a claim attached — useful, specific, but not yet confirmed. Takeaway The next step belongs to FBR: open the IRIS log, state how many taxpayers are affected, and set a timeline for a fix. Until then, this will remain a letter, not a resolution. The scorecard says history; my notebook says patience, re-checking, and the number that no one had a column for. The question is whether FBR will face its own scoreboard — or whether next year another letter will have to say the same thing.