Revenue Recognition Agent - IFRS 15 + ASC 606 Five-Step | Gosign

IFRS 15 and ASC 606 were developed as a joint IASB-FASB convergence project and the five-step model is substantively identical, but five material differences require careful reconciliation for dual-reporting entities (US-headquartered IFRS subsidiaries, EU-headquartered SEC registrants, dual-listed groups). Difference 1 (Collectability Threshold): IFRS 15.9(e) requires consideration to be 'expected' to be collected (>50% likelihood); ASC 606-10-25-1(e) requires it to be 'probable' (75-80% likelihood per US auditor convention). For contracts with marginal customer credit standing this can result in IFRS 15 contract identification before ASC 606 contract identification, creating timing differences. Difference 2 (Variable Consideration Constraint): IFRS 15.56 requires constraint to amount 'highly probable' of not requiring significant reversal; ASC 606-10-32-11 requires 'probable' threshold. The thresholds are not identical - 'highly probable' is generally interpreted as a higher standard than 'probable'. Difference 3 (Licence Accounting): IFRS 15 distinguishes between right-to-use licences (point-in-time) and right-to-access licences (over-time) based on whether entity continues to be involved with the IP; ASC 606 has a substantively similar but operationally different test - in practice most software vendors arrive at similar conclusions but with different documentation. Difference 4 (Sales Tax Presentation): IFRS 15 allows policy choice on whether to present sales tax gross or net; ASC 606-10-32-2A explicitly permits net presentation as policy. Difference 5 (Shipping and Handling): IFRS 15 requires assessment of whether shipping is a separate performance obligation; ASC 606-10-25-18B provides a practical expedient to account for shipping after control transfer as fulfilment activity. The Agent's dual-standard parallel calculation engine produces both IFRS 15 and ASC 606 results with reconciliation report - the reconciliation report is required Big-4 audit substantive testing artefact under PCAOB AS 2110 + ISA UK 540 for dual-reporting entities. Big-4 audit qualification on revenue recognition typically triggers from one of three failure modes: (a) inconsistent application of the two standards without documented reconciliation; (b) variable consideration constraint judgement that auditor disagrees with - particularly common in software with success fees and life sciences with milestone payments; (c) principal versus agent assessment that auditor disagrees with - particularly common in marketplace platforms and reseller arrangements.

Variable consideration estimation and constraint application is the most-frequent SEC AAER (Accounting and Auditing Enforcement Release) area in revenue recognition, accounting for approximately 50% of all revenue-related AAERs since 2018 per Cornerstone Research analysis. The Agent operationalises variable consideration in three integrated phases. Phase 1 (Identification): contract clauses identified by LLM extraction - volume rebates, performance bonuses, sales-based royalties (subject to specific royalty exception under IFRS 15.B63 + ASC 606-10-55-65), milestone payments, refund/return rights, performance penalties, price concessions, customer credits; each clause classified by type with confidence score plus features. Phase 2 (Estimation Method Selection): human accountant selects between expected value method (probability-weighted across possible outcomes - typical for portfolio of similar contracts) and most likely amount method (single most likely outcome - typical for binary outcomes like single milestone payment) per IFRS 15.53 + ASC 606-10-32-8; method selection captured with rationale; method should not be changed for similar contracts unless circumstances change. Phase 3 (Constraint Application): for each variable consideration component, the human accountant assesses five factors per IFRS 15.57 + ASC 606-10-32-12 - (a) susceptibility to factors outside entity's influence (market volatility, regulatory changes, third-party actions); (b) extended uncertainty period; (c) limited entity experience with similar contracts; (d) practice of providing broad price concessions; (e) broad range of possible outcomes. Constraint reduces estimated variable consideration to the amount that is 'highly probable' (IFRS 15) / 'probable' (ASC 606) of not requiring significant reversal. Reassessed each reporting period under IFRS 15.59 + ASC 606-10-32-14. Sales-based royalties have a specific exception under IFRS 15.B63 + ASC 606-10-55-65 - revenue recognised only when sale or usage occurs, regardless of constraint analysis. SEC AAER pattern: companies estimating high variable consideration that subsequently does not materialise, requiring restatement; the Agent's constraint logic with reassessment trail provides defensible documentation. Big-4 audit substantive testing under AS 2401 includes recalculation of variable consideration estimates plus testing of historical accuracy plus comparison with similar contracts.

