Reconcile an AWS Marketplace SaaS deposit to the underlying bills

Start with the bank deposit and the related marketplace disbursement records, then obtain the billed-sales detail. AWS explains that its collections and disbursement dashboard lists invoices with a disbursement event, including partial, full or failed disbursements. Invoices without such an event need to be reviewed through the billed revenue dashboard.

This distinction matters when the bank total agrees but some customer invoices remain unsettled. A deposit reconciliation proves the identified cash movement; it does not prove that every bill has been collected. Preserve the report date, currency and selected filters so the review's population can be reproduced.

Use available disbursement and transaction identifiers to connect the bank receipt with the marketplace lines. Group by settlement currency and receiving bank account. Keep any bank fee or exchange difference separately supported rather than adjusting an unrelated customer invoice to make the total agree.

Inspect partial and failed disbursement statuses individually. Record what was sent, what reached the bank and what remains unresolved. A failed transfer may require action on the receiving account, while a partial amount may relate to customer collection or a specific settlement event. Use the detailed record to identify the reason rather than inferring it from the smaller deposit alone.

Reconcile gross billed amounts, refunds, marketplace charges and other reported adjustments using the relevant fields and supporting documents. AWS's billed revenue dashboard provides separate measures including listing fees and seller net revenue. Retain those components so the accounting team can apply the approved presentation rather than booking only the cash deposit to sales.

For illustration, a group of transactions might produce $25,000 of gross billings, a $1,000 refund and $750 of identified marketplace charges, leaving $23,250 before other adjustments. That arithmetic is an illustrative settlement bridge, not an assumed fee rate or a conclusion about gross-or-net revenue recognition. Match the actual account's report fields and contractual terms.

Build a rollforward of billed amounts not yet reconciled to disbursements. Show new bills, collections or settlements, refunds and other supported adjustments. Distinguish amounts not yet due from overdue items using the actual payment terms. AWS notes that customers can have different terms, so age from invoice date alone does not establish delinquency.

Assign an owner to investigate unexpected delays and document the marketplace support reference where needed. Check data-refresh timing before escalating a newly issued invoice that is not yet visible. Preserve unresolved items in the reconciliation so they cannot disappear simply because the next deposit arrived.

Give accounting the agreement, service period, billing and settlement evidence. The date a marketplace pays the seller is not sufficient on its own to determine when the service was earned under the applicable framework. Keep the approved revenue schedule and receivable or settlement-account reconciliation linked to the same transaction identifiers.

At month-end, reconcile the marketplace clearing balance to the outstanding detail and compare the next receipts with the prior open items. Retain original exports and the completed bridge. A reviewer should be able to trace a deposit back to customer bills and explain what remains unsettled without rebuilding the report filters from memory.