# Billing

Billing is how you charge the customers you sell to: define the units you meter, price them, put that price on an offer, report the usage, and issue the invoice. How much of the lifecycle you run yourself depends on the channel. When you bill through your own Stripe account, Suger issues the invoice and collects the payment. When you sell through AWS, Azure, GCP, or Oracle Cloud, the marketplace bills the buyer and pays you your share — Suger supplies the metered usage those invoices are built from, then tracks what comes back.

Start with the [Overview](/billing/overview/) if you are new to it: it walks the whole path once and explains when you actually get paid on a marketplace deal. Every page in this section is linked below.

## Go from a price to a paid invoice

1. **Define what you charge for** — [Billable Metrics](/billing/billable-metrics/) name the unit you measure and how it is aggregated, and must exist before any usage-based offer. A [Price Model](/billing/price-model/) turns that into money: a flat fee as installments or recurring commits, usage metering, or both, on a billing cycle and interval you choose.
2. **Set up the customer and the deal** — create a [Buyer](/billing/buyer/) for the customer you bill directly, send an [Offer](/billing/offer/) carrying the product, contract dates, and price model, and the accepted offer becomes an [Entitlement](/billing/entitlement/) — the active contract that drives billing and tells you when it ends.
3. **Report the usage** — send usage records through [Metering](/billing/metering/), from your own backend, a connected billing engine, or a CSV upload. Suger aggregates hourly and daily, then totals each billable dimension when the period closes.
4. **Invoice and collect** — Suger generates an [Invoice](/billing/invoice/) from the entitlement and its aggregated usage, which you can edit while it is still a draft. Once finalized, the [Payment](/billing/payment/) pipeline charges it automatically and records every transaction and its status.
5. **Track and reconcile** — [Revenue](/billing/revenue/) reports invoiced, collectable, disbursed, and refunded amounts, with charts on the buyer and entitlement pages. [ERP Reconciliation](/billing/erp-reconciliation/) breaks a lump-sum marketplace payout back into the individual contracts and invoices behind it, and syncs the result to your accounting system.

## Change a deal after it goes live

- **[Amend or Cancel an Entitlement](/billing/amend-cancel-entitlement/)** — marketplaces do not allow direct edits to an active contract, so each cloud has its own mechanism: an AWS agreement-based offer, an Azure net-new private offer, a GCP replacement offer. This page covers what each one can and cannot change.
- **[AWS Refunds and Cancellations](/billing/aws-refunds-cancellations/)** — request a refund and cancel an active AWS entitlement from the console, and track the request on the entitlement record. Order matters: once you cancel, you can no longer refund from the console.
- **[Usage Credit](/billing/usage-credit/)** — add a USD allowance that is consumed ahead of commits and included quantity. It only has an effect on entitlements with a usage-based metric, and the amount cannot be reduced once added.

## Scope and limits

:::info
**Direct billing runs on Stripe.** Buyers, payments, and Suger-issued invoices go through the Stripe billing integration — the only payment integration supported today. A buyer's partner cannot be changed after the buyer is created, so a customer you bill on two partners needs two buyer records.

**Metering spans the marketplaces.** Usage reporting is normalized across AWS, Azure, GCP, and Oracle Cloud. Snowflake and Alibaba usage is reported through their own marketplace sections.

**ERP reconciliation** has native integrations with Oracle NetSuite and QuickBooks.

**Two things this section is not.** What *you* pay Suger is [Suger Billing](/get-started/billing/). Cross-channel revenue reporting, aging, and payout tracking live in the [Revenue](/revenue/) workspace.
:::