Skip to main content

GST & compliance

ERPNext + TCS 206C(1H) After 1 Apr 2025: The Omission & 194Q Boundary (2026)

TCS under 206C(1H) stopped from 1 April 2025; buyer-side TDS under 194Q stayed. How to stop ERPNext collecting it without breaking prior-year entries.

Updated 12 Oct 20269 min readBy ManojFirst published 31 Jul 2026

From 1 April 2025, TCS under section 206C(1H), on the sale of goods, no longer applies (Finance Act, 2025). Section 194Q, the buyer-side TDS on the purchase of goods, stayed. If your ERPNext instance still adds 206C(1H) TCS to receipts after that date, you are collecting a tax that no longer applies and reporting TCS you shouldn't. This guide covers what changed, the 194Q boundary that remains, and how to end-date the old category without breaking prior-year entries.

A repealed tax is more dangerous in an ERP than a new one: nothing errors, the category keeps applying, and every large customer is overcharged until one of them asks why. I lead ERPNext and Frappe programmes at MithTech, a team of Frappe specialists in Bengaluru. Check this one if your categories were set up before 2025 and not reviewed since.

What changed, and what didn't

From October 2020 to March 2025, one high-value goods sale could face two overlapping levies. Section 206C(1H), from 1 October 2020, made a seller whose turnover exceeded ₹10 crore in the preceding year collect 0.1% TCS on receipts above ₹50 lakh from a buyer in the year, at the time of receipt. Section 194Q, from 1 July 2021, made a buyer whose turnover exceeded ₹10 crore deduct 0.1% TDS on purchases above ₹50 lakh from a seller, at credit or payment. Where the buyer deducted under 194Q, the seller did not also collect under 206C(1H).

The Finance Act, 2025 (section 72(c)) ended the overlap: 206C(1H) does not apply from 1 April 2025. From that date the seller collects nothing under it, and only the buyer's 194Q TDS remains. Transactions either side of the date record differently, which an ERP handles badly when the tax category has open-ended validity.

Interactive

What Applies Decider

Select your role and whether the transaction is before or after 1 April 2025 to see whether 206C(1H) TCS, 194Q TDS, both, or neither applies.

No TCS under 206C(1H) — do not collect

From 1 April 2025, section 206C(1H) TCS on sale of goods does not apply (Finance Act, 2025, section 72(c)). As the seller you no longer collect 0.1% on receipts over ₹50 lakh. If ERPNext is still adding it, you are charging your customer a tax that no longer exists — end-date the category.

Checked 2026-10-14: 206C(1H) does not apply from 1 April 2025 (Finance Act, 2025, section 72(c)); 194Q unchanged. Verify the current CBDT position and confirm applicability with your CA.

Are you still collecting it?

The practical question is narrow: does a receipt dated after 31 March 2025 still pick up 206C(1H)? If yes, every large-customer receipt since has been over-charged.

Calculator

Wrongful Collection Checker

Set the receipt date, whether ERPNext still adds 206C(1H), and the buyer's FY receipts to see whether you are collecting a tax that no longer exists and roughly how much.

lakh

You are collecting a tax that no longer exists

On receipts of ₹75 lakh from this buyer, you are adding roughly ₹2,500 of 206C(1H) TCS that is not owed from 1 April 2025. Every such receipt over-charges the customer and creates a TCS liability and return entry you should not be filing. End-date the Tax Withholding Category.

Illustrative: 0.1% on receipts above ₹50 lakh per buyer, the pre-omission 206C(1H) mechanic. Confirm exact figures and any residual obligations with your CA.

How do you end-date it without breaking history?

The instinct, deleting the 206C(1H) category, is wrong. Historic Payment Entries reference it, and prior-year TCS returns depend on it; deleting orphans them. The correct move is a dated rate row that stops collection from 1 April 2025 while leaving every pre-cutover transaction on its original treatment.

Code recipe

Diagnose · End-date · Reconcile · Prevent

Copy-paste the diagnosis, the non-destructive end-date steps, the reconciliation of wrongful collection, and the habits that keep repealed taxes from firing.

Confirm whether ERPNext is still collecting 206C(1H) TCS on post-cutover receipts.

text
1. Accounting > Tax Withholding Category — find the
   206C(1H) / "TCS on sale of goods" category.
2. Check its rate rows and validity dates. If there is
   no row that STOPS collection on/after 1 Apr 2025,
   it is still live.
3. Sample a Payment Entry dated after 1 Apr 2025 for a
   TCS-flagged customer with FY receipts > ₹50L.
   Does it still add 0.1% TCS? If yes → you are
   collecting an omitted tax.
4. Note: 194Q (buyer TDS) categories are UNAFFECTED —
   do not touch those.

0 of 4 steps done

Tick a step’s number when it is done; the ticks stay on this device.

Diagnose

Find the 206C(1H) / "TCS on sale of goods" Tax Withholding Category and check its rate rows and validity dates. Then sample a Payment Entry dated after 1 April 2025 for a TCS-flagged customer with receipts in the year above ₹50 lakh. If it still computes 0.1% TCS, the category is still live. Leave the 194Q buyer-TDS logic alone; only 206C(1H) stopped.

End-date, don't delete

In the category's rate table, add a row with a from-date of 1 April 2025 that stops collection (or set the existing row's to-date to 31 March 2025). Pre-cutover receipts keep their original row; post-cutover receipts pick up nil. This preserves an auditable boundary instead of a destructive change that breaks prior returns.

