Revenue Recognition Review Checklist Template (ASC 606 & IFRS 15)

Revenue errors are rarely made at month-end. They are made when a contract with a side letter, a bundled licence or a usage tier is signed and nobody in finance reads it before the first invoice goes out.

This free revenue recognition review checklist is for controllers, revenue accountants and CFOs who need every new or changed customer contract assessed before revenue is recorded. It takes one contract through the five-step model in ASC 606, IFRS 15 and the revised Section 23 of FRS 102: the contract, performance obligations, transaction price, allocation and timing, then contract costs, disclosure data, a review memo and controller approval. Three scope questions decide whether the contract modification, over-time measurement and non-standard technical review phases appear, so a standard order form gets a short review and an unusual deal gets the full one.

Use This Template Free See Live Example
No Credit Card Required

Last reviewed: October 2026

Where the Contract Review Sits in the Revenue Cycle

Revenue passes through three processes that are easy to confuse. The billing run raises invoices on the contract’s payment terms. The month-end close books revenue from schedules already set up. The contract review, which this checklist runs, decides what those schedules should be in the first place, one contract at a time, before any revenue is recognised on it.

Under all three frameworks, revenue follows the transfer of control of goods or services, not the invoice. A three-year subscription billed annually in advance, a hardware sale with installation, or a licence with a year of support each produce a revenue pattern that differs from the billing pattern, and the difference sits on the balance sheet as a contract asset or a contract liability. If the review is wrong, every later close repeats the error.

Billing run

Invoices what the contract says

  • Monthly, across all customers
  • Follows payment terms and usage
  • Creates receivables, not revenue decisions
Month-end close

Books revenue from the schedules

  • Monthly, across the ledger
  • Reconciles deferred revenue and contract balances
  • Relies on schedules being right
Contract review

Decides what the schedule should be

  • Per contract, at signing or modification
  • Applies the five steps and records judgements
  • Ends in a memo and an approval

What the Revenue Recognition Review Checklist Covers

Seven phases take one contract from intake to approval. Phase 2 appears only for a contract modification, Phase 5 only when a performance obligation is satisfied over time, and Phase 7 only for non-standard terms or a contract above your review threshold.

Intake

Phase 1: Contract Intake & Scope

Owned by the revenue accountant. The scope questions decide which later phases this review shows.

  • Log the contract and name the deal owner, revenue accountant, controller and CFO — every later task is assigned from these fields
  • Attach the full contract set — master agreement, order forms, statements of work, amendments, side letters and any email that changes terms
  • Check for contracts that must be combined — with the same customer, at or near the same time, negotiated as a package or with linked prices
  • Answer the scope questions — is this a modification of an existing contract, may any obligation be satisfied over time, and are there non-standard terms or a value above the review threshold
  • Record the framework and the policy elections that apply — ASC 606, IFRS 15 or FRS 102 Section 23, and the practical expedients the company has adopted
If Modified

Phase 2: Contract Modification

Shown only when the contract changes the scope or price of an existing one. Classify the modification first, because it decides what the later steps are applied to.

  • Confirm the modification is approved and enforceable — in writing, orally or by customary business practice, including unpriced change orders
  • Test whether it is a separate contract — distinct goods or services added, at a price that reflects their standalone selling prices
  • If not, choose the method — treat it as a termination and new contract when the remaining goods or services are distinct, or as a cumulative catch-up when they are not
  • Link this review to the original contract review — so the history of judgements on the customer stays in one trail
  • Quantify the effect on revenue already recognised — any catch-up is recorded in the period of the modification
Steps 1–2

Phase 3: Contract & Performance Obligations

  • Confirm a contract exists — approved, rights and payment terms identifiable, commercial substance and collection probable
  • Determine the enforceable contract term — termination-for-convenience clauses can make it much shorter than the stated term
  • List every promise, including implied ones — set-up, training, support, updates, and customer options that may be material rights
  • Test each promise for distinctness — capable of being distinct and distinct in the context of the contract
  • Assess principal versus agent for anything a third party provides — whether you control the good or service before it reaches the customer
  • Classify each licence — a right to access recognised over time, or a right to use recognised at a point in time
  • Test each performance obligation against the three over-time criteria — including whether a right to payment for work to date is enforceable
Steps 3–4

