GST Rate Differences on Marketplace Invoices
Sooner or later every marketplace seller finds it: the platform's tax report shows a GST rate on some orders that does not match what the books say the product attracts. Maybe hundreds of orders went out at the wrong rate before anyone noticed. Rate differences are not cosmetic — the customer invoice the marketplace generated in your name carries that rate, and your GST liability follows the law, not the invoice. This article explains where rate differences come from, how to find them fast, and what fixing them involves.
Where rate differences are born
- Wrong HSN on the listing. The platform derives the rate from the listing's tax classification. A guessed or outdated HSN applies the wrong rate to every order of that SKU — the deep dive is in our HSN guide for marketplace sellers.
- Rate notifications changing under you. GST rates get amended; a listing correct at creation can become wrong after a notification, until someone updates it.
- Value-dependent rates. Some goods (apparel and footwear are the classic examples) have historically carried different rates by value band. Discounted selling prices crossing a band boundary flip the applicable rate order by order.
- Bundles and freebies. Kits combining items with different rates raise composite-versus-mixed supply questions the platform's engine resolves one way and your CA might resolve another.
- Books-side errors. Sometimes the marketplace is right and your item master is wrong. The comparison catches both.
The liability asymmetry every seller should understand
Your obligation is to pay the legally correct tax on each supply. The two error directions are not symmetric:
| Scenario | Consequence |
|---|---|
| Invoice charged a lower rate than legally applicable | You still owe the difference; the shortfall is your cost unless recovered, plus interest exposure |
| Invoice charged a higher rate than legally applicable | Excess collected must be handled per law — it cannot simply be pocketed; refunds and adjustments have rules |
Either way, the exposure compounds silently with volume, which is why detection speed matters more than perfection.
Rate errors also have a commercial face. Marketplace display prices are tax-inclusive, so a listing carrying too high a rate quietly inflates your customer price and costs you conversions against correctly classified competitors, while too low a rate wins sales whose margin evaporates when the differential surfaces later. When you do correct a listing, record the correction date carefully — it becomes the boundary between the old exposure and the clean period, and every subsequent reconciliation and audit answer will lean on it. A dated log of classification changes is one of the cheapest audit artefacts you can maintain.
A detection routine that actually scales
- Maintain a master rate map: SKU → HSN → expected rate, dated, with CA sign-off for material SKUs.
- Each month, compare the marketplace tax report's applied rate per order line against the master. Every deviation is either a listing bug, a value-band effect, or a master error.
- Triage by SKU, not by order. A thousand mismatched orders are usually five mismatched SKUs.
- Fix the listing first — it stops the bleeding — then decide historical treatment with your CA.
- Correct the books and returns as advised: the treatment of past under- or over-charged orders (payment of differential, credit notes, amendments) is a professional-judgment area.
Making the comparison automatic
Step 2 is a per-line comparison across every order — spreadsheet-hostile, software-trivial. When TallySutra imports Amazon, Flipkart, and Meesho reports, it books each line at the rate the marketplace actually applied and keeps vouchers balanced against settlements; lines that fail validation or do not match expectations land in the exception queue for review instead of being silently posted. That gives you an auditable record of what was charged versus what your books expected — the raw material for the conversation with your CA. Rate-related divergences are one of the mismatch families covered in our broader guide to GST mismatches.
Boundaries of this article
Deliberately absent here: current rate values for any product category, because rates change by notification and quoting them is how articles become misinformation. Classification and the treatment of historical errors are legal questions with real money attached — engage a qualified CA or tax professional before paying differentials, issuing corrective documents, or amending returns. For the surrounding return-filing context, see our GSTR-1 guide.
Frequently asked questions
The marketplace charged the wrong GST rate on my orders. Who is liable?
You are — the invoice is issued in your name and your liability follows the legally correct rate. If a lower rate was charged, the differential is your exposure; if higher, the excess has its own prescribed treatment. Take both to your CA.
Why would the same SKU show different GST rates on different orders?
Value-dependent rate bands are the usual cause: goods whose rate varies by sale value flip bands when discounts move the price. Bundles and rate notifications taking effect mid-month produce the same symptom.
What is the fastest way to find rate errors across thousands of orders?
Compare applied rates in the marketplace tax report against a SKU-to-expected-rate master, then triage by SKU — a large mismatch count usually collapses into a handful of misclassified listings.
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