EcomLedger/
Home
For Indian marketplace sellers
Every order. Every portal.
Every rupee — accounted for.
Match every order against what Amazon, Flipkart, Myntra, Meesho and Nykaa actually settled — and prepare GSTR-1 from the same data.
Where the payout goes
Why a settlement is lower than the order value
Six reasons, and where each one is accounted for in the workbook.
Commission and fee deductions
Every fee line the portal charges, captured separately rather than as one lump, so you can see which one moved.
Returns
A returned order still carries its forward and return logistics. Return Analysis shows the rate by state, pincode and SKU.
TDS and TCS
Withheld on your behalf, so they are not a cost — shown positive, and added back into Total Realization.
Orders not settled yet
Pending Orders and Pending Value separate a timing gap from a real shortfall. Most low realisation is this.
Account-level deductions
Charges with no order id at all. The Non Order Settlement sheet lists each one; NOD Summary pivots them by month.
Sale vs payment disagreement
Where the invoice and the settlement genuinely disagree on the same order, flagged per order with both figures.
Portal detail
What each portal charges, and what it does differently
Grey chips are charges deducted from the payout, amber are taxes withheld on your behalf, green are amounts credited back to you.
Amazon
GSTR-1Reconciliation
Charges & deductions captured
CommissionFBA Weight HandlingFBA Pick & PackFixed Closing FeeTechnology FeeShippingPromotional ChargesMiscellaneousGST on ChargesTDS u/s 194-OTCS — CGST / SGST / IGSTReimbursementsSPF Realised
Specific to this portal
- The settlement file is classified into 14 categories rather than three buckets, so a weight-handling overcharge is visible separately from commission.
- Sale/Payment Mismatch compares Taxable Amount from the invoice against Product Taxable from the settlement, and only flags a gap above both ₹50 and 50% — about 1% of orders, not 21%.
- Ratio vs Median marks orders more than 10 points off the median realisation ratio, computed over paid orders only so unpaid ones do not drag the median down.
- A fully refunded order whose return lands next month is labelled Likely Return in Next Month rather than left as an unexplained mismatch.
Flipkart
GSTR-1Reconciliation
Charges & deductions captured
CommissionLogisticsFixed FeesOther ChargesTDSTCSSPF Realised
Specific to this portal
- Order status comes from the Seller Order Report, scanned across every month rather than only the one being reconciled — a status recorded later still reaches the right order.
- Flipkart prefixes
order_item_idwithOI:in that report, and the compiled sale key carries the same prefix, so the two match on a plain compare. Do not add prefix-stripping — it was tried and it broke the match. - Return cancellations are handled on the sale side so a cancelled return does not double-count.
Meesho
GSTR-1Reconciliation
Charges & deductions captured
CommissionLogisticsOther FeesTDSTCSSPF Realised
Specific to this portal
- The payment file is read from the Order Payments sheet, whose real header sits on the second row.
- Supplier Listed Price and Supplier Discounted Price come from the Order Report; where a sub-order repeats, the latest row by Order Date wins.
Myntra
GSTR-1Reconciliation
Charges & deductions captured
CommissionForward LogisticsReturn LogisticsRoyalty ChargesTDSTCSSPF RealisedNon Order Settlement
Specific to this portal
- Myntra’s fees are GST-inclusive at 18%. That was established from the data, not assumed: Logistics_Commission ÷ fixed_fee is exactly 1.1800 at the median, and a real row reconciles to the paisa. Input credit is taken at 18/118 of the charge.
- Only Commission, Logistics and Royalty are actually deducted —
fixed_feeand the additional-charge columns are components of those, not separate deductions. Adding them would double-count. - A Reverse-type payment arriving a month after the sale, with no return recorded yet, is labelled Likely Return instead of an unexplained orphan settlement.
- An SPF credit raised against a single order carries that order id in
Invoice_Ref; it is moved onto the order and off the Non Order Settlement listing — but the bank figures still see it, because that money did reach the bank. - Myntra supplies no return reason anywhere.
cancellation reasonlooks right but is populated for RTO and cancelled orders only, never for returns.
Nykaa
GSTR-1Reconciliation
Charges & deductions captured
CommissionLogisticsOther FeesTDSTCSSPF Realised
Specific to this portal
- Sales and returns include Cancelled, Lost and RTO so reconciliation sees the full picture; GSTR-1 filters back to Delivered only, so the return is unaffected.
GSTR-1 only
Tata Unistore, Home Centre, JioMart and Pepperfry
These four compile and file correctly — sale, return and tax data all flow into the Global Master Sheet and the return. What they do not have yet is a settlement parser, which is what reconciliation needs: each marketplace names its fees differently, signs them differently and handles returns differently, so the adapter has to be written per portal.
EcomLedger · Home
job —