Google Cloud Marketplace Disbursement Report

A Google Cloud Marketplace disbursement report is the monthly file in which Google itemizes what it is paying you for the previous month’s usage. Google publishes two, a summary Disbursements report and a Detailed Disbursements report that shows each deduction, withholding and refund offset between a customer’s charge and your payout, and neither gives the date the money moved.

---

Acme’s controller has Google’s monthly deposit on the bank statement, and it is smaller than what Acme’s customers were charged. Some of the gap is Google’s fee. Some is usage Globex covered with credits from a commitment it had already bought. And Umbrella’s row shows an amount withheld, with no word on when, or whether, it will be paid.

None of it is an error. Google’s reports explain the gap, in fields most finance teams never open, and leave out one thing: the date the money moved. This guide answers finance’s month-end questions in turn from Google’s own report pages, all last updated October 13, 2026. Why AWS, Microsoft and Google Cloud disagree with one another is covered in why your marketplaces report different numbers; this post stays inside Google’s reports.

What is the Google Cloud Marketplace disbursement report?

The Google Cloud Marketplace disbursement report is Google’s monthly record of the money it is paying you, and it comes in two versions. The Disbursements report “details the money that is transferred from Google to you for the month.” The Detailed Disbursements report covers the same money “with a more detailed breakdown when compared to the disbursements report,” and its charges “match the charges from your customer’s invoice for the month.”

At month end, finance reads them beside Charges and Usage and Customer Insights:

Report	When Google generates it	What it is the source of
Charges and Usage	By the tenth business day, for the previous month	What customers were charged (Charges) and what accrued to you (Due Partner)
Disbursements	By the tenth business day, for the previous month	The month’s payout by paying Google entity: Amount before adjustments, Customer Refund and Total, plus the special entities Released Payout and Abandoned Payout
Detailed Disbursements	By the tenth business day, for the previous month	The payout by SKU, customer account and private offer, with each deduction, withholding and refund offset
Customer Insights	Daily, a day behind; monthly, on the first calendar day of the next month	Who each customer is, and usage by the date it started

Google describes the detailed report as a breakdown “for accounting and financial reconciliation purposes” and says: “We strongly recommend that you turn on this report.” In a CSV export to a Cloud Storage bucket or Google Drive folder, you choose the reports each destination receives, so check that it’s selected. Google’s BigQuery export includes it, as the table marketplace_report.detailed_disbursement, beside the incremental insights reports; enabling the export backfills “approximately the last two years,” and Google keeps the data for five years.

Which report answers which reconciliation question?

Each month-end question maps to a report and the fields that answer it, except one: no field says when the money reached your bank. Work down the table, in Google’s column names:

Question	Report	Field
What were customers charged?	Charges and Usage; Detailed Disbursements	Charges; cust_charges
What did a customer actually pay, after credits?	Detailed Disbursements	Google’s formula: cust_charges - total_deductions + marketplace_fee_amount
What accrued to us?	Charges and Usage	Due Partner
What is Google paying us this month, in total?	Disbursements	Amount, Customer Refund, Total
What is the payout per customer, SKU and offer?	Detailed Disbursements	aggregated_payout, on rows split by sku_id, account_id, private_offer_id and payout status
What came off before the payout?	Detailed Disbursements	total_deductions and its five parts
What is held back for a customer who hasn’t paid?	Detailed Disbursements	withheld_amount, probation_start_date, probation_end_date
What held-back money was paid or written off?	Disbursements; Detailed Disbursements	Released Payout and Abandoned Payout rows; released_amount, abandoned_amount
What did refunds take back, and what is still to come off?	Detailed Disbursements	refund_balance_deducted, refund_balance_outstanding
Which Google entity paid, and to which bank account?	Disbursements; Detailed Disbursements	Entity, Payment Type; disbursement_entity
Which private offer earned it?	Detailed Disbursements	private_offer_id, empty for a purchase that isn’t a private offer
Who is the customer?	Customer Insights	The row whose external_account_id equals the payout row’s insights_account_id
When did the money move?	None	report_creation_date is when the report was generated, not a payout date

The rest of this guide takes the rows that need more than a lookup.

When does Google send the reports and pay out?

Google generates a month’s Charges and Usage, Disbursements and Detailed Disbursements reports by the tenth business day of the next month, and pays “typically on the 21st of every month.” It pays “the aggregated amount due from all customers for the month,” and “You don’t need to invoice Google Cloud.”

The reports never carry the payout date. In the Detailed Disbursements report, report_creation_date is “The date when the report was generated,” with one value per report, and report_timezone “always has a value of -0800.” The only payment dates in the file sit in extraordinary_payment_note, which Google fills only for an extraordinary payment, with information “such as the approval date and processing date.” For the day a monthly payout moved, use your bank statement, or the Payouts view on Google’s Payments page, which Google describes as “Information about the funds disbursed to your bank account.”

