Amazon B2B vs B2C MTR Reports: GST Treatment Explained
Sellers enrolled in Amazon Business receive orders from GST-registered buyers, and Amazon splits the tax reporting accordingly: the Tax Document Library offers the MTR in two variants, B2C and B2B. They look similar, but they feed different tables of your GST returns and carry different compliance stakes. Treating B2B rows like B2C rows is one of the quieter ways sellers earn notices, so here is the split in full.
What separates the two reports
The B2C MTR covers supplies to unregistered consumers — the columns include Seller GSTIN, Invoice Number, Invoice Date, Transaction Type (Shipment/Refund/Cancel), Order ID, SKU, Quantity, Ship To State, Tax Exclusive Gross, IGST/CGST/SGST rate and tax, and Invoice Amount. The B2B MTR covers supplies to buyers who provided a GSTIN at purchase, and it additionally identifies the buyer's registration details, because these transactions must be reported invoice-wise with the counterparty's GSTIN. That buyer GSTIN is exactly what lets your customer claim input credit — which is why B2B accuracy matters to someone other than you.
Why the split matters in GSTR-1
GSTR-1 reports registered-buyer supplies invoice-by-invoice with buyer GSTINs, while consumer supplies are reported in consolidated form. The practical consequences:
- A B2B invoice with a wrong or missing buyer GSTIN blocks your customer's credit and invites correction requests.
- B2B invoices flow to the buyer's GSTR-2B, so your filing is visible to your customer's accountant — errors do not stay private.
- E-invoicing obligations can apply to B2B supplies once your turnover crosses the notified threshold; whether and when they apply to you is a question for your CA.
Exact table-level disclosure and any threshold questions should be confirmed with your CA — the reports give you the data, not the filing positions.
Import implications in Tally
| B2C rows | B2B rows | |
|---|---|---|
| Party handling | Consolidated retail party or state-wise parties | Buyer identified with GSTIN for invoice-wise reporting |
| GSTR-1 flow | Consolidated disclosure | Invoice-wise with buyer GSTIN |
| Error blast radius | Your return only | Your return and your buyer's ITC |
| Volume | Usually high | Usually lower, higher stakes per row |
Both files import the same mechanical way — group rows by invoice, preserve tax splits and place of supply — but the B2B path needs the buyer registration data carried into the voucher so Tally's GST reports can disclose invoice-wise. If you import only the B2C file, your Amazon Business sales silently vanish from the B2B side of your return.
A monthly routine for dual-report sellers
- Download both MTR variants for the month; if the B2B file is empty, archive it anyway as evidence of nil B2B supplies.
- Import B2C and B2B batches separately so voucher-level reporting stays clean.
- Spot-check a handful of B2B vouchers for buyer GSTIN accuracy before filing.
- Reconcile the combined sales against settlements as usual — settlement files do not care whether an order was B2B or B2C.
TallySutra's Amazon to Tally import detects which MTR variant you uploaded, applies the appropriate party and reporting treatment, and holds rows with malformed or missing buyer GSTINs in the exception queue rather than importing them as consumer sales — the failure mode that causes the most rework at filing time. For the place-of-supply logic that both report types share, see multi-state GST and place of supply.
B2B pitfalls that surface at filing time
Three failure patterns account for most B2B rework. The first is the silent-merge: a pipeline that ignores the report variant imports B2B rows as consumer sales, GSTR-1's invoice-wise section under-reports, and the error surfaces only when a buyer's accountant calls about missing credit — weeks later, with an amendment now required. The second is the malformed GSTIN: a buyer's registration that fails validation should stop the row at import, because filing it invalid helps nobody and correcting a filed return costs far more than resolving one held exception. The third is the forgotten B2B credit note: returns happen on business orders too, and the reversal must carry the same invoice-wise, GSTIN-linked treatment as the original supply — a B2C-style consolidated credit note against a B2B invoice creates exactly the mismatch the buyer's GSTR-2B will expose. The common thread is that B2B errors are visible to a counterparty with their own compliance stake, so the tolerance for casual handling is effectively zero. A monthly habit of sampling a few B2B vouchers against the source report, plus an import pipeline that validates buyer GSTINs before posting, removes nearly all of this class of trouble.
Frequently asked questions
A buyer gave a GSTIN but the order appears in my B2C report — what happened?
Amazon classifies a transaction based on the buyer's account and whether a valid GSTIN was attached at purchase. Orders from business accounts without a captured GSTIN report as B2C, and you generally cannot reclassify them after the fact. Book the row as the report states it, and direct the buyer to Amazon's process for GST invoice issues rather than editing your books.
Do B2B and B2C rows differ in tax computation?
No — the GST rate, the IGST versus CGST/SGST split, and place-of-supply logic work identically in both files. What differs is reporting granularity: B2B supplies are disclosed invoice-wise with the buyer's GSTIN so the buyer can claim credit, while B2C supplies are consolidated. Your voucher amounts are the same either way; the disclosure path is not.
Should B2B and B2C sales use separate sales ledgers in Tally?
It is not mandatory, but separate ledgers or at least separate voucher series make GSTR-1 preparation and review much easier, and they give you a clean view of how much Amazon Business contributes to revenue. If your CA reviews returns before filing, the split saves them time every month. TallySutra keeps the batches distinct automatically when both files are uploaded.
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