Revenue Recognition Memo Template (IFRS 15, ASC 606)

Revenue Recognition Memo: [Contract or arrangement name]

Technical accounting memo for one customer contract or one contract type: contract summary, the five-step analysis (contract, performance obligations, transaction price, allocation, timing), principal versus agent, contract costs, modifications, disclosure, journal entries and conclusion. Structure aligned with the five-step model in IFRS 15 Revenue from Contracts with Customers (effective for annual periods beginning on or after 2018-01-01) and FASB ASC Topic 606 and Subtopic 340-40, cited by standard and paragraph number only. Obtain the standard for the normative text. Replace every [bracketed] value and every row marked Example. This is a document format, not accounting, audit, tax, legal or financial advice.

Document control

Approvals

Revision history

Contents

1. Summary and conclusion
2. Contract facts and documents reviewed
3. Step 1: Contract identification and combination
4. Step 2: Performance obligations
5. Step 3: Transaction price
6. Step 4: Allocation to performance obligations
7. Step 5: Timing of recognition
8. Principal versus agent
9. Contract costs
10. Contract modifications and renewals
11. Journal entries and financial statement effect
12. Presentation and disclosure
13. IFRS and US GAAP comparison
14. Controls, systems and monitoring
15. Glossary and references
16. Standard and licence note

1. Summary and conclusion

State the conclusion first, then the judgements that drive it. Keep the summary factual and quantified. If a judgement is close, say so and point to the section that sets out the alternative view, because the auditor will look for it.

Example: Corvid Commerce GmbH signed a three-year arrangement with Larkspur Outfitters on 2027-01-15 for 200 in-store terminals, a 36-month subscription to the Corvid retail platform and a fixed-fee implementation. The fixed consideration of EUR 390,000 is allocated to three performance obligations on a relative stand-alone selling price basis: terminals EUR 106,537 (recognised at delivery on 2027-02-01), implementation EUR 26,634 (recognised over February and March 2027 as hours are incurred) and the subscription EUR 256,829 (recognised evenly over 36 months from go-live on 2027-04-01, EUR 7,134 per month). Usage fees above the monthly allowance are allocated wholly to the month in which the usage occurs. FY2027 revenue from the fixed consideration is EUR 197,378, and a contract liability of EUR 12,622 remains at 2027-12-31. Corvid is principal for the terminals. The main judgement is that the terminals and implementation are distinct from the subscription (section 4).

2. Contract facts and documents reviewed

Read every document that forms part of the enforceable arrangement: master agreement, order forms, statements of work, price schedules, service-level terms, side letters and any written commitments made by sales staff. Ask the deal team directly whether any undocumented promises exist, such as free extra months, price protection or a promise to build a feature, and record the answer with the name of the person who confirmed it.

2.1 Documents reviewed

2.2 Key terms

3. Step 1: Contract identification and combination

Assess the criteria in IFRS 15 paragraph 9 (ASC 606-10-25-1) one by one, with evidence for each. Collectability deserves its own line, supported by the credit check or payment history, because a weak customer changes the whole accounting model for the contract. Record the contract term for accounting purposes: it is the period during which both parties have enforceable rights and obligations, which can be shorter than the stated term when the customer can cancel without a substantive penalty.

Then consider combination under IFRS 15 paragraph 17 (ASC 606-10-25-9). List every other contract with the same customer or its related parties signed within a window your policy defines, and record why each one is or is not combined.

Example conclusion: One contract exists from 2027-01-15. The enforceable term is 36 months of subscription plus the delivery and implementation period, because early termination requires payment of all remaining fixed fees. No other contract with Larkspur Outfitters was signed within 90 days, so no combination applies.

4. Step 2: Performance obligations

Start with a complete inventory of promised goods and services, including implied promises created by customary business practice. Exclude administrative tasks that do not transfer a good or service, such as internal account set-up. For each promise, record whether the customer can benefit from it on its own or together with readily available resources, and whether it is separately identifiable within the context of the contract. Reference IFRS 15 paragraphs 22 to 30 (ASC 606-10-25-14 to 25-22) for the criteria and write your evidence in the table; do not restate the criteria.

Decide next whether any obligation is a series of distinct goods or services that are substantially the same and transfer with the same pattern (IFRS 15.22(b) and 23; ASC 606-10-25-14(b) and 25-15). A monthly platform subscription is often accounted for as a series, which matters for variable consideration in section 6.

Consider customer options for additional goods or services. An option that gives a discount the customer would not receive without entering into the contract is a material right and a separate obligation (IFRS 15 B39 to B43; ASC 606-10-55-41 to 55-45). A renewal at the then-current list price is not a material right.

The most sensitive judgement in a hardware and software bundle is usually whether the device and the service are highly interdependent. In the example, the terminals run a general operating system, other certified point-of-sale applications run on them, and the platform also runs on third-party devices. That evidence supports a distinct conclusion. If Corvid's terminals only worked with the Corvid platform and the platform only worked with Corvid terminals, the analysis would be closer and you would document the alternative of a single combined obligation recognised over the subscription term.

