GST input credit ecommerce: stop the quiet leak
Input tax credit is real money sitting in your ledger. On marketplaces it leaks quietly, through mismatched invoices and lazy reconciliation. Here is how the mechanics actually work, and the monthly ritual that keeps your working capital clean.
- Input tax credit only survives if your purchase invoices match what your suppliers actually filed. Matching is the whole game.
- Marketplaces collect TCS on your sales. That credit is claimable, but only after you reconcile it against the collector statements.
- Run reconciliation monthly, not at year end. Clean ITC is working capital you already earned.
Most sellers treat GST as a filing chore. Something the accountant does near the deadline. That is exactly how input tax credit leaks.
On marketplaces the leak is worse, because your transactions are high volume, spread across states, and mixed with platform deductions you did not initiate. If you are not reconciling every month, you are almost certainly losing credit. And lost credit is lost cash.
Let us walk the mechanics.
How input tax credit works, in plain terms
When you buy inventory, packaging, or services for your business, you pay GST on that purchase. When you sell, you collect GST from the customer. Input tax credit is the mechanism that lets you set the tax you paid against the tax you owe. You remit the difference.
The catch is that the credit is not automatic just because you hold an invoice. The credit only becomes usable when your supplier has reported that same invoice in their own return. Your claim has to match their declaration. No match, no clean credit.
This is why your relationship with suppliers is also a compliance relationship. A supplier who files late or files sloppily is costing you money, even if their product is fine.
TCS: the marketplace layer
Marketplaces are required to collect a small slice of tax at source on the taxable value of your sales. They deposit it against your GSTIN and file a collector statement. That collected amount is a credit you can claim.
But it does not claim itself. You have to reconcile the platform statement against your own sales records. Where sellers go wrong is assuming the marketplace numbers are gospel. They are usually close. Close is not exact. Returns, cancellations, and settlement timing all create small gaps that add up across thousands of orders.
This ties directly into your settlement discipline. The same order flow that drives your payout also drives your tax position. Reconcile them together, not in separate silos. A seller who reconciles settlement and tax as one exercise catches gaps that either view alone would miss.
There is a timing point worth understanding. TCS credit becomes usable to you only after the platform files its collector statement and the amount reflects against your GSTIN. So a sale in one month may show as a claimable credit only in a later cycle. If you match your books against the wrong period, the numbers will never line up. Anchor to the period the credit actually appears, not the period the sale happened.
Matching GSTR-2B
Your auto-populated statement is the reference point for what credit the system believes you are entitled to. Your job is to match your books against it, line by line, every month.
Three things happen in that match:
- Invoices in your books that appear in the statement. Good. Claimable.
- Invoices in your books that do not appear. A supplier problem. Chase it.
- Invoices in the statement that are not in your books. A recording gap on your side, or a duplicate.
The discipline is boring and that is the point. Sellers who skip it discover the gap only at year end, when suppliers have moved on and corrections are hard.
Where credit actually leaks
A few patterns show up again and again.
| Leakage | What causes it |
|---|---|
| Mismatched invoices | Supplier files under wrong GSTIN, wrong invoice number, or late |
| Blocked credits | Purchases that are simply not eligible under the current rules |
| Ignored TCS | Platform-collected tax never reconciled or claimed |
| Return mismatches | Credit notes not synced between your books and the platform |
Blocked credits deserve a note. Some categories of expense are not eligible for credit at all, regardless of how clean your invoice is. The exact list shifts, so check the current rules rather than assuming last year’s treatment still holds.
The reconciliation ritual
Make it a fixed monthly routine, on a set date, owned by one person.
- Pull your purchase register for the period.
- Pull the auto-populated statement.
- Match line by line. Flag every mismatch.
- Pull the marketplace TCS and collector statements. Reconcile against your sales and settlement reports.
- Chase suppliers on missing invoices before the window closes.
- Record what you claimed, what you deferred, and why.
That last step matters. A clean audit trail turns a future notice from a panic into a lookup.
When to bring in a CA
The monthly matching is operational. A trained ops person with a decent reconciliation tool can run it. What you outsource to a professional is judgment: eligibility questions, blocked credit disputes, notices, and annual returns.
Think of the CA as your check against the current rules, because GST treatment on categories and rates does change. On the mechanics side, this is exactly the kind of hygiene our Amazon India Account Management engagements build into the monthly rhythm, so tax reconciliation is not a year-end scramble.
Why this protects working capital
Every rupee of credit you fail to claim is a rupee of cash you earned and then abandoned. On marketplace margins, where your unit economics are already tight, that leak decides whether a month clears profit. Clean ITC is not a compliance nicety. It is working capital you already have a right to.
Start next month
Pick a date. Assign one owner. Match your purchase register against the auto-populated statement, reconcile the platform TCS, and write down every gap. Do it twelve times a year and the year-end clean-up disappears. Skip it, and you are financing the government with money that is legally yours.