Marketplaces · Amazon
Both halves of Amazon's Merchant Tax Report, read the way GST law reads them: shipments are invoices, refunds are credit notes against the original invoice, and a promotion reduces the tax as well as the base.
This adapter has been checked against real exports from a working seller account, and its edge cases are pinned as tests.
Where it goes wrong
None of these produces an error message. Each produces a return that looks complete and is wrong, which is exactly why they are worth spelling out.
Amazon writes 0.03 where the return needs 3. Read literally, every tax figure in the return is out by a factor of a hundred, and the file still looks well formed.
A discounted order shows the full tax in the head column and the relief in a separate promo tax column. Adding only the head column overstates tax on every discounted order.
A zero-value replacement is not a supply, but it did use a number. Treating it as a cancellation understates the documents issued in Table 13.
B2B is usually a small tail of turnover. A return built from it looks complete and omits nearly all the sales, so fynxIQ blocks rather than files it.
Also supported
Drop every marketplace’s files in together. fynxIQ merges them into one ledger per GSTIN, keeps each document series separate in Table 13, and reports each operator separately in Table 14.
Meesho splits a month across two downloads. The amounts are in one and the document numbers in the other, joined on the sub-order number.
Sales, returns, cancellations and replacements read from one file, with the event type deciding which is which.
Forward and reverse movements arrive in one register, with the credit note number sitting on the return rows themselves.
Point the fields at the columns once and any spreadsheet becomes a supported source. The mapping is saved and reused every month.