The ecommerce team says it had a record month. Finance says payouts were flat. Both are right, and the gap between them is where money gets lost.
It happens in almost every brand that sells through marketplaces. The monthly review opens with the ecommerce team presenting strong numbers: orders up, revenue up, share of search holding. Then finance presents its view: bank receipts from the marketplaces, settlement totals, net revenue booked. The numbers do not match, sometimes by a wide margin. The meeting turns into an argument about whose data is right.
Usually, nobody is wrong. The two teams are measuring different things, at different times, from different sources. The problem is not the disagreement. It is that nobody owns the bridge between the two numbers, and the bridge is where errors, missing claims and unexplained deductions hide.
Why the numbers differ
Different definitions of revenue. Ecommerce teams usually report gross order value from seller dashboards: everything ordered, at the selling price. Finance reports what was actually settled, after cancellations, returns, commissions, fees, taxes withheld at source, and other deductions. These are not two estimates of the same figure. They are different figures.
Different timing. An order placed on the 29th may be delivered on the 2nd, settled on the 9th, and returned on the 15th. Ecommerce counts it in the month it was ordered. Finance may count the payment in the next month, and the refund in the one after. During festive months, these timing differences become very large.
Different sources. The e-commerce dashboard, the marketplace settlement report, the ad platform invoice, and the bank statement all come from different systems with different levels of detail. Some show order-level data; some only show batch totals.
Costs that live in different places. Advertising may be invoiced separately or deducted from payouts. Promotional contributions may be netted against settlements. Some fees appear weeks after the orders they relate to.
Why the gap is costly
When the gap between the two views is explained only at an aggregate level, as in “it’s returns and timing”, the specific errors inside it are never found. A commission charged at the wrong rate, a reimbursement never received, a return refunded without the item coming back or a deduction that was never agreed upon all sit inside that unexplained difference. Many marketplace claims also have time limits. By the time anyone looks closely, some of the money can no longer be recovered.
There is also a decision cost. If ecommerce believes a channel is growing profitably and finance believes it is not, budgets, pricing and inventory decisions get made on whichever view is louder in the room.
Closing the gap
Agree on definitions. Write down what each team means by gross sales, net sales, settled revenue, and contribution, and report all of them side by side rather than choosing one.
Build the bridge at order level. Every order should be traceable from placement to delivery, settlement, any return, and final net value. A monthly bridge that explains the difference between gross orders and bank receipts, line by line, turns an argument into a checklist.
Flag exceptions continuously, not at month-end. Fee mismatches, missing reimbursements, and unexplained deductions are easiest to recover when caught within days. Finance and ecommerce teams increasingly use automated reconciliation to compare expected against actual for every transaction and raise claims within the marketplace windows. This kind of marketplace revenue recovery works best when it runs alongside daily operations rather than as a quarterly clean-up.
Give the bridge an owner. Neither team naturally owns the gap. Assign it explicitly, often to a commercial finance or marketplace operations role, with a monthly target for unexplained variance.
A shared month
The goal is not for finance and ecommerce to report the same number. Their numbers answer different questions and both are needed. The goal is to explain every rupee of the difference between them, and to claim back the parts that can still be explained. When that happens, the monthly review stops being an argument about whose data is right and becomes a conversation about what to do next.
