One IRIS Field, Three Exemptions: Reading the Lahore Tax Bar's Letter With a Referee's Eye

One software field. Three savings schemes. And one written letter in which the arithmetic is cleaner than the story.

The Public Interest Litigation Committee of the Lahore Tax Bar Association has told the Federal Board of Revenue, in writing, that a software error sits inside the IRIS income tax return system. The error falls on depositors holding Behbood Savings Certificates, Pensioners' Benefit Accounts and Shuhada Family Welfare Accounts. All three schemes sit inside the Income Tax Ordinance 2026, and the exemption claim on all three is built on the same class of paper. One name is logged in this file alongside the committee — Waheed Shahzad Butt.

At first glance this is not a sports story. That is the first glance's mistake.

The file reached me labelled 'cricket_asia'. The label was wrong. There is no team in it, no match, no cricket board, no player. There is a tax administration, a return-filing software, and a committee of lawyers writing to get one field corrected.

I built a football law desk inside a cricket-first newsroom, and the desk's first lesson was this: before the debate, I open the laws of the game, then the minute, then the camera angle, then the precedent. My pilot was an Indian Super League fixture between Mumbai City FC and Kerala Blasters — fourteen broadcast clips, three penalty-area incidents, one red-card appeal, and a law number attached to every call. Clicks were low. The file survived.

For the 2026 World Cup in Russia I kept a ledger across all sixty-four matches. In the France versus Australia group game, Antoine Griezmann was awarded a VAR penalty in the 58th minute after Josh Risdon's foul — I logged it under law, camera angle, on-field call, final call and precedent. That ledger taught me one rule: a decision tree is not a mood; it is a paper trail.

In 2026, when the pandemic pushed the ISL into a Goa bio-bubble, I re-watched ninety-five disciplinary and handball decisions from the first sixty matches. The empty stadium made every audit line sound louder. That season I caught the inconsistent application of 'arm away from body' and sent my editor a six-page memo.

I now read this letter the same way. Here, the document takes the place of the camera angle.

Document one: the committee's letter, addressed to the FBR. Document two: the IRIS return form in which the error is alleged. Document three: the provision of the Income Tax Ordinance 2026 that fixes the tax treatment of income from these three schemes. Document four, still missing: the FBR's reply, or its circular.

The audit rule is simple. One document, one claim, one paragraph.

The committee's claim is that because of a software error inside IRIS, the treatment these three classes of depositors are receiving is not the treatment the Ordinance 2026 requires. So this is not merely a numbers glitch; it is a legal-treatment glitch. A single software field is changing a right here — and once a filing system starts standing in for a statute, the question stops being about refunds and becomes about process.

The committee's arithmetic is detailed and internally consistent. That is its strength, and that is its limit. The ledger said one thing; the replay said another. Here the ledger belongs to the committee, and the replay — the reconciliation against the FBR's own records — has not run yet.

I would place this file in the 'medium-low' band, and I will log the reason. The source is a letter from an advocacy committee, not the output of an independent investigation. The arithmetic is consistent but unverified by the FBR. This letter is not a tribunal finding, and presenting it as one would be exactly the error I never make on the field.

Three questions belong in every file like this. First — which version of the return form? IRIS changes over time; a field that was correct in one build can break in the next. Second — which field, and which provision does it connect to? Third — what does the Ordinance say, and does a circular already exist that clarifies this treatment? None of those three answers is currently on the public record. That, not the error, is this file's real weakness: three unfinished answers.

The cost is distributed unevenly too. The software sits on a department's desk; the damage lands in a pensioner's account. All three schemes rest on the same logic — small savings, social security, and support for families of martyrs. The exemption reasoning is identical across them. If the software got one class wrong, the probability is that it got all three wrong, because all three run off the same field logic.

This is where my 2026 memo earns its keep. That season's problem was not one decision; it was the inconsistent application of one rule. The real question here is the same — is the error a one-off, or is the very logic that built the field wrong? If it is the second, then the next scheme, the one not yet drafted, will repeat it. And the story will stop being about returns and become a story about system design.

I bring a parallel across from my other desk. The registration and compliance systems of sports bodies are field-based in the same way — player registration windows, central contract conditions, absence-reporting forms. Where a box is ticked wrongly, the next decision changes: sometimes eligibility, sometimes participation. Reading AIFF and FIFA statutes against the BCCI's, I have written the same lesson repeatedly: when an institution's form becomes its law, the audit of that institution must begin with the form, not the statement.

The empty-stadium lesson applies again. Crowds make noise; applause covers decisions. There is no crowd in this file — no press conference, no studio debate. There are only depositors in three schemes, who may not even know that a field in their return is speaking against them.

And that is the committee's real contribution. It did not turn a computer bug into a headline; it turned it into a process complaint — which class of paper, which head of income, which provision. That is the difference between noise and a letter.

Now an unpleasant part. The easiest reaction to this letter is 'the government has admitted the mistake', or 'the government is doing all of this deliberately'. Both are haste.

My file holds one precedent. Mohammad Azharuddin's life ban was later overturned in court. Even an official, tribunal-verified finding does not always hold. So treating an advocacy letter as a verdict on day one is dishonesty toward process.

Second unpleasant part: even if the FBR fixes the error, the system is not fixed. A patch saves a file; it does not change a rule. And until the rule changes, the next scheme, the next form and the next bug are all standing ready.

Third, and most important. The arithmetic in the letter may well be right. I am not calling it wrong. I am only saying that 'it turned out to be right' and 'it was proven the right way' are two different things — and in the tribunal-facing world, the first routinely discredits the second.

Now forward. What is missing from this file is not the error — it is the date. The committee has written its letter. The FBR has said nothing so far. The file is open, and open files do not close themselves.

The rule on my desk is clear: when a file opens, set the publication date and the decision rule at the same time. Here that rule should read — "if the FBR issues a circular on this field, I write the verdict that day; if nothing arrives in three months, I write that nothing arrived."

The question is not what the software did. The question is whose responsibility it is to fix it, and how long that responsibility can stay unanswered.