Marketplace settlement reconciliation: bridge orders to the bank

The marketplace dashboard shows ₹100,000 of sales. The settlement report shows a ₹75,000 payout. Finance sees ₹74,000 in the bank. Explain the ₹75,000 calculation first, then the ₹1,000 bank shortfall.

Reconcile transaction lines to the payout, then the payout to the bank. A controller should be able to follow every link; a “matched” percentage alone cannot show where money went.

Establish the scope of the settlement first

Choose one seller account, marketplace, currency and settlement period. Preserve the report ID, export time and original file. Record the source's timezone and distinguish transaction dates, settlement dates and bank value dates.

Start from the platform's credited transaction amount for the settlement. That is not automatically the same as orders placed during the calendar period or revenue recognised under the merchant's accounting policy. A cancelled order may never enter the same financial flow; an older order's refund may appear in the current settlement.

Amazon's current settlement documentation describes its Flat File V2 report using amount type, amount description and amount fields. It also distinguishes this report from deprecated formats. Finance must approve the categories for the entries the merchant actually receives. Amazon settlement reports.

Preserve source signs and raw descriptions alongside normalised categories. A new charge description should become an exception until finance identifies it. Mapping an unfamiliar negative amount to “commission” because that balances the file would turn uncertainty into a false explanation.

Work through the ₹75,000 payout

Assume the following entries are present in one completed illustrative statement. This is a simplified cash reconciliation, with all amounts in INR on one consistent report basis. It is not a tax calculation or a revenue-recognition policy.

Now compare that expected payout with the platform's payout record. If the platform also reports ₹75,000, the first bridge balances.

The bank contains a credit of ₹74,000 with a compatible remittance reference. The second bridge has a ₹1,000 difference. Keep it open. Possible explanations include a missing bank line, an incorrect allocation or a separately documented adjustment. Confirm the cause from the records.

Do not put the difference into a fee category simply to close the workbook. A proposed adjustment needs its own evidence and the finance team's approval. The investigation might ultimately show that the bank receipt belongs to a different payout.

A net balance can still conceal an error. Omitting a ₹2,000 charge and an unrelated ₹2,000 positive adjustment leaves the same total. This is why the process must compare source row coverage and categories as well as the final value.

Use different keys for different matches

Keep the source identifiers that belong to each layer. An order number helps explain an order-related charge. A settlement ID groups a payout calculation. A bank reference helps allocate received cash. None is a universal key for all three.

Amazon also documents a method for determining which released transactions make up a payment using matching identifiers. Use the identifiers supplied by each marketplace. Verify the report and API contracts for the seller account being integrated. Amazon payment transactions.

Some entries are account-level charges and legitimately have no order ID. Keep them attached to the relevant statement and evidence. Inventing an order allocation would make later SKU profitability appear more precise than the records justify.

For imports, use the provider's stable transaction identity where available. Otherwise, define a tested ingestion identity that preserves repeated legitimate lines while detecting a repeated file. Matching only on amount and date can both merge distinct transactions and accept the same transaction twice.

Carry reserves and timing differences forward

The ₹5,000 reserve is a withheld balance in this example. It is not assumed to be a final expense. Its closing position must carry into the next reconciliation.

If a later statement releases ₹3,000 and records no other reserve movement, the remaining tracked reserve is ₹2,000. Include the released ₹3,000 once in that later payout bridge. Do not also treat it as another sale.

Keep three clocks visible: when the commercial event happened, when the marketplace recorded its financial effect, and when the money reached the bank. A refund appearing after the original sale's settlement should retain its link to that sale and its actual later posting period.

One bank credit may cover several payout components, and one payout may require more than one bank allocation in the merchant's records. Allow explicit many-to-many allocations with value limits. The total allocated from a bank transaction must not exceed the amount available from that transaction.

Age unresolved items by the event relevant to the next action. A payout awaiting bank arrival needs a different follow-up from a disputed fee already deducted. Finance should approve the timing policy; the article does not prescribe a universal settlement deadline.

Give the exception queue a working owner

Each exception needs an owner, evidence and a next action:

• Missing financial event: marketplace operations checks whether the report period, pagination or later update explains the absence.
• Unknown charge: commercial finance obtains the applicable description and agreement before approving a mapping.
• Refund mismatch: refund operations checks whether the case was approved, submitted, processed or still unresolved.
• Bank allocation gap: treasury or the controller checks remittance and bank evidence.
• Source total failure: the integration owner investigates the import before downstream accounting relies on it.

AI may help suggest a category for an unfamiliar description or extract a reference from a document. The proposed mapping should retain its source evidence and reviewer decision. Deterministic arithmetic and identifier checks are easier to audit for known statement structures.

Scope a pilot that finance can reproduce

Choose one marketplace, one seller account and enough completed statements to include an ordinary payout, a refund, a reserve movement and an exception. Agree the approved accounting handoff before enabling ledger writes.

Use native ERP reconciliation when the required identifiers and allocations survive import. A controlled staging area is useful when the source formats differ or raw reports need to remain available beside the normalised entries. Evaluate commercial reconciliation software on the same cases rather than on a vendor's advertised match rate.

For acceptance, demonstrate all of the following:

1. Every imported row is accounted for as included, deliberately excluded with a reason, or unresolved.
2. Reimporting the same statement does not create additional transactions.
3. The ₹75,000 example reconstructs from its components, while the ₹1,000 bank gap remains open.
4. A reserve release carries forward correctly without becoming sales.
5. Two offsetting omitted entries are detected even when the net total matches.
6. A reviewer can trace an approved correction back to its source and authorisation.

Measure unexplained value, age, evidence completeness and time spent resolving exceptions alongside the count matched automatically. A smaller exception queue is useful only when the underlying differences are resolved.

Close the two bridges with evidence

A defensible settlement explains what the platform calculated and what the merchant received. Differences remain visible until supported records or authorised decisions resolve them.

1. Select one completed settlement and preserve its original reports.
2. Reconstruct the payout using approved transaction categories.
3. Allocate bank receipts separately and assign every remaining difference.
4. Test duplicate imports, late refunds and reserve releases before adding more marketplaces.