Flipkart TCS & TDS in Tally: Correct Treatment Guide
Two small percentages quietly leave every Flipkart settlement: GST TCS and income-tax TDS. Individually tiny, they compound into serious money over a year, and both are fully recoverable if your books track them properly. Mis-book them as expenses and you donate them to the exchequer. Here is the correct treatment in TallyPrime.
Two different taxes, two different laws
Sellers often conflate the two deductions because they appear side by side in the settlement report. They are unrelated:
| GST TCS | Income-tax TDS | |
|---|---|---|
| Law | Section 52, CGST Act | Section 194-O, Income-tax Act |
| Rate | 0.5% of net taxable supplies | 0.1% of gross sales |
| Collected by | Flipkart as e-commerce operator | Flipkart as e-commerce operator |
| Where credit appears | GST portal (TCS credit received) | Form 26AS / AIS |
| How you recover it | Accept credit, moves to cash ledger, offsets GST liability | Adjust against income-tax liability or claim refund in ITR |
Rates and mechanics summarised here reflect current law as generally applied; your CA should confirm the position for your specific registrations and any rate notifications in force for the relevant period.
Ledger setup in TallyPrime
Create two asset ledgers, typically under Current Assets or Duties & Taxes as your CA prefers: TCS Receivable (GST u/s 52) and TDS Receivable (u/s 194-O). The critical point is that neither is an expense. TCS is a credit that lands in your GST cash ledger once accepted; TDS is prepaid income tax that reduces your final tax bill. Booking either to P&L overstates costs and loses the audit trail you need to claim them.
Posting from the settlement report
The Flipkart settlement report carries TCS and TDS columns at order-item level. For each settlement group, the entry pattern is: debit bank for Settlement Value, debit fee ledgers and GST-on-fees input ledger, debit TCS Receivable and TDS Receivable for the period totals, credit the Flipkart party ledger for gross. This is the same balanced structure covered in our settlement report explainer; TCS and TDS are simply two more debit legs. Returns reduce net taxable supplies, so TCS on returned items reverses in later settlement rows; item-level posting handles this automatically, monthly lump sums often do not.
Claiming the credits
- GST TCS: each month, Flipkart files its TCS return and the amount appears on the GST portal under TCS credit received. Accept it, and the amount moves to your electronic cash ledger, usable against output GST liability. Reconcile the portal figure against your TCS Receivable ledger; differences usually trace to returns timing or a period cut-off.
- Income-tax TDS: verify the deduction appears in Form 26AS/AIS against Flipkart's TAN. At return time, claim it as prepaid tax. If your final liability is lower, it comes back as a refund.
The reconciliations are where things go wrong in practice. If your ledger says one figure and the portal says another, someone has to trace it to order items, and that requires your books to hold item-level or at least period-matched detail rather than a single annual journal.
Automating the capture
None of this is conceptually hard; it is clerically brutal at volume. TallySutra reads the settlement report you upload from Seller Hub and splits TCS and TDS into their receivable ledgers automatically as part of generating balanced TallyPrime vouchers, so the portal reconciliation becomes a comparison of two reports rather than a forensic exercise. To be precise about scope: TallySutra prepares your books via file upload and Tally XML export; it does not file GST returns or accept TCS credits on the portal for you, and it has no live connection to Flipkart. The features page shows where the tax split fits in the import pipeline, and the same treatment logic applies on other marketplaces too, as covered in our Meesho TCS and TDS guide.
Handled correctly, TCS and TDS are a cash-flow timing cost, not a real cost. Handled sloppily, they become unclaimed credits and portal mismatches that surface at the worst possible time, during an assessment. The ledger discipline described here is what keeps you on the right side of that line; your CA has the final word on the claims themselves.
Keep the supporting trail organised as you go: the settlement reports carrying the TCS and TDS columns, month-wise extracts of the portal's TCS credit statements, and the 26AS snapshots you reconciled against. Assessments for marketplace sellers frequently turn on whether claimed credits can be traced to source documents, and a dated folder per month costs minutes to maintain against days to reconstruct two years later when a notice arrives.
Frequently asked questions
Is Flipkart TCS an expense for the seller?
No. GST TCS collected under Section 52 at 0.5% is a recoverable credit: once Flipkart files its TCS return and you accept the credit on the GST portal, the amount moves to your electronic cash ledger and offsets output GST liability. It should sit in an asset ledger like TCS Receivable, never in the profit and loss account as an expense.
How is TDS under Section 194-O different from GST TCS?
TDS under 194-O is income tax, deducted at 0.1% of gross sales by the marketplace, and appears in your Form 26AS against Flipkart's TAN. GST TCS at 0.5% is a GST-law collection that surfaces on the GST portal. They are recovered through entirely different routes, the income-tax return versus the GST cash ledger, so they need separate receivable ledgers in Tally.
What if the GST portal TCS figure does not match my books?
Differences usually come from returns timing, since TCS reverses when items are returned, or from period cut-offs where a settlement straddles month-end. Trace the difference at order-item level using the settlement report's TCS column. Item-level posting in Tally makes this a quick comparison; lump-sum monthly journals make it painful. Ask your CA before accepting a mismatched credit.
TallySutra turns Amazon, Flipkart and Meesho reports into reconciled, reviewed TallyPrime vouchers — duplicate-safe, with every rupee traceable to its source row.
Book a 30-minute demo