Marketplace Settlement Reconciliation: When the Bank Ties but Group Margin Does Not

Executive summary

• A Noon or Amazon deposit reflects settlement deductions, VAT and timing. It should reconcile to cash without becoming the group’s revenue figure.
• Two brand entities can clear every bank item yet report different revenue and margins because one books gross sales and the other books net deposits.
• March sales, April settlements and later returns create open positions that need one cut-off rule and an owner in every entity.
• Commission, fulfilment, advertising and tax lines need common classifications, with source invoices and unsettled balances kept traceable.
• A repeatable group bridge maps each storefront’s statement to one reporting structure before finance consolidates brand performance.

Entity A reports AED 100,000 of March marketplace revenue. Its April Noon settlement pays AED 69,950. Entity B sells a similar volume, but reports lower revenue after its controller books the net payout as sales. The group controller combines the entities and gets margins neither brand manager recognises.

Marketplace settlement reconciliation now becomes a group reporting problem. Both entities can clear their bank reconciliations. The discrepancy appears when finance compares the brands. Settlement deductions, reporting dates and accounting policy have entered the revenue line.

Marketplace settlement reconciliation starts before the bank deposit

A marketplace statement reconciles customer activity to cash payable to the seller. It includes returns, commission, fulfilment, advertising deductions, fee VAT and amounts withheld for later settlement. The sales report and deposit answer different questions. Netting everything against revenue hides trading performance.

Entity A’s AED 100,000 sales exclude output VAT. This illustrative UAE statement includes customer VAT, a later return and platform deductions. The withholding remains receivable until release or adjustment. Each component needs its own treatment.

The deposit ties to AED 69,950, yet says little about revenue. The AED 4,600 reserve is a receivable, not a selling cost. Customer VAT and VAT on marketplace fees have different roles. Posting the deposit directly to revenue erases those distinctions.

The same orders produce two different revenue numbers

The impact reaches the board pack. A brand that reports fees as expenses shows more revenue than a brand that nets them into sales, despite comparable trading. If fulfillment sits in cost of sales for only one brand, their gross margins diverge further. Group totals then shift with the brand mix.

Entity A books gross sales, with commission and fulfilment as expenses. Entity B reports the net payout as revenue, without separately classifying deductions. Both generate similar customer sales, yet their combined P&L mixes different reporting bases. As sales shift between brands, group revenue changes even when product performance does not.

Finance must approve revenue presentation, including the principal-versus-agent assessment under applicable standards. The underlying contracts determine that judgement. A net bank receipt does not justify net revenue reporting. The group also needs one margin definition covering fulfilment, commission and advertising.

Each entity ledger still balances. The controller needs a bridge from local sales to the group basis. Otherwise, management may blame rising marketplace fees for a margin decline caused by inconsistent postings.

March sells, April pays, May takes the return

Marketplace settlement dates follow the platform’s calendar. March orders may enter an April settlement; a May return may reverse a March sale. Noon identifies transaction dates and sale currencies, while Amazon reports settlement periods and transaction types. Group finance still needs its own cut-off rule.

Booking revenue on receipt shifts March trading into April. A second controller may accrue March sales but delay return estimates until May. Both banks reconcile while margin follows different calendars. Finance needs a roll-forward of unsettled proceeds, later returns and reserves tied to originating orders.

Finance data reconciliation across systems becomes critical here. Orders, statements, deposits and ledgers carry different dates and detail. Preserve the links between them rather than force one monthly total.

A GCC group may also hold separate AED and SAR settlement positions for the same marketplace. The group should retain each original currency until the local statement is reconciled, then apply its approved reporting rates. Converting unmatched bank deposits into the presentation currency too early can conceal a missing refund or reserve. It creates a new FX explanation for what started as an open settlement item.

The fees that quietly distort the brand P&L

Advertising can reduce seller proceeds or appear on a separate invoice or payment method. Noon advertising invoices can feed into its weekly seller payment position. Finance must match spending to invoices and settlement deductions. Otherwise, a campaign is omitted or counted twice.

Fulfilment needs consistent classification. Marketplace-fulfilled and seller-fulfilled orders often carry costs in different accounts. If one brand puts fulfilment above gross profit and another below it, gross margins stop being comparable. Group mapping keeps classification differences out of the performance story.

VAT needs a separate check. The UAE standard rate is 5% and Saudi Arabia’s is 15%, while actual treatment depends on the supply and invoice. Noon distinguishes fee amounts from VAT on fees. Controllers must reconcile that VAT to supporting invoices and tax accounts. Reserves and timing items belong in open balances, not tax expense.

Marketplace settlement reconciliation needs one group policy

Set common categories for sales, refunds, commission, fulfilment, advertising, fee VAT, reserves and cash. Map every Noon and Amazon line to them while retaining the statement ID, entity, storefront, currency and date. Local ledgers can differ; the group needs one controlled reporting map.

Ownership matters. Entity controllers validate statements, match deposits and explain open items. Group finance approves revenue presentation, margin definitions and cut-off. Kudwa can connect accounting records and structured spreadsheet inputs into one reporting model, maintaining approved mappings across entities. Finance still owns policy and source-level checks.

Chart of accounts standardisation across entities follows the same logic. Account names may differ while group classifications stay consistent. Amazon commission and Noon referral fees become comparable after mapping. Review unmatched descriptions whenever the marketplace adds a charge.

Keep exceptions visible. Every unmatched statement line needs an owner, a reason and a resolution date. A group review should show aged reserves separately from disputed fees and timing differences. That prevents the next month’s settlement from silently clearing an unexplained prior-period balance.

A workbook survives one storefront. The group needs repeatability.

One seller can manage this bridge in a spreadsheet. Add three brands, UAE and KSA storefronts, two currencies and two marketplaces, and every close brings more fees, reserves and returns. The workbook may still add up while classifications drift between preparers.

The controller must reproduce the bridge each month from statements to reporting categories, local ledgers, outstanding items and the board pack. When brand margin moves, finance should separate fee increases and returns from posting policy.

Kudwa can support this recurring group view by combining connected entity accounts with operational data through supported inputs. Finance must first agree mappings and reconcile marketplace records. The platform remains the settlement record, and the CFO owns the group reporting basis.

See how Data in One Place can bring entity finance and operational data into a common reporting structure, and book a demo using your current marketplace settlement workflow.

‍