# Revenue

Revenue is the finance workspace for deals you have already sold. It normalizes what each connected channel reports — AWS, Azure, GCP, and Stripe, plus Snowflake in Revenue Records — into one set of revenue records, then follows the money through billing, cash collection, and disbursement — so you can answer what was invoiced, what buyers still owe, what has actually landed in your account, and which channel keeps the most of every dollar.

This workspace reports; it does not bill. On a cloud marketplace, the marketplace invoices the buyer and later pays out your share. On Stripe, Suger issues the invoice and collects. Either way, Revenue shows the result — to set up what you charge and to issue an invoice in the first place, use [Billing](/billing/).

Two controls at the top of most pages scope everything below them: a **channel** filter (one channel, or all of them) and a **date range**, which defaults to the last 90 days on the Overview. Set both before reading any number on the page.

## Follow the money, stage by stage

1. **[Overview](/revenue/overview/)** — the workspace home: Bookings, Billings, Cash Collected, and Disbursed stage cards, the revenue trend, and channel mix. Each card links through to the page that backs it.
2. **[Revenue Records](/revenue/revenue-records/)** — the ledger behind every other number: one normalized row per revenue event, with a raw tab showing exactly what each channel reported before Suger normalized it.
3. **[Invoices](/revenue/invoices/)** — the accounts-receivable view: total outstanding, DSO, aging buckets, and the full record behind any single invoice.
4. **[Cash & Disbursements](/revenue/cash-and-disbursements/)** — money on its way to you: payouts received, payouts still outstanding, the ones that need review, the disbursement schedule with expected-versus-received amounts, and the installments still to come.
5. **[Revenue Analytics and Reports](/revenue/revenue-analytics-and-reports/)** — ARR, MRR, and retention; revenue, margin, and days-to-payout compared across channels; and a library of finance reports you can run and export as CSV or PDF.

## Configure how revenue is reported

- **[Revenue Settings](/revenue/revenue-settings/)** — choose gross or net reporting per channel or product, review each channel's sync configuration, and connect the bank accounts used for cash matching.

## Scope and limits

:::info
**Channels.** The Overview dashboard filters by AWS, Azure, GCP, and Stripe; Revenue Records also carries a Snowflake channel. Settings is the one page the channel filter does not scope.

**Freshness.** Figures are never real time, and they do not refresh at all until Suger switches the revenue background jobs on. They are **off by default**, and the switch is a single environment-wide setting Suger controls — not a per-organization toggle, so there is nothing to enable for your organization specifically. Once those jobs are running, channel sync runs hourly, accounts-receivable aging is recalculated daily at midnight UTC, CRM deal ingestion runs hourly at ten minutes past the hour (offset to stagger it from the main sync), and bank reconciliation runs daily at 4 AM UTC. If your figures never move, the revenue jobs most likely are not running yet — contact [support@suger.io](mailto:support@suger.io).

**Currency.** Amounts are converted to a base currency — USD unless you change it — at the rate for the record's **invoice date**, falling back to the current date when a record has no invoice date. The converted amount and the rate are stored on the record, so opening a page never re-converts it on the fly — but every sync re-normalizes that channel's records, so a stored rate can be recomputed by a later sync. See [Revenue Settings](/revenue/revenue-settings/) for the full FX rules, including the 35-day fallback window.

**Not the same as Billing.** [Billing](/billing/) is where you define billable metrics and price models, send offers, meter usage, and issue invoices to your customers. Revenue is where you read what those invoices became across every channel, and when the cash arrives.
:::

:::info
**Oracle is ingest-only.** Suger ingests Oracle Cloud Marketplace revenue from the OCI publisher disbursement report, so Oracle rows can show up in your revenue data — and in the channel filter, which lists whatever channels your data contains alongside your configured connections. Oracle is **not** a revenue connection you can manage: it has no row in [Revenue Settings](/revenue/revenue-settings/), no connection health, no backfill trigger, and no sync interval. The connection list there covers AWS, Azure, and GCP as marketplace channels plus Stripe as the payment channel. The OCI report also exposes only about **three trailing months**, so asking for older Oracle history returns nothing extra.
:::