FICO India TDS Part 2: Postings, Advances, Thresholds and Exemptions

📌 KEY POINTS
✅ On invoice posting, TDS reduces the vendor liability and credits a TDS payable account per section.
✅ On an advance payment, payment-based TDS is deducted; when the invoice is later cleared against the advance, double deduction must be avoided.
✅ Threshold-based sections deduct only once cumulative payments cross the limit, which needs tracking per vendor and year.
✅ Lower or nil deduction certificates change the rate for a period and amount limit.
⚠️ Reversing an invoice must reverse its TDS — otherwise the TDS payable and the return disagree.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 1 configured TDS. Part 2 follows it through daily postings.

━━━━━━━━━━━━━━━━━━━━
▶ 1. INVOICE DEDUCTION
When a vendor invoice is posted, SAP proposes the withholding types active for the vendor, calculates the base and posts TDS: the vendor is credited with the net amount and the TDS payable account with the deducted amount. The withholding tax data on the line item shows type, code, base and amount and later feeds challans and returns.

━━━━━━━━━━━━━━━━━━━━
▶ 2. ADVANCES AND CLEARING
An advance (down payment) to a vendor triggers the payment-based type, deducting tax at payment. When the final invoice is posted and the down payment cleared, configuration and correct posting must ensure that the invoice does not deduct tax again on the part already taxed. Testing this clearing is one of the most important TDS test cases.

━━━━━━━━━━━━━━━━━━━━
▶ 3. THRESHOLDS
Some sections require deduction only after cumulative payments to a vendor in a financial year exceed a limit, or a single payment exceeds a limit. SAP supports threshold checks on the withholding code, but cumulative tracking must be correct across company codes and periods within the legal entity. Teams often supplement this with a report that shows vendors approaching thresholds.

━━━━━━━━━━━━━━━━━━━━
▶ 4. EXEMPTIONS AND CERTIFICATES
A vendor may present a certificate for lower or nil deduction from the tax department, valid for a period and an amount. In SAP this is maintained as an exemption on the vendor's withholding data with rate, validity dates and certificate number. Once the amount or period is exhausted, normal deduction resumes, so monitoring is needed.

━━━━━━━━━━━━━━━━━━━━
▶ 5. REVERSALS AND CORRECTIONS
If an invoice is reversed, its TDS is reversed too, and the reversal must happen before the challan is deposited, or the correction is handled in the next return as a correction statement. Corrections after filing are time-consuming, so validation at posting is far better than repair later.

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

1. Post a vendor invoice with TDS and display the withholding data.
2. Post an advance with TDS, then the final invoice clearing the advance.
3. Confirm no double deduction occurred on the cleared portion.
4. Maintain a test exemption certificate and post an invoice under it.

✅ CHECKPOINT: invoice, advance, clearing and exemption cases all produce the correct TDS once.

Quarterly returns showed TDS deducted twice for several contractors. Advances had been taxed at payment, and when invoices were posted the users cleared advances in a separate step, so the invoice deduction ran on the full amount. The posting procedure was changed to clear down payments during invoice entry, and a monthly report now flags vendors with TDS exceeding the expected rate on total payments.

• Double deduction when advances are cleared.
• Thresholds tracked manually and missed.
• Expired exemptions still applied.
• Reversing invoices after challan deposit without a correction plan.

• Test advance and clearing as a core TDS case.
• Report vendors near thresholds.
• Exemptions with validity and amount monitoring.
• Validate TDS before month-end deposit.

Expect questions on how double deduction on advances is avoided, how thresholds are handled and how exemption certificates are maintained.