Revenue Recognition methodology

Revenue Recognition is integrated with other Stripe objects to provide intelligent default settings for how to recognise revenue.

Revenue Recognition automatically calculates all transactions that happen within Stripe down to the millisecond, including subscriptions, invoices, one-time payments, refunds, disputes, and so on.

Chart of accounts

Stripe built Revenue Recognition on top of a double-entry accounting ledger that tracks debits and credits resulting from your business activity.

To get the most out of Revenue Recognition, it helps to understand the default chart of accounts and the debits and credits that impact those accounts.

Data modeling for Revenue Recognition

See the following descriptions of how Revenue Recognition handles common Stripe resources to learn how Revenue Recognition uses data modelling.

Subscriptions and Invoicing

Subscriptions and Invoices are higher level resources that contain detailed information about each transaction.

Subscriptions create invoices on each cycle, with each subscription item corresponding to an invoice line item. The period of each line item is automatically populated with the period of the subscription item.

Revenue Recognition treats each invoice line item as its own performance obligation. When the invoice finalises, the total recognisable amount is deferred and subsequently amortised evenly over the period of each invoice line item.

If a period isn’t set on an invoice line item, the amount on that invoice line item is recognised entirely when the invoice is finalised. Use the Data Import feature to configure your invoice data, or set rules to customise when and how invoice line items are recognised.

For more details and examples regarding how Revenue Recognition handles subscriptions and invoices with specific scenarios involving upgrades, downgrades, discounts, taxes, and so on, review the Subscriptions and Invoicing page.

One-time payments

One-off payments created through Checkout contain information about the product, price, and tax starting 1 May 2025.

One-off payments created in the Dashboard or through the Charges and PaymentIntents APIs don’t contain as much information as invoices.

Because no service period or fulfillment information exists for them, by default, one-time payments are recognized immediately when the payment occurs.

Import data to add a service period or split a payment into different revenue recognition schedules. This allows you to customise revenue treatment behaviour and configure rules such as payment amount, description, and customer email.

For more details and examples on how Revenue Recognition handles one-off payments, review the One-off payments page.

Refunds and disputes

Revenue Recognition handles refunds and disputes by generating contra revenue to offset already recognized revenue.

For transactions with both already-recognized and deferred revenue, the recognized portion is added to either the refunds or disputes contra revenue account, which cancels out the deferred revenue.

For more details and examples on how Revenue Recognition handles refunds and disputes, review the Refunds and Disputes page.

External transactions

You can track revenue collected outside of Stripe using invoices. Configure the invoice as you would any other, and then mark the invoice as paid either directly in the Dashboard, or through the paid_out_of_band option in the API.

Invoices marked as paid outside of Stripe contribute not to the cash account, but rather to the external asset account.

Multi-currency

If your business handles transactions in multiple currencies, accurately recognizing revenue can be complicated.

Revenue Recognition processes transactions and generates journal entries based on your account’s settlement currencies. Transactions with presentment currencies that aren’t supported as settlement currencies are automatically converted to your account’s default settlement currency.

For payments and paid invoices, we use the exchange rate for the actual money movement (that is, reflected on the balance transaction). If you incur a time delay between issuing a bill (for example, an invoice) and it getting paid, the difference in amounts because of changing exchange rates between the two times is added to the FxLoss account.

For more details and examples on how Revenue Recognition handles multiple currencies, review the Multi-currency page.

Data availability

Revenue Recognition computes your data twice daily, at 0:00am UTC and at 12:00pm UTC.

The data processed at 0:00am UTC encompasses account activity from the prior day’s 12:00pm to that day’s 11:59pm UTC. The 12:00pm UTC update covers activity from 0:00am to 11:59am UTC of the same day.

It can take up to 24 hours to process the data. Users in time zones far from UTC might notice slight delays in reports because late-day activity in PST corresponds to early hours of the following day in UTC.

As an example, you might have account activity occurring on 1 August 2023, from 0:00 am to 11:59 am UTC. You can expect to see this activity reflected in the Revenue Recognition reports by 4 August 2023, at 12:00 pm UTC. Similarly, you can access reports for activity from 12:00 pm to 11:59 pm UTC on 1 August 2023 by 5 August 2023, at 0:00 am UTC.

Journal entries

Every billing activity in Stripe generates a set of journal entries. A journal entry is a record of a transaction. Each journal entry consists of a debit and a credit account. For example, an entry which finalises an invoice would debit AccountsReceivable and credit DeferredRevenue. Paying an invoice would debit Cash and credit AccountsReceivable.

These entries can occur in asset, liability, equity, expense, or revenue accounts. You can learn more about the definitions of each account that will appear in a journal entry under our Chart of accounts section.

The table below shows the applicable billing activities for common journal entries. You can export journal entries to CSV using the debits and credits report, which you can find in the Reports tab in the Dashboard. In addition, there are options to download debits and credits reports by the event type, which provide a brief description of the recorded event, which can help you understand the nature of each journal entry.

The activities above are all based on positive amounts. It is important to note that these billing activities can be reversed. These reverse activities occur when activities are triggered on negative invoice line item amounts.

Negative Line Item

A negative line item occurs when the value of the line item becomes higher than the amount it is paid for. This occurs typically during a subscription downgrade or upgrade when the product tier changes.

Here is an example of journal entries which contains a negative line item caused by a downgrade:

• On 1 April, the invoice is generated for a monthly subscription worth 90 USD and the customer pays for it.
• On 21 April, the customer requests a downgrade of their service to a 30 USD subscription. This results in 2 unbilled line items for the remaining time of the subscription.
  • il_1 is for the remaining time on new plan worth 10 USD
  • il_2 is for the remaining time of old plan worth -30 USD
• On 1 May, the invoice is generated containing the line items generated by the downgrade as well for the new line item, il_3, representing the month of May. The customer pays for the invoice on the same day.
• On 4 May, the customer requests a full refund on the invoice for May, resulting in full refunds on the line item created by the downgrade as well as the new line item for May. We process the refund.