One marketplace payout, many invoices: prepare a matching schedule

Explain a batch settlement with invoice allocations, fees, refunds and a single bank-credit reference.

A batch payout compresses several customer events into one transfer. Your evidence should unpack that compression. The bank credit alone rarely explains which invoices, fees or refunds contributed to the settlement. A separate mapping schedule makes the relationship readable without inventing missing customer information.

Start from the payout statement

Save the statement that lists the items included in the batch. Identify invoice or job references, gross amounts, platform charges, adjustments and the settlement total. Distinguish marketplace earnings from any balance carried forward. If the platform does not provide a required detail, flag the gap and ask support rather than filling it with a guessed address or entity name.

Allocate once and review the bridge

Connect each underlying invoice to the batch identifier and record the amount allocated. Check that the same item was not included in an earlier payout. Keep refunds and chargebacks as separate events. Compare the resulting provider total with the final credit through the conversion evidence. Ask the AD how it wants a batch explanation attached to the accepted declaration or receipt process.

Reconstruct the batch boundary first

Find the statement identifying which transactions were included in the payout. A balance displayed by the marketplace can include earnings not yet released, reserves, adjustments or carried amounts. Do not assume that the full account balance equals the batch sent to your bank. Record the payout identifier and the statement period before allocating anything to invoices.

Keep the original transaction list alongside your working schedule. If the platform uses job or order references instead of invoice numbers, add a mapping rather than replacing one identifier with another. Where customer details are incomplete, identify the gap and ask the platform or bank what evidence is acceptable. Do not manufacture an overseas address from a similar name found online.

Check allocation at both invoice and payout level

Each invoice allocation should be supported by a source transaction, and the total allocation should connect to the settlement after documented adjustments. Review both directions. Selecting one invoice should lead to the relevant batch; selecting one batch should reveal all its component items. This catches receipts accidentally allocated twice across successive monthly files.

Separate platform charges, refunds, withholding and reserves. These may affect the reconciliation differently and should not be collapsed into a generic deduction. If a report already gives net amounts, do not subtract the same charges again. Keep any unapplied remainder visible and explain what evidence you are waiting for before calling the batch fully reconciled.

Explain the platform’s commercial role

A marketplace may facilitate customer payments, contract with the exporter or perform another role depending on the actual terms. Use your agreement and transaction documents to identify that role. Do not assume that every platform is always the buyer or always an unrelated processor. The party explanation should match your actual account and engagement.

Ask the bank how it wants the batch and customer mapping supplied through its accepted process. Keep the response and attachment version. When a later batch includes a reversal from an earlier period, link that event back to the original transaction instead of hiding it among new earnings. The working schedule should explain the business history as well as the final bank credit.

A fictional example

A payout contains USD 600 from one job and USD 400 from another, less USD 100 in documented charges. The schedule identifies both jobs and explains the USD 900 payout. Neither invoice is rewritten as a new USD 900 sale.

Preparation checklist

Keep the complete batch report.
Separate new earnings from carried balances.
Check that every allocation is used only once.

Can I name the platform as the customer in every case?

Use the actual contractual arrangement. The platform may have a different role from the underlying buyer; explain uncertainty to the bank.

FICTIONAL WALKTHROUGH

A new batch includes an old adjustment

A fictional marketplace payout contains USD 700 from one project and USD 500 from another, plus a USD 50 reversal relating to an older project. The preparer lists all three events and identifies the old reference. The reversal is not described as a charge on the new projects.
The payout also contains documented platform charges. The reviewer checks whether the report’s displayed transaction values are gross or net and avoids subtracting the charges twice. Each new invoice links to its transaction, and the old adjustment links to its original record.
The final bank-facing note explains the batch identifier, supported adjustments and conversion route. Any incomplete buyer information is raised as a question. The team retains the complete statement so a later reviewer can reproduce the allocation.

Your next step

See the marketplace example

Sources and scope

Sources reviewed 9 October 2026. The routines and fictional examples are editorial preparation suggestions. They do not confirm your bank’s acceptance, classification or transaction status.