The IRIS Box That Won't Accept Zero: Why Pensioners' and Martyrs' Families' Savings Accounts Are Being Taxed

The Public Interest Litigation Committee of the Lahore Tax Bar Association has written to the Federal Board of Revenue with a single demand: fix the software error in the IRIS income tax return form. Advocate Waheed Shahzad Butt is among the names attached to the letter. The account holders caught by that error are not ordinary filers. They hold Behbood Savings Certificates, Pensioners' Benefit Accounts and Shuhada Family Welfare Accounts — people who have retired, and families that have lost a member to martyrdom. A wrong pre-filled value puts them in a fight where they must prove a negative: that no tax is owed on them at all.

I have spent three decades reading forms more closely than scorebooks — medical forms, club administration papers, accreditation sheets. That habit says the real story sits in a default setting nobody reads. IRIS, the Integrated Revenue Information System, is the FBR's online return portal, and under the Income Tax Ordinance 2026 millions of returns pass through it each year. The logic is simple: profit on debt from banks and National Savings arrives pre-filled, the taxpayer confirms it, the return moves on. When that pre-filled value is wrong, the taxpayer has two options — accept it, or fight to correct it somewhere his objection is not heard.

The design of these three instruments matters because their tax status is not identical. Behbood Savings Certificates are the savings vehicle of older and retired people; nobody buys them to take a risk, they are bought by someone with a single source of income. The Pensioners' Benefit Account serves the same cohort. The Shuhada Family Welfare Account is different in kind: it exists for families that have lost their earner. At least one of these categories — the Shuhada Family Welfare Account — enjoys an exemption from tax. For a financial instrument whose entire purpose is that the state keeps its hands off, being taxed through a software error is not a policy failure but the inversion of policy.

The arithmetic the committee sets out is detailed and internally consistent. It rests on the Ordinance 2026 framework in which withholding happens at source, and the rate shifts depending on whether the taxpayer is a filer or a non-filer. That is where the real damage sits: a person whose income is low enough that filing is unnecessary is precisely the person the system treats as a non-filer. Low income does not lower the burden; the higher rate lands on him. The committee's case is that one wrong field triggers the whole chain — withholding first, then the figure on the return, then the assessment, then a notice that sends a pensioner looking for a lawyer.

The letter also stresses that the burden of the error is placed on the person with no power to fix the system and no time to understand it. A man of sixty or seventy logs into IRIS, sees a pre-filled figure, and finds no option that says: this is wrong, make it zero. That is not a technical defect, it is an accountability defect. When the system's default is itself wrong, the duty to correct it cannot rest on the person who cannot change that default.

Now the part where the easiest reading turns out wrong. The convenient story is that this is a bug, a patch will come, it will be fixed. I read it as a design problem, not a bug. The return form is built on the assumption that every savings instrument is taxable, with exemptions bolted on afterwards as exceptions. In a system where exemption is the exception and tax is the rule, the default will always lean towards tax, because collecting is the state's job and exempting is its generosity. Which is why a tax authority's software is policy by other means: a checkbox, a pre-filled value, a dropdown decide who pays, sometimes more effectively than the statute.

It must also be recorded that this letter is not an investigation. It is an advocacy committee's document, and no public FBR response has surfaced. The committee's arithmetic looks coherent, but the revenue department has not verified it — until it does, this is a strong claim, not an established fact. In my experience the worst damage in such cases comes from the gap between correction and verification; by then notices are out, and withdrawing them takes far longer than a patch.

What to watch is clear. First, whether the FBR implements the fix by circular or leaves it to a software update — a circular means past cases get looked at too. Second, what happens to deductions already made and notices already issued; a fix that applies only to future returns will let this error trail people for years. Third, and most telling, whether the Shuhada Family Welfare Account gets its own category in the system or stays in the same single box as every other savings scheme. The day that box is separated, we will know whether this was a fix of intent or only of form.