IRIS Software Error: Lahore Tax Bar Association Asks FBR to Fix Return Filing for Savings Certificate Holders

This report begins not with a ruling but with a letter.

The Public Interest Litigation Committee of the Lahore Tax Bar Association has written to the Federal Board of Revenue (FBR) asking it to correct a software error in IRIS, its integrated income tax return system. The error affects taxpayers whose income comes from instruments such as Behbood Savings Certificates, the Pensioners' Benefit Account and the Shuhada Family Welfare Account. Behind all three sits the same kind of taxpayer: not someone with a large salary, but someone with a small, fixed, monthly sum they have relied upon. The committee's demand is straightforward: fix the defect, and remediate the returns already affected by it.

The letter is now public, but it should not be read as an investigation. It is an advocacy document, and the most important piece of evidence is the one still missing — an FBR response.

Context: what IRIS is, and why these three instruments matter

IRIS is the FBR's unified income tax return system, the channel through which an ordinary Pakistani taxpayer files annually, selects income categories, claims deductions and sees the final liability. To the taxpayer it is a form. To the state it is a decision engine, because the category selected on screen determines the rate applied and the exemption preserved.

Behbood Savings Certificates and the Pensioners' Benefit Account have for decades been fixed-return instruments chosen by middle- and low-income savers, particularly retirees and household savers. The Shuhada Family Welfare Account is different in nature: it exists for families who have lost someone in the security forces. All three share one feature — the income arrives as profit or interest rather than salary or business profit, and under the Income Tax Ordinance 2026 such income is treated in a specific way, with its own category, its own deduction and, in many cases, its own treatment.

That is where software and statute collide. The law states how the income shall be treated; the software determines whether the taxpayer can reach that treatment at all. If the correct option is absent from the form, or selectable but not reflected in the computation, the law survives on paper and the taxpayer is shut out in practice. The committee has made that gap the centre of its complaint.

Core: the real cost of a defect is paid by the taxpayer

The least important part of this story is which button does not work. The most important part is who receives the bill when the state's software is wrong.

Tax systems run on an unspoken rule: the filing obligation belongs to the taxpayer, and so does the liability for error. If the portal will not let you select the right category, and you do not put that on the record, then years later, when a notice arrives, you have no way to prove you did everything correctly within the limits of the system as it then existed. A bug lasts a day; its mark on a taxpayer's record is permanent.

For these three instruments the cost doubles, because here a software fault lands directly on the cohort least able to absorb it — people who cannot retain a chartered accountant every year, or take time off to contest a notice. A corporate group's tax department logs a portal defect in three emails. A retired clerk has no such machinery. His only route is a bar association, or a letter that speaks for him.

There is a second layer. The tax treatment of savings income is often tied to conditions for deduction or exemption, tested at the point of filing. If the software places that income in the wrong bucket, the effect is not confined to this year's liability — it can touch carry-forward positions, refund claims, and even the filer status of the person concerned. To the taxpayer it is a bug; in the documents it is an entry that is not true, written in his own hand.

That is why the committee's demand is not merely for a fix but for remediation of files already affected. The first half is about the future. The second is about people already out of pocket. Repairing the portal does not repair the returns already submitted.

Contrarian angle: the missing trail, not the bug

The convenient story is that this is a software bug and it will be fixed. In my experience those stories age fastest, because the real problem is never the bug — it is how the bug was discovered and who logs it.

What we have is an advocacy committee's letter. We do not have an FBR statement. We do not know when the defect was first reported, how many taxpayers were affected, whether the FBR acknowledged it, or whether it was corrected in an earlier version. That absence is the story.

A large revenue system needs a public error register — which defect was reported when, acknowledged when, fixed when, and which files it touched. Where no such register exists, remediation depends entirely on non-government letters and bar-association pressure. And in that arrangement, the speed of repair is set not by the taxpayer who bore the loss but by the strength of the body speaking for him.

A further point follows. When the revenue department's own machine errs and a taxpayer files wrongly in reliance on it, which way does the rope of penalty and interest get pulled? In practice it is pulled toward the taxpayer, because his name is on the return. This is not merely a technical problem; it is an inverted pyramid of accountability — the error happens at the top and the price is paid at the bottom. My own files contain several such cases, where a machine's fault was converted into an individual's lapse. I am not alleging conspiracy here. I am saying the system's default never changes: error above is absorbed into paperwork below.

What is not yet verified

Let us be clear. This report rests on an advocacy document and should be read with that limit. The arithmetic and the technical description in the committee's letter are described as internally consistent, but they have not been verified by the FBR or by any independent audit. The case advanced by Waheed Shahzad Butt and the Public Interest Litigation Committee is a claim, not a finding. Nor do I have any indication that the FBR has responded.

So a reader should wait for three things: an official FBR response, an official figure for affected files, and confirmation of whether the defect persists or has been fixed in an update. While those three questions remain open, the story is incomplete.

The question ahead

The real test is not when the IRIS defect is patched. It is what happens to the taxpayers whose records already carry the error, and whether the FBR will find them and answer them, or leave them to file application after application. The day a revenue department's own software starts leaving a public trail the way a cricket scorecard does — every defect logged, every fix date-stamped — we will stop depending on letters to understand tax administration. Until then, a retired clerk's return is his most reliable testimony, and that is a sorry state of affairs.