FICO India TDS Part 4: TCS on Sales and Managing Annual Rule Changes

📌 KEY POINTS
✅ TCS is collected by the seller from the buyer on specified sales and deposited like TDS.
✅ In SAP it uses withholding tax on the customer side, often added to the invoice amount and posted to a TCS payable account.
✅ Some purchases of goods are covered by TDS on the buyer side; rules define which applies so tax is not collected and deducted twice.
✅ Finance Acts regularly change sections, rates and thresholds, so codes must be versioned and tested each year.
⚠️ Changing a rate in an existing code affects open items and reports — create new codes or validity periods instead.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
This final part covers the sales side and how to keep TDS/TCS current year after year.

━━━━━━━━━━━━━━━━━━━━
▶ 1. WHAT TCS IS
For specified goods and transactions, the seller must collect tax from the buyer at source and deposit it. Unlike TDS, which reduces what the payer pays, TCS increases what the buyer pays. Scope has changed several times through Finance Acts, so the list of applicable cases must be confirmed with the tax team each year.

━━━━━━━━━━━━━━━━━━━━
▶ 2. SAP SETUP
TCS uses withholding tax types and codes for customers, with customer master settings similar to vendor TDS. On a sales invoice the TCS amount is added to the receivable and credited to a TCS payable account. Deposits, challans, certificates and quarterly returns follow the same pattern as TDS, with separate forms.

━━━━━━━━━━━━━━━━━━━━
▶ 3. INTERACTION WITH TDS ON GOODS
Where a buyer is required to deduct TDS on purchase of goods and the seller would otherwise collect TCS on the same transaction, the law defines precedence so that tax is not applied twice. In SAP this is handled through customer and vendor flags and declarations collected from trading partners. Without clear rules, both sides may apply tax, creating disputes.

━━━━━━━━━━━━━━━━━━━━
▶ 4. ANNUAL CHANGES
Each Finance Act can introduce new sections, change rates or thresholds, or remove provisions. The safe approach is to maintain changes as new withholding codes or with validity dates, test postings and returns in a sandbox, and update vendor and customer assignments with a mass change, all before the effective date — usually the start of the financial year.

━━━━━━━━━━━━━━━━━━━━
▶ 5. GOVERNANCE
Keep a register of all withholding codes with section, rate, validity and owner. After each change, run test cases for invoices, advances, clearing, thresholds and exemptions, and compare a sample quarter's return extract before and after. This turns a stressful annual exercise into a routine one.

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

1. List current TCS cases with the tax team.
2. Configure a customer withholding type and code for one case in test.
3. Post a sales invoice and check the receivable and TCS payable.
4. Create a change plan template for the next Finance Act.

✅ CHECKPOINT: TCS posts correctly and a repeatable plan exists for annual rule changes.

After a Finance Act change, a team edited the rate in an existing withholding code mid-year. Reports and corrections for earlier quarters suddenly showed the new rate, and open items calculated differently. They reverted the change, created a new code valid from the effective date and mass-updated vendors, keeping history intact.

• Editing rates in existing codes instead of new codes or validity.
• No declarations from trading partners on TDS/TCS precedence.
• Applying changes after the effective date.
• Treating TCS as a pricing condition only, without withholding reporting.

• Code register with section, rate, validity and owner.
• Annual change plan with sandbox testing.
• Mass updates of master data before the effective date.
• Clear partner declarations for precedence rules.

Interviewers ask how TCS differs from TDS in postings, how double application with TDS on goods is avoided, and how you manage annual changes without breaking history.