Free Revenue Recognition Schedule Template (2026)

A customer might pay for a 12-month subscription upfront, sign a contract that includes implementation and support, or upgrade partway through the year.

‍

In each case, finance still needs to work out how much of that contract belongs in the current month and how much should be recognized later.

‍

A revenue recognition schedule helps finance teams track that difference. It shows how much revenue belongs in each accounting period, what remains deferred, and how the schedule ties back to the general ledger.

‍

This free template gives you a starting point. It includes contract allocations, monthly revenue recognition, deferred revenue, a revenue waterfall, contract modifications, journal entries, and reconciliation checks.

‍

[tldr]

Download the free revenue recognition schedule template

Get the free template

‍

The workbook has six tabs:

‍

Tab	What it covers
Start Here	Key checks and a short instruction for using the workbook
Contract Allocation	Contract terms, standalone selling prices, allocations, and recognition patterns
Revenue Schedule	Monthly revenue recognition and three proration methods
Deferred Rev	Deferred revenue roll-forward, remaining revenue, and GL reconciliation
Modifications	Examples showing how contract changes can affect the schedule
JEs Reconciliation	Billing entries, monthly revenue entries, and reconciliation checks

‍

The same sample contract runs through the entire workbook, so the allocation, revenue schedule, deferred revenue balance, and journal entries all connect.

What is a revenue recognition schedule?

A revenue recognition schedule shows how much revenue a company should recognize from a contract in each accounting period.

‍

It's especially useful when customers pay in advance or when a contract covers several months.

‍

Say a customer pays $120,000 upfront for a 12-month software subscription. The company receives the full amount immediately, but assuming the service is provided evenly throughout the year, it would recognize the revenue over the 12-month service period rather than recording $120,000 on day one.

‍

Under ASC 606, revenue is recognized when or as the related performance obligations are satisfied ^[¹^].

‍

The schedule gives finance a clear view of how much revenue has been recognized, how much remains, and what should be recorded at month-end.

Revenue recognition schedule vs. deferred revenue schedule vs. revenue waterfall

These schedules use much of the same contract information, but they answer different questions.

‍

Schedule	What it shows
Revenue recognition schedule	How much revenue is recognized in each accounting period
Deferred revenue schedule	Opening deferred revenue, new billings, recognized revenue, and the closing liability
Revenue waterfall	Revenue expected to be recognized in future periods from existing contracts
Remaining performance obligations (RPO)	Contracted revenue allocated to obligations that have not yet been fully satisfied

‍

A revenue waterfall should also not be confused with an ARR bridge.

‍

An ARR bridge tracks changes in recurring revenue from new business, expansion, contraction, and churn. It's a SaaS operating metric. A revenue recognition schedule is an accounting schedule.

‍

Deferred revenue and RPO can differ too. Deferred revenue generally relates to amounts already billed or collected before the related revenue is recognized. RPO can also include contracted amounts that have not yet been billed.

How to create a revenue recognition schedule

1. Identify the contract and performance obligations

Start with the customer contract. Record the service dates, billing terms, contract value, and the goods or services promised to the customer.

‍

Then determine which promises are separate performance obligations.

‍

Under SaaS revenue recognition, a SaaS contract might include:

‍

a software subscription
implementation services
premium support

‍

Those services may have different recognition patterns, so finance needs to identify them before calculating monthly revenue.

2. Determine and allocate the transaction price

Next, determine the transaction price and allocate it across the performance obligations where required.

‍

The sample contract in the template is worth $130,000 and includes three obligations:

‍

Performance obligation	Contract price	Standalone selling price	Allocated amount
Subscription	$108,000	$120,000	$104,000
Implementation	$12,000	$15,000	$13,000
Premium support	$10,000	$15,000	$13,000
Total	$130,000	$150,000	$130,000

‍

The allocations are based on the relative standalone selling prices, or SSPs, the basis ASC 606-10-32-31 sets out ^[²^].

‍

For example, the subscription represents 80% of the total $150,000 SSP. So: $130,000 × 80% = $104,000.

‍

The same calculation allocates $13,000 each to implementation and premium support.

3. Determine when each obligation should be recognized

The next step is deciding when revenue from each obligation belongs in the financial statements.

‍

In our example, the subscription and premium support are recognized over the service period. Implementation is treated as a separate performance obligation. To keep the example simple, the template assumes it meets none of the ASC 606-10-25-27 over-time criteria ^[³^], so it is recognized at a point in time, when the work is completed on April 30, 2026. That is not a free choice in practice: implementation services often do meet one of those criteria, and when they do, revenue is recognized as the work is performed.

‍

That gives us:

‍