Performance obligation identification under IFRS 15 step 2 + ASC 606 step 2 is consistently identified as the most-frequent revenue recognition restatement area per PCAOB inspection findings and SEC AAER trend analysis. The two-criteria distinct test under IFRS 15.27 + ASC 606-10-25-19 requires both criteria to be met: (a) capable of being distinct - customer can benefit from good or service either on its own or together with other resources readily available; (b) distinct in the context of the contract - promise to transfer good or service is separately identifiable from other promises in the contract. The first criterion is straightforward; the second criterion is the source of restatement risk because it requires assessment of whether promises are 'separately identifiable' considering three indicators per IFRS 15.29 + ASC 606-10-25-21: (a) significant integration service combining goods or services into bundle that customer contracted for; (b) modification or customisation of one good or service by another; (c) highly interrelated promises where each is significantly affected by the other. Software-plus-implementation is the canonical example: if implementation modifies the licence sufficiently that the licence is not usable without implementation, they are a single performance obligation; if implementation is independently usable (e.g. implementation services provided after standard licence delivery), they are separate. Equipment-plus-installation, machine-plus-maintenance, hardware-plus-software embedded systems, manufacturer-plus-warranty arrangements, telecom-plus-handset arrangements all require this judgement. The Agent operationalises performance obligation identification in three phases. Phase 1 (LLM Extraction): contract text analysed for enumerated deliverables, embedded service-level commitments, integration clauses, modification clauses; each potential performance obligation captured with confidence plus features. Phase 2 (Distinct Test Application): human accountant applies two-criteria distinct test plus three integration indicators with explicit rationale; criterion-by-criterion analysis captured in Decision Layer; comparison with similar prior contracts. Phase 3 (Audit Defence Documentation): full evidence packet including contract terms, applied criteria, integration analysis, comparison with prior contracts, statutory auditor coordination - per PCAOB AS 2201 + AS 2401 + AS 3101 Critical Audit Matters requirements. Performance obligation identification appears as Critical Audit Matter under AS 3101 in approximately 38% of S&P 500 audits per 2024 inspection cycle - the Decision Layer documentation reduces auditor uncertainty and CAM length.

Principal versus agent assessment under IFRS 15.B34-B38 + ASC 606-10-55-36 determines whether revenue is presented gross (entity is principal, recognising entire transaction value plus corresponding cost) or net (entity is agent, recognising only commission/fee). The presentation difference can change top-line revenue by orders of magnitude with corresponding margin compression - a marketplace platform processing USD 1 billion in customer transactions might recognise USD 1 billion gross revenue (principal) or USD 100 million net commission revenue (agent), with the equivalent income statement impact at margin level but vastly different optical comparison metrics. The control-based assessment under IFRS 15.B34-B38 + ASC 606-10-55-37 establishes the principle: entity is principal if it controls the specified good or service before transfer to customer; entity is agent if it arranges for another party to provide the good or service. Three control indicators applied collectively rather than as bright-line tests under IFRS 15.B37 + ASC 606-10-55-39: (a) primary responsibility for fulfilling promise to provide good/service; (b) inventory risk before transfer to customer or after customer return; (c) discretion in establishing prices. Marketplace platforms (Amazon Marketplace, Etsy, eBay, Uber, Airbnb), drop-ship arrangements, distributor relationships, software resellers, ticket resellers, travel arrangements - all require this assessment with material gross-versus-net presentation impact. SEC AAER pattern: companies presenting gross when control analysis supports agent (net) presentation; the resulting overstatement of revenue triggers AAER plus class-action plaintiff lawsuit. The Agent's three-indicator analysis with explicit control evidence per indicator provides defensible documentation. Cross-jurisdictional auditor focus: PCAOB AS 2401 fraud risk procedures for revenue plus SEC Division of Corporation Finance comment letter process plus FRC + ESMA enforcement priorities all consistently target principal versus agent presentation - particularly for marketplace platforms and reseller arrangements. UK FRC inspections have cited principal versus agent as an enforcement priority every year since IFRS 15 effective date 2018.

Significant financing component assessment under IFRS 15.60-65 + ASC 606-10-32-15 is required where timing of payment provides customer or entity with significant financing benefit, requiring separation of revenue from interest income/expense. The practical expedient under IFRS 15.63 + ASC 606-10-32-18 allows the entity not to assess the financing component where the period between transfer of promised goods/services and payment is one year or less - the Agent applies this expedient deterministically. For periods exceeding one year, the financing component is recognised: customer prepayment scenarios (advance subscription, prepaid service) result in interest expense plus revenue increase; deferred payment scenarios (extended payment terms, deferred settlement after performance) result in interest income plus revenue decrease. Discount rate is the rate that would be reflected in a separate financing transaction at contract inception under IFRS 15.64 + ASC 606-10-32-17 - typically the entity's incremental borrowing rate adjusted for customer credit risk, or the customer's incremental borrowing rate if observable. Presentation under IFRS 15.65 + ASC 606-10-32-20: separate from revenue as interest income/expense. Common application areas: long-term construction contracts with extended payment terms, multi-year service contracts with prepaid amounts, subscription contracts with multi-year prepayment, leasing arrangements with non-leasing services. The Agent's deterministic one-year practical expedient application followed by discount rate calculation provides PCAOB AS 2201 evidence chain. Big-4 audit substantive testing under AS 2401 includes recalculation of financing component plus testing of discount rate selection - the Agent's audit-ready evidence eliminates manual workpaper preparation.

