FICO India TDS Part 3: Challans, Certificates and Quarterly Returns

📌 KEY POINTS
✅ Deducted TDS must be deposited by the due date using a challan; the challan details are then linked to the deductions it covers.
✅ Certificates (Form 16A for non-salary TDS) are generated from the return data and issued to deductees.
✅ Quarterly returns report every deduction per section with deductee PAN and challan details.
✅ The TDS payable account must reconcile with deductions, challans and returns each month and quarter.
⚠️ Deductions without matched challan details lead to defaults in the return processing and demands.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Parts 1–2 posted deductions. Part 3 turns them into deposits, certificates and returns.

━━━━━━━━━━━━━━━━━━━━
▶ 1. MONTHLY DEPOSIT
After month end, deductions per section and TAN are summed and the tax is paid to the government using a challan. In SAP, the payment is posted against the TDS payable accounts. Late deposit attracts interest, so the payment run for TDS is part of the monthly close calendar.

━━━━━━━━━━━━━━━━━━━━
▶ 2. UPDATING CHALLAN DETAILS
Once the challan is paid, its identification details (such as bank, date and serial number) are recorded in SAP and linked to the deductions it covers. India localisation provides programs for challan update and certificate printing. This linkage is what lets the quarterly return state which challan paid which deduction.

━━━━━━━━━━━━━━━━━━━━
▶ 3. CERTIFICATES
Deductees receive TDS certificates — Form 16A for non-salary deductions — which are generated from the official system based on the filed return. SAP provides the data to prepare and track them. Vendors depend on these to claim credit, so missing or wrong certificates create supplier escalations.

━━━━━━━━━━━━━━━━━━━━
▶ 4. QUARTERLY RETURNS
The non-salary TDS return for residents reports each deduction with deductee PAN, section, amount and challan details. Data is extracted from SAP, validated with the official validation utility and filed. Errors such as invalid PANs or unmatched challans cause defaults that must be corrected through correction statements.

━━━━━━━━━━━━━━━━━━━━
▶ 5. RECONCILIATION
Monthly, reconcile the TDS payable balance with deductions minus deposits. Quarterly, reconcile return totals with GL deductions and challans, and after processing, check the official statement for defaults. TCS on sales follows a similar cycle with collection instead of deduction.

━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP

1. Sum one month's deductions per section and TAN and post the deposit.
2. Update challan details against the covered deductions.
3. Extract the quarter's data and check PANs and challan links.
4. Reconcile the TDS payable account to zero after deposit.

✅ CHECKPOINT: every deduction in the quarter is linked to a challan and appears in the return.

A quarterly return was processed with defaults because challans were paid on time but never updated against the deductions in SAP, so the return extract showed deductions without challans. The team built a month-end step to update challan details immediately after payment and a pre-filing check that blocks the extract if any deduction lacks a challan.

• Paying challans without updating details in SAP.
• Invalid PANs discovered only at filing.
• TDS payable account not reconciled monthly.
• Late deposits without a close calendar.

• Deposit and challan update as fixed close steps.
• PAN validation at vendor creation.
• Pre-filing checks for unmatched deductions.
• Quarterly reconciliation and default follow-up.

Interviewers ask how challans are linked to deductions in SAP and how you make sure the quarterly return reconciles with the books.