Subscription: $104,000 recognized over time
Premium support: $13,000 recognized over time
Implementation: $13,000 recognized in April

‍

The subscription and support therefore give us $117,000 of ratable revenue to spread across the service period.

4. Choose a recognition method

The contract runs from March 15, 2026, through March 14, 2027, so it does not line up neatly with calendar months.

‍

Finance therefore needs a policy for handling the partial first and final months. The workbook compares three approaches:

‍

daily proration
monthly recognition with prorated first and final months
a half-month convention

‍

ASC 606 does not automatically require one of these methods. The recognition method should depict how the service is transferred to the customer and be applied consistently to similar performance obligations (ASC 606-10-25-31 and 25-32) ^[⁴^]. A half-month convention is a simplification rather than a method the standard names, so it only works where the result is not materially different from a measure of progress that depicts that transfer.

5. Calculate the revenue for each month

Once the method is chosen, calculate the revenue that belongs in each reporting period.

‍

For daily proration: $117,000 ÷ 365 days = about $320.55 per day

‍

The contract begins on March 15, so there are 17 service days in March: $117,000 ÷ 365 × 17 = $5,449.32

‍

April has 30 service days: $117,000 ÷ 365 × 30 = $9,616.44

‍

Because the $13,000 implementation obligation is also completed in April, total April revenue becomes: $9,616.44 + $13,000 = $22,616.44

6. Check the schedule before posting

Once the schedule is complete, confirm that the total revenue adds back to the allocated transaction price.

‍

In the sample workbook:

‍

Total allocated transaction price: $130,000
Total scheduled revenue: $130,000
Difference: $0

‍

The workbook also checks the deferred revenue balance and journal entries before the schedule is used for month-end reporting, a step on any month-end close checklist.

Revenue recognition schedule example

Let's use the sample contract from the template.

‍

A SaaS company signs a $130,000 contract that runs from March 15, 2026, through March 14, 2027. The contract includes a software subscription, implementation services, and premium support.

‍

After allocating the transaction price, $117,000 relates to subscription and support and is recognized over time. Another $13,000 relates to implementation and, under the template's point-in-time assumption, is recognized when that work is completed.

‍

Using daily proration, the schedule begins like this:

‍

Month	Service days	Ratable revenue	Implementation	Total revenue
March 2026	17	$5,449.32	$0	$5,449.32
April 2026	30	$9,616.44	$13,000	$22,616.44
May 2026	31	$9,936.99	$0	$9,936.99
June 2026	30	$9,616.44	$0	$9,616.44

‍

The amount changes slightly between 30-day and 31-day months because the daily method recognizes revenue based on the number of service days.

‍

The template also lets you compare this with monthly and half-month proration.

‍

For March, the three methods produce:

‍

Method	March revenue
Daily	$5,449.32
Monthly proration	$5,346.77
Half-month	$4,875.00

‍

All three recognize the same $117,000 over the full service period. What changes is the timing between individual months.

‍

The final month includes a small rounding adjustment so the entire schedule adds back to $117,000 exactly.

How to calculate deferred revenue using a revenue recognition schedule

Deferred revenue arises when a customer is billed or pays before the company has satisfied the corresponding performance obligation.

‍

A basic roll-forward is: Opening deferred revenue + billings + adjustments − revenue recognized = closing deferred revenue

‍

In the sample, the entire $130,000 contract is billed upfront on March 15. At March 31:

‍

Opening deferred revenue: $0
Billings: $130,000
Revenue recognized: $5,449.32
Closing deferred revenue: $124,550.68

‍

The calculation is: $0 + $130,000 − $5,449.32 = $124,550.68

‍

As more revenue is recognized, the deferred revenue balance continues to fall. By September 30, cumulative recognized revenue reaches $77,109.61.

‍

That leaves: $130,000 − $77,109.61 = $52,890.39

‍

The template compares that amount with the general ledger so finance can investigate any difference during the close.

How contract modifications affect the schedule

Revenue schedules also need to change when customer contracts change. Common examples include added seats, additional services, upgrades, renewals, and changes to pricing.

‍

The accounting depends on what changed and how the new goods or services are priced:

Adding services at standalone selling price

Suppose the customer adds $30,000 of distinct services on September 15, 2026, and the new services are priced at their standalone selling price.

‍

Because the added services are distinct and priced at standalone selling price, ASC 606-10-25-12 treats the addition as a separate contract ^[⁵^].

‍

There are 181 service days remaining: $30,000 ÷ 181 = about $165.75 per day

‍

The original schedule continues as before, while the added services get their own schedule.

Changing the remaining contract

Now suppose the customer adds the same services for $20,000 instead.

‍

