Summary
An unexplained marketplace deduction should not be booked automatically as a fee. Rebuild the payout from transaction-level events, then classify each difference as a contracted fee, customer event, timing reserve, or unsupported adjustment. Post supported items to the right account, carry temporary items as balances, and dispute only the residual that lacks a source record or contract basis.
What equation should every marketplace payout satisfy?
Every payout should equal an opening balance plus sales-related inflows, less refunds, disputes, fees, reserves and transfers, adjusted for releases and currency conversion. Amazon’s Finances API describes financial events by order, financial-event group or date range and warns that orders from the last 48 hours might not yet appear. A bank-only comparison can therefore manufacture a deduction that is actually a cutoff difference.
Expected cash = opening balance + captured sales + released reserves + reversals − refunds − disputes − contracted fees − new reserves ± adjustments ± FX settlement difference.
Match the equation at payout ID and currency level before aggregating by month. The minimum keys are legal entity, marketplace account, settlement batch, transaction ID, event date, available date, payout date, original currency and bank reference. A monthly plug hides whether USD 800 is one unsupported adjustment or 400 order-level fees of USD 2 each.
Which four deduction classes lead to different accounting decisions?
Four classes cover most payout gaps: contracted fees, customer events, timing reserves and unsupported adjustments. Stripe’s current balance-transaction documentation distinguishes charge, refund, payment reversal, dispute-related adjustment, fee and payout activity, and recommends the reporting_category field for accounting classification rather than relying on type alone. The label “adjustment” is a starting clue, not an expense account.
| Class | Typical source | Accounting response | Escalation trigger |
|---|---|---|---|
| Contracted fee | Commission, fulfillment, advertising, payment fee | Post by fee nature and tax evidence | Rate or basis differs from contract |
| Customer event | Refund, chargeback, cancellation, compensation | Link to the original order and inventory event | No order or claim ID |
| Timing reserve | Rolling reserve, pending balance, deferred payout | Keep as marketplace receivable or restricted balance | Release date passes without movement |
| Unsupported adjustment | Manual debit, correction, clawback | Hold in a suspense account while investigating | No source object, notice or contractual basis |
Classification must follow the economic event rather than the sign of the line item. A negative refund is not a marketplace service fee, and a reserve is not an expense merely because it reduces current cash. IFRS 15 separates revenue from cash timing by recognising consideration for transferred goods or services; settlement presentation cannot decide revenue by itself.
How much evidence is enough to post a deduction?
A deduction is ready to post when its amount, source event, contractual basis, legal entity and accounting nature agree. Start with the settlement line, follow its source or order ID, retrieve the related refund, dispute or fee record, confirm the applicable rate card, and connect the movement to the payout. Stripe documents a source field for the related object and a source_id join in Sigma for precisely this trace.
Evidence strength can be ranked from Level 1 to Level 5. Level 1 is only a bank shortfall; Level 2 adds a payout statement; Level 3 adds transaction IDs; Level 4 adds the source object and contract; Level 5 adds tax evidence and the ledger posting. Post routine expenses at Level 4 or 5, keep timing items on balance sheet accounts, and leave Level 1 or 2 residuals in suspense.
Amazon’s API model also exposes financial event groups, OriginalTotal, ConvertedTotal, BeginningBalance, FundTransferDate and TraceId. Those fields separate the batch total, conversion, starting balance and bank transfer trail. When a platform offers equivalent fields under different names, preserve its native vocabulary in the reconciliation rather than translating every event into a generic “marketplace fee.”
How does a payout bridge prevent a false margin alarm?
A payout bridge separates profit effects from cash timing before management changes prices or advertising. Consider a labeled simulated case: a marketplace shows CNY 500,000 of captured sales, CNY 42,000 of refunds, CNY 35,000 of contracted fees, a new CNY 20,000 reserve and a CNY 3,000 adjustment. Expected cash is CNY 400,000 before opening balance, reserve releases and FX effects.
The CNY 20,000 reserve does not reduce margin when the seller still has an enforceable receivable; it changes available cash. The CNY 42,000 refund may affect revenue, refund liabilities, inventory recovery and fulfillment cost depending on the underlying order. The CNY 3,000 adjustment stays unresolved until a source object or notice establishes whether it is a dispute, reversal, correction or actual platform charge.
Management should investigate both the amount and the population. A CNY 10,000 residual across 5,000 orders may indicate a missing rate field, while one CNY 10,000 debit may be a manual clawback. Set thresholds in both currency and count, and compare the exception rate with prior payouts so a small systematic leak is not dismissed merely because each line is individually immaterial.
When should finance dispute the platform instead of adjusting the books?
Dispute the platform when the residual has no traceable source, conflicts with the governing rate or duplicates a previously settled event. The dispute pack should identify marketplace account, payout ID, transaction ID, currency, amount, event date, expected treatment and attached evidence. A screenshot of the net payout alone is weak because it does not isolate the disputed event from valid fees and timing movements.
Adjust the books when new reliable evidence changes the economic classification, not merely because support closes a ticket. A reserve release should clear the reserve receivable; a won chargeback should reverse the earlier dispute effect; a corrected fee should update the appropriate expense and tax evidence. Preserve the original posting, correction reference and support outcome so the next close does not recreate the same exception.
Escalate internally when a deduction crosses reporting periods, affects multiple legal entities, changes indirect-tax evidence or remains open beyond its expected release date. A 7-day service ticket may be operationally acceptable, but a 90-day unsupported debit needs controller review. The aged register should distinguish waiting-for-platform, waiting-for-internal-data, accounting-correction and legal-or-contract-review states.
Questions finance teams ask about marketplace deductions
Should every amount deducted before payout be booked as a marketplace fee?
No. Refunds, disputes, reserves, payment reversals, currency effects and manual adjustments have different economic meanings. Classify the source event first and use a fee account only when the contract and evidence support a fee.
Why can the settlement report and bank receipt differ even when nothing is missing?
Cutoff, pending balances, reserve movements, payout timing and currency conversion can create a temporary difference. Reconcile opening balance through the payout date and retain original and converted currency fields.
What is the minimum evidence for disputing an unsupported adjustment?
Provide the account, payout and transaction identifiers, amount, currency, date, expected calculation, contract or rate evidence, and the source report showing that no valid event explains the debit.
Sources
Primary materials checked on 2026-08-29: Amazon’s official Selling Partner API Finances model, Stripe’s balance-transaction type documentation, and the IFRS Foundation’s IFRS 15 overview.