Skip to content
Create account
or
Sign in
The Stripe Docs logo
/
Ask AI
Create account
Sign in
Get started
Payments
Revenue
Platforms and marketplaces
Money management
Developer resources
APIs & SDKsHelp
Overview
Billing
OverviewAbout the Billing APIs
Subscriptions
Invoicing
Usage-based billing
Quotes
Customer management
Billing with other products
Revenue recovery
Automations
Test your integration
Tax
Overview
Use Stripe tax
Manage compliance
Reporting
Overview
Select a report
Configure reports
Reports for multiple accounts
Reports API
Revenue recognition
    Overview
    Get started
    How Revenue Recognition works
    Data freshness
    Pricing
    Multi-currency
    Connect platforms
    Revenue Recognition for Usage-Based Billing
    Revenue contracts
    Reports
    Overrides
    Audit your numbers
    Examples
    Revenue recognition rules
    Revenue Recognition settings
    Map to your chart of accounts
    Performance obligations API
    Import data to Stripe
    Export data from Stripe
    Standalone selling price
Data
Overview
Query business data
Sigma
Data Pipeline
Import external data
HomeRevenueRevenue recognition

Revenue Recognition for usage-based billingPrivate preview

Learn how revenue recognition works with usage-based billing.

The Stripe Revenue Recognition feature for usage-based billing helps with the revenue recognition process for businesses that use usage-based billing models. It allows you to recognize revenue that aligns with actual customer consumption, which can help provide accurate financial tracking and improved cash flow management.

Usage-based metered event

No further setup is required if you have a usage-based billing metered event through Stripe Billing. Stripe Revenue Recognition automatically recognizes this revenue for you.

As an example, say you have a customer on a pricing model where it costs 1 USD per unit with a subscription for 100 units. They consume these units over multiple days and months as follows:

  • 20 units on March 2
  • 25 units on March 30
  • 15 units on April 1
  • 25 units on April 20
  • 15 units on April 28

In this case, the customer consumes a total of 45 units in March and 55 units in April without being billed. The ledger entries for this revenue recognition are as follows:

MonthDebitCreditAmountDescription
MarchUnbilledAccountsReceivableRevenue45.00Revenue in March from 45 usage units.
AprilUnbilledAccountsReceivableRevenue55.00Revenue in April from 55 usage units.

Billed usage-based metered event

Based on your configuration, Stripe creates an invoice for the consumed units that reflects the recorded usage.

To continue with the previous example, Stripe finalizes an invoice on April 1, for a total consumption of 60 units. At the end of the month, the journal entries appear as follows:

MonthDebitCreditAmountDescription
MarchUnbilledAccountsReceivableRevenue45.00Revenue in March from 45 usage units.
AprilUnbilledAccountsReceivableRevenue55.00Revenue in April from 55 usage units.
AprilRevenueUnbilledAccountsReceivable60.00The reversal of revenue with the April invoice for billed usage units.
Was this page helpful?
YesNo
  • Need help? Contact Support.
  • Check out our changelog.
  • Questions? Contact Sales.
  • LLM? Read llms.txt.
  • Powered by Markdoc