The Tag Said Cricket, the Ledger Said Tax: Inside the IRIS Entry That Would Not Reconcile

The file landed on my desk carrying the tag cricket_asia. The header row had no runs, no overs, no economy, no wickets. It had profit on debt, withholding rate, instrument code and return status. I opened the notebook before I opened the spreadsheet — a habit since 2026, when I sat in the scorer's chair at Feroz Shah Kotla and counted 1,412 legal deliveries, 38 maidens and 12 edges to slip across four days, and watched Delhi's seamers beat Mayank Agarwal's outside edge 19 times while he made 176. The scorecard said one thing. My log said another. The same thing happened here. The scorecard belongs to a government software platform; the ball-by-ball log belongs to a committee of lawyers. The 1,412th entry never hurts. The silence after it does.

This is not a cricket story. It is a tax-collection story. The Public Interest Litigation Committee of the Lahore Tax Bar Association has written to the Federal Board of Revenue, asking it to correct a software error inside IRIS, Pakistan's online income tax return system. The letter names Waheed Shahzad Butt on the committee's behalf.

The matter concerns three savings instruments: Behbood Savings Certificates, Pensioners' Benefit Account and the Shuhada Family Welfare Account. All three sit under National Savings, and all three follow one philosophy — holding money safely for people whose other savings options have run out: widows, pensioners, families of martyrs. Withholding rates on the profit these instruments pay differ from ordinary profit on debt, and that difference is fixed within the framework of the Income Tax Ordinance 2026, where the section dealing with deduction of tax on profit on debt (Section 151) applies.

That rate differential is the technical spine of the committee's complaint. When an account holder files a return on IRIS, the software must read the instrument code and pick the right rate table. If the mapping fails, the system either applies the standard rate, or demands tax on profit that was already deducted at source. Both roads end at the same place — the account holder does not receive the figure he counted.

This is where my part begins. The committee's arithmetic is detailed and internally consistent. Every number matches the next one. Consistency is not verification. Arithmetic that is internally consistent only proves the writer added and subtracted correctly at his own desk; it does not prove the system he accuses made that mistake.

And yet the shape of the error is familiar, because I count shapes like this every day. National Savings deducts withholding at source, which means the profit reaches the account holder already taxed. IRIS then has two jobs: pick up the deducted amount as a credit, and apply the correct rate to what remains. Fail either step and you get exactly the fault the letter describes — double taxation, an inflated demand, or a refund stuck for months.

I did what I always do. I broke the claim down to its smallest unit. That unit here is not a delivery; it is one entry — one account holder, one instrument code, one withholding rate, one demanded amount, one date. The letter speaks to that unit but speaks in aggregates. Phrases like "thousands of account holders" dissolve the precision my notebook used to carry, where every ball had its line, its length and its bowler type in separate columns.

So I keep the sample size inside the sentence. How many returns are affected? For which period? Under which jurisdiction? How many account holders filed their own complaints, and how many were merely counted in the letter's list? Until those figures reach my desk, I will call this claim a question, not a law — and I name my questions rather than mumble them.

The second thing I hold on to is splitting process from outcome. The headline will say "software bug". The process story is smaller — a rate table failed to map, which is a question of a few lines of code. If the problem is mapping, the cure is equally small: fix the table, re-run the wrongly generated demands in a batch, release the stuck refunds. A fix that lives in a line of code should not be converted into a parliamentary debate.

What stings here is what stings in any large dataset — who gets recorded and who does not. A Shuhada Family Welfare Account holder rarely has the time or the means to file a grievance. A Behbood widow may not have a smartphone to open the IRIS portal at all. The committee speaks from Lahore; the account holder may be in Chitral, Dera Ismail Khan or Tharparkar. His voice enters the letter's list only when somebody else writes on his behalf. That is the real visibility problem — the story is about a bug, but the pain belongs to people whose data has not been created yet.

I also log the moment no column can hold. Nobody claps in front of a tax system; no stadium hums; no commentator shouts. In 2026, when I logged 14,400 deliveries across 60 IPL matches played behind closed doors, the hardest job was turning crowd noise into a variable — and I found that chasing teams won 57.5% of matches against 51.2% in 2026, a swing team strength alone could not explain. Here the hardest job is turning silence into a variable. Lawyers who write letters get heard; the ordinary taxpayer sees only an error message, and that message never enters any system of mine.

Now the part I wrote before I read the letter, because the sugar rush of an argument tempts anyone, and a clean counter-case feels boring in the moment.

First: source quality is medium-low. This is not an independent investigation but a letter from an advocacy committee, and the FBR has issued no verification or official response so far. In advocacy, arithmetic is a tool, not evidence. Second: correlation and causation are different animals. If hundreds of returns show inflated demands, that could come from an IRIS mapping failure — or from the account holder mis-describing the nature of his savings, or from a withholding certificate carrying the wrong figure, or from what looks like an error actually being a correct and harsh application of a law the committee disagrees with. In all three cases the citizen suffers, but the cure sits in three different places.

Third, and for me the most important: the tag that called this file cricket and the system that printed the wrong figure on a return are symptoms of one disease. A mapping error, a code error, a tag error. In any data system the least debated and most destructive element is mapping, precisely because it never makes a headline. Until the FBR writes a line of its own, this letter is one side of a case, not a verdict. And I still remember the old notebook in my cupboard where 19 beaten outside edges sat beside a 176 — open it today and the scorecard will still say 176. Asking is my job. Believing is yours.

What to watch next: the FBR's response. If it releases an IRIS patch, the next question is what happens to demands already raised — whether refunds come with retrospective effect, and who goes looking for the people who under-reported their profit out of fear. If it stays silent, the same account holder will fill the same form next filing season and read the same error message. I am waiting for one government department to walk back to its own card and tell us where the ball actually pitched.