Revenue recognition examples: How to recognize revenue in different scenarios

Revenue recognition determines when a business can record revenue in its financial statements for the goods and services it provides. The timing of revenue recognition depends on the type of transaction, the actual terms of the contract, and when the business fulfills its obligations to the customer. For example, revenue from sale of a product can be recognized as soon as it is delivered, whereas revenue from an annual subscription needs to be recognized periodically over the subscription period.

Understanding how revenue recognition works in different scenarios help businesses maintain accurate financial records, comply with their respective accounting standards, and report revenue accurately. Below are 15 common scenarios, each with a small worked example and the treatment under ASC 606, IFRS 15, and Ind AS 115. All three follow the same five-step model, so the logic is identical across them.

Core subscription scenarios

1. Monthly subscription

This is one of the most straightforward cases. A customer pays $100 for a monthly subscription. If you invoice at the start of the month and the service is delivered across the month, the amount initially sits as deferred revenue and recognized as revenue at the month-end.

2. Annual subscription paid upfront

Let's say a customer pays $12,000 on January 1 for a year of software access.

When payment is received:    
Debit: Cash $12,000  
Credit: Deferred revenue $12,000

Each month:  
Debit: Deferred revenue $1,000 
Credit: Revenue $1,000

At the end of the year, the deferred balance will become zero and the full $12,000 is revenue.

3. Multi-year contract

A customer pays $30,000 upfront for a service that is to be delivered over three years. Revenue is recognized evenly at $10,000 per year. The remaining amount sits as deferred revenue on the balance sheet. The portion expected to be recognized within the next 12 months is classified as current, while the remaining amount sits as non-current deferred revenue.

If the customer pays way ahead of service delivery, check whether the arrangement includes a significant financing component. If it does, then the price need to be adjusted to reflect the time value of money, and the financing effect (interest) will be recognized separately over the period.

4. Usage-based pricing

A customer is charged $0.01 per API call and makes 100,000 calls a month. Revenue to be recognized based on usage is $1,000 at the end of the month. If there is a minimum commitment involved, revenue will be the guaranteed minimum or actual usage, whichever is higher.

For estimation and constraint rules, see our guide to usage-based revenue recognition.

5. Free trials

Lets say the user signs up for a 14-day free trial. No revenue is to be recognized during the trial period as there is no payment yet. The revenue recognition process begins on the date when the customer becomes a paying customer and not when signup happens.

6. Subscription pause

After paying upfront for an annual subscription, a customer requests a two-month pause in service. No service will be delivered during this break, so no revenue is recognized. The subscription end date moves forward by two months and the revenue process continues once the service resumes.

Fees, services, and pricing structure

7. One-time setup fee

A customer pays a $1,200 setup fee alongside an annual subscription. If the setup is not a distinct service, meaning the customer can't benefit from it on its own, the fee is recognized as revenue over the entire subscription term at $100 every month. If it delivers something separately useful, like a complete data migration, the fee is recognized as revenue when the work is delivered.

8. Project milestones

A $10,000 project runs over five months. Revenue follows progress measured by milestones. If the project is 30% completed in month one, recognize $3,000. If the project is delivered in three months, recognize revenue each month based on what is completed in that month. Under revenue recognition rules, a project’s estimated duration doesn't determine when revenue is recognized. What matters is how much of the promised work is completed.

9. Discounts and promotions

A $12,000 annual plan sold at 25% discount has a transaction price of $9,600. This should be recognized at $800 every month. It shouldn't be recognized at $1,000 every month with a discount booked on the side. Similar treatment is done for a "pay for 12 months, get 2 free" offer. $12,000 needs to be spread over 14 months instead of 12 and should be recognized at $857.14 a month.

10. Bundled products and services

A software bundle is sold for $10,000. The standalone prices are $8,000 for software access and $4,000 for implementation. The bundle price is allocated in proportion:

Software: $10,000 x $8,000/$12,000 = $6,666.66, recognized at $555.55 a month
Implementation: $10,000 x $4,000/$12,000 = $3333.33 recognized when implementation is completed

11. Gift cards and prepaid credits

For prepaid credits and gift cards, revenue is recognized when the credit is utilized. The portion expected to go unutilized (breakage) can be recognized in proportion to redemptions based on past data. We have covered this in detail in our guide on revenue recognition for gift cards.

When the contract changes

12. Mid-cycle upgrade

A customer buys a $100 per month plan and upgrades to a $200 plan in the middle of the month. In such a case, the customer will pay the prorated difference of $50 (15 days x $100 difference ÷ 30). Revenue for the month is $50 for the first half from the original plan and $100 for the second half from the upgraded plan, a total of $150.

13. Downgrade

Suppose the reverse happens, where a customer downgrades from a $200 plan to a $100 plan in the middle of the month. Revenue for the second half of the month is $50 instead of $100, and a $50 credit is issued to the customer. If that credit is applied to the next invoice, it sits as a liability until then.

14. Cancellation

A customer on a $1,200 annual plan cancels after six months, leaving half of the subscription amount in deferred revenue. What happens next depends on your refund policy. If they can keep access until the end of the period, keep recognizing $100 every month. If access is revoked and the amount is non-refundable, then recognize the remaining $600 immediately. If access is revoked and the amount is refundable, then move the $600 from deferred revenue to cash/refund payable account.

15. Refunds

There are two scenarios. For an unearned service, reverse it from deferred revenue like what we saw in the previous example. For money-back guarantee programs, estimate expected refunds based on past patterns and recognize revenue net of them. For example, if 10% of sales are typically paid back, recognize 90% and put the remaining 10% as a refund liability. True it up as actual refunds come in.

Keeping these straight at scale

None of the above scenarios are difficult to process for a given customer. The real problem happens at scale when 100s and 1,000s of customers trigger various scenarios. Zoho Billing includes a revenue recognition module that distributes invoice revenue across the actual service period, tracks deferred and recognized revenue as subscriptions change, and offers various revenue recognition reports that help businesses with a live view of where they stand. For arrangements that don't follow a standard ratable schedule, manual revenue recognition lets you control recognition at the line-item level.

Conclusion

Irrespective of the variations, all the scenarios ask the same question: Has the customer received what they paid for yet? If yes, it is counted as revenue. If not, it sits as deferred revenue until the obligation is fulfilled. Keep that question in mind and most cases become a matter of mathematics and documentation. If you want to learn about how to book journal entries for these examples, see our guide on booking revenue recognition journal entries.

Frequently asked questions (FAQs)