Two things trip up month-end matching:

• The month label. A CSV’s name carries the usage month, and BigQuery’s partition date the month after. In Google’s examples, 2025-04-01 Detailed Disbursements Report covers April 2025 usage, and in BigQuery the same month is the partition whose _PARTITIONDATE is 2025-05-01. A Disbursements or Charges and Usage file named 20210401 covers April 2021.
• The number of deposits. Projects that share a payments profile still get their own reports, but “Revenue earned through all projects will be issued into one monthly payment.” And Payment Type sets the shape: old means “one or more payments from Google US or a regional Google entity to your US-based bank account,” and new means “a single payment to your local bank account.”

Amounts are “presented in the partner’s local currency” unless a field says otherwise, as cust_remaining_commit does: it’s in USD. If you’re paid in a currency other than USD, the payment is “subject to the exchange rate active at the time the usage was measured.”

Why is the payout less than the customer was charged?

Because Google takes five deductions before it pays you, and the Detailed Disbursements report sums them in total_deductions. Google defines it as “the total amount that was deducted before the payout was made to you,” computed as:

trial_credits_used + reseller_discount + marketplace_fee_amount + cud_credits_used + partner_testing_discount

Column	Google’s description
trial_credits_used	”Total free trial credits and coupon credits consumed.”
reseller_discount	”The amount of the reseller discount that you configured.”
marketplace_fee_amount	”The amount that Cloud Marketplace keeps as part of the Revenue Share agreement that you have with Google.”
cud_credits_used	”The amount of Committed use discount (CUD) credits applied. This includes both prepay and postpay credits.”
partner_testing_credit	”This is only applicable for products that were procured using a Cloud Billing account linked to your partner projects.”

The formula and the field list disagree on one name: the formula’s last term is partner_testing_discount, but the partner-testing column Google documents is partner_testing_credit, and no column carries the formula’s name. Map the term to that column, and check your own file’s header, since Google says automated processing should operate “based on the names of the columns.”

The fee rate isn’t one number either. marketplace_fee_percent gives the rate on each row, and starting April 21, 2025, Google calculates the revenue share percentage “in accordance with the Vendor Net Revenue Schedule, where applicable.”

What did the customer actually pay?

Google answers this in its description of cust_charges, “The computed cost for using your product”: “The actual end customer charge can be reduced by applied credits. You can compute it by cust_charges - total_deductions + marketplace_fee_amount.” The fee is added back because it comes out of your share, not the customer’s bill. Take a row where Globex ran 10,000.00 of usage and covered 4,000.00 of it with commitment credits, with no other credits or discounts:

Line	Amount
cust_charges	10,000.00
total_deductions	4,000.00 of cud_credits_used, plus the row’s marketplace_fee_amount
Actual end customer charge	10,000.00 − (4,000.00 + fee) + fee = 6,000.00

The Charges and Usage report’s Due Partner, “Payment accrued for you,” is calculated as (Charges - Trial Use + Prepay Credits + Postpay Credits + Reseller Discount) * revenue share, and Google adds the credits and reseller discount there “because their values are negative numbers.” The detailed formula subtracts its deductions instead, so normalize signs before you join the two reports. Google gives no formula for aggregated_payout itself: treat cust_charges minus total_deductions as a check, not a rule, and look to the refund and withholding columns for any remainder.

Why is part of a customer’s payout withheld?

Because the customer’s Cloud Billing account is on probation for nonpayment: Google holds back what it would have paid you until the account is back in good standing, then releases it, or abandons it if the account never recovers. In Google’s words, withheld_amount “tells you how much we would have paid you if we’d collected it from the customer. When the Cloud Billing account is back in good standing, we release the withheld funds in the next payment to you. If it never returns to good standing, we abandon the withheld funds.”

Field or row	Report	What it means
withheld_amount	Detailed Disbursements	What Google held back this month for a customer on probation
released_amount; Released Payout row	Detailed Disbursements; Disbursements	Money Google “had withheld, because the customer was delinquent, which it has now received, and is paying to you”
abandoned_amount; Abandoned Payout row	Detailed Disbursements; Disbursements	Money “that will never be paid because Google has determined it is uncollectible”
probation_start_date	Detailed Disbursements	For an account still on probation, “the first day in the current month where we withheld funds,” which “might not be the very first day”
probation_end_date	Detailed Disbursements	The last day Google withheld funds; “If this is blank, then the Cloud Billing account is still on probation”

