Revenue Recognition settings examples

Amortisation granularity

This example uses the following assumptions:

• On 15 June 2024 at 12:00:00 PM UTC, a customer starts a 4-month subscription that costs 120 USD.
• The subscription generates an invoice.
• The invoice finalises and the customer pays 120 USD.

In this example, the invoice and revenue periods are from 15 June 2024 12:00:00 PM UTC to 13 October 2024 12:00:00 PM UTC. The 120 USD is recognised across 15.5 days in June, 31 days in July, 31 days in August, 30 days in September and 12.5 days in October. We can use this example to demonstrate the differences between our supported amortisation methods.

If you looked at the summary after October ends, amortisation by millisecond applied, you might see something like:

If you looked at the summary after October ends, amortisation by day applied, you might see something like:

If you looked at the summary after October ends, amortisation by month evenly applied, you might see something like:

If you looked at the summary after October ends, amortisation by month evenly, first and last month pro rata applied, you might see something like:

Catch-up revenue

This example uses the following assumptions:

• On 1 November 2024, at 00:00:00 UTC, a customer is billed for an invoice that costs 92 USD.
• The invoice has service periods from 1 Oct 2024 to 1 Jan 2025 for all of its line items.
• The invoice finalises and the customer pays 92 USD.

In this example, the service period for the transaction begins prior to the invoice finalisation, triggering the catch-up revenue effect. We can use this example to demonstrate the differences between enabling and disabling catch-up revenue.

After December ends, with catch-up revenue enabled, the summary might look like:

After December ends, with catch-up revenue disabled, the summary might look like: