Revenue Records

Revenue Records is the ledger behind every metric in the workspace. It shows the unified revenue records that Fours normalizes from each channel, alongside the raw source records they were built from.


Overview

Open Revenue → Revenue Records. The page has a trend chart, two tabs, and a wide, exportable table — there are no summary cards here; the totals live on the Overview lifecycle cards.

Revenue Records: trend chart with Invoice/Collectable/Disburse series, the Lifecycle column, and the Columns control circled

The chart series are circled in red — ① Invoice Amount, ② Collectable Amount, ③ Disburse Amount — and in orange, ① the per-row Lifecycle stage column (Billing, Cash Collected, Disbursed) and ② the Columns control for customizing the table.

Two tabs switch between the normalized and source views:

  • All Records — one normalized row per revenue event, with a consistent set of columns across every channel.
  • Raw Records — the source-level records exactly as each channel reported them.

Scope the page

  1. Set the date range (defaults to the last 90 days).
  2. Choose a currency — the table and chart show only records in that currency, and amounts are never converted.
  3. Optionally narrow to one channel with the workspace Channel filter in the title row, beside All amounts in USD (or the currency you chose).

The chart above the table plots Invoice Amount, Collectable Amount, and Disburse Amount for the current scope — the channel, date range, currency, and the Lifecycle column filter; search does not narrow the chart. It groups by day when the date range spans seven days or less, and by month otherwise. Use its menu to Download SVG, PNG, or CSV of the charted series.

All Records

The All Records table has one normalized row per revenue event. Columns include the product and entitlement, CRM opportunity, buyer and country, lifecycle stage (Billing, Cash Collected, Disbursed), invoice date and amount, partner fee (amount and percent), collectable amount, due date and payment term, disburse date and amount, payout currency, tax, refund details, category, channel, sales motion, reseller, and the payment, earning, invoice, bank-trace, and disbursement reference identifiers. Every amount shows the record’s currency code in front of it, the partner fee included — on a euro record, Partner Fee reads EUR 1,291.01, like Invoice Amount and Collectable Amount beside it. Partner Fee and Partner Fee (%) are rounded to two decimal places, and a row with no invoice amount leaves both empty, as it leaves Invoice Amount.

To work with the table:

  1. Type in search to narrow the list. Search runs on the server across the whole result set, not just the rows on screen.
  2. Select Columns to show or hide columns and focus on what you need. To move a column, drag its header; the first column stays first.
  3. Select the expand control at the end of a row to open its full normalized detail.
  4. Select Export CSV to download the records that match — see below. Columns and Export CSV sit together at the end of the page’s filter bar.

If the service refuses an export, Fours shows Failed to export revenue records and downloads nothing. On the Raw Records tab, a channel’s table that the service refuses — for example for a date range wider than the service window — shows a red banner with the reason (Could not load revenue records: … or Could not export revenue records: …) and hides the total, so a refusal looks different from a genuinely empty period.

Search is a case-insensitive substring match — a fragment matches anywhere in the value, so acme finds Acme Corp. It covers seven fields: the record ID, buyer name, invoice ID, buyer ID, entitlement ID, disbursement reference, and offer external ID. A term that matches none of those returns nothing, even if it appears in another column. Search terms are capped at 256 characters.

Several columns carry an in-product tooltip explaining what the value is — hover the column header. Two are worth reading before you reconcile:

  • Tax Amount — for AWS this is tax AWS collected from the buyer and remits itself. It is informational, never disbursed, and excluded from your collectable amount. A negative value is tax returned to the buyer on a refund.
  • Disburse Date — GCP records fall back to their expected payout date here, because Google never reports an actual one. See GCP Revenue.

Reading the AWS partner fee

On AWS rows, the partner fee amount and the partner fee percentage are deliberately not the same calculation, so the percentage will not reproduce if you divide the fee amount by the invoice amount:

FigureWhat it includes
Partner fee (amount)AWS’s listing fee plus the VAT AWS charges you on that listing fee.
Partner fee (%)The listing fee without its VAT, over a base that has the seller-remitted tax removed.

The percentage is built this way on purpose: including a tax charged to you in a rate meant to describe AWS’s cut inflates it. Read the fee amount as what AWS actually kept, and the percentage as AWS’s effective rate. The listing-fee VAT is a separate thing from the buyer tax on the invoice — see Invoices for the two AWS tax lines.

Reading the GCP partner fee

On GCP rows, Partner Fee and Partner Fee % read — unless the fee came from one of Google’s reports that state it: the Detailed Disbursements report, or the Charges and Usage report when every charge row behind the record carries complete fee figures. Fours fills that in when it syncs the record, so a GCP record it has not synced since then shows — until a sync finds that evidence. When the fee is known, the percentage is fee ÷ the fee base Google reported × 100, and it reads — when there is no fee base.

A GCP row that carries only a payout adjustment — an amount Google withheld, released, or abandoned, with no charge of its own — has no invoice ID.

