Revenue Recognition Agent

Revenue recognition is the accounting topic with the highest audit density - and the point where judgement calls most quickly turn into restatements. The Revenue Recognition Agent ensures that every IFRS 15 assessment is documented, justified and assigned to a named decision-maker. The Finance function no longer needs to defend why a performance obligation was deferred - it can present the complete decision path. (US: ASC 606 under US GAAP follows substantially the same five-step model.)

IFRS 15 Is a Governance Problem, Not a Calculation Problem

The five-step model of IFRS 15 looks on paper like a chain of calculations. In practice, it consists of a chain of judgement calls, each of which must be individually auditable. Are two deliverables separately identifiable or one integrated solution? Does control transfer at a point in time or over time? How is variable consideration estimated? Each of these questions decides millions in the income statement - and each is an entry point for auditor queries.

The pressure is real: 63 percent of all SEC enforcement actions related to restatements concerned revenue recognition and internal controls over financial reporting (source: Cooley PubCo on SEC Enforcement). KPMG updated its IFRS 15 handbook again in July 2025 because IASB reviews confirmed: the complexity lies not in the calculation logic but in the need for end-to-end judgement documentation.

For CFOs this means: the risk arises not because someone calculated wrong. It arises because a judgement was made in an accountant’s head and never written down. When the same accountant is asked six months later at the audit meeting why two deliverables were treated as one, the answer is often no longer reconstructable. That is precisely where restatement risk originates.

How the Decision Layer Structures Nine IFRS 15 Decisions

The Revenue Recognition Agent decomposes the five-step model into nine discrete decision steps. Each step has a named decider. Two steps rest with the human because they are pure judgement: the identification of separate performance obligations and the assessment of control transfer. Five steps run rule-based because they are deterministically derivable from contract data. Two steps use LLM support because they require text processing: the initial contract extraction and the disclosure note draft.

This allocation follows a core rule of the Decision Layer architecture. Judgement is not delegated to software - software prepares the judgement. The agent provides the accountant with all relevant contract clauses, the company’s historical precedents and an IFRS 15 criteria checklist. The decision stays with the human. But it is made in a structured way, with documented rationale and applied criteria.

A Concrete Scenario: The Software Multi-Element Arrangement

An enterprise software provider signs a three-year framework agreement for EUR 4.8 million (USD 5.2 million). The contract contains software licences, an implementation project, support and a performance-based bonus on achieved KPIs. Without an agent, an accountant would need to manually answer the question: are licence and implementation one deliverable or two? How is the bonus probability-weighted? What standalone price underlies the support?

With the agent, the process runs differently. Contract extraction identifies all potential performance obligations and presents them to the accountant. The accountant decides based on IFRS 15 criteria: the implementation is not distinct because it is what makes the software licence usable. This assessment is recorded in the Decision Layer with rationale, applied criterion and decision-maker name. The agent then handles price allocation by relative standalone prices, calculates variable consideration using the expected value method and creates the posting proposal. Nine months later, the statutory auditor asks why the implementation was not recognised separately. The accountant opens the decision path. The answer is documented.

Revenue recognition shifts from a top audit risk to a documented, defensible process

The visible effect is not time savings. The judgement work remains because it must remain. What changes is audit readiness. Revenue recognition shifts from a top-risk area to a documented process with named decision-makers and traceable criteria. In year-end discussions, the conversation moves from “How did you arrive at this revenue split?” to “We made the assessment on 14 March - here is the documentation.” That is the difference between a defensive and a confident audit meeting.