--- title: "Usage Metering and Marketplace Billing Automation" url: https://www.fours.com/platform/billing-metering/ canonical: https://www.fours.com/platform/billing-metering/ type: Platform description: "Marketplace revenue reconciled without a spreadsheet. Collect usage, price it against the plan the buyer bought, report it and match the money back to the deal." --- # Usage Metering and Marketplace Billing Automation > Canonical HTML version: https://www.fours.com/platform/billing-metering/ 1. [Home](/) 2. / 3. [Platform](/platform/overview/) 4. / 5. Billing & Metering # 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](/schedule-demo/) [Read the docs](https://doc.fours.com/billing/) **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.](/platform/hero-billing.webp) 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 ![](/logos/fours-mark.svg) 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 VS ## 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 __![](/integrations/lago.svg) Lago __![](/integrations/metronome.svg) Metronome __![](/integrations/orb.png) Orb_ _Normalized across sources_ Where the usage comes from ![](/integrations/lago.svg)![](/integrations/metronome.svg)![](/integrations/orb.png) Your product or metering platform ![](/logos/fours-mark.svg) Fours Normalized usage ![](/solutions/marks/aws.svg)**Usage metering** _Received usages, normalized_ 48.2K events Received usages Record Buyer Reported ![](/solutions/marks/aws.svg) rec-8f21a Acme Corp 2 min ago ![](/solutions/marks/azure.svg) rec-8f19c Umbrella 5 min ago ![](/solutions/marks/gcp.svg) 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 ![](/logos/fours-mark.svg) Fours Priced usage ![](/solutions/marks/aws.svg)**Priced usage** _Pricing applied to metered records_ Validated Usage dimensions Dimension Included Rate ![](/solutions/marks/aws.svg) API requests 5M $0.010 ![](/solutions/marks/aws.svg) Data processed 10 TB $0.008 ![](/solutions/marks/aws.svg) 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. _![](/solutions/marks/aws.svg) AWS__![](/solutions/marks/microsoft.svg) Microsoft __![](/solutions/marks/gcp.svg) Google Cloud_ _Metering APIs_ _Rejection alerts_ Where the number goes Priced usage ![](/logos/fours-mark.svg) Fours ![](/solutions/marks/aws.svg)![](/solutions/marks/microsoft.svg)![](/solutions/marks/gcp.svg) The marketplace ![](/solutions/marks/aws.svg)**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 __![](/integrations/netsuite.png) NetSuite __![](/integrations/quickbooks.png) QuickBooks __![](/integrations/stripe.svg) Stripe __![](/integrations/chargebee.svg) Chargebee_ Where the money is matched ![](/solutions/marks/aws.svg)![](/solutions/marks/microsoft.svg)![](/solutions/marks/gcp.svg) Marketplace disbursement ![](/logos/fours-mark.svg) Fours ![](/integrations/netsuite.png)![](/integrations/quickbooks.png) Finance systems ![](/solutions/marks/aws.svg)**Cash & disbursements** _Marketplace payouts and Stripe_ Reconciled Received **$69.9K** Outstanding **$2.25K** Issues **0** Disbursement schedule Buyer Expected Status ![](/solutions/marks/azure.svg) ITProCloud GmbH $4,726 Received ![](/solutions/marks/aws.svg) 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. ![intel](/home/partners/intel.svg) ![notion](/home/partners/notion.svg) ![webflow](/home/partners/webflow.svg) ![glean](/home/partners/glean.svg) ![airtable](/home/partners/airtable.svg) ![fivetran](/home/partners/fivetran.svg) ![bmc](/home/partners/bmc.svg) ![coderabbit](/home/partners/coderabbit.png) ![launchdarkly](/home/partners/launchdarkly.svg) ![harness](/home/partners/harness.svg) ![fireblocks](/home/partners/fireblocks.svg) ![ramp](/home/partners/ramp.svg) ![deel](/home/partners/deel.svg) ![dbt](/home/partners/dbt.svg) ![clari](/home/partners/clari.svg) ![teleport](/logos/company/teleport.svg) ![logicmonitor](/home/partners/logicmonitor.svg) ![redis](/home/partners/redis.svg) ![dialpad](/home/partners/dialpad.svg) ![fireworks](/home/partners/fireworks.svg) ![1password](/home/partners/1password.svg) ![knowbe4](/home/partners/knowbe4.svg) ![kong](/home/partners/kong.svg) ![chainguard](/home/partners/chainguard.svg) ![dataiku](/home/partners/dataiku.svg) ![zuora](/home/partners/zuora.svg) ![vanta](/home/partners/vanta.svg) ![tailscale](/home/partners/tailscale.svg) ![pulumi](/home/partners/pulumi.svg) ![baseten](/home/partners/baseten.svg) ![risingwave](/home/partners/risingwave.png) ![hootsuite](/home/partners/hootsuite.png) ![elevenlabs](/home/partners/elevenlabs.png) ![callsign](/home/partners/callsign.png) ![fortinet](/home/partners/fortinet.svg) ![pingidentity](/home/partners/pingidentity.png) ![redpanda](/home/partners/redpanda.png) ![qdrant](/home/partners/qdrant.png) ![aiven](/home/partners/aiven.svg) ![thoropass](/home/partners/thoropass.png) ![](/home/partners/intel.svg) ![](/home/partners/notion.svg) ![](/home/partners/webflow.svg) ![](/home/partners/glean.svg) ![](/home/partners/airtable.svg) ![](/home/partners/fivetran.svg) ![](/home/partners/bmc.svg) ![](/home/partners/coderabbit.png) ![](/home/partners/launchdarkly.svg) ![](/home/partners/harness.svg) ![](/home/partners/fireblocks.svg) ![](/home/partners/ramp.svg) ![](/home/partners/deel.svg) ![](/home/partners/dbt.svg) ![](/home/partners/clari.svg) ![](/logos/company/teleport.svg) ![](/home/partners/logicmonitor.svg) ![](/home/partners/redis.svg) ![](/home/partners/dialpad.svg) ![](/home/partners/fireworks.svg) ![](/home/partners/1password.svg) ![](/home/partners/knowbe4.svg) ![](/home/partners/kong.svg) ![](/home/partners/chainguard.svg) ![](/home/partners/dataiku.svg) ![](/home/partners/zuora.svg) ![](/home/partners/vanta.svg) ![](/home/partners/tailscale.svg) ![](/home/partners/pulumi.svg) ![](/home/partners/baseten.svg) ![](/home/partners/risingwave.png) ![](/home/partners/hootsuite.png) ![](/home/partners/elevenlabs.png) ![](/home/partners/callsign.png) ![](/home/partners/fortinet.svg) ![](/home/partners/pingidentity.png) ![](/home/partners/redpanda.png) ![](/home/partners/qdrant.png) ![](/home/partners/aiven.svg) ![](/home/partners/thoropass.png) Customer outcomes ## More partner-driven growth. Less operational drag. Marketplace revenue, co-sell referrals and partner programs, run by teams who moved off spreadsheets and portals. [See all customer stories](/resources/customer-stories/) > \[Fours\] isn’t just useful in one stage — it impacts our entire process, from pipeline sharing to deal closure and finance tracking. **Amin Marts** _Strategic Alliances & Ecosystem Leader, JumpCloud_ One record to finance [Read story](/resources/blog/jumpcloud/) > \[Fours\] saves me at least half a headcount in billing operations. **StreamNative** _From the StreamNative customer story_ 4 months of engineering time saved [Read story](/resources/blog/streamnative/) > With \[Fours\], I can search entitlements and kick off a renewal without needing to dig through ACE or Salesforce. It pulls in all the data I need: contract terms, expiration dates, customer details, and gets me started in seconds. **Teleport** _From the Teleport customer story_ Seconds to start a renewal [Read story](/resources/blog/teleport/) ## Your marketplace revenue, already reconciled. Thirty minutes on your billing motion and where the manual work is today. [See Fours in action](/schedule-demo/) Usage to revenue, one system