TCS without POS-specific config | HelloBooks POS POS inherits TCS rules from your existing entity-level configuration. No second tax table to maintain, no manual “add TCS line” at the till — the cashier just settles, the engine applies the right rate.
TCS without POS-specific config
POS inherits TCS rules from your existing entity-level configuration. No second tax table to maintain, no manual “add TCS line” at the till — the cashier just settles, the engine applies the right rate.
Part of HelloBooks POS · Compliance & tax (India)
Section 206C TCS at retail-grade volume is a configuration problem more than a calculation problem — different rates for different goods, different thresholds per buyer, different exemptions. HelloBooks already solves that for the back office; the till just inherits the same setup.
Every detail, dialled in
Built for the till, validated against the canonical accounting engine — so every POS sale closes the books cleanly.
Engine-level rate resolution
Items carry a TCS section reference; customers carry a PAN-aware threshold counter; the engine resolves the right rate at settle. The cashier never picks a TCS rate at the till.
- Per-item TCS section
- Per-customer threshold counter
- Exemption handled by the engine
- No till-level TCS UI
Threshold tracking across outlets
TCS thresholds are per buyer-PAN — and that buyer might shop at three outlets. The engine tracks cumulative purchases by PAN; the right outlet starts collecting TCS the moment the threshold is crossed.
- PAN-level cumulative tracking
- Cross-outlet awareness
- Threshold config per section
- Auto-apply when crossed
TCS returns covered
Form 27EQ rolls up POS + back-office TCS together. No POS-only return, no parallel reconciliation.
- Form 27EQ aggregates POS
- Quarterly return ready
- Customer 27D auto-issued
- TRACES sync intact
Why teams move off legacy tills
- POS does not know TCS
- Cashier types TCS amount manually
- Cross-outlet thresholds untracked
- 27EQ misses POS sales
- Engine resolves TCS at settle
- PAN-level cumulative tracking
- Cross-outlet by default
- 27EQ covers POS + back-office
Questions, answered
Where is TCS configured?
Once, on the entity, in the back-office TCS module. The till inherits the same setup — there is no POS-specific TCS configuration to maintain.
How is the threshold tracked?
Per buyer-PAN, cumulatively across all outlets. The engine knows how much that buyer has bought from your entity this financial year.
Does this cover Section 206C(1H) collection by the seller?
Yes. The seller-side aggregate-turnover threshold is checked at the entity level, and individual buyer thresholds are checked at settle.
Where does the customer see the TCS line?
On the printed receipt, the e-invoice payload, and Form 27D. Clean, auditable, no surprise.
Related POS features
Ready to automate your books?
Join 2,000+ businesses saving 20+ hours per month. Get started free — no credit card required.