The IRIS Error and FBR's Silence: Behbood Certificate Holders' Tax Returns and an Unanswered Letter

The file reached my desk labelled 'cricket_asia'. I opened it and found no scorecard, no DRS controversy, no match referee's demerit sheet. Inside was a letter — from the Public Interest Litigation Committee of the Lahore Tax Bar Association, addressed to the Federal Board of Revenue. The demand was precise: correct a software error in the IRIS income tax return system. The people named in the letter were not cricketers; they were ordinary holders of Behbood Savings Certificates, Pensioners' Benefit Accounts and Shuhada Family Welfare Accounts. A widow, a retired clerk, a martyred soldier's wife. This is not a cricket report, and I will not dress it up as one. It is not useless on my desk, though. Across four decades, every controversy I have opened — Bengaluru 2026 or Kazan 2026 — has come down to three questions: who holds the authority, under which clause, and what is the appeal path. All three are present in this tax letter, and on all three the FBR has produced no document. So this is not a cricket story. It is a procedural story, and procedure is my beat. First, what IRIS is. Income tax returns in Pakistan no longer travel on paper. The FBR's IRIS is an integrated electronic system through which registration, filing, verification notices, refunds and appeals all pass through a single window. Its strength is that the taxpayer cannot change anything by walking in; the machine computes and the taxpayer accepts. That is also its weakness. The moment an error enters the computation, the power to correct it no longer sits with the taxpayer. He can only complain. Now the three savings instruments. Behbood Savings Certificates are the most trusted of Pakistan's National Savings schemes, especially in households with no second source of income. The Pensioners' Benefit Account is post-retirement survival. The Shuhada Family Welfare Account belongs to families who lost their man on security duty. The social logic of all three is identical: the return on them should stay outside tax, so that a small saving does not evaporate before it grows. This is not a hidden concession; it is declared policy. The legal basis sits in the Income Tax Ordinance 2026. The Second Schedule exempts specified income, and designated categories of National Savings schemes fall within it. My old habit applies here: one governing clause at a time, quoted short, with the practical consequence stated in plain language. The consequence is simple — if the law has placed an income outside tax, the return form's field must not push it back into the taxable column. The form should mirror the Schedule, not interpret it. The letter's authorship matters. The PIL Committee of the Lahore Tax Bar Association, with Waheed Shahzad Butt named in it. A tax bar's ordinary job is running a professional body of lawyers; its PIL wing has a wider brief, stepping into matters where a single administrative error lands on thousands of taxpayers at once. The argument for intervention here is exactly that: this is not one taxpayer's grievance, it is a whole category's. Now the technical core. The committee alleges that IRIS is folding the exempt return from these instruments into taxable income, or failing to map the applicable exemption field correctly in the return. The result is a tax payable figure above the actual liability, and a demand placed before a taxpayer who neither earned it nor understands it. The committee claims the arithmetic repeats the same error — not separate data-entry slips across separate cases, but a single configuration or mapping fault. That claim is what makes the letter serious, because consistency is evidence of error and also evidence of misreading. Here I must stop and price the source. This is an advocacy committee's letter, not an independent investigation. Its arithmetic is detailed and internally consistent — meaning that if you accept its premises, the sums hold. But consistent arithmetic is not proof of a correct claim; consistent misreading exists too. And from the material available to me, no public FBR response to the letter is on record. That is the largest gap in this report, and I will not hide it. So what is verified is only this: a committee has raised a specific technical claim, put numbers behind it, and received no formal answer. What is not verified is which layer the fault sits in — the form's design, the system's computation rule, or the interpretation an officer loaded into the system. These are three different places with three different fixes. The letter calls all three a 'software error', which is convenient shorthand but inadequate for an inquiry. My three-question template applies, the one I built in 2026 listening to referee instructors debrief in Kazan. First: who holds authority? Here the answer is clear — the FBR owns IRIS entirely. The taxpayer can neither see nor edit the computation; he only sees the output. The body that decides and the body that prints the decision are the same. In my trade we call that the right of review, and here it has already been taken from the taxpayer. Second: under which clause? The exemption rests on the Second Schedule of the 2026 Ordinance; that much is clean. But which provision opens the correction route is the point where I will not guess. My desk's rule is old: if I cannot name the section, I do not print the claim. The remedies the letter proposes are practical — recompute, review demands already issued, identify affected taxpayers. Each of those should carry the provision it sits under. Until that provision is on paper, the list is a demand, not a solution. Third: what is the appeal path? On paper it exists — internal rectification, then appeal before the Commissioner (Appeals), then the tribunal. But a path existing and a path being walkable are different things. The taxpayer here is not the person who can absorb the cost of appeal. Someone disputing a few thousand rupees of tax will not hire counsel, pay filing fees, take dates and wait six months. The procedure inverts its own purpose: the right of appeal is equal on paper and unequal in practice. And here a cross-code comparison, because that is my habit — but with the structural difference named. Cricket's DRS has umpire's call: when the replay is inconclusive, the field decision stands. Football's VAR has a 'clear and obvious error' threshold, and the on-field referee reviews and overturns his own decision — the decision stays with the person who made it. In this tax case, both principles are missing. There is no umpire's call, because the machine's decision is final; there is no clear-and-obvious threshold, because no scale of error is declared. There is no review at all. I will not stretch the comparison further, because if the structural difference — number of reviews, who owns the decision, conditions of appeal — cannot survive the test, the comparison should be dropped. Here the difference is so wide that the comparison does only one job: it shows that even in sport the machine is not given the last word, and in tax administration it has been. Now the least-written part. Holders of Behbood certificates, Pensioners' Benefit Accounts and Shuhada Family Welfare Accounts do file returns, but they are not tax specialists. They treat the system's output as correct because they have neither the means, the time, nor the language to check it. When the machine prints a wrong figure, the burden of challenging it lands on the person the system got wrong. That is the real asymmetry — not technical, human. The replay shows the foul; the ledger shows who pays. And in this ledger the cost is always collected from the last man in the chain, who has no review, no forum, no counsel. The contrarian turn, because the easy version of this story does not satisfy me. The easy version is: a software bug exists, the FBR should fix it, done. My objection is that the bug is the smallest part of the story. The larger story is that the whole exemption architecture rests on a Schedule, and the form's mirror of that Schedule changes after every year's Finance Act. On the day the Schedule moves and the form lags, thousands of taxpayers file wrong returns having done nothing wrong. This is not a one-off incident but the output of a structure — one in which statute, form and system run at three different speeds with nobody formally tasked to declare them in alignment. A second contrarian note, because nobody else will say it. This letter is not proof. The committee's arithmetic is consistent, but consistent arithmetic and a correct legal reading are different things. It is entirely possible the dispute is not technical but legal — the system doing what the Schedule's letter says, the committee reading the Schedule's intent. In such cases the winner is not software but a court's interpretation. And a structural observation is due: a tax bar's business is litigation. I do not say that as an accusation — I say it because an institution with an interest in a dispute should be read with the same care we apply to a board's press note. The same rule, both sides. So what is verified in this chain? A letter, a committee, a name, a technical claim, and a silence. That is all. What is absent matters just as much — no public FBR response, no independent audit, no dated change log recording what changed in the system and when. And that last absence weighs heaviest on me. A referee's eye is not a verdict; it is a delayed pattern. The pattern here is that we have a machine that delivers decisions and no document explaining why. I opened the ledger again, and the software error had a receipt — but the receipt carried no date. That is this report's open question, and I am leaving it open. The next test is not whether the FBR fixes one field. The next test is whether IRIS publishes a public change log — dated, clause-referenced, and stating how many returns in which year were affected. Until that log appears, every taxpayer is his own third umpire, and he is not even allowed to see the replay.