Two consequences follow for the books, in our reading. A Released Payout or Abandoned Payout row often settles usage from an earlier month, since Google says the probation start date “might be in an earlier month” when it is releasing or abandoning funds, so don’t match it against this month’s charges. And while the end date is blank, this month’s start date doesn’t tell you when withholding began; earlier months’ files do. Keep a running withholding balance per customer account: add each month’s withheld_amount, and clear it as released or abandoned amounts arrive.

How do refunds show up in the disbursement reports?

As offsets against your future payouts, reported in the month Google issued the customer credit rather than the month of the usage it refunds. Google “computes the portion of those charges that were previously paid to you, and offsets that amount against your future payments,” and summarizes the adjustment “in the Charges and Usage report and Disbursement report for the month when we issued the customer credit.”

• Disbursements. Customer Refund is “Any adjustment due to having refunded money to customers,” between Amount, “before any adjustments,” and Total, “The final amount after adjustments.” Notes gives “The reason for the adjustment.”
• Detailed Disbursements. refund_balance_deducted is “The amount that Google subtracted from the payout amount for this month due to customer refunds.” first_refund_date and last_refund_date bound the usage the refund was computed on, refund_reason says why, and refund_processed_date is when Google processed it.
• The carry-over. “If the offset related to a customer’s refund is greater than the month’s payout,” refund_balance_outstanding is “the offset amount remaining after the payout.” Carry it forward as a deduction still to come.
• The wire-back. If the offset “would take more than four months to pay back” at your recent monthly payout rate, Google “might request that you wire the funds back.”

Requesting a refund in the first place takes a Partner Support Desk case with one customer identifier, covered in the marketplace credit request, at scale.

Why don’t Customer Insights and Detailed Disbursements agree on usage?

Because they date usage differently: the Detailed Disbursements report “includes usage that was reported by the service during the covered month, while the customer insights report includes usage that started during the month.” Google’s example is a customer who runs your software from 10 PM PT on March 31 to 3 AM on April 1. The five hours are reported on April 1, so they appear on April’s Detailed Disbursements report, and on March’s Customer Insights report, because they started in March. Google says the difference “ensures that if a usage report from your service or one of Google’s services is delayed, you’re still paid the correct amount.”

Late reporting widens the gap. The Detailed Disbursements report’s min_usage_start_time “might include usage from the previous month” when usage is reported or processed late. Customer invoices are created on month boundaries in US and Canadian Pacific Time, and if your own service reports usage, Google says to report it “by 6 AM US and Canadian Pacific Time on the first of the month” for it to appear on the previous month’s invoice. Incremental insights reports add “any usage from previous dates that wasn’t included in previous reports,” and Google strongly recommends them because they “aid your reconciliation of reported usage with the monthly disbursement reports.” BigQuery export turns them on.

So before you call a difference a metering error, check whether it falls at a month boundary or arrived late.

How do you match a payout row to a customer?

Through the Customer Insights report: the Detailed Disbursements report’s insights_account_id “maps to the external_account_id field” there, and that row names the customer. The Detailed Disbursements report’s own account_id “isn’t the same as the customer’s Cloud Billing account ID,” while the Customer Insights report’s account_id is the Cloud Billing account itself, so never join the two reports on a shared column name.

From	To	Key
Detailed Disbursements	Customer Insights	insights_account_id = external_account_id
Detailed Disbursements	Charges and Usage	c_u_account_id = the Charges and Usage account_id, “When applicable”
Charges and Usage	Customer Insights	Insights Account Id = external_account_id, with the by-account breakdown turned on

external_account_id “is present for all customers, even those with personal accounts,” but Google excludes identifying information for personal accounts, so a matched row can read n/a where the company would be.

What should you check in Google’s reports at month end?

Seven checks, in this order, turn Google’s reports into a month you can close. They cover only what is specific to Google; where they fit the rest of the routine, from disbursement matching through variance review, is in the monthly marketplace close checklist.

1. Confirm the files. All three monthly reports by the tenth business day, with Detailed Disbursements going to the destination your tools read. Google recommends Essential Contacts notifications, in the Cloud Billing category, for “Delayed reports,” “Reports with incomplete or inaccurate data” and “Reports that had to be regenerated.”
2. Label the month by usage. Take it from the CSV name, or the month before the BigQuery partition date, never from report_creation_date.
3. Tie the deposit. Match the Disbursements Total to the money received, allowing for several payments when Payment Type is old and summing the reports of projects that share a payments profile. A Released Payout row is money now being paid; an Abandoned Payout row is money that never will be.
4. Walk charges to payout. Set cust_charges less total_deductions against aggregated_payout row by row, reading partner_testing_credit for the formula’s partner_testing_discount.
5. Roll the withholding balance. Add new withheld_amount, clear released and abandoned amounts, and list every account whose probation_end_date is blank.
6. Carry refunds forward. Note refund_balance_deducted, carry refund_balance_outstanding into next month, and flag any balance that would take more than four months of payouts to clear.
7. Explain usage gaps. Compare against the incremental insights reports, and rule out month-boundary and late-reported usage before you call a gap a metering error.