Buyer payment term

The Buyer Payment Term column prefers the term the channel itself supplied. Only when the channel supplies none does Fours derive one, as Net N days from the gap between the invoice date and the payment due date. For AWS, that supplied term is the buyer net term snapshotted onto the record when the agreement was accepted, so it keeps reading correctly even if the buyer’s terms change later. See AWS Revenue.

Raw Records

The Raw Records tab shows source-level records for the channels you’ve connected, so you can compare what a channel reported against Fours’ normalized row. Cloud marketplace channels render a per-channel detail table; direct (Stripe) billing renders a payment-transactions view. On the AWS table, each billing event’s Date is when AWS performed it — the event’s action date — or, when AWS gave none, the date Fours received the event.

If a connected channel has no raw-record view, the tab reads Raw records are not available for followed by that channel’s name. If no channels are connected, it shows No connected channels are available for raw records.

Saved view

Revenue Records’ views are listed in the rail under Saved views · Revenue Records — see Saved views for saving, sharing, and who can change a view. A view here keeps the Channel filter, the All Records or Raw Records tab, the search, the currency, the date range (a preset or custom dates), the Lifecycle filter, and the columns shown — and their order — in the records table and the Raw Records tables. It does not keep the sort.

Without a view, the page remembers a few choices in this browser: the columns you show and their order, the table’s sort, and the Lifecycle filter. The search, currency, date range, and tab reset when you leave the page. These choices are kept apart from the revenue tables on product, buyer, and entitlement pages, and from the Revenue app in Insulin.

KPI calculation formulas

Revenue Records has no summary KPIs; its chart totals the records currently in scope (channel, date range, currency, and the Lifecycle filter), placed by invoice date in UTC — or, without one, by service start, billing-period start, provider update, or last update. Every series is net of refunds — except AWS’s Collectable Amount, and AWS’s Disburse Amount, which subtracts only a refund AWS took out of a payout (see their rows) — though a refund that failed, was canceled, or is awaiting action is not subtracted here, unlike on the Overview. A voided, canceled, or written-off record counts as zero.

Charted seriesApplies toFormulaCalculation details
Invoice AmountAzure, GCP, Stripe, Oracle, SnowflakeΣ invoice amountCommon across these channels. An Oracle record’s invoice amount is the used amount from the OCI disbursement report, converted from the report’s local currency to USD at the report’s own rate.
Invoice AmountAWSΣ (original invoice amount, else invoice amount) − refund invoice amountFor a record AWS credited that a sync has processed since Fours began recording AWS credits, Fours keeps the original, pre-credit invoice amount and subtracts the credit once; any other AWS record uses its invoice amount. Never below zero.
Collectable AmountAWSΣ collectable amount exactly as AWS reported itAWS is the one channel Fours does not recompute: it preserves the collectable amount AWS supplies. That amount is net of marketplace fees and includes seller-remitted tax — the tax AWS disburses to you, which you then remit onward. Tax AWS collects and remits itself is informational and never affects it. Refunds are not subtracted: the amount already reflects the credits AWS applied.
Collectable AmountAzureΣ (invoice amount − channel fee)Channel fee only; no tax deduction. Never below zero.
Collectable AmountGCPΣ (invoice amount − channel fee − prepay credit) when Google’s reports confirm the fee; otherwise Σ the amount Google reports as due to youPrepay credit is the part of the charge drawn from the buyer’s prepaid balance, when there is one. Without a confirmed fee, the amount is Google’s due-to-vendor figure for the charge rows, plus any withheld amount Google later released that Fours matched to the charge. Either way, an amount Google withheld and then paid out — released or abandoned — is added to the record for the month Google reports it. No tax deduction. Never below zero.
Collectable AmountStripeΣ invoice amountDirect billing treats the full invoice as collectable.
Collectable AmountOracleΣ amount after tax, as the OCI disbursement report gives itConverted from the report’s local currency to USD at the report’s own rate; Fours does not recompute it from a channel fee.
Collectable AmountSnowflakeΣ expected payout amountThe payout Snowflake expects for the invoice, as reported; a void invoice counts as zero.
Disburse AmountAWSΣ (disburse amount − refund disbursed amount)Only a refund AWS took out of a payout is subtracted, never the refund invoice amount, and the result is not floored at zero.
Disburse AmountAzure, GCP, Stripe, Oracle, SnowflakeΣ disburse amountCommon across these channels. A GCP amount counts as soon as Google reports it, before its expected payout date, and includes any released or abandoned amount Google paid with it once Google’s Detailed Disbursements report confirms that month’s payout. An Oracle amount is the payout in USD; a Snowflake amount is the total net amount disbursed for the invoice.

See Overview for how these amounts roll up into the lifecycle stage cards, and Revenue Settings for base-currency and FX handling.

Spotted something wrong or out of date on this page? Tell us and we'll correct it.