TDS Decimal Paisa Settlement Mandate (Section 288B / TRACES System): Complete Compliance Guide for CAs & CFOs
Statutory Framework & Legal Background
Recent technological and backend updates by the Central Board of Direct Taxes (CBDT) on the TRACES portal have effectively eliminated automatic rounding off of Tax Deducted at Source (TDS) and Tax Collected at Source (TCS) challan matching down to the nearest rupee. Under the operational mechanics of Section 288B of the Income Tax Act, 1961, tax amounts computed on invoices were historically rounded off to the nearest multiple of ten paisa or one rupee. However, automated validation checks on OLTAS (Online Tax Accounting System) and TRACES now strictly enforce exact decimal matching between the deducted amount and the deposited challan paisa.
When deductors file quarterly statements via Form 24Q, 26Q, 27Q, or 27EQ, any fractional discrepancy—such as a tax liability of ₹1,234.30 matched against a rounded challan payment of ₹1,234.00—triggers an automated default under Section 201(1) for short deduction, alongside interest liability under Section 201(1A) at 1% or 1.5% per month. Furthermore, these unresolved paisa differentials accumulate across hundreds of line items, generating high volumes of automated mismatch notices that demand manual revision, generating compliance friction for Chartered Accountants and corporate finance teams.
Failure to reconcile these minor fractional balances can also complicate the issuance of Form 16/16A certificates, leading to mismatches when deductees claim credit in their respective Income Tax Returns (ITRs). This creates downstream compliance risks and disputes regarding credit matching under Section 199 read with Rule 37BA.
Scope of Expansion & Applicability Matrix
The exact paisa settlement mandate applies universally across all corporate deductors, deductors other than companies, banks, government offices, and non-resident entities executing withholding tax obligations under Chapter XVII-B of the Income Tax Act, 1961. The applicability matrix covers various transaction types:
- Section 192: Salary payments involving complex monthly apportionments and pro-rata calculations where fractional rupees frequently occur.
- Section 194C & 194J: Contractor payments and professional fees where running bills, retention moneys, and GST split-ups generate exact decimal figures.
- Section 194Q & TDS on Goods: High-volume purchase transactions where percentage-based deductions generate multi-decimal paisa figures.
- Foreign Remittances (Section 195): Cross-border payments involving exchange rate conversions that inherently result in exact fractional paisa amounts.
Step-by-Step Operational & ERP Workflow
To prevent short-deduction demands and manual reconciliation bottlenecks, finance teams must update their Enterprise Resource Planning (ERP) and accounting software workflows using the following operational framework:
- Disable Automatic Integer Rounding: Configure SAP, Oracle, Tally Prime, or Zoho Books to compute and store TDS exact figures up to two decimal places rather than rounding off at the voucher generation stage.
- Implement Buffer Challan Funding: Adopt a proactive buffer payment strategy where advance tax challans or general TDS deposits include an unallocated buffer amount (e.g., ₹50 to ₹500 depending on volume) to absorb cumulative decimal variances.
- Automate Challan-to-Invoice Mapping: Utilize automated matching tools to map exact paisa liabilities to specific challan serial numbers (BSR code, challan identification number, and deposit date) prior to generating FVU files.
- Regular TRACES Dashboard Audits: Perform fortnightly reviews of the online default summary on the TRACES portal to identify fractional short-payment flags before quarterly returns are finalized.
Comparative Compliance Analysis
| Compliance Parameter | Previous Practice (Rounded System) | New Mandate (Exact Paisa Matching) |
|---|---|---|
| Tax Computation | Rounded off to the nearest rupee under Section 288B. | Calculated and retained in exact paisa (two decimal places). |
| Challan Deposition | Payments rounded to whole rupees. | Challan amount must match exact fractional liability. |
| TRACES Validation | Accepted minor rounding variances without raising defaults. | Flags fractional short-deductions and generates Section 201 notices. |
| Reconciliation Effort | Minimal; automated rounding aligned totals effortlessly. | High; requires manual tracking or buffer deposits to clear paisa gaps. |
Action Plan Checklist for Finance & Audit Teams
Execute the following verified checklist items to safeguard your organization against avoidable TDS default notices:
- ✔ ERP Parameter Review: Inspect accounting software settings to ensure tax calculation modules capture two decimal places without automatic rounding plugins.
- ✔ Buffer Pool Allocation: Establish a designated subsidiary ledger for unallocated TDS buffer deposits to absorb fractional rounding discrepancies.
- ✔ Deduction vs. Deposit Reconciliation: Mandate a pre-filing reconciliation report matching line-by-line deduction paisa with deposited challan amounts.
- ✔ Staff Training: Train accounts payable and taxation teams on the operational mechanics of the TRACES exact-match validation rules.
- ✔ Vendor Contract Review: Ensure purchase orders and invoicing terms account for exact withholding tax computations to eliminate billing disputes.