Beyond Section 165: A Judicially Guided, Technology-Driven Framework for Withholding Tax Enforcement under Sections 161 & 162

Muhammad Saqib Raza, Advocate High Court

Section 165 of the Income Tax Ordinance, 2001 [“the Ordinance”] read with relevant rules obligates taxpayers or prescribed persons to file monthly, quarterly, and annual withholding tax (WHT) statements with the Federal Board of Revenue (FBR) through its IRIS portal. These must include party-wise details of payments made, including cases where tax was not deducted—due to either exemption, certificate, statutory regulatory order (SRO), threshold, or other valid justification.

While this may have been justifiable in a manually-driven tax administration era, the landscape has significantly changed. With the comprehensive automation of FBR’s IRIS system and integration of sales tax returns into its framework, this requirement now imposes unnecessary compliance costs, duplication of effort, and administrative inefficiencies.

Today, the IRIS portal already records every WHT challan, including the names of both the withholding agent and the recipient, the section of the Ordinance under which tax was deducted, the gross amount, and the tax deposited. Further, sales tax returns also include party-wise details of all suppliers and vendors. This wealth of digitized data presents a strong case for FBR/PRAL to develop automated reconciliation reports. These could serve the very function currently served by statements under Section 165—but with greater speed, reliability, and accuracy.

FBR could verify whether payments were made to each party, whether tax was deducted/deposited, and whether any balance remains under “payables” or “advances.” Furthermore, the IRIS system can easily be programmed to identify parties with exemption certificates in a given period, or link non-deduction cases with the filer status of the recipients. If tax was already discharged by the payee, recovery under Section 161 would not be permissible—only default surcharge under Section 161(1B) of the Ordinance could be levied.

Judicial Backing for Procedural Safeguards

This position finds strong support from recent case law. In MCB Bank Ltd v. CIR (2021 SCMR 1325), the Supreme Court categorically held that vague or general notices under Section 161—issued without objective material—amount to roving inquiries and violate procedural fairness. The Court ruled that notices must be based on objective reasons or information, satisfying a reasonable standard, before jurisdiction under Section 161 can be assumed.

Building upon this jurisprudence, the Appellate Tribunal Inland Revenue in ITA No. 1889/IB/2024 – Wise Communication Systems (Pvt.) Ltd., laid down a twelve-step procedural framework for valid enforcement of Section 161. These include: verification of return and WHT statements, confrontation notices under Rule 44(4), and final show-cause issuance only after reconciliation discrepancies are established.

Similarly, the Lahore High Court in Nishat Chunian Ltd v. FBR (2014 PTD 2078) clarified that reconciliation under Rule 44(4) is a legitimate administrative step—not automatically indicative of non-compliance. Authorities must first identify discrepancies and request specific information. The Court stressed that reconciliation requests do not equate to default unless deliberately evaded.

The same reasoning was reaffirmed in Akhtar Saeed Medical & Dental College v. FBR (2015 PTD 267) and Noor Sugar Mills Ltd v. FOP (2015 PTD 1653). Both judgments upheld the legality of reconciliation notices under Rule 44(4), noting they merely seek verification—not initiate penal consequences. However, taxpayers are still required to respond with detailed explanations, especially where tax was not deducted.

The most recent and highly instructive case is Chawala Footwear v. CIR (C.A.16 OF 2022 dated 14.01.2025), where the Supreme Court upheld the validity of a Section 161 notice that contained complete party-wise details, vendor names, payments made, and legal basis for withholding obligations. The Court held that once such objective material is presented, the burden shifts to the taxpayer to demonstrate lawful non-deduction. This case reinforces the Supreme Court’s stance in MCB that only detailed, data-backed notices—following a defined process—can ground valid proceedings.

These authorities make it abundantly clear:

• The burden of proving default under Section 161 begins with the department.
• General, vague, or speculative notices violate constitutional due process.
• Taxpayers cannot be deemed in default merely because they did not file a WHT statement; procedural steps such as reconciliation and confrontation are mandatory first.

Cost Implications & Unjust Burden on Taxpayers

The preparation and filing of WHT statements under Section 165 imposes considerable compliance burden. Taxpayers must compile extensive party-wise data, often engage professional accountants or IT experts, and spend significant time uploading files in the required format. Ironically, these efforts are undertaken not for the taxpayer’s own benefit, but to aid the FBR in its revenue collection duties—essentially making the taxpayer an unpaid tax collector.

