Recognize revenue from metered and usage billing data

domain: accounting-general · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Ingest raw usage events from your metering system (API or message queue), including customer_id, product_id, usage_quantity, usage_timestamp, and unit_price or rate_schedule reference.
  2. Apply the rate schedule to each event to compute the billable amount; aggregate events by customer, product, and billing period to produce a usage summary matching what the billing system will invoice.
  3. Determine the revenue recognition timing: for usage-based arrangements, ASC 606-10-55-18 permits recognizing revenue in the amount billed if the billed amount corresponds directly to the value delivered; document this election in your revenue recognition policy.
  4. Write a recognition journal entry at the end of each billing period (or upon invoice generation): debit accounts receivable or unbilled revenue, credit revenue, for the aggregated usage amount per customer per product.
  5. For partially delivered periods (e.g., month-end cut-off with usage not yet billed), accrue unbilled revenue by computing usage through the period-end date and posting to an unbilled AR account, reversing at the start of the next period.
  6. Reconcile recognized revenue against the metering system's total event quantity multiplied by rate for each period to detect rating engine discrepancies before they reach the GL.

Known gotchas

Related routes

Pull revenue recognition data from a subscription billing rev-rec module
accounting-general · 6 steps · unrated
Aggregate usage-based metered billing correctly to avoid over- or under-charging
stripe.com · 6 steps · unrated
Implement usage-based billing with Stripe Billing Meters and metered subscriptions
stripe.com · 6 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans