Revenue Recognition Policy

A written revenue recognition policy built on the five-step model, with mapped performance obligations, selling price evidence, deal review before signature and the judgements auditors and investors will test.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Then open the Marketplace in the app, search for Revenue Recognition Policy, and click Install. It goes into your own files, and works offline from then on.

Before you start: this plan is general information to help your team organise its work. It is not financial, investment, tax, accounting or legal advice, and it does not recommend any product, investment or deal. Rules differ between countries, so check decisions that matter with qualified, licensed advisers in the countries concerned. Investing can lose money, and raising or managing other people's money is regulated in most countries.

What it installs.

1

Pillar

1

Area

50

Projects

201

Starter tasks

🧾 Finance & Accounting

Revenue Recognition Policy

Deciding when and how revenue is recognised for contracts, milestones and bundles, documenting the policy and applying it consistently for auditors and investors.

  1. Revenue stream and contract type inventory
  2. Confirming which revenue standard applies to you
  3. Five-step model applied to your main contract
  4. Written revenue recognition policy, first full draft
  5. When a contract exists for revenue purposes
  6. Performance obligation catalogue by product and service
  7. Standalone selling price evidence pack
  8. Over time or point in time, decided per obligation
  9. Revenue judgements risk register
  10. Policy owner, approvers and change control
  11. Weekly deal desk revenue review
  12. Non-standard terms escalation route
  13. Monthly revenue schedule tie-out
  14. Contract asset and contract liability roll-forward
  15. Delivery and acceptance evidence sampling
  16. Quarterly variable consideration estimate
  17. Revenue control testing each quarter
  18. Quarterly revenue judgements memo
  19. Annual revenue policy refresh
  20. Contract modification log
  21. Principal versus agent assessment practice
  22. Measuring progress with input and output methods
  23. Variable consideration and the constraint, worked examples
  24. Significant financing component check
  25. Licences of intellectual property, access or use
  26. Warranties, returns and refund liabilities
  27. Reading revenue notes in peer annual reports
  28. Sales contract clauses that support clear recognition
  29. Sales commission capitalisation schedule
  30. Bundle allocation model for discounted packages
  31. Milestone billing versus recognition gap analysis
  32. Revenue subledger or spreadsheet, choosing the tool
  33. Loss-making contract identification
  34. Bill-and-hold and consignment arrangements review
  35. Customer options and material rights review
  36. Payments to customers, listing fees and co-op marketing
  37. Auditor walkthrough of the revenue process
  38. Investor due diligence revenue pack
  39. Revenue assessment before a new pricing launch
  40. Transition to a new revenue framework
  41. Audit committee briefing on revenue judgements
  42. Founder's first enterprise contract, revenue review
  43. Moving from invoice-basis income to policy-based revenue
  44. New finance manager inheriting a revenue policy
  45. Group-wide policy consistency across business units
  46. Revenue timing briefing for sales and delivery teams
  47. Revenue disclosure note with disaggregation
  48. Long-term contract revenue on cost-to-cost progress
  49. Revenue journal analytics for unusual entries
  50. IFRS 15 and ASC 606 differences reconciliation

Where it starts.

Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.

Revenue stream and contract type inventory

Before any policy can be written you need a plain list of every way the business earns money: product sales, services, licences, support, implementation fees, rebated volume deals and anything sold through a partner. Most companies find two or three streams nobody has thought about, such as set-up fees or free pilots that convert. The inventory becomes the table of contents for the whole policy.

First tasks

  • Export last year's revenue by ledger account and sort it by size
  • List every revenue stream with its billing and delivery pattern
  • Pull three signed contracts for each stream into one folder
  • Flag streams with acceptance, return or refund terms for review

Confirming which revenue standard applies to you

IFRS 15, ASC 606, the revenue section of a national small-company framework and IFRS for SMEs all agree on the broad idea but differ in detail, and a company sometimes reports under one framework locally and another for a parent or investor. Confirming in writing which framework governs your statutory accounts, and any other reporting you owe, prevents a policy built on the wrong rulebook.

First tasks

  • Check last year's accounts for the framework named in the basis of preparation
  • Ask your accountant or auditor to confirm the framework in writing
  • Ask lenders and investors whether they require reporting under a different framework
  • Write the governing standard at the top of the policy draft

Five-step model applied to your main contract

The five steps are identify the contract, identify the performance obligations, set the transaction price, allocate it, and recognise revenue as each obligation is satisfied. Reading them in the abstract teaches little; walking your largest standard contract through all five, clause by clause, shows where your real judgements sit and gives the policy its first worked example.

First tasks

  • Choose the standard contract that brings in the most revenue
  • Read the five steps in the standard's own wording once end to end
  • Annotate the contract with the clause that answers each step
  • Write up the walkthrough as a two-page worked example

Make it yours.

Install Revenue Recognition Policy, then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.