The IRIS Field: When the Return Software Outruns the Tax Statute

A brief landed on my desk last Monday. The label on top read cricket_asia. I opened the file and found no cricket in it — no team, no scorecard, no umpire, no board arguing over the terms of an NOC. What I found was a letter. The Public Interest Litigation Committee of the Lahore Tax Bar Association had written to the Federal Board of Revenue stating that IRIS — the FBR's online income tax return system — carries a software error, and that the error is corrupting the returns of taxpayers who hold investments in Behbood Savings Certificates, the Pensioners' Benefit Account, or the Shuhada Family Welfare Account. Waheed Shahzad Butt's name appears on the letter on the committee's behalf. I write about cricket. For twenty-one years I have read rulebooks rather than scorecards — first the Laws, then the playing conditions, then board constitutions. That is why I did not close the file. Its architecture was the architecture of my own work: a written rule, an instrument that applies it, and a gap between the two into which an ordinary person is falling. The only difference was that the field here was a web form and the batter was a pensioner. Let me be clear about what I am standing on. I have one letter, from an advocacy committee, with detailed arithmetic that is internally consistent. I do not have an official FBR response, an independent audit, or a court order. I will not add what is absent. I will place what exists where it belongs. It matters what IRIS is, because this dispute grew out of its architecture. IRIS is not a form-filling website; it is the FBR's integrated tax management platform, where registration, returns, withholding statements, refunds and notices all sit in one place. It is linked to the national database, to banks, to employers. When a taxpayer opens a return, some of the information is already on the screen. He did not enter it; a third party did. That is where the trouble begins. Now look at the three savings instruments named in the letter. Behbood Savings Certificates, the Pensioners' Benefit Account and the Shuhada Family Welfare Account are not market products. They are the state's own schemes, run through National Savings, and their design purpose is that pensioners, widows and the families of martyrs can live on a stable, low-risk monthly income. Their objective is subsistence, not yield. That is why the profit from them is exempt under Part I of the Second Schedule to the Income Tax Ordinance 2026 — in my clause index the entry sits under clause (74), and I re-check it after every Finance Bill. The reasoning is simple: when the state runs a welfare savings scheme and then taxes it, it is taxing its own intent. The money should not be taken twice. There is a constitutional hook here, and I raise it because it is the centre of the argument. Article 77 of the Constitution of Pakistan provides that no tax shall be levied for the purposes of the Federation except by or under the authority of an Act of Parliament. The root of a tax must lie in law, not in a dropdown on a screen. A referee does not invent the rule; he remembers where it was written. A software field should be held to the same discipline. The actual machinery runs further back. The bank or National Savings centre paying the profit deducts tax at source — under section 151 of the Income Tax Ordinance, on profit on debt — and that deduction travels to the FBR in a statement under section 165. The same information then populates the taxpayer's IRIS account automatically. In principle this is good design: the taxpayer types nothing. In practice it works only as long as every line of income on the screen is tagged to the clause that actually governs it. This is where, on my reading, the chain can break in three distinct places, and the letter's account sits at one of them. First, mapping: the bank's statement carries a category, and if IRIS routes that category into ordinary profit instead of the exempt head, the exemption survives on paper and vanishes on screen. Second, invocation: most return utilities do not apply an exemption automatically; the taxpayer must select the right schedule, the right clause and the right amount. A person who does not select it does not file an unlawful return — he files an expensive one. Third, credit matching: if the tax already deducted is not netted correctly against the income, the return begins to show a demand, a demand with no legal basis, only a field's consequence. I went back to the tape; the tape had not gone back to me. The tape here is the screenshot, the PDF, the acknowledgement slip the taxpayer keeps. The number printed on it becomes law for him, whether it came from a clause or from a bug. That is the real injury in this story: the taxpayer cannot prove the screen was wrong, because the screen is his only evidence. I read the committee's arithmetic twice. It is internally consistent — the amount that should fall under the exemption, the amount already deducted, and the shortfall between them agree with one another. But consistent is not the same as correct. I checked the margin, not the headline, and the margin explained the call: the letter is one side, an FBR reply would be the other, and the other is not yet on the table. Two rulebooks sat on the table, and neither one blinked — here the first book is the Ordinance, the second is the screen, and before they collide someone has to say which one governs. It would also be wrong to treat this as purely a software question. Software is only where the crack becomes visible; the crack itself is in the burden. The duty to claim an exemption has been placed on a man who has no law degree, no accountant, no broadband. To expect a seventy-year-old widow who has kept money in Behbood certificates all her life to locate clause (74) of Part I of the Second Schedule and tick the correct dropdown is not a legal condition; it is an administrative shortcut. A scheme designed so that the state would lean toward her now requires her to lean toward the system. Comparison is my habit, so let me make one under explicit conditions. India's income tax utility produces the same problem: bank interest arrives pre-filled, and the exemption must be claimed manually in a separate schedule. The difference is that in India there is a tradition of both CBDT circulars and courtroom challenges when the utility errs. In Pakistan, who stands behind this letter matters too — a tax bar association, a body of professionals who earn their living from this very statute. The power question is direct: the institution that can read a schedule is the institution that can write to the FBR. The person holding only a passbook cannot. Until that asymmetry is named, comparing two rulebooks is decoration. Now the part least likely to be said aloud. This letter is a request, not a ruling. The error it describes has not been acknowledged by any authority, and its arithmetic has not been independently checked. Nor is it true that noise proves malfunction and silence proves cleanliness. The quiet grounds taught me that silence is also evidence, but evidence of a limited kind: it establishes that no comment was issued and no corrective notification was published. It does not establish that the error exists, nor that the FBR has denied it. I will not cross the line between what evidence permits and what it merely allows. One thing I will stake a claim on, because it is design rather than politics. Administrative software is now the most effective part of the law, because it is what the public meets; the courtroom is not. A clause nobody reads becomes a dropdown, and a dropdown, wrongly ticked, defeats the clause. Whatever the facts here turn out to be, the question stands: taxing power rests with Parliament — should its exercise be delegated to the engineer who designs the form? Consistency is not a mood; it is a ledger kept in public. So I have opened an account on this file in my usual way — date, letter, claim, and a blank column where the FBR's answer should go. If a circular appears in the coming weeks, the real question will not be its existence but its date: will the correction apply retrospectively, or only to returns filed after that day? For people who have lived under a wrong demand for three years, that single line will decide whether the fix was relief or just another screen. The larger question will not be answered by any circular. If an error on a screen can make a widow pay more tax than the law requires, where is her route to challenge that error written down? On the day that route becomes as easy as the dropdown was, we will be able to say the system improved. Until then we are only discussing a bug — and the bill for that bug is still being paid by the weakest person in the room.