GSTR-2B Reconciliation of Marketplace Fee ITC
Marketplaces bill you relentlessly — commission on every order, closing fees, weight-handling fees, ad campaigns, storage. Each of those invoices carries GST you can generally claim as input tax credit. But since ITC claims are anchored to GSTR-2B, the auto-drafted statement built from your suppliers' filings, the credit is only safely yours when the marketplace's invoice shows up there and matches your books. This article lays out a working reconciliation routine for marketplace fee ITC.
GSTR-2A vs GSTR-2B: know which one governs
Both are auto-drafted ITC statements, but they behave differently. GSTR-2A is dynamic — it keeps changing as suppliers file or amend. GSTR-2B is static: generated for each month, it does not change afterwards, which is what makes it usable as the claiming baseline. Practical rule: use 2B to decide the month's claim, and use 2A to investigate history when something is missing.
Where marketplace fee invoices hide
The reconciliation is only as good as your invoice collection. Marketplaces issue tax invoices for their fees inside seller portals — typically monthly commission invoices, separate ad invoices, and sometimes distinct invoices from different group entities (the selling-services entity, the ads entity, the logistics entity may bill under different GSTINs). Build a monthly download checklist per platform, because an invoice you never downloaded is an invoice you will never match.
The monthly matching routine
- Book every fee invoice from Amazon, Flipkart, and Meesho into your purchase ledgers with the supplier GSTIN, invoice number, taxable value, and GST amount.
- Download GSTR-2B for the month from the portal.
- Match on GSTIN + invoice number + tax amount. Tolerate rounding paise; investigate anything else.
- Classify the differences — that is the real work (table below).
- Claim in GSTR-3B only what is matched and eligible; park the rest for follow-up.
| Difference | Likely cause | Action |
|---|---|---|
| In books, not in 2B | Marketplace filed late, or billed your GSTIN incorrectly | Defer the claim; check next month's 2B; raise with seller support if it persists |
| In 2B, not in books | Invoice never downloaded or booked — commonly ads or storage invoices | Retrieve the invoice, book it, claim once matched |
| Amount mismatch | Credit note netted on one side only, or booking error | Re-check invoice PDF vs books; correct the wrong side |
| Wrong GSTIN (multi-state sellers) | Fees billed to a different state registration than the one booking them | Move the booking to the right GSTIN's books; fix the seller-portal GSTIN mapping |
Deferred claims need a home of their own. When an invoice sits in books but not in 2B, the claim moves to next month — and without a tracking mechanism, deferred credits are quietly forgotten. Keep a rolling deferred-ITC register: invoice, supplier GSTIN, amount, months checked, and status. Review it every filing cycle and sweep it hard before the annual claiming cutoff, because credit that never got claimed in time is simply lost. The register also becomes your evidence trail if a claimed credit is later questioned.
Eligibility still applies after matching
Appearing in 2B is necessary, not sufficient. The standard conditions for ITC still govern: you hold a valid tax invoice, the service was received, tax was paid to the government by the supplier, and you file your returns. Also watch for platform-issued credit notes against earlier fee invoices — these appear in 2B as reductions and require corresponding ITC reversal in your claim. Our piece on ITC on marketplace commission and fees goes deeper into eligibility questions.
Scaling this beyond a spreadsheet
A seller on three marketplaces easily faces dozens of fee invoices monthly across multiple billing entities, plus thousands of order-level fee lines inside settlement reports that must tie back to those invoices. Doing this in a spreadsheet each month is where ITC leaks. TallySutra imports Flipkart, Meesho, and Amazon reports and generates balanced TallyPrime vouchers with fees split to expense ledgers and their GST components posted separately, reconciled against settlements — so your books carry a clean, claimable fee-GST trail ready to stand against 2B. The full workflow, including the exception queue for unmatched rows, is on our features page.
Keep the caveats in view
ITC rules — blocked credits, reversal triggers, time limits for claiming — carry conditions this article does not exhaust, and they get amended. Treat this as an operational routine, not legal advice, and have a qualified CA or tax professional confirm eligibility and reversals before you finalise each month's claim.
Frequently asked questions
Why claim ITC from GSTR-2B instead of GSTR-2A?
GSTR-2B is a static monthly statement that does not change after generation, making it a reliable claiming baseline. GSTR-2A is dynamic and keeps updating, so it is better used for investigating missing or amended invoices.
A marketplace fee invoice is in my books but not in 2B. Can I claim it?
The safe practice is to defer the claim until it appears in 2B, since ITC claims are anchored to that statement. Chase the marketplace if it stays missing, and let your CA decide edge cases.
Why do Amazon or Flipkart invoices show different GSTINs in 2B?
Marketplace groups often bill through separate entities for selling services, advertising, and logistics, each with its own GSTIN. Match invoices entity-wise rather than expecting one supplier GSTIN per platform.
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