Revenue
Track billed revenue, marketplace fees, and payouts from your GCP Marketplace orders in Fours.
Overview
Google handles billing on its side — it charges your customers, deducts its marketplace fee, and disburses your earnings. Fours does not process GCP payments. Instead, Fours ingests the billing reports Google delivers to your Cloud Storage report bucket and normalizes them into unified revenue records, so GCP revenue sits alongside your AWS, Azure, and Snowflake revenue in one place.
Fours syncs several GCP reports:
| Report | What it contains |
|---|---|
| Charges and Usage | The primary billing source — the amount charged to the customer and the amount due to you (the seller). |
| Disbursements / Detailed Disbursements | The confirmed payout amounts Google sent you, including the marketplace fee. This is the only source of a GCP record’s disbursed amount. |
| Insights | Customer and company metadata used to enrich buyer records. |
Fours resolves each charge to the matching Fours buyer, product, and entitlement where possible.
Where to find GCP revenue
GCP is a first-class channel in Fours’ revenue surfaces:
- Open Revenue → Revenue Records.
- Set the Channel filter to GCP.
Two tabs are available:
- Joined Records — one normalized row per order, with billed amount, marketplace fee, collectable amount, and disbursement.
- Raw Records — the source charge-and-usage rows exactly as Google reported them.
You can also see GCP revenue for a single buyer on its detail page, for a single entitlement on its detail view, or for a product. See the Revenue Records documentation for the full page reference.
What each amount means
Fours maps the raw GCP report data into the normalized record as follows:
| Revenue record field | GCP source | Meaning |
|---|---|---|
| Billed (Invoice amount) | Charges | What Google billed the customer. |
| Collectable | Due to partner/seller, plus released and abandoned payouts | What you receive after Google’s marketplace fee. When Google later pays out an amount it had withheld — released (the customer paid) or an abandoned payout — Fours adds it to the record of the original withheld charge when it can match exactly one — same entitlement, product, buyer, SKU and currency, inside Google’s probation period — and otherwise leaves it on the record of the month Google reports it with. |
| Partner fee | Detailed Disbursements, or Charges and Usage | Google’s marketplace fee. Left empty when Google’s reports don’t let Fours determine it — see How Fours determines the GCP fee. |
| Disburse amount | Detailed Disbursements payout | Money Google actually paid out to you, released and abandoned payouts included. Zero until the Detailed Disbursements report arrives. |
| Expected payout (due date) | Derived from the charge month | The 21st of the month after the charge month, in UTC. Fours computes this itself; Google does not report it. |
| Disburse date | — | Not populated for GCP. Google does not report the date a payout actually left its side, so this field stays empty on GCP records. |
How Fours determines the GCP fee
Fours fills in the fee only from what Google’s reports support, in this order:
- Detailed Disbursements — when the payout report carries a usable marketplace fee for the record’s charges and Fours can match the payout to them unambiguously, the fee comes from that report. A line that only pays out a released or abandoned amount adds no fee: Google repeats a fee there for usage billed earlier, but doesn’t deduct it again.
- Charges and Usage — otherwise Fours computes it: the charges, less free-trial usage and the amounts of prepay credits, postpay credits and reseller discounts (Google reports those as negative values; Fours subtracts their size), minus the amount due to you and any withheld amount. A report with no Reseller Discount column counts reseller discounts as zero; a blank cell in a report that has the column still leaves the fee unknown. Fours computes the fee only when every report row behind the record carries all of those values in a single currency, with no released, abandoned or refund-deducted amount.
- Neither — the fee is left empty rather than estimated.
Credits and discounts reduce the base the fee is charged on, so they don’t inflate the fee, and an amount Google withholds isn’t counted as fee. Google defines these report fields in Charges and usage report.
How a GCP refund appears
A refund does not create its own revenue record. Google reports refunds as rows in the same charge-and-usage report as the charges, and Fours turns each one into a credit memo linked to the original monthly revenue record it refunds. The refunded amounts are then projected onto that original record, where they show up in the Refund Invoice Date, Refund Invoice Amount, Refund Disburse Date and Refund Disburse Amount columns.
Two consequences worth knowing:
- There is no duplicate negative row. The refund is visible on the record it belongs to, so a month’s revenue reads as one line with its refund attached, rather than a positive line and a negative line you have to pair up yourself.
- The memo carries Google’s own reason text, verbatim, when the report supplies one.
A whole report month is reconciled together. If Google republishes a month’s report with rows in a different order, Fours rebuilds that month’s memos as a set rather than patching them one at a time — otherwise a re-ordered report would leave the earlier memos in place and the projection would count the refund twice.
Why a GCP record has no disburse date
Google reports the charge month and, later, the payout amount — but never the date on which it paid you. A GCP revenue record is therefore created with no disburse date and a disbursed amount of zero, and Fours fills in the money afterwards from the Detailed Disbursements report.
To keep the record on a timeline anyway, Fours derives an expected payout date — the 21st of the month following the charge month, in UTC — and stores it as the record’s payment due date. That expected date, not a disburse date, is what drives the record’s payment status:
Read the states as follows:
| Payment status | When a GCP record is in it |
|---|---|
| PENDING | The expected payout date has not arrived yet. |
| PAID | The expected payout date has passed and the Detailed Disbursements report has apportioned a non-zero amount to the record. A refund or clawback month carries a negative amount, and that also settles the line — otherwise a credit would sit in aging as overdue forever. |
| OVERDUE | The expected payout date has passed and the confirmed amount is still zero. |
Two places in the product show this explicitly: on Invoices, a GCP invoice’s subline reads Expected payout <date> where other channels read Due or Overdue; and in reports, a GCP row with no disburse date is flagged Is Estimated.
Sync
Revenue sync runs automatically once your GCP Marketplace integration is connected. Fours reads new report files as Google delivers them and updates the corresponding revenue records.
- The first sync performs a historical backfill; subsequent syncs re-scan a trailing window so late-arriving charges and disbursements are picked up.
- To rebuild that history later, run a full sync on the integration. It re-reads the Insights, Charges and Usage, Disbursements and Detailed Disbursements reports from the integration’s Report Start Date — or the year before the run, when none is set — and rebuilds the revenue records up to two days before the run started. It needs the integration’s GCP Project Number, and it skips the revenue records while Revenue Record Sync Disabled is on.
- Until the Detailed Disbursements report arrives, a record’s disbursed amount stays zero and it sits at its expected payout date. Once the report lands, Fours apportions the real per-line payout 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 is ever filled in — see Why a GCP record has no disburse date.
- Because the Detailed Disbursements report is the only source of a confirmed payout, a sync that cannot read it is aborted rather than completed. Completing it would zero out every previously confirmed amount and flip those records to overdue.
FAQ
Why is my collectable amount lower than the billed amount?
The collectable amount is what Google reports as due to you. Besides Google’s marketplace fee, free-trial usage, credits, reseller discounts and any amount Google is withholding for now can all make it lower than the billed amount. Google withholds your share of a customer’s charges while that customer’s billing account is on probation; when it later releases the amount or pays it out as an abandoned payout, Fours adds it to the collectable amount, and counts it as disbursed once Google’s Detailed Disbursements report confirms the payout for that entitlement and month. The same rule applies to the revenue record and to the Disbursed revenue figure on an entitlement’s or product’s page. See How Fours determines the GCP fee for how the fee itself is worked out.
Why don’t GCP records show tax?
Google’s marketplace reports do not break out a separate tax line, so Fours leaves the tax field empty for GCP records.
When will I see the final disbursement?
The confirmed payout amount appears once Google delivers the Detailed Disbursements report and Fours’ next sync ingests it. Before that, the record’s disbursed amount is zero and it carries only its expected payout date — the 21st of the month after the charge month.
Why is the disburse date empty on my GCP records?
Because Google never reports it. Google tells you the charge month and, later, the payout amount, but not the day the money moved. Fours leaves the disburse date empty rather than substituting the report’s generation date, and tracks the record against its expected payout date instead. See Why a GCP record has no disburse date.
Spotted something wrong or out of date on this page? Tell us and we'll correct it.