Marketplace revenue,
reconciled without a spreadsheet.

Usage collected from your product or your metering platform, priced against the plan the buyer actually bought, reported to the marketplace, and matched back to the money that lands.

See Fours in action Read the docs

300+ ISVs $10B+ cloud transactions processed 99.9% reconciled

The Fours billing console: normalized usage records, the pricing applied to them, and marketplace disbursements matched against expected revenue.

Illustrative sample data — not customer results.

Billing and metering is mission critical.
Build it in-house and it breaks.

The gap between what a customer used and what the marketplace actually paid you is where finance loses its days.

Today

Usage tracked in spreadsheets Exported per cloud, then reconciled by hand

Disbursements arrive without context No link back to the deal that earned them

Errors surface at month end A rejected metering record is found weeks after it failed

Finance closes by assembling the numbers first

With Fours

Usage normalized across sources One shape whether it comes from your API or your metering platform

Disbursements matched automatically Against expected revenue and the opportunity that produced it

Failures surface when they happen Rejected records are flagged and retried rather than discovered later

Finance closes against records that are already there

Four steps between a usage event and recognized revenue.

The part of marketplace selling that quietly becomes someone’s month-end job.

Usage arrives from wherever you already measure it.

Send events straight from your product through the API, or connect the metering platform you already run. Either way the usage is normalized into one shape before anything is priced, so a customer on AWS and a customer on Azure are counted the same way.

Usage API Lago Metronome Orb Normalized across sources

Where the usage comes from

Your product or metering platform

Fours Normalized usage

Usage metering Received usages, normalized 48.2K events

Received usages

Record	Buyer	Reported
rec-8f21a	Acme Corp	2 min ago
rec-8f19c	Umbrella	5 min ago
rec-8f04b	Globex	12 min ago

Dimensions · api_request_cnt · revenue_unit · free_unit

Illustrative sample data — not customer results.

Priced against the plan the buyer actually bought.

Pricing rules apply the tiers, volume discounts and overages on the offer that buyer accepted, rather than a list price someone has to remember to adjust. Every event is validated, and records that fail are retried instead of quietly disappearing.

Tiers Volume discounts Overages Event validation Automatic retries

Where the price is applied

Normalized usage

Fours Priced usage

Priced usage Pricing applied to metered records Validated

Usage dimensions

Dimension	Included	Rate
API requests	5M	$0.010
Data processed	10 TB	$0.008
Active seats	250	Committed

Illustrative sample data — not customer results.

Reported to the marketplace that has to bill it.

Metering records go to AWS, Microsoft or Google Cloud on the schedule each one expects, so the buyer is charged on their own cloud bill against the commitment they already made. A rejected record surfaces as an alert rather than a gap you find at month end.

AWS Microsoft Google Cloud Metering APIs Rejection alerts

Where the number goes

Priced usage

Fours

The marketplace

Channel performance Revenue by channel · 90 days Live

Total revenue $3.6M

Top channel AWS

Net margin 93%

AWS Marketplace 88%

Azure 9%

Stripe 3%

Illustrative sample data — not customer results.

The money that lands, matched to the deal that earned it.

Marketplace disbursements are matched automatically against expected revenue and the opportunity that produced them, then exported for revenue recognition. Finance closes against records rather than assembling them first.

Disbursement matching Revenue recognition NetSuite QuickBooks Stripe Chargebee

Where the money is matched

Marketplace disbursement

Fours

Finance systems

Cash & disbursements Marketplace payouts and Stripe Reconciled

Received $69.9K

Outstanding $2.25K

Issues 0

Disbursement schedule

Buyer	Expected	Status
ITProCloud GmbH	$4,726	Received
Acme Corp	$12,400	Scheduled

Illustrative sample data — not customer results.

Frequently asked questions

From finance teams closing the books on marketplace revenue.

What is marketplace metering?

Reporting how much a customer used your product to the marketplace that bills them, so the charge lands on their cloud bill accurately and on time.

Can we keep the metering platform we already use?

Yes. Usage can come straight from your product through the API, or from Lago, Metronome or Orb. It is normalized into one shape either way.

How is revenue leakage prevented?

Every usage event is validated before it is reported, failed records are retried automatically rather than dropped, and marketplace disbursements are reconciled against expected revenue so a shortfall surfaces instead of hiding.

Which finance systems are supported?

NetSuite, QuickBooks, Stripe and Chargebee, with exports shaped for revenue recognition.

Can we meter across more than one marketplace at once?

Yes. Usage is reported to AWS, Microsoft and Google Cloud on the cadence each one expects, from one place.

What happens when a metering record is rejected?

It is flagged as an alert and retried. The point is that a rejected record is something you hear about when it happens, not something finance discovers at month end.