Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
TDS quarterly return reconciliation must match three data sets — books, the return being filed, and Form 26AS credits that eventually appear for deductees — with the Q4 return due May 31 carrying the highest risk because errors affect every deductee's ITR-season credit claim. Late filing attracts a ₹200 per day Section 234E fee capped at total quarterly TDS.
Reconcile in three sequential steps. First, match the TDS ledger to the draft return by section and amount. Second, verify every challan in the return against OLTAS by BSR code, serial number, and deposit date, and confirm deposit dates fall within the correct quarter. Third, after filing, sample-check counterparty Form 26AS entries to confirm credits flow to the correct PANs at the correct sections.
Section-wise TDS ledger export mapped to the return template. OLTAS challan verifier keyed by BSR and serial. Post-filing Form 26AS sampler across deductee PANs.
Error-free quarterly return filed 10 to 15 working days before the deadline, zero Section 234E late fee exposure, and confirmed Form 26AS credits for all deductees before ITR season opens.
TDS quarterly return reconciliation is the process of verifying, before filing, that the TDS deducted in the company’s books matches the return being submitted — and verifying, after filing, that the return data flows correctly into counterparty Form 26AS records. Errors at either stage create compliance exposure and credit disruption for business partners.
2026 Migration Update — From Q1 FY 2026-27 onward, quarterly TDS returns under the Income Tax Act 2025 will be filed using numeric payment codes rather than the familiar 194-series section codes, and deductee certificates will be issued in the new Form 131 format. FY 2025-26 returns and any correction statements for that year continue in the legacy section-code structure. See the payment codes 1001–1092 reference and the Form 131 TDS certificate guide.
What TDS Quarterly Returns Cover
Form 26Q covers non-salary TDS deductions under sections including 194C (contractor payments), 194J (professional fees), 194H (commission), 194I (rent), and 194A (interest). It is filed quarterly by every deductor making these payments. Form 27Q covers TDS on payments to non-residents under Section 195. Both forms follow the same quarterly filing schedule: Q1 due 31 July, Q2 due 31 October, Q3 due 31 January, Q4 due 31 May.
Each quarterly return contains: the deductor’s TAN and PAN, challan details for each tax deposit made during the quarter (BSR code, serial number, date, amount), and a row for each deductee with their PAN, section code, amount paid, and TDS deducted.
Three-Way Reconciliation Process
Step 1 — Books vs Return
Before preparing the return, reconcile the TDS ledger (or accounts payable aging report) against the return data. The total TDS per section in the books must match the return. Common differences arise from payments that span a month-end (accrued but not settled), TDS deducted on advance payments, or manual adjustments posted outside the standard AP workflow.
Step 2 — Return vs Challan Deposits
Each challan in OLTAS must match one or more entries in the return. Verify the BSR code and serial number for each challan deposit against the bank confirmation. TDS deposited on the 7th of the month for the prior month’s deductions must be assigned to the correct quarter in the return. Q1 covers April–June deposits; including a July 7 challan in Q1 is a common error.
Step 3 — Return vs Counterparty Form 26AS
After filing, verify that TDS credits appear in the Form 26AS records of key deductees within 10–15 business days. For large vendors or contractors with significant TDS amounts, this validation confirms the return was processed correctly.
Pre-Filing Validation Checklist
| Validation Step | What to Check | Common Error Found | Tool |
|---|---|---|---|
| Deductee PAN validation | All PANs present and valid | Invalid or missing PAN — FVU rejects | NSDL PAN verification or TRACES |
| Challan deposit verification | BSR code + serial match OLTAS | Transposed digits, wrong quarter | OLTAS challan inquiry |
| Section code assignment | Correct section for each payment type | 194J vs 194C confusion on mixed contracts | AP category mapping |
| Duplicate deductee rows | No deductee appears twice in same challan | Copy-paste errors in return preparation | RPU duplicate check |
| Aggregate amount per deductee | Sum of rows matches challan total | Rounding differences across rows | Cross-totalling in RPU |
Quarterly Filing in Practice
The Q4 return (January–March, due 31 May) carries the highest risk because it immediately precedes ITR season for most deductees. Companies that begin ITR preparation in June rely on Form 26AS credits from all four quarters being accurate. A Q4 return filed with PAN errors or challan mismatches creates a gap in Form 26AS credits that affects deductees’ claims in June and July.
Starting reconciliation preparation 10–15 working days before the 31 May deadline allows time to verify deductee PANs through TRACES portal, resolve any challan status issues, and validate the FVU file before uploading. Organisations with 200+ deductee rows per quarter find that manual reconciliation through VLOOKUP-based spreadsheets breaks down at this scale. TDS reconciliation software that maps AP data to TDS section codes, validates PANs against TRACES in bulk, and cross-checks challan deposits against OLTAS records reduces Q4 preparation time materially. Reconciliation software India platforms purpose-built for Indian compliance handle the three-way reconciliation — books, return, and Form 26AS — in a single workflow rather than across three separate tools.