Then load those postings into Formance Reconciliation and write one matching policy keyed on the provider ID. A policy that pairs each bank statement line to its ledger posting by ID gives you a break list you can clear before the month closes.
Cloud marketplace revenue from AWS, Google Cloud, and Microsoft reaches finance as a net deposit, so reconciling it means matching fees, refunds, and shifted payment dates. Your script joins three provider report formats to one bank statement using provider-specific identifiers, and a corrected provider report can break those joins.
A $600,000 annual private offer closes on AWS Marketplace, and finance books $600,000. Weeks later, the bank receives $582,000. The payout script you own cannot link the $582,000 deposit to a marketplace report row. The $18,000 difference could be the listing fee, a refund, tax, or a second deal that hasn't paid yet.
Until someone traces the $18,000 difference, finance cannot close the month, and auditors cannot tie booked revenue to cash. Recording the fee and the net payout as separate, traceable postings resolves the mismatch.
Why cloud marketplace payouts never match the invoice
A marketplace deposit never matches the invoice because each provider deducts its own fees from the billed amount. Payment timing also creates a second mismatch, as each provider runs its own schedule.
AWS defines seller net revenue as the amount billed for the transaction, net of AWS Marketplace fees, refunds, and United States (US) sales and use tax. AWS disburses funds only after the buyer pays. The payment then takes roughly 1–2 business days to reach your bank after the disbursement date.
Microsoft charges a 3% standard store service fee and deducts it at the time of payout. Microsoft pays monthly and publishes an estimatedPaymentDate that can vary slightly.
Each deduction is a separate economic event, and your invoice records none of them. An invoiced amount is a claim on the provider that can still go uncollected or be reverted, and the deposit is the settled event.
If your core ledger treats the invoice as cash, it records value that has not settled, and every uncollected invoice creates drift between the ledger and the bank. Transaction finality is the point at which a payment can no longer be reverted, and for a marketplace, that point is disbursement, not the invoice.
Until then, the invoice is only a claim on the provider. For marketplaces, post the invoice to a receivable and move value toward cash only when the provider reports a disbursement.
Which marketplace report fields tie a payout to a bank deposit
Each provider links a payout to its report rows with a different key and cadence, so your core ledger must store that key as metadata on the posting. Without the key, reconciliation falls back to guessing from amounts and dates.
AWS Marketplace disbursement report fields
AWS links a payout to a bank deposit through two keys: a transaction reference that runs from invoice to disbursement, and a bank trace identifier (ID) that runs from disbursement to deposit.
The billing event data feed records each invoice through the actions INVOICED, FORGIVEN, COLLECTED, and DISBURSED. The transaction_reference_id field cross-references the Billed revenue dashboard.
On disbursement rows, bank_trace_id holds the bank-assigned trace ID, which you can match to your bank's reports. A disbursement can cover a month of invoices or be an on-demand payout.
Google Cloud Marketplace disbursement report fields
Google reconciles monthly through one Detailed disbursements report, with rows keyed by product, account, and private offer.
The report arrives by the tenth business day of each month and covers the previous month's usage and revenue. BigQuery also provides the report as table marketplace_report.detailed_disbursement.
The summary Disbursements report carries Amount (before adjustments), Customer Refund, and Total (the final amount after adjustments). Google's page gives no rule for tying Total to the deposit, so reconcile the bank deposit against Total.
Neither Google report includes a bank reference, so match the deposit by amount and date. Match Total to the deposit amount within the payment window, and store the report month on the posting so the match stays traceable.
Microsoft Marketplace payout report fields
Microsoft ties transactions to payouts through the paymentId field, which appears in both transaction-history and payments data, where applicable.
The Earnings Marketplace fields describe it as a "Unique identifier correlates all transactions in the transaction report with a payment in the payment report."
In the Payments report, Microsoft notes that paymentId usually appears on your bank statement (SAP payments only). The transactionType field separates purchase, refund, reversal, and chargeback rows.
How to post cloud marketplace revenue in a core ledger
Give each marketplace its own receivable account, and settle the fee and net payout in one atomic transaction so both postings succeed or fail together.
Formance is an open-source, programmable core ledger that unifies fiat and digital assets with regulatory-grade traceability. Formance Ledger records payouts and doesn't move money. Funds stay with AWS, Google, Microsoft, and your bank, and Formance Ledger records every balance.
Every posting follows double-entry accounting, which means each transaction records the same amount as a debit in one account and a credit in another. In a marketplace payout, the receivable decreases by $600,000, while the fee expense and pending bank accounts increase by $18,000 and $582,000. These amounts equal the $600,000 that left the receivable.
Formance expresses these postings in Numscript, a domain-specific language for describing money movements. A script names the source account, the destination accounts, and how the amount splits. The ledger runs it as one atomic transaction, so it records every posting or none.
The example below assumes principal treatment and uses the $600,000 annual software as a service (SaaS) private offer from the introduction. Under agent treatment, do not post a separate fee expense. Book only the net fee or commission as revenue, and exclude amounts collected for third parties.
The contract value already sits in @counterparties:marketplaces:aws:receivable, booked when AWS raised the invoice. When the DISBURSED row arrives, one transaction:
•Moves $600,000 out of the receivable.
•Sends 3%, or $18,000, to @platform:expenses:marketplaceFees:aws.
•Sends the remaining $582,000 to @platform:banks:operating:pending, where it waits for the bank statement line with the same bank_trace_id.
The transaction also stores transaction_reference_id and bank_trace_id as metadata.
// MARKETPLACE_DISBURSEMENT// Event: settle the AWS receivable into fee expense and pending bank fundsvars { string $transaction_reference_id string $bank_trace_id}send [USD/2 60000000] ( source = @counterparties:marketplaces:aws:receivable destination = { 3% to @platform:expenses:marketplaceFees:aws remaining to @platform:banks:operating:pending })set_tx_meta("event_type", "marketplace_disbursement")set_tx_meta("transaction_reference_id", $transaction_reference_id)set_tx_meta("bank_trace_id", $bank_trace_id)
Google and Microsoft payouts use the same posting structure with different accounts and identifiers:
•Google: Transfers value from @counterparties:marketplaces:google:receivable, sends the fee to @platform:expenses:marketplaceFees:google, and stores private_offer_id and sku_id as metadata.
•Microsoft: Transfers value from @counterparties:marketplaces:microsoft:receivable, sends the 3% store service fee to @platform:expenses:marketplaceFees:microsoft, and stores paymentId.
None of the three marketplaces has a pre-built connector, so you need a custom integration. Build a translation layer that maps each provider's financial data to your ledger's data model.
Revenue recognition runs in separate postings beside the cash. The $600,000 contract releases $50,000 a month from deferred to recognized revenue, regardless of when AWS disburses. Formance Reconciliation pairs these records with external statements using policy-based matching rules.
Five controls for cloud marketplace revenue reconciliation
AWS, Google Cloud, and Microsoft all restate, lag, and recoup after the fact, so marketplace data needs five controls on top of the general invariants in ensuring ledger integrity.
The five controls are idempotent ingestion, tolerance windows, regenerated report reversals, ratable release, and separate postings for refunds, chargebacks, and recoups.
Control
AWS
Google Cloud
Microsoft
1. Idempotent ingestion keyed on provider IDs
Key on transaction_reference_id.
Key on the composite (sku_id, account_id, private_offer_id, payout status) plus the report month.
Keep the receivable open until the tenth business day.
Short window around estimatedPaymentDate, then raise an alert.
3. Regenerated reports post reversals
A FORGIVEN event marks a reverted invoiced charge, so post a reversal.
Post a reversal and a corrected posting for each changed row. Post each Abandoned Payout and Released Payout row on its own. Compare versions with temporal queries.
A transactionType of reversal or chargeback marks a correction. Post it as its own reversal keyed to the original transactionId and paymentId.
4. Ratable release for multi-year private offers
Release over the term in postings separate from cash.
Same as AWS.
Same as AWS.
5. Refunds, chargebacks, and recoups as separate postings
Post a reversing entry tied to transaction_reference_id.
Refunds appear in the Customer Refund field. Post each as its own transaction keyed to the original IDs.
Key negative rows to the original transaction. Post ReasonCode adjustments to a separate adjustments account and reconcile them in aggregate.
The five controls keep each deposit traceable to the provider row that produced it, even when a provider restates a report, pays late, or recovers funds. Each correction becomes its own posting instead of an edit to history, so finance can close the month, and auditors can tie booked revenue to cash.
Month-end checklist for cloud marketplace reconciliation
Run five reconciliation checks at month-end, one per control. A month-end checklist for cloud marketplace reconciliation proves the five controls worked. Without it, a duplicate posting, a missed reversal, or a stale receivable stays hidden until the auditors find it.
1Idempotency: no transaction_reference_id, Google composite key, or paymentId appears on more than one live posting, including across split Microsoft export files.
2Timing: every AWS receivable more than three business days past its disbursement date, and every Microsoft receivable past estimatedPaymentDate, is flagged.
3Restatements: every Google regeneration notice and every "Abandoned Payout" or "Released Payout" row has a corresponding reversal or release posting.
4Ratable release: each multi-year private offer released exactly one month of deferred revenue.
5Recoups: every transactionType refund, reversal, or chargeback row, and every Microsoft write-off, has its own posting.
Pull last month's disbursement report and take the five largest deposits. For each one, find the report row that carries the same bank_trace_id (AWS), paymentId (Microsoft), or Total (Google), and confirm the fee posting and the net posting add up to the invoiced amount. Any deposit you cannot match this way is a break, and it is cheaper to find now than during the audit.