Any CSV or Excel export
- Drop the file in. fynxIQ reads the headers and proposes a mapping.
- Correct anything it guessed wrong. It shows sample rows so you can see what each column holds.
- Save it. Next month the same file is recognised on sight.
Marketplaces · Anything else
Point the fields at the columns once and any spreadsheet becomes a supported source. The mapping is saved and reused every month.
There is no fixed adapter here. You point the fields at the columns once and the mapping is saved and reused every month.
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.
The arithmetic rules still run in full, but they cannot tell you a column was pointed at the wrong field. Compare against the marketplace summary the first time you use one.
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.
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.