Marketplaces · Meesho
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.
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.
A row reading 229.66 taxable with 77.12 shipping is not 306.78. Multiply 229.66 by 1.18 and you get exactly the invoice total. Adding shipping inflates the base by a third.
Values arrive as 229.66101694915255. fynxIQ derives the base backwards from the clean invoice total instead, so taxable plus tax equals the total exactly.
A June order returned in July has no matching sale in July. That is what makes a rate show a negative net value with no positive counterpart, and it is correct.
TAMIL NADU, not 33. An unrecognised spelling is never guessed, because the place of supply decides which state receives the tax.
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.
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.
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.