Payment reconciliation for marketplace sellers: the complete guide

A single bank credit covering 300 orders can hide a hundred small errors indefinitely. This is the complete reconciliation method for AJIO and Meesho sellers, the three-way match, aging buckets, and how to turn unexplained gaps into filed disputes.

Here is a true pattern, with the numbers rounded for privacy. A seller doing roughly 300 orders a month across AJIO and Meesho checked her payments the way most sellers do: panel total versus bank total, once a month. The two matched within about 2%, which felt fine, 2% is rounding, surely. When we ran the same month order by order, the “rounding” decomposed into eleven double-charged return fees, two penalties with no matching late event, and four delivered orders that had never settled at all. The total was quiet. 

The orders were screaming.That is the entire case for payment reconciliation in one paragraph: a single bank credit covering 300 orders is a place where errors go to hide. Marketplace settlement systems are mostly right, but “mostly right” across thousands of automated fee, penalty, reversal, and adjustment events means a steady drip of individually small mistakes. Each one is too small to notice in a total and too real to ignore in aggregate. This guide is the complete method for finding them: the three-way match, the aging buckets, and the discipline of turning unexplained gaps into disputes filed inside the window.

Why one number for 300 orders hides everything

Totals fail for three structural reasons. First, errors are symmetric-looking: a ₹40 short-payment here and a legitimate ₹40 adjustment there cancel inside a five-digit sum while one of them is wrong. Second, cycles bleed: any payout mixes this week's matured orders with last month's return reversals and a claim outcome from six weeks ago, so the total never maps cleanly to a period you can reason about. Third, and most expensive, missing orders make no sound. A delivered order that never enters any settlement produces no line, no debit, no anomaly in the total. It is just revenue that silently never arrived. From sellers we've sat with at 5 to 25 orders/day, the missing-settlement case is the single most common five-hundred-plus-rupee find in a first reconciliation, and it is literally invisible to total-versus-total checking.

The three-way match

Reconciliation done properly matches three documents against each other, per order:

• Your order ledger. What you actually shipped: order ID, dispatch timestamp, item, expected payout under your rate card. If you do not have an expected payout per order, build it, reconciliation without an expectation is just reading.

• The settlement statement. What the marketplace says happened: gross, fees, taxes, penalties, reversals, net. This is the platform's claim about reality, order by order.

• The bank credit. What was actually paid. Statements occasionally promise what the transfer does not deliver; the bank line is the ground truth the other two answer to.

The triangle matters because any two legs can agree and still be wrong. Statement matches bank? You still miss orders that never settled. Ledger matches statement? You still miss a transfer that bounced or netted oddly. The match runs ledger → statement → bank for every order, and the residue, the lines that do not tie out, is your work queue.

Visit us:- https://robnu.com/blog/payment-reconciliation-guide-sellers