Examples of retail channels. Logos identify their respective brands; this display does not imply a Fundle partnership, endorsement or certified integration.
“Which settlement differences remain unexplained after returns and fees?”
Fundle Brain
01
Bring in matching periods
Collect sales, cancellations, returns, settlement files and the applicable fee schedules. Preserve each file’s date range and original identifiers.
02
Normalise and validate
Standardise dates, amounts and channel references. Separate duplicates and unmapped records before calculating the expected payout.
03
Explain the variance
Apply the relevant fee rules and account for returns and settlement timing. Classify the remaining difference so the reviewer knows what to investigate.
04
Track the actual resolution
Record the claim, response and confirmed adjustment. Keep identified, disputed and recovered amounts separate throughout the process.
BUILT AROUND THE WORK
Reconcile the order, not just the total.
Marketplace finance is a chain of events: an order, a shipment, a return, a fee and a payout. Fundle brings the records into a common structure so the team can see which differences are expected, which are timing-related and which require a claim.
01
Trading and settlement views
Review sales, expected commission, deductions and settlement in the same channel and period context. Use category comparisons and return behaviour to explain changes.
02
Masters and commercial rules
Map channel identifiers, articles and fee rules to the relevant business records. Keep unmapped orders visible instead of allowing them to disappear from reconciliation totals.
03
An investigation workspace
The workspace includes uploads, sales ledger, calculations, reconciliation, discrepancies and recovery sections. Organise the investigation around the source records and the reason for the difference.
04
Evidence that travels with the case
Carry the order identifier, settlement reference, expected amount, actual amount and calculation into the review. A finance owner needs enough evidence to reproduce the exception.
THE OPERATING FLOW
From the first question to the next useful action.
A marketplace payout is lower than the sales report. The workflow follows each order through cancellation, return, commission and settlement before asking the finance team to investigate a genuine discrepancy.
01
Bring in matching periods
Collect sales, cancellations, returns, settlement files and the applicable fee schedules. Preserve each file’s date range and original identifiers.
02
Normalise and validate
Standardise dates, amounts and channel references. Separate duplicates and unmapped records before calculating the expected payout.
03
Explain the variance
Apply the relevant fee rules and account for returns and settlement timing. Classify the remaining difference so the reviewer knows what to investigate.
04
Track the actual resolution
Record the claim, response and confirmed adjustment. Keep identified, disputed and recovered amounts separate throughout the process.
BRING YOUR BUSINESS QUESTION
Give Fundle Brain something useful to work on.
Start with the question. Define the data and workflow needed to answer it.
↗Which settlement differences remain unexplained after returns and fees?
↗Which categories have a rising deduction-to-sales ratio?
↗Which cases have supporting evidence but no recorded resolution?
CONNECT
Start with the right data.
Order and settlement files, returns, channel identifiers, fee schedules and contract-specific rules.
PUT IT TO WORK
Leave with a useful output.
Reconciliation results, unmapped records, deduction explanations and review-ready exceptions.
MEASURE WHAT MATTERS
Unexplained deductions / resolution time / recovered value
Measure matched-record coverage, unexplained variance, age of open cases and confirmed recovery. A flagged amount is an investigation value; recovery is recorded only when the adjustment or cash is confirmed.
GOOD QUESTIONS
Before we get started.
Does a portal name mean a live API connection?
No. A deployment can use approved files or a supported API. The connection method, coverage and refresh frequency are agreed for each marketplace.
Can we begin with downloaded reports?
Yes. File-based reconciliation is a valid starting point. Agree the expected formats, reporting cadence and commercial rules before expanding to any supported API connection.
Why does source-row traceability matter?
Totals can hide offsetting errors. The source row lets the reviewer trace an exception back to the original order or payout and explain the calculation without rebuilding it manually.
