IRIS Rate-Mapping Error: Excess Tax Deducted on Behbood and Shuhada Family Accounts, Lahore Tax Bar Writes to FBR

The letter the Lahore Tax Bar Association's Public Interest Litigation Committee sent to the Federal Board of Revenue contains no sensation. No scandal, no leak, no allegation against an officer. There is a rate-mapping in a piece of software, and beneath it are the people with neither the time, the energy, nor the access to a lawyer to file a complaint. The demand is technical: fix the error in IRIS, the income tax return system.

The file reached me labelled "cricket_asia". By the first paragraph it was clear the label was wrong — no team, no player, no match, no cricket board. When a file's label and a file's contents stop speaking to each other, my first job is to trust the contents and not the label. So this report is about what the contents actually hold: Pakistan's tax administration, and a software bug with far more concrete a price than any cricket scorecard.

I am a cricket analyst, not a tax specialist — this is outside my beat, and I am not going to hide it. But the method I use for a post-match post-mortem works here too: the post-mortem begins exactly where the receipt stops explaining anything. In this case the receipt has not stopped; it has printed the wrong number, and that is the whole story.

Context: what IRIS is, and what these accounts are

FBR's IRIS is Pakistan's online tax return and tax-management platform. Filing returns, refund claims, tax credits, and most importantly — setting withholding tax rates — all happen inside this one system. When a citizen declares interest or profit income, the system must decide which section and which rate apply. It does not "think" this through; it works off a fixed mapping table. The day that table is wrong, the system levies the wrong tax on thousands of people — and does so silently.

At the centre of the dispute are three savings schemes: Behbood Savings Certificates (BSC), the Pensioners' Benefit Account (PBA), and the Shuhada Family Welfare Account (SFWA). All three are National Savings instruments paying above ordinary bank-deposit profit, and their purpose is explicit — to support people with no other source of income. Behbood is mainly for widows and senior citizens, PBA for retired employees, SFWA for families who lost members in national service. What these three groups share: they are the least organised, the least likely to complain, and the least software-literate.

The legal architecture is that profit on these accounts is taxed at source — deduction of tax on "profit on debt" under Section 151 of the Income Tax Ordinance 2026. Under that section a concessional rate is provided for these specific schemes, commonly cited as 10 percent — while non-filers, or those outside the Active Taxpayer List (ATL), attract a much higher rate. That is where the software has to pick the right category. And that, according to the committee, is where IRIS is picking the wrong one.

Core: where the error sits, and how heavy it is

The committee's argument is straightforward. In IRIS's rate-mapping, Behbood, PBA and SFWA accounts are not being held in their own concessional category but dropped into the general "profit on debt" higher-rate category. The result: a taxpayer legally entitled to the concessional rate is being deducted at the higher one. On paper this looks like a difference of a few percentage points. In reality it is not a difference — it is a slice of income that was never meant to go anywhere else.

Here an old habit of mine earns its keep: never read a percentage as a percentage, read it in the context of the man's pocket. For a household whose monthly income is largely this certificate's profit, a few points of rate becomes a difference in the food budget at month's end. And the deduction happens at source — the money is cut before it reaches their hands. They may not even know something went wrong until they read the slip themselves, match the rate against the statute, and understand that the match is wrong. This is the most dangerous form of software error: it is silent.

The name that surfaces on the committee's side is Waheed Shahzad Butt — and his letter is not merely a complaint, it is arithmetic. The letter sets out that the gap between the concessional rate and the applied rate, compounded over a three-year or ten-year certificate term, becomes a substantial sum. For me that is the letter's strongest part. A grievance that arrives with numbers survives in court and in the office; one that arrives only with sentiment lasts until the end of the email.

Now the part the committee stresses and which stings most — the nature of the affected population. This is not a commercial class that will call a CA and pull a refund next quarter. These are widows, pensioners, families of martyrs. Many have no filing history, no tax adviser, no way of knowing what happened to them. The committee's claim is that this group is hit hardest precisely because it has no mechanism to catch the error. In my post-mortem language: the error rate is highest where monitoring capacity is lowest. That is not coincidence, it is the consequence of design.

The contrarian angle: perhaps the software is not wrong

Here I have to try to break my own report, because if I don't, someone else will — and then my analysis will look weak.

First, and most important: only one side of this matter is available. The information comes from an advocacy committee's letter, not an independent investigation, and there is no official FBR response on record. Source quality is medium-low. The arithmetic is detailed and internally consistent — I read it and found no obvious break — but consistency is not truth. Clean arithmetic can stand on a wrong foundation.

Second, and sharper: it is possible the software is not wrong and the law is. Remember, the concessional rate is often tied to being a filer, or being on the ATL. A large share of holders in these three schemes — widows, the elderly, families of martyrs — are by definition people who do not file returns. If the statute says the concessional rate is only for filers, then the higher rate IRIS applies is not an error but correct implementation. Then the real problem is not in the software but in the architecture of Section 151 — and its remedy is not a software patch but a legislative amendment. That distinction is not small. In one you fix a bug; in the other you have to go to parliament.

Third, a point I would enter for the committee: if this were genuinely an ATL-status matter, the complaint's scope would not be this clean and this consistent. If the error were simply "higher rate for non-filers", that would be a long-standing arrangement, not a new grievance. The letter's argument is that the fault is in the mapping, where the scheme's identity itself is not being recognised correctly. I would put it this way: correlation is not causation. Seeing the higher rate and non-filer status appear together does not prove one caused the other. Both could come from a third cause — the same faulty rate-mapping, which hits non-filers hardest because they have no route to correction.

And a fourth thing that always bothers me: when an advocacy committee writes to FBR, one of its purposes is also to get the matter on record, build pressure, and if needed open the route to a public interest petition. That is not wrong — that is the democratic machinery. But it means the letter should be read as a document of claims, not a document of facts. That is how I have read it.

What to watch next

The next signal is in FBR's response, and it has three possible shapes — each with a different meaning. If FBR issues a circular correcting the rate-mapping, it means the error is conceded and it was software-level. If FBR stays silent, it means it considers its position lawful and the matter goes to court. And if FBR says the concessional rate requires filing, then the question shifts from software to the policy that demands paperwork from the families of martyrs — when the scheme was built to support them.

The second signal will come from banks and National Savings centres. If the same mapping is wrong at the withholding-agent level, the problem is bigger than IRIS and more expensive to repair. The third signal — and for me the most important — is how many people come forward to check their own slips. The lower the population's error-detection rate, the slower the correction.

As for the label on this file — it should be corrected. "cricket_asia" is not looking for a letter about the tax on Behbood certificate holders. But I suspect whoever applied that label accidentally put a necessary story in front of me. One line of software, and beneath it thousands of people who never tried to find out how much was being cut from them, or why. Until someone asks where the last digit on the receipt came from, that digit will keep being taken as true.