How EcomLedger works — the reconciliation workspace

The workspace

One screen per client, portal and month

Pick the client, pick the marketplace, pick the month, and drop in the files exactly as the portal gave them to you. Nothing is renamed, reformatted or pre-cleaned first.

ecomledger.co.in/app/reco Demo data

The Payment Reconciliation screen with a client, the five marketplaces and a
month chosen, and four empty upload cards each reading drop files here.

The same screen after upload: each card shows how many files it holds and
their size, and the workbooks produced on the server are listed below.

The GSTR-1 Generator screen: nine portals, a drop zone holding four Amazon
exports, the stored header mapping and the annual turnover setting.

Each client keeps its own year-till-date sheet per portal, so the month you pick is the month that gets added to it.

Real screens from the running app, with a demo client and synthetic files. No client’s data appears in any screenshot on this site.

How a month runs

Six steps, and you only do the first two

Pick client, portal, month

Each client keeps its own year-till-date sheet per portal. Choosing the month is the only scheduling decision there is.

Drop the files

Sale, payment, and optionally the order report and non-order settlements. Upload as many times as you like — they add up, and each card shows what it is holding.

Compile

Each portal’s own column names are mapped through the Header Master into one schema. When a marketplace renames a column, the mapping changes, not the engine.

Match

Order by order against the settlement, carrying forward every earlier month’s payments — so an order sold in July and paid in September lands on the July row where it belongs.

Flag

Every order ends with a remark: settled, pending payment, a reversal booked before the return was reported, a payment against no order value, or a genuine sale-versus-settlement disagreement.

Download

One workbook per client per portal, updated rather than replaced, with the summary sheets rebuilt from the order rows underneath them.

What is different about it

Three things general reconciliation tools do not do

One pipeline

GSTR-1 from the same data

The month you file and the month you reconcile are compiled from one set of master sheets. Most reconciliation tools stop at the settlement and leave the return to somebody else; most GST tools never look at the payout at all.

Accumulates

Year-till-date, not per period

Each run adds a month to a running workbook rather than producing a fresh report. That is what lets a September settlement correct a July order instead of sitting in a separate file nobody reconciles back.

Per portal

Adapters, not one generic matcher

Amazon’s settlement splits into fourteen charge categories; Myntra bills some fees inclusive of GST and raises credits with no order at all; Flipkart invoices shipping as separate lines. Each is handled where it differs.

What comes back

Spreadsheets, because that is what gets checked

Order-level working, an overview and monthly P&L, return analysis, state and SKU breakdowns, a charts dashboard, and the GSTR-1 files themselves — every calculated figure a live formula, so anyone can click a cell and see where the number came from.

Every sheet it writes, one by one → · What each marketplace charges →

Try it on one month

Upload a single month for one portal and compare the workbook against what you already know. That is the fastest way to find out whether it is telling you the truth.

Create an account Read the FAQ first

Every account is reviewed before it is switched on.

EcomLedger · Home job —

Every order. Every portal.Every rupee — accounted for.

One screen per client, portal and month

Six steps, and you only do the first two

Three things general reconciliation tools do not do

Spreadsheets, because that is what gets checked

Try it on one month

Every order. Every portal.
Every rupee — accounted for.