The IRIS Bug and Three Savings Accounts: The Real Question Inside the Lahore Tax Bar's Letter

The most consequential file in Pakistan's tax system right now is not a budget speech. It is a letter from Lahore.

The Public Interest Litigation Committee of the Lahore Tax Bar Association has written to the Federal Board of Revenue with a single, specific demand: fix the fault in the IRIS software that is causing the income tax returns of certain savings-account holders to be computed wrongly. Waheed Shahzad Butt's name appears on the letter on the committee's behalf. The arithmetic is set out at length, and it does not break. Add it line by line and the total holds.

But the letter carries more weight than a software complaint. It is about people who cannot afford a tax lawyer.

What IRIS is, and why it matters

IRIS is the FBR's integrated e-filing platform — the single window through which income tax returns, sales tax returns and a range of statutory declarations are filed in Pakistan. Over the past decade it has displaced paper filing. For a taxpayer, that means the entire record now sits on a server, and everything that flows from that record — refunds, demand notices, penalties — rests on that server's computation.

When the system works, this is an improvement. When it does not, the taxpayer has no obvious place to complain, because no officer made the mistake. The mistake is in the code, and there is no counter at which you can talk to code.

That is where the committee's letter begins.

Three accounts, and their special status

The matter concerns three specific savings instruments: Behbood Savings Certificates, the Pensioners' Benefit Account, and the Shuhada Family Welfare Account. These are National Savings schemes — instruments designed by the state itself, at fixed rates, for fixed tenures, for clearly named categories of people.

The names say who they are for. Behbood Certificates are held largely by widows. The Pensioners' Benefit Account belongs to a retired employee — it is the money that runs a month. The Shuhada Family Welfare Account belongs to families that have lost a member and to whom the state itself issued the instrument as compensation.

What the three share is this: small-ticket, fixed-return, last-resort accounts. There is no business risk in them, no capital gain, no trading. They produce interest and nothing else — profit on debt — and at a fixed rate.

That is precisely what makes them vulnerable.

The anatomy of the fault

Under the Income Tax Ordinance, 2026, tax is withheld at source on profit on debt. The institution running the scheme deducts the tax before paying the interest into the account holder's hands, and issues evidence of the deduction. When filing the return, the taxpayer claims that deduction, and it is set off against the tax due.

The committee's letter contends that in IRIS this set-off does not reconcile correctly for these three schemes. The tax already withheld at source and the credit the system displays do not match — and the result is a liability arising in the return where a refund, or nil liability, should have arisen.

One point of transparency belongs here. The chain of calculation in the letter is detailed and internally consistent; the addition does not break from one step to the next. But no independent audit of the IRIS code is public, and no formal response from the FBR to this letter appears in public sources. What exists is a well-built argument from one side, drafted in the manner of a legal petition — not an officially verified finding. Reading it as a conclusion would be a mistake. It should be read as a question, and the obligation to answer it now sits with the revenue authority.

Why these three accounts

This is where the case separates itself from ordinary software complaints.

All three schemes share a technical characteristic: their tax treatment is defined differently from ordinary profit on debt. The state created them for named categories of people, so the rates and exemptions that apply to them are written separately from those for general interest income. In any large return-processing system, such categories are identified by a distinct flag or code. If that flag is not mapped correctly — or if the system defaults these accounts into the general profit-on-debt category — the number will come out wrong even though the taxpayer has done nothing wrong.

The pattern here is clear, and it is uncomfortable. The three categories the state created with the intention of protecting them — the widow, the pensioner, the family of a martyr — are the three the system cannot distinguish from the general category. The distinction survived in the name and did not make it into the code.

And if the taxpayer wants to fix it himself

The great strength of a return-filing system is that a taxpayer can check his own entry and correct what looks wrong. The question is whether there is anywhere in this fault to make that correction.

If the field in which these accounts' special status could be recorded does not exist inside the system, the taxpayer is left with no route at all. He is entering the correct information, the correct figure, and the system is filing it in the wrong place. This is not the taxpayer's error. It is the taxpayer's helplessness.

And that helplessness is not cheap. This class of filer has no chartered accountant, no tax adviser, no contact who can draft an appeal. The appeal process takes time, takes paperwork, and the cost often exceeds the amount in dispute. So this class pays quietly. That is the quietest part of the fault — the people least able to bear it are also the least likely to lodge a complaint about it.

The other question: fault, or design

An uncomfortable question arises here, and it is not the one the letter asks.

The letter calls this a software fault. Fault is a convenient word, because a fault has a remedy — a patch arrives, the matter closes. But if the problem is not in the code but in the design — if the system was never built to recognise state-protected categories — then a patch will not do the job. After the patch, the same taxpayer will be standing at the same screen with the same question next year.

The second question attached to this is more uncomfortable still: the additional demand generated by this fault, where does it go, and what happens to it when the taxpayer does not challenge it? The letter does not ask this. It should be asked — of the revenue authority, and of the public accounts committee that reviews these figures. A wrong demand that ought to have become a refund, and never did, stops being a coding error.

And why this letter had to be written at all

The third point is the one that tells me the most. Why was this letter written?

An institution like the Lahore Tax Bar exists to represent taxpayers. When it files a letter through its public interest litigation committee about a system bug, it is itself reporting something: that this class of taxpayer has no ordinary, functioning channel for grievance. If a channel existed, a committee of lawyers would not have had to draft a public-interest argument.

I am reading this letter from Brisbane, a country where filing a return is a kind of civic ritual and where an administrative error is corrected through a pre-set process. Comparing the two is pointless, because the administrative architecture differs. But one thing is the same everywhere: the credibility of a tax system is built not on its rates but on the speed with which it corrects its own errors.

What to watch

Three things in this case are worth watching, and all three point the same way.

First, whether the FBR responds to the letter in writing — and if it does, whether it accepts the fault or disputes the interpretation. Second, if a correction comes, whether it is retrospective or applies only to future years — because for taxpayers who paid this amount last year, a forward-only fix means nothing. Third, and most important, whether these three categories are given a distinct institutional identity inside the system, so that the next change does not reproduce the same error.

Watch the refund line, not the apology. An apology has no ledger; a refund does. And what speaks loudest in this whole affair is that the job of keeping account of money owed to a widow now rests with a committee of lawyers, and the answer rests with a piece of software.