How does Fours handle Google Cloud Marketplace payouts?

Fours reads Google’s reports from your Cloud Storage report bucket, keeps each Google Cloud revenue record’s disbursed amount at zero until the Detailed Disbursements report arrives, and tracks the record against an expected payout date that Fours computes itself: the 21st of the month after the charge month, in UTC. This is Fours behaviour, as Fours’ documentation describes it:

• Reports. Charges and Usage is the primary billing source, the Disbursements and Detailed Disbursements reports supply “The confirmed payout amounts Google sent you,” and Insights enriches buyer records. Because Detailed Disbursements is “the only source of a GCP record’s disbursed amount,” a sync that can’t read it is aborted rather than completed, so it can’t zero out amounts already confirmed.
• Status. The expected payout date drives the record’s payment status: PENDING before it; PAID once it has passed and the Detailed Disbursements report has apportioned a non-zero amount to the record, including the negative amount of a refund or clawback month; and OVERDUE once it has passed with the confirmed amount still zero.
• Apportionment. Fours splits each payout line across the records for that entitlement and charge month “by each record’s share of the collectable amount, so the parts add up to the payout exactly.”
• No disburse date. Fours never fills one, and never substitutes the report’s generation date. A Google Cloud invoice reads Expected payout with its date where other channels read Due or Overdue, reports flag a row with no disburse date Is Estimated, and Google Cloud records stay out of metrics that measure the gap between invoicing and payout, such as Avg days to payout on Channel Performance.
• Refunds. Each refund becomes a credit memo linked to the monthly record it refunds, carrying Google’s reason text verbatim when the report supplies one, so a month reads as one line with its refund attached rather than a positive row and a negative row to pair by hand.

The records are under Revenue → Revenue Records with the Channel filter set to GCP: Joined Records shows one normalized row per order, and Raw Records the charge-and-usage rows exactly as Google reported them.

Frequently asked questions

When does Google Cloud Marketplace pay out?

Google says you receive payouts “typically on the 21st of every month.” The Charges and Usage, Disbursements and Detailed Disbursements reports for the previous month arrive by the tenth business day, and none of them records the date your monthly payout moved.

What is the difference between the Disbursements and Detailed Disbursements reports?

The Disbursements report gives the month’s payout by paying Google entity: the amount before adjustments, customer refunds and the total. The Detailed Disbursements report breaks the payout down by SKU, customer account and private offer, with each deduction, withholding and refund offset.

Why is my Google Cloud Marketplace payout lower than the customer’s charges?

Google deducts trial and coupon credits, the reseller discount, its marketplace fee, committed use discount credits and partner testing before paying you, summed in total_deductions. Refund offsets and money withheld from customers on probation can lower the month further.

What does withheld mean in a Google Cloud Marketplace report?

The customer’s Cloud Billing account is on probation for nonpayment, so Google holds back what it would have paid you. It releases the money in the next payment once the account is in good standing again, or abandons it if the account never recovers.

Why do Customer Insights and Detailed Disbursements show different usage?

The Detailed Disbursements report counts usage reported during the month; Customer Insights counts usage that started during it. Usage from 10 PM PT on March 31 to 3 AM on April 1 appears in April’s Detailed Disbursements and March’s Customer Insights.

How does Fours date a Google Cloud Marketplace payout?

Fours sets an expected payout date, the 21st of the month after the charge month in UTC, because Google doesn’t report one. A record is PENDING before that date, PAID once it has passed and a confirmed amount has arrived, and OVERDUE if none has.

Takeaways

• Google publishes two disbursement reports: Disbursements gives the month’s payout by paying entity, and Detailed Disbursements itemizes it by SKU, customer account and private offer. Turn the detailed one on.
• A month’s reports arrive by the tenth business day of the next; payouts come “typically on the 21st.” No field gives the date the money moved, and report_creation_date isn’t one.
• total_deductions adds trial credits, the reseller discount, the marketplace fee, CUD credits and partner testing; read the formula’s partner_testing_discount as the partner_testing_credit column.
• Withheld money returns later as a Released Payout, or never, as an Abandoned Payout. Refunds come off future payouts, and refund_balance_outstanding is still to come.
• Label each file by its usage month: a CSV’s name and its BigQuery partition date are a month apart.

Fours reads Google’s Charges and Usage, Disbursements and Detailed Disbursements reports into revenue records, apportions each confirmed payout across the records it covers, and tracks Google Cloud payouts against an expected date rather than inventing one Google never reports. See how it matches payouts to the deals that earned them in Fours’ marketplace billing and disbursement reconciliation.