Marketplace Payment Reconciliation (Meesho, Flipkart, Amazon)

About the Marketplace Payment Reconciliation (Meesho, Flipkart, Amazon)

Marketplaces pay sellers in batches, net of commission, fees, shipping, TCS and TDS, and the order report, the payments file and your bank statement rarely agree on their own. This tool reads the files you download yourself — the payments / settlement file, the order report, the returns / RTO report, your bank statement and your cost prices — from Meesho, Flipkart and Amazon.in (or any marketplace whose columns you match), and checks every order line: whether it was paid, how much reached you, what was deducted and why, and where the money went.

The result is a list of exceptions to recover — delivered orders never paid, settlements below the usual for the same SKU and price, money taken back, returns not back with you, shipping or commission charged above your other orders, payouts that never reached the bank — plus the deductions by type, every payout matched with the bank, COD and prepaid payment lag and SKU-wise profit with your own cost prices. Open exceptions carry over to next month in this browser and close themselves when a later file shows them paid. Your files are read in your browser and never uploaded.

Common uses

• Month-end check of a Meesho, Flipkart or Amazon account before the books are closed.
• Finding the orders to raise in a seller support ticket, with the text ready to paste.
• Seeing which SKUs actually make money after fees, returns and packaging.
• Accountants reconciling a client’s marketplace receivable with the bank.

What is checked, order by order

• Delivered, not paid: a delivered order with no payment row more than your number of days after delivery (seven more when the report gives only the order date).
• Paid less than expected: below your own expected settlement per unit (a column of your cost sheet), or below the usual settlement — the median of the other delivered orders of the same SKU at the same sale amount, when there are at least three — by more than your percentage.
• Negative settlement: the rows of an order add up to less than zero outside a return.
• Returns not back: an RTO or customer return that the returns report does not show as received.
• Charges on returns: the fees and shipping a return or RTO cost you.
• Commission, shipping and weight: commission as a share of the sale, or shipping per unit, well above the other orders of the SKU (shipping by zone when the file names it), and orders charged on a volumetric weight far above the dead weight.
• Cancelled but paid, paid more than once and paid but not in the order report are listed to check.

Where “expected” comes from

No fee table is built in: marketplaces change commission, fixed fees and shipping slabs by category and often, so a built-in rate card would be wrong for many sellers. Expected settlements come only from your own figures (an Expected settlement column in your cost sheet) or from your own other orders of the same SKU and price, and the page says which. To model fees for a new price, use the Marketplace Fee Calculator.

Deductions by type

Every amount column of the payments file is read as what it is — sale, refund, offers you fund, commission, fixed and platform fees, collection fees, shipping, return shipping, fulfilment, other fees, GST on fees, TCS, TDS, penalties, advertising, compensation and recoveries — from its heading, and you can change any of them under Columns. Columns that add up others (Flipkart’s Marketplace Fee and Taxes, for example) are left out so nothing is counted twice, and each row’s amounts are checked against its settlement column: the page tells you if they do not add up. Amazon’s settlement report, with one amount per row, is read by each row’s amount description.

TCS and TDS in the payments

The TCS and TDS the marketplace holds back are not costs: TCS under section 52 of the CGST Act, 2017 is collected on the net value of taxable supplies — 0.5% in total, as 0.25% central tax (Notification 15/2024–Central Tax) with the matching 0.25% State tax on supplies within your State, or 0.5% integrated tax on supplies to other States — and reaches your electronic cash ledger once you accept it on the GST portal; TDS on e-commerce sales (0.1% of the gross amount, Income-tax Act, 2025, section 393(1), Table Sl. No. 8(v) — section 194-O of the Income-tax Act, 1961 for earlier years) is income tax paid for you, shown in Form 26AS. This tool shows both as the file states them; to check them against the GST portal and Form 26AS, use E-commerce TCS & TDS Credit Reconciliation. Rates change: check the current ones.

Payouts and the bank

Payment rows with the same reference — Meesho’s transaction id, Flipkart’s NEFT id, Amazon’s settlement id — make one payout (Amazon’s Transfer rows and the first row of each settlement report are used as they are). Each payout is looked for in the bank statement’s credits by its reference in the narration first, then by the same amount (within your rounding) from two days before to your number of days after its date, preferring narrations that name the marketplace. Payouts outside the statement’s dates are not looked for, and marketplace credits in the bank that match no payout are listed too.

Limitations

• It reads the files you download; it has no access to your seller panel, needs no API key and cannot fetch reports for you.
• Presets match the columns of the reports as sellers download them; marketplaces rename and add columns from time to time, so check the column matches, especially the first time.
• Order ids that Excel has turned into numbers like 1.23457E+17 have lost their digits: download the report again and do not save it in Excel first.
• At most 50,000 rows are read from one sheet; split longer periods into several files.
• Bank statements are read from CSV or Excel. For a PDF statement, convert it first with Bank Statement PDF to Excel.
• The checks show where to look. The marketplace’s own statements, invoices and policies decide what is owed; this is not accounting or legal advice.

Privacy

Your files are read in your browser and never uploaded. Column matches, settings, saved cost prices and the open exceptions that carry over (order ids, SKUs, amounts and your notes) are kept in this browser’s storage until you remove them.