Phase 4: Transaction Price & Allocation

  • Separate fixed from variable consideration — discounts, rebates, refunds, credits, price concessions, bonuses, penalties and usage fees
  • Estimate variable consideration — using the expected value or the most likely amount, whichever better predicts the outcome
  • Apply the constraint and document the reasoning — include only what is unlikely to reverse significantly when the uncertainty resolves
  • Check for a significant financing component, non-cash consideration or payments to the customer — each changes the transaction price
  • Determine standalone selling prices — observable prices first, otherwise adjusted market assessment, expected cost plus margin, or the residual approach where allowed
  • Allocate the price and any discount — on relative standalone selling prices, unless the criteria for allocating to specific obligations are met
Over Time

Phase 5: Over-Time Measurement

Shown only when at least one performance obligation is satisfied over time.

  • Choose an output or input method for each obligation — the one that best depicts transfer of control, applied consistently to similar obligations
  • Exclude inputs that do not depict progress — uninstalled materials, wasted effort and costs from inefficiencies
  • Fall back to cost recovery where progress cannot yet be measured — revenue only to the extent of costs expected to be recovered
  • Update the measure of progress at each reporting date — changes are changes in estimate, booked as a cumulative catch-up
  • Assess whether the contract is loss-making — IAS 37 under IFRS, ASC 605-35 for construction- and production-type contracts under US GAAP
Step 5

Phase 6: Recognition, Contract Costs & Approval

  • Identify when control transfers for point-in-time obligations — right to payment, legal title, physical possession, risks and rewards, and customer acceptance
  • Review bill-and-hold, consignment, acceptance and repurchase terms — each can delay or prevent recognition
  • Set up the revenue schedule and compare it with the billing schedule — the difference is the contract asset or contract liability
  • Account for contract costs — capitalise incremental costs of obtaining the contract, such as commissions, unless an expedient or policy choice applies
  • Capture the disclosure data — disaggregation category, contract balances, and remaining performance obligations with expected timing
  • Write the contract review memo — conclusion and evidence for each step, attached to this task
  • Controller approval of the revenue treatment — required before revenue is recognised on the contract
Non-Standard

Phase 7: Technical Accounting Review & CFO Approval

Shown only for non-standard terms or a contract value above the review threshold set in Phase 1.

  • Prepare a technical accounting memo — facts, issue, the paragraphs of the standard applied, alternatives considered and the conclusion
  • Quantify the effect against the standard treatment — revenue by period, contract balances and any change to forecasts
  • Consult the external auditors where the judgement is significant — and record their response on the task
  • Confirm the review control is evidenced — who reviewed what and when, for SOX 404 testing or the year-end audit
  • CFO approval of the revenue treatment — the checklist halts until it is given
  • Feed the outcome back to the deal desk — update the list of standard terms and the review threshold if this keeps recurring

Where ASC 606, IFRS 15 and FRS 102 Differ

ASC 606 and IFRS 15 were issued as a converged standard and share the five steps, but they are not identical. The differences below are the ones most likely to change the answer, which is why Phase 1 records the framework.

Topic ASC 606 (US GAAP) IFRS 15
Collectability (Phase 3)Collection must be probable, meaning likely to occur, a higher barCollection must be probable, meaning more likely than not
Constraint on variable consideration (Phase 4)Include only to the extent it is probable that a significant reversal will not occurInclude only to the extent it is highly probable that a significant reversal will not occur; the boards intended the same level of confidence
Financing component (Phase 4)No adjustment needed if the gap between transfer and payment is expected to be one year or lessThe same one-year practical expedient
Sales taxes (Phase 4)Policy election to exclude sales and similar taxes collected from customers from the transaction priceNo election: assess each tax as principal or agent
Shipping after control passes (Phase 3)Policy election to treat it as a fulfilment costNo election: often a separate performance obligation
Licences (Phase 3)Functional intellectual property is generally a right to use; symbolic intellectual property, such as brands, is a right to accessRight to access where your activities significantly affect the intellectual property the customer is exposed to; otherwise a right to use
Loss-making contracts (Phase 5)No general rule in ASC 606; ASC 605-35 applies to construction- and production-type contractsIAS 37 onerous contract provisions
Contract costs (Phase 6)ASC 340-40: capitalise incremental costs of obtaining a contract you expect to recover; expense them if the amortisation period is one year or lessThe same requirement and expedient, in IFRS 15 itself
Disclosures (Phase 6)Private companies may elect not to disclose remaining performance obligations and may give a reduced disaggregationFull disclosures; obligations in contracts of one year or less may be left out of the remaining obligations disclosure

