Reconciling The Range and Mirakl records

What changed when The Range moved to Mirakl?

The Range replaced its previous in-house marketplace infrastructure with Mirakl. Mirakl describes a phased transition in its official partnership announcement.

That establishes the platform change, not the financial cutover for your seller account. An old order may be visible in the new system while its payment, refund or fee still needs tracing through a particular statement. Your exports, migration correspondence and settlement records establish that detail.

The worked examples below are wholly fictional. They explain reconciliation methods and do not describe a particular seller’s results.

• Mirakl: The Range partnership announcement

Which records should you collect from both systems?

Retain original downloads before editing them. Cover the accounting period and enough later activity to follow outstanding orders, refunds and payouts.

Record each export’s filters, date basis and timezone. A file requested for a full year can still contain only part of it. Check returned dates and reconcile each transaction breakdown to its statement.

• Old and new order exports: references, lines, quantities, amounts and status dates.
• Transaction histories: sales, refunds, commissions, fee credits and adjustments.
• Settlement statements and remittance breakdowns, including final old-system payments.
• Fee invoices, credit notes, dispatch and delivery evidence, and relevant seller terms.
• Bank statements and existing accounting entries from imports, integrations and manual postings.

Does an order in both portals mean sales were counted twice?

No. It proves an overlap in records; the accounting effect needs a separate check. Match customer order references, then compare lines, quantities, original values, cancellations and refunds. Separate old-only, new-only and shared orders. Identify their financial transactions and settlement references before deciding what belongs in the books.

Fictional example: order DEMO-201 for three lamps appears in both exports. Its total is £144. The old remittance population contains no transaction for it; the new statement contains the sale once. That is one sale with two operational records.

Check the level of each amount field. If the export repeats £144 beside all three £48 lines, adding that field gives £432. Use appropriate line amounts or one total per order. Inspect your actual export; layouts can differ.

Which date should determine year-end cut-off?

Order creation, dispatch, delivery, platform updates, statement issue and bank receipt answer different questions. Build a timeline instead of choosing whichever date makes a report agree.

Recognition depends on the contract, accounting framework and reporting period. For businesses applying the revised FRS 102 revenue requirements, the FRC explains recognition by reference to the transfer of promised goods or services. Confirm which requirements apply to your period; a portal field is not automatically the contractual event.

The fictional seller below has a 31 October year-end and a supported policy of recognising these goods on delivery. Where migration updated a status later, retain evidence of the underlying event instead of silently using the update date.

• FRC: revenue from contracts with customers

How do you reconcile money still due at year-end?

Build the closing balance from relevant transactions and opening funds, then follow it into later settlements. Include all qualifying old-system activity, not just orders placed around migration.

In the fictional example below, there is no opening balance, other adjustment or earlier payout. Tax is excluded to make the timing bridge clear.

The later £1,644 payout contains both periods. Treating all of it as year-end receivables, or all as new-period sales, would lose the distinction.

Are held funds and a transfer in transit the same thing?

No. If your statement shows funds on hold, check whether they are already included in its closing balance. Do not add a reserve twice.

A payout released before year-end but received afterwards is different from funds still held by the platform. Support it with the payout reference and later bank receipt, using the provider’s definitions. A statement marked paid is not the receiving bank’s evidence.

What should you do with refunds and cancellations?

Check the dated transaction and its original sale. A current refunded label does not establish when the refund arose. A return request, returned parcel and processed refund may be separate events.

Look for commission refunds, charges and credit notes. A cancelled order may have no sale to recognise, but check its financial activity. Consider whether later evidence affects the year-end estimate of returns or recoverability; do not move every subsequent refund into the earlier period.

The Range has a separate Marketplace Partner returns process. That customer guidance identifies the operational route; it does not determine the seller’s accounting cut-off.

• The Range: Marketplace Partner returns

Correcting the accounts without duplicate entries

Map what is already recorded. A sale may appear through an integration, settlement invoice or journal. Matching the bank payout does not prove that sales and fees are correctly presented.

For a supported period-end accrual, document the sales, fees, closing asset and how the later normal posting will clear it. A dated reversal can be appropriate where that later posting would repeat the activity. Recheck both periods afterwards.

Assess VAT separately. A payout date does not replace the applicable tax-point and scheme rules, and a fee deduction is not automatically sufficient invoice evidence.

Finish with a schedule showing each balance, supporting records, later clearance and unresolved items. If evidence is missing, record the question and next action rather than post a balancing figure.

• HMRC: VAT time-of-supply rules

Accounting reconstruction where earlier balances need investigation