5. Step 3: Transaction price

Build the transaction price from its components (IFRS 15 paragraphs 46 to 72; ASC 606-10-32-2 to 32-27). For each variable element, record the estimation method (expected value or most likely amount), the inputs, and whether the constraint applies. Explain your constraint conclusion in terms of the factors that make a reversal more or less likely, such as dependence on customer behaviour, a long uncertainty period or limited experience with similar contracts.

Assess financing when the timing of payments differs significantly from the timing of transfer. Note the practical expedient for periods of one year or less (IFRS 15.63; ASC 606-10-32-18) and the reasons why a difference in timing may arise for purposes other than financing.

Example arithmetic: the upfront payment of EUR 150,000 less the allocated amounts for the terminals (EUR 106,537) and implementation (EUR 26,634) leaves EUR 16,829 paid in advance for the subscription. The financing assessment uses this excess, not the full upfront amount.

6. Step 4: Allocation to performance obligations

Determine a stand-alone selling price for each obligation at contract inception (IFRS 15 paragraphs 76 to 80; ASC 606-10-32-31 to 32-35). Prefer observable prices from stand-alone sales to similar customers. Where none exist, use an estimation method and explain why it is the best evidence available. Keep the SSP study as a separate, dated document approved by the pricing or revenue committee, and refresh it at least annually.

Allocate any discount proportionately unless the conditions for allocating it to fewer obligations are met (IFRS 15 paragraphs 81 to 83; ASC 606-10-32-36 to 32-38). Allocate variable consideration entirely to one obligation or to one distinct period of a series when the conditions in IFRS 15 paragraphs 84 to 86 (ASC 606-10-32-39 to 32-41) are met, and document both conditions explicitly.

The relative allocation formula used below is:

Example check: EUR 390,000 / EUR 410,000 = 0.95122, so each obligation receives 95.122% of its SSP and the bundle discount of EUR 20,000 (4.88% of total SSP) is spread proportionately. The allocated amounts add back to EUR 390,000 (106,537 + 26,634 + 256,829). The usage fee relates specifically to Corvid's effort in a given month and allocating it to that month is consistent with the allocation objective, so it is excluded from the relative allocation.

7. Step 5: Timing of recognition

For each obligation, test whether one of the over-time criteria is met (IFRS 15 paragraph 35; ASC 606-10-25-27). If none is met, identify the point in time when control passes, using the indicators in IFRS 15 paragraph 38 (ASC 606-10-25-30): right to payment, legal title, physical possession, risks and rewards, and acceptance. For over-time obligations choose an output or input method that depicts performance (IFRS 15 paragraphs 39 to 45) and apply it consistently to similar obligations.

Customer acceptance clauses need care. When acceptance is a formality because the terminals meet agreed specifications that Corvid can test before shipment, it does not delay recognition. When acceptance depends on subjective criteria or on the customer's environment, recognition waits for acceptance.

7.1 Revenue schedule

Example check: monthly subscription revenue is EUR 256,829 / 36 = EUR 7,134.14. Nine months give EUR 64,207, twelve months EUR 85,610 and the last three months EUR 21,402 after rounding, so the four years add to EUR 256,829. Implementation was split by hours: 160 hours in February (EUR 10,654) and 240 hours in March (EUR 15,980), totalling 400 hours and EUR 26,634.

7.2 Recognition flow

The diagram shows when each part of the bundle reaches revenue.

8. Principal versus agent

When another party is involved in providing goods or services, first identify each specified good or service, then decide whether the entity controls it before it is transferred to the customer (IFRS 15 paragraphs B34 to B38; ASC 606-10-55-36 to 55-40). Use the indicators, such as primary responsibility for fulfilment, inventory risk and pricing discretion, to support the control conclusion, not to replace it. A principal recognises revenue gross; an agent recognises the net fee or commission.

9. Contract costs

Identify costs that would not have been incurred if the contract had not been obtained, such as sales commissions, and decide whether to capitalise them (IFRS 15 paragraphs 91 to 94; ASC 340-40-25-1 to 25-4). Record whether the practical expedient for amortisation periods of one year or less is elected. Fulfilment costs that are not within another standard are capitalised only when the criteria in IFRS 15 paragraph 95 (ASC 340-40-25-5) are met.

Amortise the asset on a systematic basis consistent with the transfer of the related goods or services (IFRS 15 paragraph 99; ASC 340-40-35-1). When the commission relates to several obligations delivered at different times, split it. Consider anticipated renewals when the renewal commission is not commensurate with the initial one. Test the asset for impairment against the remaining consideration less costs to be incurred.

Example: Sales commission of 4% on the fixed contract value is EUR 15,600 (EUR 390,000 x 4%). Corvid capitalises it and splits it by the allocated transaction price: 34.15% relates to the terminals and implementation (EUR 133,171 / EUR 390,000), so EUR 5,327 is expensed in FY2027 as those obligations are satisfied. The remaining EUR 10,273 is amortised over the 36 subscription months at EUR 285 per month. Renewal commissions equal 4% of the renewal value, which Corvid considers commensurate, so renewals are not included in the amortisation period.