FRS 102 now follows the five steps. The FRC’s Periodic Review 2024 rewrote Section 23 as Revenue from Contracts with Customers on the five-step model, for periods beginning on or after 1 January 2026, so the first calendar-year accounts affected are for 2026. It keeps some simplifications: a policy choice to expense or capitalise incremental costs of obtaining a contract, simpler allocation of discounts, a choice on whether to adjust for the time value of money when payment is received in advance, and fewer disclosures. On transition, companies can restate comparatives or record the cumulative effect in opening retained earnings. Companies that bill in advance, sell bundles or run long contracts should review them now.

What else is changing. FASB’s ASU 2025-07 clarifies that share-based payment received from a customer in a revenue contract stays within ASC 606 until the right to receive or keep it becomes unconditional, for annual and interim periods beginning after 15 December 2026. The IASB completed its post-implementation review of IFRS 15 in September 2024 and concluded the standard is working as intended, with no fundamental change planned.

Why Run Contract Reviews in CheckFlow?

1

No revenue before approval

The controller’s approval task halts the checklist until it is answered, and a non-standard contract adds a CFO approval on top. Start a review through the API when a deal closes, so no signed contract is missed.

2

The right depth for each contract

Three questions in Phase 1 decide the rest. A standard renewal at list price skips the modification and technical review phases. A bespoke multi-year deal with milestones gets all of them.

3

Evidence your auditors can test

The contract set, the review memo and each judgement are attached to the task that produced them, and every step records who completed it and when. Export the trail when the auditors select a sample of contracts.

Once the schedule is approved, the Monthly Invoicing & Billing Run Checklist invoices it and the Month-End Close Checklist books and reconciles it. Contracts usually reach finance through the Contract Review & Approval workflow, and the SOX Internal Control Testing Checklist tests the review control.

CheckFlow is not a revenue recognition engine or an accounting system: it does not calculate allocations or build schedules. It runs the review workflow around those tools, so every contract is assessed, approved and evidenced before the first revenue entry.

Frequently Asked Questions

What are the five steps of revenue recognition?

+

Under ASC 606, IFRS 15 and the revised FRS 102 Section 23: identify the contract with the customer, identify the performance obligations in it, determine the transaction price, allocate that price to the performance obligations, and recognise revenue when or as each obligation is satisfied. Phases 3 to 6 of this checklist follow those steps in order.

What is the difference between ASC 606 and IFRS 15?

+

They share the same model and most of the wording. The main differences are a higher collectability threshold under ASC 606, US-only policy elections for sales taxes and shipping, different guidance on classifying licences, different treatment of loss-making contracts and lighter disclosure options for US private companies. The table above sets them out.

When is revenue recognised over time rather than at a point in time?

+

When at least one of three criteria is met: the customer receives and consumes the benefit as you perform, your work creates or enhances an asset the customer controls as it is built, or your work creates an asset with no alternative use to you and you have an enforceable right to payment for work completed to date. Otherwise revenue is recognised at the point control transfers.

Do sales commissions have to be capitalised?

+

Under ASC 340-40 and IFRS 15, incremental costs of obtaining a contract that you expect to recover are capitalised and amortised, unless the amortisation period would be one year or less, when they can be expensed. That period can be longer than the initial contract if renewals are expected. Under the revised FRS 102 there is a policy choice to expense or capitalise them.

Does the new FRS 102 revenue section affect small UK companies?

+

Yes, if they report under FRS 102, including small entities using Section 1A. The revised Section 23 applies to periods beginning on or after 1 January 2026, with simplifications and fewer disclosures than IFRS 15. Micro-entities using FRS 105 get a further simplified version of the same five-step model from the same date.

Is CheckFlow free for this template?

+

14-day free trial, no card required. The Business plan is $10 per user per month after the trial. Full details at checkflow.io/pricing.

Review Every Contract Before the First Revenue Entry, Not After the Audit

Free trial — no credit card required.