Contract modification accounting under IFRS 15.18-21 + ASC 606-10-25-10-13 has three possible outcomes with materially different financial statement impact, and the determination of which outcome applies is the source of significant restatement risk - particularly for software vendors with ongoing licence amendments, construction companies with change orders, and SaaS subscription companies with upgrade/downgrade scenarios. Outcome 1 (Separate Contract): if modification adds distinct goods/services priced at standalone selling price reflecting their value, the modification is accounted for as a separate contract - zero impact on existing contract revenue. Outcome 2 (Termination of Existing Contract and Creation of New Contract): if remaining goods/services are distinct from those already transferred, the existing contract is terminated and the new contract is created with remaining consideration including unrecognised consideration from existing contract. Outcome 3 (Cumulative Catch-up Adjustment): if remaining goods/services are not distinct from those already transferred (typical for over-time satisfaction with single performance obligation), the modification is accounted for as part of the original contract with cumulative catch-up adjustment to revenue based on revised transaction price and progress. The Agent operationalises modification accounting in four phases. Phase 1 (Modification Identification): LLM detects amendment plus side letter plus change order plus scope-change document; each modification captured with effective date and amendments. Phase 2 (Distinct Test on Remaining Goods/Services): human accountant applies distinct test on remaining goods/services post-modification to determine outcome 1 vs 2 vs 3; rationale captured. Phase 3 (Pricing Test for Outcome 1): if remaining goods/services are distinct, additional test on whether pricing reflects standalone selling price - if yes, outcome 1; if no, outcome 2. Phase 4 (Calculation per Outcome): outcome 1 - separate revenue stream begins; outcome 2 - existing recognition stops, new recognition starts with unrecognised consideration; outcome 3 - cumulative catch-up calculated on revised transaction price and progress. Software vendors with continuous licence amendments under enterprise agreements, construction companies with change orders affecting cost-to-cost progress, telecom contracts with plan amendments, SaaS subscription companies with mid-term upgrades or downgrades all require this analysis - the Agent's Decision Layer provides per-modification audit trail with PCAOB AS 2201 + AS 2401 + ISA UK 540 evidence.

The major revenue recognition platforms occupy adjacent positions in the IFRS 15 / ASC 606 implementation stack with different deployment models. Workday Revenue Management plus Workday Adaptive Planning Revenue is cloud-native with native ASC 606 + IFRS 15 five-step model engine, performance obligation registry, variable consideration constraint application, significant financing component calculation, allocation calculations with audit trail; tightly integrated with Workday Financial Management for SOX 404 evidence chain plus Workday Compensation for variable compensation alignment - particularly favoured at mid-market through enterprise (USD 500M-USD 30B revenue) cloud-first organisations. SAP S/4HANA Revenue Accounting and Reporting (RAR) replaces legacy SAP RR engine with native ASC 606 + IFRS 15 module, performance obligation tracking, variable consideration estimation, contract asset and contract liability balance reporting; tightly integrated with SAP S/4HANA Sales + SAP CPQ + SAP Subscription Billing - the typical choice at SAP-anchored multinationals (USD 5B+ revenue) requiring tight ERP-to-revenue integration. Oracle Revenue Management Cloud Service plus Oracle Fusion Cloud ERP provides cloud revenue recognition with ASC 606 + IFRS 15 five-step model engine, contract repository with performance obligation registry, transaction price allocation across SSP, variable consideration constraint, integration with Oracle CPQ + Oracle Subscription Management; Oracle EPM Cloud for revenue forecasting - typical at Oracle-anchored enterprises and finance-led implementations. Zuora RevPro (formerly RevPro from Leeyo, acquired by Zuora 2017) is the subscription-economy specialist with ASC 606 + IFRS 15 five-step model engine, performance obligation registry, contract modification handling, integration with Zuora Billing + Zuora CPQ - particularly strong in SaaS, subscription media, IoT recurring revenue; the dominant choice at subscription-first companies (Zoom, DocuSign, Atlassian, Twilio, Snowflake using or having historically used RevPro). NetSuite Advanced Revenue Management plus NetSuite Revenue Recognition is the mid-market choice in NetSuite ecosystem with ASC 606 + IFRS 15 module integrated with NetSuite ERP. Sage Intacct Contract and Revenue Management is the alternative mid-market choice with ASC 606 + IFRS 15 module integrated with Sage Intacct Subscription Billing. Aptitude Software RevStream is the enterprise revenue recognition platform with strong adoption in telecom, technology hardware, life sciences, and complex multi-element arrangements. The Agent integrates with all of these as either (a) the upstream contract-extraction plus performance-obligation-proposal layer feeding the revenue recognition engine, (b) the downstream SOX-evidence plus disclosure-note plus fraud-pattern-detection layer pulling from revenue outputs, or (c) the orchestration layer running parallel deployments where different business units use different revenue systems. F500 multinationals already on Workday Revenue or SAP RAR typically retain those for the calculation engine while the Agent handles cross-jurisdictional IFRS 15 / ASC 606 reconciliation plus structured judgement documentation plus PCAOB AS 2401 fraud pattern detection plus disclosure note drafting plus Critical Audit Matter evidence packaging. The Agent's Decision Log structure is Workday-Revenue + SAP-RAR + Oracle-RMC + Zuora-RevPro + NetSuite-ARM + Sage-Intacct + Aptitude-RevStream API compatible for evidence loading.