Because the price is below standalone selling price, the change is not a separate contract. Assuming the remaining services are distinct from those already delivered, ASC 606-10-25-13(a) accounts for it prospectively, as if the original contract were terminated and a new one created. By September 14, the company has recognized $58,980.82 of the original ratable amount.

‍

That leaves: $117,000 − $58,980.82 = $58,019.18

‍

Add the $20,000 modification: $58,019.18 + $20,000 = $78,019.18

‍

Spread over the remaining 181 days: $78,019.18 ÷ 181 = about $431.05 per day

‍

The company uses the new rate going forward rather than changing revenue already recognized.

‍

Other modifications can require different treatment. When the remaining goods or services are not distinct, ASC 606-10-25-13(b) requires a cumulative catch-up adjustment instead, so finance should review the specific terms of the change.

Revenue recognition journal entries

Once the schedule is complete, the amounts need to reach the general ledger.

Recording the upfront invoice

The customer is billed $130,000 on March 15 before the full service has been delivered.

‍

The entry is:

‍

Account	Debit	Credit
Accounts receivable	$130,000
Deferred revenue		$130,000
Total	$130,000	$130,000

‍

Assuming the contract is non-cancellable and the invoice is due, the company has an unconditional right to the $130,000. The invoice therefore creates a receivable and a deferred revenue liability (a contract liability in ASC 606 terms) ^[⁶^]. It does not create $130,000 of revenue.

Recognizing March revenue

At March 31, the schedule shows $5,449.32 of revenue.

‍

Account	Debit	Credit
Deferred revenue	$5,449.32
Subscription revenue		$4,843.84
Support revenue		$605.48
Total	$5,449.32	$5,449.32

‍

This reduces the deferred revenue liability and records the portion earned during March. In April, the same process also includes the $13,000 implementation revenue once that performance obligation is completed.

How to review and reconcile a revenue recognition schedule

The schedule should be reviewed during the month-end close, especially when new contracts or modifications have been added.

‍

A few checks are particularly useful:

‍

Check the contract dates: Make sure the service period matches the signed agreement.
Review the allocation: Confirm the transaction price and SSP calculations still agree with the contract.
Compare scheduled and posted revenue: The amount recognized in the ledger should agree with the schedule.
Reconcile deferred revenue: Compare the closing schedule balance with the general ledger liability.
Review contract changes: Check new upgrades, renewals, credits, and other modifications before close.
Check the totals: Total recognized revenue plus any amount remaining should reconcile to the allocated transaction price.

‍

The sample workbook includes these checks directly. At the end of the schedule:

‍

Allocated transaction price: $130,000
Total scheduled revenue: $130,000
Ending deferred revenue: $0
Journal entry difference: $0

‍

That makes it easier to see whether a problem comes from the schedule itself or from what was posted to the general ledger.

Automate revenue recognition schedules with DualEntry

A spreadsheet can work well when the number of contracts is manageable and the arrangements are relatively straightforward.

‍

The process becomes harder as contract volume grows. Finance may be managing different billing terms, multiple performance obligations, upgrades, renewals, change orders, and journal entries across hundreds or thousands of customer contracts.

‍

DualEntry's revenue recognition software brings these workflows into the accounting system.

Finance teams can manage SSP-based revenue allocations, recognition schedules, deferred revenue, contract changes, and related journal entries without maintaining a separate spreadsheet for every contract.

‍

That keeps the schedule closer to the underlying accounting data and reduces the amount of manual work required during close.

Revenue recognition schedule FAQs

What are the five steps of revenue recognition under ASC 606?

The five steps of revenue recognition under ASC 606 are to identify the contract with the customer, identify the performance obligations in that contract, determine the transaction price, allocate the transaction price to those performance obligations, and recognize revenue when or as each obligation is satisfied.

How do you create a deferred revenue schedule in Excel?

Start with the opening deferred revenue balance, add new billings or deferrals, subtract revenue recognized during the period, and include any relevant adjustments. The closing balance should reconcile with the deferred revenue liability in the general ledger.

What is the difference between a revenue schedule and a revenue waterfall?

A revenue recognition schedule shows how much revenue is recorded in each accounting period. A revenue waterfall focuses on the amount expected to be recognized in future periods from contracts already in place.

What is ratable revenue recognition?

Ratable revenue recognition spreads revenue systematically across the period in which a service is provided. For example, a software subscription that provides the same service throughout a 12-month period may be recognized evenly over that service period if the method appropriately reflects how the performance obligation is satisfied.

How do you calculate monthly revenue recognition?

The calculation depends on the recognition method. For a simple annual subscription recognized evenly by month, you could divide the amount allocated to the subscription by 12. For contracts that begin or end partway through a month, finance may instead prorate the first and final periods using days of service or another supportable method.