# Billing Integrations

If you already meter usage in a billing platform, Fours can forward it to every connected cloud marketplace instead of you reporting it a second time through the [Metering API](/metering/#report-usage-with-the-fours-metering-api). Each connection is no-code, and none of them require migrating off the platform you use today.

## Platforms Fours meters from

| Platform | What Fours forwards | How often | Setup guide |
| --- | --- | --- | --- |
| Metronome | Usage | Hourly or daily, whichever you choose | [Metronome](/integrations/metronome/) |
| Orb | Usage, costs, or invoice totals | Daily | [Orb](/integrations/orb/) |
| Lago | Subscription usage or costs | Hourly | [Lago](/integrations/lago/) |
| Chargebee | The metered overage Chargebee has already priced, as an amount rather than units | Hourly, at 5 minutes past the hour | [Chargebee](/integrations/chargebee/) |

**[Metronome](/integrations/metronome/)** forwards usage metered in your existing Metronome instance. Its guide covers org-level and user-level connections, how the sync works, what happens when a sync fails, and the billing modes available.

**[Orb](/integrations/orb/)** forwards usage, costs, or invoice totals. Its guide covers the billing modes, invoice mode, and how to connect an Orb customer to a Fours buyer.

**[Lago](/integrations/lago/)** forwards subscription usage or costs. Its guide covers the billing modes and how to connect a Lago customer to a Fours buyer.

**[Chargebee](/integrations/chargebee/)** forwards the metered overage Chargebee has already priced for each linked buyer, as an amount in the entitlement's currency on the single key `chargebee`. Its guide covers turning on **Enable Auto Report Usage**, mapping the `chargebee` key to a marketplace dimension, how each billing window is settled against its Chargebee invoice — including discounts and voided invoices, which come back as credit on the entitlement — and how to connect a Chargebee customer to a Fours buyer.

## Setting one up

Connect a platform from [**Settings > Integrations**](https://console.suger.io/settings?tab=integrations) in the Fours console. You provide the platform's API credentials, then map your internal billing dimensions to your marketplace dimension keys. Once the connection is active, the platform routes usage to Fours, which verifies it and reports it to the marketplaces.

Chargebee takes two more steps. Its connect dialog asks only for your Chargebee site name and API key, and a new connection reports nothing until you open the card's **Edit** dialog and turn on **Enable Auto Report Usage**. Then enter each buyer's **Chargebee customer ID** on the buyer — Fours syncs only the buyers that carry one. See [Chargebee](/integrations/chargebee/) for both steps.

You can run a native integration and the Metering API side by side. See [Automate usage with billing integrations](/metering/#automate-usage-with-billing-integrations) on the Metering page for how the two combine, and what happens if your billing platform has an outage.

## Other billing and finance connections

Stripe, Zuora, QuickBooks, NetSuite, Avalara, and AWS Billing connect to Fours as well, but they handle payments, subscriptions, accounting, and tax rather than feeding metered usage. They are listed under **Bill, meter, and close the books** in the [integrations catalog](/integrations/).