Amazon Multi-State GST: Place of Supply in TallyPrime

By TallySutra Team · 25 August 2026 · 6 min read

Sell on Amazon for a quarter and your goods will have crossed more state lines than you have. Every one of those crossings is a GST event: place of supply decides whether a sale carries IGST or CGST plus SGST, and where your inventory sits decides where you must be registered. The MTR hands you the raw data — this guide covers turning it into correct vouchers and knowing when your registration footprint needs to grow.

Place of supply: what the MTR already tells you

For goods, the general rule puts the place of supply where the goods are delivered — which the MTR captures as Ship To State. The tax-type logic then compares two fields that both live in the report:

• Supplying state: the state code embedded in the Seller GSTIN column (the first two digits).
• Destination: the Ship To State column.

Same state, the sale is intrastate — CGST plus SGST. Different states, interstate — IGST. The MTR's own tax columns already reflect this determination on each row, so an import pipeline should preserve Amazon's computed split and verify it against the two state fields, flagging rows where they disagree rather than recomputing silently. Special scenarios (bill-to/ship-to differences, exports) have their own rules; treat the general rule as the default and route oddities to your CA.

The example that makes it concrete

Rows three and four are the multi-state wrinkle: once inventory ships from an FBA warehouse in another state under a registration there, the supplying state changes — and with it, which sales are intrastate.

FBA warehouses and your registration footprint

Storing inventory in an FBA fulfilment centre generally amounts to having a place of business in that state, which is why sellers enrolling warehouses across states typically obtain GST registration in each such state — Amazon itself asks for the relevant GSTINs during FBA enrolment for a state. The operational consequences stack up quickly:

• Each GSTIN files its own returns and needs its own books — in Tally terms, usually one company per GSTIN.
• Amazon issues separate MTR data per Seller GSTIN, and the Seller GSTIN column tells you which registration each row belongs to.
• Moving your own stock between your registrations (into an out-of-state FBA warehouse) is itself a GST-relevant transfer with documentation requirements.

Which states you must register in, and the stock-transfer mechanics, are consequential and fact-specific — decide them with your CA before enrolling warehouses, not after the notices.

Keeping multi-GSTIN books straight in Tally

1. One Tally company (or clearly segregated books) per GSTIN, each importing only its own rows — split by the Seller GSTIN column.
2. Duty ledger discipline: IGST, CGST, and SGST ledgers configured correctly in each company, since a misconfigured duty ledger corrupts every voucher that touches it.
3. Per-GSTIN reconciliation: settlements also need allocating, because one bank deposit can cover orders across registrations.
4. Watch the B2B dimension too — buyer GSTINs add invoice-wise reporting on top of place-of-supply logic, as covered in B2B vs B2C MTR reports.

TallySutra's Amazon to Tally importer reads the Seller GSTIN on every row, keeps batches segregated by registration, verifies the IGST-versus-CGST/SGST split against the state fields, and exceptions any row where the arithmetic and the geography disagree. The features page shows the validation set. The goal is simple to state and hard to do by hand at volume: every voucher in the right company, with the right tax type, provably consistent with the report it came from.

Bringing a new state registration online without breaking the books

The riskiest fortnight in multi-state selling is the one where a new GSTIN goes live: orders start fulfilling from the new state while habits and pipelines still assume the old single-registration world. A short go-live checklist prevents the mess — create the new Tally company with correctly configured duty ledgers before the first order ships; confirm the import pipeline splits rows by Seller GSTIN rather than dumping everything into the original company; agree the stock-transfer documentation with your CA in advance, since your first movement of goods into the new state's warehouse happens before its first sale; and diarise the new registration's return calendar separately. The first month-end after go-live deserves double-checking: verify each company's sales tie to only its own GSTIN's rows and that the intrastate-versus-interstate mix shifted the way the new geography predicts. Sellers who skip this find their original company quietly booking another state's supplies for weeks — an unwinding exercise nobody enjoys.

Frequently asked questions

Related reading

• Automate Amazon Bookkeeping in Tally for Small Sellers
• Amazon Seller Central Reports Every Accountant Needs
• Amazon Cancelled Orders: Accounting Treatment in Tally