Verify the boundary

Confirm a Payment Entry dated 31 March 2025 still computes TCS and one dated 1 April 2025 computes none. That single before/after test is what proves the change is correct and dated, not a blanket switch-off that would misstate history.

Reconcile what was already collected

For receipts after the cutover where 206C(1H) was collected, total it up and decide the treatment with your CA: usually a refund or adjustment to the customer and a correction to the TCS statement, depending on whether the amount was already deposited. It is the customer's money; stopping going forward doesn't settle what was collected. Your bank reconciliation shows where refunds land.

When the config was set once and never revisited

Tax categories are usually set up at go-live and then trusted. That works until a Finance Act changes the law, and the person who set up the 206C(1H) category is not the person reading the 2025 Budget. The category keeps applying, and because it produces a plausible number on every large receipt, nobody questions it.

The control is a standing review tied to the statutory calendar. Every Finance Act, someone owns walking the Tax Withholding Categories against the year's changes before the new financial year starts — omissions, rate changes and new sections all land in the same place. Date-bound every category so a rate cannot outlive the law that created it, and add a warning that flags any post-cutover transaction still computing a repealed levy.

Draft policy for your finance lead and CA to ratify. Every TDS/TCS Tax Withholding Category carries explicit validity dates; no category applies a rate with open-ended validity. On each Union Budget / Finance Act, the categories are reviewed against the year's changes before the new financial year begins, and the review is signed off. The 206C(1H) category is end-dated to 31 March 2025 and never deleted, preserving prior-year entries. Any 206C(1H) collected on later receipts is quantified and refunded or adjusted, with the statement corrected as the CA advises. Confirm the current CBDT position and any transitional guidance with your CA before adoption.

End-date it, or delete it?

Delete the category (do not)
Historic entries keep their treatmentPrior-year Payment Entries are orphaned
Prior-year TCS returns still reconcilePrior returns no longer tie to the category
Clean, auditable before/after boundaryNo record of when or why collection stopped
Reversible and explainable to an auditorDestructive and hard to justify
Post-cutover receipts compute nilPost-cutover receipts compute nil — but at the cost of history

At a glance

AspectWhat to know
What stoppedTCS under 206C(1H) on sale of goods, from 1 April 2025
What stayedBuyer-side TDS on purchase of goods (194Q; new numbering under the 2025 Act from 1 April 2026)
ERPNext fixEnd-date the TCS category at 31 March 2025; never delete it
TestA 31 March 2025 receipt computes TCS; a 1 April 2025 receipt doesn't

FAQ: what do people ask most?

Is TCS still applicable on sale of goods in India?

Not under section 206C(1H): the Finance Act, 2025 stopped it from 1 April 2025, so sellers no longer collect 0.1% on receipts above ₹50 lakh from a buyer. Other TCS provisions on specific goods still apply. The buyer-side TDS on purchase of goods (194Q) still applies where its conditions are met.

Why is ERPNext still collecting 206C(1H) TCS after April 2025?

Because the Tax Withholding Category was set up with open-ended validity and never given an end date, so it keeps applying the 0.1% rate after the law stopped it. Nothing errors; the category just keeps applying to later receipts. End-date it with a rate row from 1 April 2025 to stop it.

What is the difference between 194Q and 206C(1H)?

194Q is TDS the buyer deducts on the purchase of goods, at credit or payment, whichever is earlier. 206C(1H) was TCS the seller collected on the sale of goods, at receipt. They fell on opposite parties at different moments. From 1 April 2025 only the buyer-side TDS remains.

How do I stop 206C(1H) TCS in ERPNext without breaking prior years?

Do not delete the category. In its Tax Withholding Category rate table, add a row from 1 April 2025 that stops collection (or set the existing row's to-date to 31 March 2025). Pre-cutover receipts keep their original treatment; post-cutover receipts compute nil. Verify with a receipt each side of the date.

What if we already collected 206C(1H) after 1 April 2025?

That is the customer's money. Total what was collected on later receipts and, with your CA, refund or adjust it and correct the TCS statement; the treatment depends on whether the amount was already deposited. Stopping collection going forward doesn't settle what was taken.

Does the omission affect 194Q compliance in ERPNext?

No. Only 206C(1H) stopped. Leave your 194Q buyer-TDS categories as they are, deducting 0.1% on qualifying purchases, but add rate rows for each new tax year. From 1 April 2026 the Income-tax Act, 2025 renumbers the provision, so review the category names and rows with your CA. The old 194Q-vs-206C(1H) precedence question no longer arises.

What is the bottom line?

A repealed tax that keeps applying is a quiet error, because the number always looks right. Check whether your 206C(1H) category is still live, end-date it at 31 March 2025 rather than deleting it, and settle anything collected since with your CA: it belongs to the customer. Then give every tax category end dates, so the next Finance Act is a scheduled review, not a buyer's complaint.

Your next step

Not sure your ERPNext tax categories kept up with 2025 and 2026?

GST & compliance

Now see GST compliance

Comments & ratings

No comments yet. Start a new discussion.

0

Manoj · Published on 31 July 2026

Worked with us? Leave a Google review

Questions about this? Talk to the team.

Book a 30-minute Google Meet, WhatsApp us, or send a message. The engineer who works on this replies.

Send us a message

Your details go to our team's CRM and are used only to reply.