10. Contract modifications and renewals

Set out the decision path for modifications under IFRS 15 paragraphs 18 to 21 (ASC 606-10-25-10 to 25-13): a separate contract, a termination of the old contract and creation of a new one (prospective), or a cumulative catch-up adjustment. The outcome depends on whether the added goods or services are distinct and whether the price increase reflects their stand-alone selling prices. Record how the billing system will flag modifications so the revenue team reviews them before the period closes.

11. Journal entries and financial statement effect

Record a receivable for an invoice only when the right to payment is unconditional: the invoice is due, or the contract is non-cancellable so that the amount is owed regardless of performance. Otherwise recognise the contract liability only when cash is received. In the example the contract can be terminated only on payment of all remaining fixed fees, and the signature invoice is due on issue, so JE-01 books a receivable.

Prepare entries for each event in the first reporting period and a year-end roll-forward of contract balances. A receivable exists when the right to consideration is unconditional (only the passage of time is required); a contract asset exists when revenue is recognised before that point; a contract liability exists when consideration is received or due before the related revenue is recognised (IFRS 15 paragraphs 105 to 109; ASC 606-10-45-1 to 45-4). Present the position net at contract level.

11.1 Contract liability roll-forward

Example check: the closing contract liability equals the excess of billing over revenue at contract level: EUR 210,000 less EUR 197,378 is EUR 12,622. Over the full term, subscription billing of EUR 240,000 plus the EUR 16,829 advance from the upfront invoice equals the EUR 256,829 allocated to the subscription, so the liability unwinds to zero at 2030-03-31.

12. Presentation and disclosure

Map the contract to the revenue disclosures the group already makes: disaggregation of revenue (IFRS 15 paragraph 114; ASC 606-10-50-5), contract balances (IFRS 15 paragraphs 116 to 118; ASC 606-10-50-8 to 50-10), remaining performance obligations (IFRS 15 paragraphs 120 to 122; ASC 606-10-50-13 to 50-15), significant judgements (IFRS 15 paragraphs 123 to 126) and contract cost assets (IFRS 15 paragraphs 127 and 128). Under IFRS 18, which applies from 2027-01-01, revenue sits in the operating category of the statement of profit or loss; check the group's IFRS 18 mapping in IFRS 18 Transition Plan (finance/ifrs-18-transition-plan).

Example check: remaining obligations equal the allocated subscription price not yet recognised: EUR 256,829 less EUR 64,207 is EUR 192,622. IFRS 15 paragraph 121 offers only two exemptions from the remaining performance obligation disclosure: contracts with an original expected duration of one year or less, and revenue recognised at the amount the entity has a right to invoice (paragraph B16). Neither applies here, because the contract runs for three years and the fixed fee is billed on a schedule that differs from the value transferred. IFRS 15 has no equivalent of the US GAAP optional exemption in ASC 606-10-50-14A for variable consideration allocated wholly to a distinct period of a series. Under IFRS, future usage fees are therefore part of the remaining performance obligation to the extent they are included in the transaction price after the constraint. In the example they are fully constrained (section 5), so the figure is EUR 192,622 and the note explains that usage-based fees are excluded because they are constrained. Revisit this when usage history supports an estimate that is highly probable not to reverse; from then the unconstrained amount for the remaining term enters the figure. Under ASC 606 the group could instead elect the 50-14A exemption and state the election (ASC 606-10-50-15).

13. IFRS and US GAAP comparison

IFRS 15 and ASC 606 were developed jointly and most outcomes are the same. Differences that commonly matter for a SaaS and hardware business are listed below; confirm each against the current text of both standards, since amendments after 2014 were not always converged.

14. Controls, systems and monitoring

A revenue memo is only as reliable as the system that applies it. Document how the obligations, SSPs and recognition patterns are configured in the billing and revenue sub-ledger, and who checks the configuration. Describe the monthly controls that compare billing, usage and revenue, and the triggers that send a contract back to the technical accounting team. Link the controls to the Risk and Control Matrix (compliance/risk-control-matrix). For the design of the usage pipeline and rating engine, see SaaS Metering and Billing Design (architecture/saas-metering-billing-design).

Re-assess the memo when the contract is modified, when the SSP study changes by more than your policy threshold, when service-level credits start to occur, when a new device or platform dependency makes the bundle more integrated, or when the standard is amended.

15. Glossary and references

15.1 Glossary

15.2 References

Standard and licence note

Structure aligned with the five-step revenue model of IFRS 15 Revenue from Contracts with Customers and FASB ASC Topic 606 and Subtopic 340-40. Standards are cited by name and paragraph number only; no text, definitions or illustrative examples from the IFRS Foundation or FASB are reproduced or paraphrased, and IFRS is a trademark of the IFRS Foundation used nominatively. Obtain the current standards for the normative requirements and check later amendments and their effective dates. The worked example, Corvid Commerce Group, Larkspur Outfitters and every figure are fictional and original. This template is original text written for this collection and is not accounting advice. Template licence: MIT.