Moreover, FBR imposes heavy penalties under Section 182 for non-filing or late filing of these statements. Even though the taxpayer may have deducted and deposited all taxes correctly, technical delay or file formatting issues can result in fines. The Supreme Court and High Courts have repeatedly expressed concern over frivolous assessments made just to meet revenue targets. These practices increase litigation and erode taxpayer trust.

A Smarter Way Forward

Given the capacity of IRIS and the redundancy of manual filings, it is proposed that Section 165 be omitted entirely. Instead, FBR should deploy a structured report system using data already available within IRIS, cross-linked with:

• Sales tax returns (vendor data);
• Tax deduction challans;
• Exemption certificates issued by the system;
• Balance sheets (to verify payables/advances);
• Return filings of counterparties (to check if tax was ultimately paid).

Using this approach, FBR can automatically flag cases of possible default and issue confrontation notices under Rule 44(4), in line with the twelve-step framework laid down in ATIR’s Wise Communication case. Only where a taxpayer fails to reconcile or justify discrepancies should proceedings under Section 161 be triggered.

Additionally, this automation-based mechanism would empower the department to initiate proceedings under Section 162 of the Ordinance against the actual defaulters—i.e., the payees from whom tax was not deducted and who also failed to discharge their tax liability. Presently, FBR tends to penalize the WHT agents instead of pursuing recovery from the real beneficiaries who avoided tax.

Proceeding under Section 162 will not only ensure equitable enforcement of tax provisions but also encourage broader return filing compliance. It will shift the current departmental mindset away from issuing vague tax demands under Section 161 towards a more just approach where the actual party at fault is identified. More importantly, if the WHT agent is made to pay any tax shortfall under Section 161, identifying the defaulting recipient allows the agent to claim reimbursement. This reinforces the true essence of Section 161 as a facilitative, not punitive, provision.

Such a balanced model would strengthen accountability, promote responsible financial disclosure, and ultimately contribute to higher tax compliance and filer base expansion.

Judicial Precedents and Case Law Considered:

1. CIR, Zone-I, LTU, Lahore v. MCB Bank Limited (2021 SCMR 1325) – Condemned vague show-cause notices under Section 161; overruled Islam Steel Mills (2015 PTD 2335); emphasized objective threshold before initiating action.
2. M/s Wise Communication Systems (Pvt.) Ltd v. DCIR, LTO Islamabad (ITA No. 1889/IB/2024) – ATIR outlined a 12-step procedure to ensure due process under Sections 161/205.
3. CIR v. Marwat Enterprises (Pvt.) Ltd (2023 PTD 732) – Reiterated the requirement of due confrontation and reconciliation before raising tax demands.
4. Pepsi Cola International (Pvt.) Ltd v. FOP (PTCL 2023 CL 71) – Reinforced fair hearing and procedural safeguards.
5. M/s Nishat Chunian Ltd v. FBR (2014 PTD 2078) – Emphasized that reconciliation is not proof of default and cannot justify preemptive penalties.
6. Akhtar Saeed Medical & Dental College v. FOP (2015 PTD 267) – Reconciliation notice under Rule 44(4) is valid and non-adversarial.
7. Noor Sugar Mills Ltd v. FOP (2015 PTD 1653) – Filing of statements does not negate reconciliation obligation.
8. Sahir Associates (Pvt.) Ltd v. FOP (WP No. 25020 of 2014) – Due process and reconciliation are essential.
9. CIR v. Islam Steel Mills (2015 PTD 2335) – Overruled by Supreme Court in MCB Bank Ltd.
10. M/s Chawala Footwear v. CIR, Lahore (C.A.16 OF 2022 dated 14.01.2025)– Upheld a detailed, objective Section 161 notice; reaffirmed burden shifting only after valid notice.

Conclusion

The retention of Section 165 in its current form is an anachronism in the era of digital tax systems. With the capacity of IRIS and the judicial demand for objectivity and due process, it is time to rationalize WHT compliance. Section 165 should be omitted, and FBR should rely on system-generated reports, structured reconciliation, and data analytics to enforce withholding obligations in a manner that is both lawful and efficient. Additionally, proceedings under Section 162 should be activated against actual defaulting recipients who evade tax liability, thereby realigning enforcement strategy with fairness, technology, and statutory intention.