Revenue Recognition Agent
From contract identification through the IFRS 15 and ASC 606 five-step model to a defensible audit trail - a revenue-recognition pipeline that automates the mechanical steps and documents the seven judgement calls.
Cross-jurisdictional revenue pipeline: IFRS 15 plus ASC 606 five-step model, variable consideration, significant financing component, principal-vs-agent, SOX 404.
Analyse your processA selection from over 5,000 projects in 25 years of software development
One IFRS 15 and ASC 606 pipeline that automates the mechanical steps, documents the seven judgement calls, and keeps generative AI out of every accounting outcome.
The Agent runs the IFRS 15 and ASC 606 five-step model, with structured human judgement on the seven judgement-intensive decisions: the performance-obligation distinct test, the transaction price and its variable-consideration estimation, the variable-consideration constraint, allocation across performance obligations, the principal-versus-agent assessment, the over-time-versus-point-in-time determination, and contract-modification accounting. LLM extraction surfaces contract clauses and proposes performance obligations without deciding the accounting; the deterministic engine then measures over-time progress, posts journal entries and contract balances, and drafts the disclosure notes for human review. It flags PCAOB AS 2401 fraud-risk patterns for auditor escalation, and reconciles the IFRS 15 and ASC 606 differences for dual-reporting entities. No generative AI decides a distinct test, a transaction price, a constraint, a principal-versus-agent call or a recognition-timing question.
Outcome: Structured judgement documentation with named decision-makers and applied criteria cuts the SEC restatement risk and the PCAOB revenue-cycle finding rate (typically 35-45%), and reduces the Critical Audit Matter uncertainty under AS 3101 (performance-obligation identification appears as a CAM in 38% of S&P 500 audits). A dual-standard parallel calculation with a reconciliation report removes the IFRS 15 versus ASC 606 reconciliation effort, performance-obligation capture drops from 45 to 10 minutes per contract, Big-4 substantive testing on the revenue cycle falls 30-45%, and channel-stuffing and bill-and-hold detection reaches 90-94% accuracy on cross-system reconciliation.
Sixteen steps carry each contract from identification through allocation to recognition, mixing deterministic calculation with documented human judgement:
Revenue recognition drives 63% of SEC restatements, sits in the PCAOB top-3 inspection findings every year since 2018, and surfaces as a Critical Audit Matter in 38% of S&P 500 audits
International revenue recognition runs on two converged but materially different standards at once: IFRS 15, used across 144 jurisdictions including all 27 EU Member States and the UK, and ASC 606 under US GAAP, with five reconciling differences in the collectability threshold, the variable-consideration constraint, licence accounting, sales-tax presentation, and shipping and handling. A US-headquartered group with EU subsidiaries on IFRS 15 and a US parent on ASC 606, a UK listed entity moving its FRS 102 accounts towards IFRS 15, and a dual-listed group must run parallel calculations across both standards while applying seven judgement-intensive determinations: the performance-obligation distinct test, the transaction price with its variable-consideration estimation, the constraint (highly probable under IFRS 15, probable under ASC 606), the significant financing component, the principal-versus-agent assessment, the over-time-versus-point-in-time test, and contract-modification accounting. Layer over this SOX 404 control attestation where revenue is the most-frequent material-weakness area, the AS 2401 fraud-risk presumption, AS 3101 Critical-Audit-Matter disclosure (performance-obligation identification is a CAM in roughly 38 percent of S&P 500 audits), and the FRC and ESMA enforcement priorities that have applied every year since IFRS 15 took effect in 2018, and revenue recognition becomes the most judgement-intensive process in the multinational finance function.
A single revenue error can cascade into an uncertain-tax-position disclosure and class-action exposure
Revenue recognition is the most-frequent SEC restatement area, accounting for approximately 63 percent of all SEC enforcement actions related to restatements per Cooley PubCo on SEC Enforcement, and the most-frequent SOX 404 material weakness area for SEC registrants per 2024 PCAOB inspection findings. SEC AAER (Accounting and Auditing Enforcement Releases) targeting revenue recognition account for 50-67 percent of all AAERs since 2018 per Cornerstone Research analysis - the dominant pattern is variable consideration overestimation that subsequently does not materialise (approximately 50% of revenue AAERs), followed by performance obligation identification errors leading to premature recognition, and principal-versus-agent presentation errors leading to revenue overstatement. PCAOB inspection findings cite revenue cycle in top-3 deficiency areas across all four firms (Deloitte, PwC, EY, KPMG) every year since 2018, with performance obligation identification specifically cited as Critical Audit Matter under AS 3101 in approximately 38 percent of S&P 500 audits per 2024 inspection cycle. KPMG updated its IFRS 15 handbook again in July 2025 because IASB reviews confirmed the complexity lies not in calculation logic but in the need for end-to-end judgement documentation - the seven judgement-intensive decisions (performance obligation distinct test, transaction price including variable consideration, variable consideration constraint, allocation methodology, principal versus agent assessment, over-time versus point-in-time, contract modification accounting) each require structured human accounting expertise with documented criteria. For SEC-registered S&P 500 multinationals, a single revenue recognition error compounds into an uncertain tax position disclosure under ASC 740-10 and IAS 12, a Big-4 auditor concurrence challenge under the PCAOB revenue and fraud standards, the SEC Division of Corporation Finance comment letter process, and a class-action plaintiff lawsuit alleging securities fraud - the cumulative downside exposure from these four cascade modes typically exceeds USD 50 million for material restatements.
The revenue-recognition pipeline runs 16 steps, not the 8-10 of a single standard
Single-standard revenue recognition can be modelled in 8-10 steps; running IFRS 15 and ASC 606 together with full judgement support cannot. The Agent splits the pipeline into 16 steps because every contract needs the five contract criteria checked (approval, identifiable rights, payment terms, commercial substance, collectability), the contract data LLM-extracted and performance obligations proposed, the distinct test applied with its two criteria and three integration indicators, the transaction price determined with variable-consideration method selection and a significant-financing-component assessment, the constraint applied through a five-factor susceptibility analysis, allocation made on observable standalone selling prices or one of three estimation approaches, the principal-versus-agent call made on three control indicators, the over-time-versus-point-in-time test applied, progress measured by output or input method, modifications resolved into one of three outcomes, sales returns and the assurance-versus-service warranty distinction handled, the journal entries and contract balances posted, the disclosure notes drafted, and the PCAOB AS 2401 fraud-risk patterns (channel stuffing, bill-and-hold without substance, side letters, unusual cut-off entries) detected.
A concrete scenario: a US-headquartered enterprise software vendor with USD 2.4 billion ARR, dual-reporting under ASC 606 at the parent and IFRS 15 across the EU and UK subsidiaries, running 8,400 enterprise customer contracts including 3,200 multi-element arrangements (licence plus implementation plus support), 4,800 SaaS subscriptions with variable consideration triggers, plus 320 reseller arrangements. On a typical month, the Agent processes 280 new contracts plus 920 modifications, applies the IFRS 15.27 and ASC 606-10-25-19 distinct test with human accountant judgement on whether implementation modifies the licence sufficiently to constitute a single performance obligation, estimates variable consideration on 480 contracts using expected value method and 60 using most likely amount, applies the IFRS 15.56 and ASC 606-10-32-11 constraint with reassessment trail, calculates significant financing component on 24 contracts exceeding the one-year practical expedient threshold, assesses principal-versus-agent on 320 reseller contracts with three-indicator control analysis, determines over-time versus point-in-time, calculates progress using cost-to-cost on 240 implementation contracts and time-elapsed on 4,800 subscriptions, accounts for 920 modifications with three-outcome determination (separate contract for 540, termination-and-new for 240, cumulative catch-up for 140), drafts disclosure notes covering disaggregation plus contract balances plus remaining performance obligations of USD 4.8 billion, runs PCAOB AS 2401 fraud risk pattern analysis plus cut-off testing plus channel-stuffing signals plus bill-and-hold legitimacy checks, and supplies IFRS 15 versus ASC 606 reconciliation report covering all five reconciling differences for dual-reporting purposes.
In the Decision Layer, 6 of the 16 steps are rule-based (R) for deterministic calculation steps, 7 are human judgement (H) for accounting decisions reflecting the reality of IFRS 15 and ASC 606 (the standards are intentionally judgement-intensive at seven points), and 3 are LLM-suggestion (A) for contract data extraction, disclosure note drafting and fraud risk pattern detection. There is no generative AI in performance obligation distinct determination, transaction price calculation, variable consideration constraint, principal versus agent assessment, or revenue recognition timing decision - the LLM never auto-determines accounting outcomes without human accountant review acceptance. The Decision Layer pattern is software prepares judgement; software does not delegate judgement.
IFRS 15 versus ASC 606 reconciliation transforms revenue recognition into dual-standard parallel calculation engine for SEC-registered IFRS-reporting multinationals
The IASB and FASB joint convergence project produced IFRS 15 and ASC 606 with substantively identical five-step models, but five reconciling differences require parallel calculation for dual-reporting entities. Difference 1 (Collectability Threshold): IFRS 15.9(e) requires consideration to be ‘expected’ (>50% likelihood); ASC 606-10-25-1(e) requires it to be ‘probable’ (75-80% per US auditor convention) - 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 ‘highly probable’; ASC 606-10-32-11 requires ‘probable’ - the thresholds are not identical and dual-reporting entities reconcile and disclose. Difference 3 (Licence Accounting): IFRS 15 distinguishes between right-to-use (point-in-time) and right-to-access licences (over-time) based on entity continued involvement; ASC 606 has substantively similar but operationally different test. Difference 4 (Sales Tax Presentation): IFRS 15 allows policy choice on gross versus net; ASC 606-10-32-2A explicitly permits net presentation. Difference 5 (Shipping and Handling): IFRS 15 requires separate performance obligation assessment; ASC 606-10-25-18B provides practical expedient for fulfilment activity treatment. The Agent’s dual-standard parallel calculation engine produces both IFRS 15 and ASC 606 results with a reconciliation report - a required Big-4 audit substantive testing artefact under PCAOB AS 2110 and ISA UK 540 for dual-reporting entities. UK FRS 102 March 2024 amendments effective for fiscal years beginning 1 January 2026 align FRS 102 Section 23 Revenue with the IFRS 15 five-step model - the Agent supports quad-standard reporting across FRS 102, FRS 101, IFRS 15 and ASC 606 for UK groups with a US SEC parent.
Integration ecosystem: Workday Revenue, SAP S/4HANA RAR, Oracle Revenue Management Cloud, Zuora RevPro, NetSuite, Aptitude, plus Big-4 proprietary audit tools
The Agent integrates natively with the major revenue recognition platforms. Workday Revenue Management provides a cloud-native ASC 606 and IFRS 15 five-step engine, with Workday Financial Management supplying the SOX 404 evidence chain. SAP S/4HANA Revenue Accounting and Reporting (RAR) integrates tightly with SAP S/4HANA Sales, SAP CPQ and SAP Subscription Billing. Oracle Revenue Management Cloud Service connects to Oracle CPQ and Oracle Subscription Management, with Oracle EPM Cloud for forecasting. Zuora RevPro serves the subscription economy alongside Zuora Billing and Zuora CPQ. NetSuite Advanced Revenue Management and Sage Intacct Contract and Revenue Management cover the mid-market, and Aptitude Software RevStream covers enterprise telecom and life sciences. The contract repository can sit on Conga CLM, Salesforce Revenue Cloud, DocuSign CLM or Ironclad. Close certification and contract-balance roll-forward run through the BlackLine reconciliation, variance-analysis and journal-entry modules. Audit-evidence integration spans Deloitte ASM, PwC Halo, EY Helix and KPMG Clara with PCAOB AS 1215-compliant metadata. Submission flows to SEC EDGAR for the 10-K, 10-Q and 8-K, to UK Companies House for statutory accounts, and to the EU Member State filing portals (Bundesanzeiger, INPI, Registro Mercantil) - all with audit-trail metadata for SEC, FCA, ESMA and competent-authority compliance, and for PCAOB, AICPA and ISA UK substantive testing.
Micro-Decision Table
Who decides in this agent?
16 decision steps, split by decider
Identify the contract under IFRS 15 / ASC 606 step 1 Does the arrangement meet all five contract criteria (approval and commitment, identifiable rights and payment terms, commercial substance, probable collectability) under IFRS 15.9 / ASC 606-10-25-1? Rules Engine Auditor
Deterministic application of the five contract criteria under IFRS 15.9 and ASC 606-10-25-1: (a) parties have approved contract and committed to perform; (b) entity can identify each party's rights regarding goods or services to be transferred; (c) entity can identify payment terms for goods or services; (d) contract has commercial substance; (e) it is probable (ASC 606) or expected (IFRS 15) that entity will collect consideration to which it will be entitled. Contract approval evidence captured (executed agreement, master services agreement plus statement of work, click-through acceptance with electronic timestamp). Note: ASC 606 collectability threshold is 'probable' (75-80% likely); IFRS 15 uses 'expected' (>50%) - dual-reporting entities reconcile difference
Decision Record
Challengeable: Yes - rule application verifiable. Objection possible for incorrect data or wrong rule version.
Challengeable by: Auditor
Identify performance obligations under IFRS 15 / ASC 606 step 2 Are the goods or services in the contract distinct (capable of being distinct AND distinct in the context of the contract) under IFRS 15.27 / ASC 606-10-25-19? Human Auditor
Two-criteria distinct test under IFRS 15.27 and ASC 606-10-25-19: (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. Indicators of separately identifiable: significant integration service, modification or customisation, highly interrelated promises. Software-plus-implementation, equipment-plus-installation, licence-plus-support arrangements require human accounting judgement on whether implementation modifies the licence sufficiently to be a single performance obligation - most-frequent area of SEC AAER findings and PCAOB inspection deficiencies. LLM extraction proposes potential performance obligations from contract text; human reviewer applies distinct test
Decision Record
Challengeable: Yes - via manager, works council, or formal objection process.
Challengeable by: Auditor
LLM-extract contract data and proposed performance obligations What contract terms, deliverables, payment schedules, modification clauses, variable consideration triggers, and warranties are in the contract that may affect performance obligation identification? AI Agent Auditor
LLM extraction from contract text supports IFRS 15 steps 2, 3 and 4: identifies enumerated deliverables, embedded service-level commitments, milestone payments, variable consideration triggers (volume rebates, performance bonuses, refund clauses, penalty clauses), warranty clauses (assurance-type versus service-type indicators), cancellation provisions, modification and amendment clauses; the LLM confidence and the extracted features are logged per clause; never auto-determines performance obligations - human reviewer applies IFRS 15.27 distinct test. Contracts in scope include SaaS subscription agreements, software licence agreements, multi-element technology contracts, construction contracts, telecommunications contracts, life sciences licensing arrangements
Decision Record
Challengeable: Yes - fully documented, reviewable by humans, objection via formal process.
Challengeable by: Auditor
Determine transaction price under IFRS 15 / ASC 606 step 3 What is the transaction price including fixed consideration, variable consideration estimation, significant financing component, non-cash consideration, and consideration payable to customer under IFRS 15.47 / ASC 606-10-32-2? Human Auditor
Transaction price components under IFRS 15.47 and ASC 606-10-32-2: (a) fixed consideration - rule-based extraction; (b) variable consideration - human judgement on expected value method (probability-weighted across range) versus most likely amount method (single most likely outcome) under IFRS 15.53 and ASC 606-10-32-8 - human selects method based on transaction characteristics; (c) significant financing component under IFRS 15.60-65 and ASC 606-10-32-15 - human applies one-year practical expedient or imputes interest; (d) non-cash consideration - fair value at contract inception or transaction date depending on judgment; (e) consideration payable to customer - reduces transaction price unless for distinct good/service. Variable consideration constraint applied at this step before allocation
Decision Record
Challengeable: Yes - via manager, works council, or formal objection process.
Challengeable by: Auditor
Apply variable consideration constraint under IFRS 15.56 / ASC 606-10-32-11 Is the estimated variable consideration constrained to the amount that is highly probable (IFRS 15) / probable (ASC 606) of not requiring significant reversal in subsequent periods? Human Auditor
Constraint application requires human judgement on variability factors per IFRS 15.57: (a) amount of consideration is highly susceptible to factors outside entity's influence; (b) uncertainty about consideration amount expected to remain extended period; (c) entity's experience with similar contracts is limited; (d) entity has practice of providing broad range of price concessions or modifying payment terms; (e) range of possible outcomes is broad. Reassessed each reporting period under IFRS 15.59. Common areas: volume-based rebates, performance bonuses, sales-based royalties (subject to specific royalty exception under IFRS 15.B63), milestone payments, refund/return rights, performance penalties. ASC 606 'probable' threshold lower than IFRS 15 'highly probable' - dual-reporting entities reconcile and disclose
Decision Record
Challengeable: Yes - via manager, works council, or formal objection process.
Challengeable by: Auditor
Assess significant financing component under IFRS 15.60 / ASC 606-10-32-15 Does timing of payment provide customer or entity with significant financing benefit, requiring separation of revenue from interest income/expense? Rules Engine Auditor
Deterministic application of IFRS 15.60-65 and ASC 606-10-32-15: practical expedient applied where period between transfer of promised goods/services and payment is one year or less; significant financing component recognised where (a) advance payment or deferred payment exceeds one year, AND (b) timing difference provides customer or entity with significant financing benefit; discount rate is the rate that would be reflected in a separate financing transaction at contract inception (entity's incremental borrowing rate or customer's incremental borrowing rate); presented separately as interest income/expense under IFRS 15.65 and ASC 606-10-32-20 - not as revenue. Common in long-term construction contracts, advance subscription pricing, multi-year service contracts
Decision Record
Challengeable: Yes - rule application verifiable. Objection possible for incorrect data or wrong rule version.
Challengeable by: Auditor
Allocate transaction price to performance obligations under IFRS 15 / ASC 606 step 4 How is the transaction price allocated to each distinct performance obligation based on relative standalone selling prices under IFRS 15.74 / ASC 606-10-32-31? Human Auditor
Allocation under IFRS 15.74 and ASC 606-10-32-31: (a) observable standalone selling prices applied where available - rule-based; (b) where SSP not directly observable, entity must estimate using one of three approaches: adjusted market assessment approach, expected cost plus margin approach, residual approach (only permitted in limited circumstances under IFRS 15.79 and ASC 606-10-32-34); (c) discount allocation under IFRS 15.81 and ASC 606-10-32-36 - allocate proportionally unless evidence supports allocation to specific performance obligations; (d) variable consideration allocation under IFRS 15.84-86 and ASC 606-10-32-39 - allocated entirely to specific performance obligation if related directly. Material rights options for renewal, additional goods/services treated as separate performance obligations - human judgement on existence of material right per IFRS 15.B40
Decision Record
Challengeable: Yes - via manager, works council, or formal objection process.
Challengeable by: Auditor
Assess principal versus agent under IFRS 15.B34 / ASC 606-10-55-36 Does the entity control the specified good or service before transferring it to the customer (principal - gross presentation) or arrange for another party to provide it (agent - net presentation)? Human Auditor
Control-based assessment under IFRS 15.B34-B38 and ASC 606-10-55-36: principal recognises gross revenue and corresponding cost; agent recognises net commission/fee. Three control indicators applied collectively rather than as bright-line tests: (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, drop-ship arrangements, distributor relationships, software resellers, ticket reselling, travel arrangements, online marketplaces - principal versus agent assessment is among most-frequent restatement areas per Big-4 surveys. Material gross-versus-net presentation difference can change top-line revenue by orders of magnitude with corresponding margin compression
Decision Record
Challengeable: Yes - via manager, works council, or formal objection process.
Challengeable by: Auditor
Determine over-time versus point-in-time recognition under IFRS 15.35 / ASC 606-10-25-27 Is each performance obligation satisfied over time (one of three criteria met) or at a point in time when control transfers? Human Auditor
Three over-time criteria under IFRS 15.35 and ASC 606-10-25-27 (any one suffices): (a) customer simultaneously receives and consumes benefits as entity performs (typical for services like cleaning, hosting, insurance); (b) entity creates or enhances asset that customer controls during performance (typical for construction on customer land); (c) entity creates asset with no alternative use AND has enforceable right to payment for performance to date including reasonable margin (typical for customised manufacturing). If none met, recognition is at point-in-time when control transfers under IFRS 15.38 and ASC 606-10-25-30 - five control transfer indicators: legal title, physical possession, customer acceptance, payment obligation, customer use. Software vendors, construction companies, professional services firms apply this analysis to every contract
Decision Record
Challengeable: Yes - via manager, works council, or formal objection process.
Challengeable by: Auditor
Calculate over-time progress using output or input method What progress measurement method (output or input) best depicts transfer of control under IFRS 15.41 / ASC 606-10-25-31, and what is the cumulative progress percentage? Rules Engine Auditor
Deterministic application of selected progress method under IFRS 15.41 and ASC 606-10-25-31: output methods - surveys of work performed, milestones reached, time elapsed, units produced/delivered; input methods - cost-to-cost (most common for construction), labour hours expended, machine hours, time elapsed; input methods exclude inputs not generating progress under IFRS 15.B19 and ASC 606-10-55-21 (e.g. uninstalled materials, cost overruns due to inefficiencies, mobilisation costs not transferring control). Cost-to-cost method calculation: cumulative costs incurred divided by total estimated costs equals progress percentage; revenue recognised equals progress percentage multiplied by transaction price minus prior cumulative revenue. Method selection requires human judgement at contract inception; calculation thereafter is rule-based
Decision Record
Challengeable: Yes - rule application verifiable. Objection possible for incorrect data or wrong rule version.
Challengeable by: Auditor
Account for contract modifications under IFRS 15.18 / ASC 606-10-25-10 Is the modification accounted for as separate contract, termination of existing contract and creation of new contract, or cumulative catch-up adjustment? Human Auditor
Three modification accounting outcomes under IFRS 15.18-21 and ASC 606-10-25-10-13: (a) separate contract - if modification adds distinct goods/services priced at standalone selling price; (b) termination of existing contract and creation of new contract - if remaining goods/services are distinct from those already transferred; (c) cumulative catch-up adjustment - if remaining goods/services are not distinct (typical for over-time contracts with single performance obligation). Software vendors with ongoing licence amendments, construction companies with change orders, telecom contracts with plan amendments, SaaS subscription upgrade/downgrade scenarios all require human judgement on which outcome applies. Treatment differs materially - separate contract approach has zero impact on existing contract revenue; cumulative catch-up adjustment recalculates the entire over-time recognition
Decision Record
Challengeable: Yes - via manager, works council, or formal objection process.
Challengeable by: Auditor
Account for sales with right of return under IFRS 15.B20 / ASC 606-10-55-22 What is the refund liability and asset for products to be recovered, and what revenue is recognised at amount expected to be entitled? Rules Engine Auditor
Deterministic estimation under IFRS 15.B20-B27 and ASC 606-10-55-22: (a) revenue recognised at amount expected to be entitled excluding products expected to be returned; (b) refund liability for amount expected to refund; (c) asset for products to be recovered with corresponding adjustment to cost of sales. Estimation per expected value method using historical return data adjusted for current conditions per IFRS 15.B22. Reassessed each reporting period under IFRS 15.B25 and ASC 606-10-55-24. Common in retail, e-commerce, consumer products with stated return policies, software with money-back guarantees
Decision Record
Challengeable: Yes - rule application verifiable. Objection possible for incorrect data or wrong rule version.
Challengeable by: Auditor
Distinguish assurance-type versus service-type warranties Is the warranty an assurance-type warranty (under IAS 37 / ASC 460 cost provision) or service-type warranty (separate performance obligation under IFRS 15 / ASC 606)? Human Auditor
Distinction under IFRS 15.B28-B33 and ASC 606-10-55-30: assurance-type warranty - product complies with agreed specifications, accounted under IAS 37 (IFRS) or ASC 460 (US GAAP) as warranty cost provision; service-type warranty - additional service beyond compliance, separate performance obligation requiring transaction price allocation. Indicators per IFRS 15.B31 and ASC 606-10-55-32: (a) whether warranty is required by law - assurance; (b) length of warranty period - longer suggests service; (c) nature of tasks promised - covering hidden defects suggests assurance, providing maintenance suggests service. Mixed warranties require splitting between assurance and service components - human judgement required. Common with electronic equipment, consumer durables, automotive, complex industrial machinery
Decision Record
Challengeable: Yes - via manager, works council, or formal objection process.
Challengeable by: Auditor
Generate revenue journal entries and contract balances What are the journal entries for performance obligation satisfaction (revenue, contract asset, contract liability, accounts receivable) per IFRS 15.105-108 / ASC 606-10-45-1? Rules Engine Auditor
Deterministic posting per IFRS 15.105-108 and ASC 606-10-45-1: (a) when performance obligation satisfied - debit accounts receivable / contract asset, credit revenue; (b) when payment received before satisfaction - debit cash, credit contract liability; (c) when satisfaction occurs after payment - debit contract liability, credit revenue; (d) when satisfaction occurs before payment - debit contract asset, credit revenue. Contract asset versus accounts receivable distinction: contract asset is conditional on something other than passage of time (e.g. completion of remaining performance obligations); accounts receivable is unconditional right to consideration. Disclosure under IFRS 15.116-118 and ASC 606-10-50-8: contract balances opening and closing, significant changes, revenue recognised in current period from prior-period contract liabilities
Decision Record
Challengeable: Yes - rule application verifiable. Objection possible for incorrect data or wrong rule version.
Challengeable by: Auditor
Generate disclosure notes under IFRS 15.110-129 / ASC 606-10-50 What disclosure notes are required including disaggregation of revenue, contract balances, performance obligations, transaction price allocated to remaining obligations, significant judgements? AI Agent Auditor
LLM-supported drafting of disclosure notes per IFRS 15.110-129 and ASC 606-10-50: (a) disaggregation by category that depicts how revenue is affected by economic factors per IFRS 15.114-115; (b) contract balances opening and closing with significant changes; (c) performance obligations including significant judgements on timing, transaction price, allocation methods; (d) transaction price allocated to remaining obligations under IFRS 15.120 and ASC 606-10-50-13 - amount and expected timing of recognition; (e) costs to obtain and fulfil contracts under IFRS 15.127. ESMA enforcement priority every year since 2019 focused on disaggregation disclosure quality and remaining performance obligations transparency. LLM drafts based on portfolio-level data; accountant reviews and refines wording; never auto-files
Decision Record
Challengeable: Yes - fully documented, reviewable by humans, objection via formal process.
Challengeable by: Auditor
Detect anomalous revenue patterns and PCAOB AS 2401 fraud risk indicators Does any revenue recognition pattern (period-end channel stuffing signal, unusual cut-off entries, side-letter risk indicators, bill-and-hold without legitimate substance, percentage-of-completion variance from historical baseline) match a known fraud pattern or restatement risk? AI Agent Auditor
Pattern matching against PCAOB AS 2401 fraud risk indicators: (a) significant transactions near period-end with unusual terms; (b) bill-and-hold arrangements without legitimate business substance under SEC SAB Topic 13.A.3; (c) side letters or under-the-table arrangements modifying contract terms; (d) percentage-of-completion contracts with cost-overrun patterns inconsistent with margin trends; (e) sudden changes in customer concentration or geographic mix; (f) channel stuffing signals - shipments exceeding distributor sell-through capacity; (g) journal entries to revenue accounts by non-revenue personnel; (h) unusual cut-off entries on last working days of period. PCAOB AS 2401 presumes revenue recognition is fraud risk - LLM provides early-warning escalation, never auto-determines fraud occurrence; human auditor performs substantive procedures
Decision Record
Challengeable: Yes - fully documented, reviewable by humans, objection via formal process.
Challengeable by: Auditor
Decision Record and Right to Challenge
Every decision this agent makes or prepares is documented in a complete decision record. Affected parties (employees, suppliers, auditors) can review, understand, and challenge every individual decision.
Does this agent fit your process?
We analyse your specific finance process and show how this agent fits into your system landscape. 30 minutes, no preparation needed.
Analyse your processGovernance Notes
Of the 16 steps, 6 are deterministic, 7 are human judgement, and 3 use an LLM suggestion (contract-data extraction, disclosure-note drafting and fraud-risk pattern detection). The high human share reflects the reality of IFRS 15 and ASC 606: the standards are intentionally judgement-intensive, with seven decision points that require human accounting expertise. The Agent automates the mechanical steps and prepares the judgement decisions through structured documentation - software prepares judgement, it does not delegate it. The process is not high-risk under the EU AI Act: revenue recognition is not an employment decision or social-scoring under Annex III.
Under SOX 404 (PCAOB AS 2201) and the related fraud, risk and Critical-Audit-Matter standards, the revenue cycle is a significant cycle for SEC registrants and the most-frequent SOX 404 material-weakness area. The Agent's Decision Log provides PCAOB AS 2201 evidence on the preventive controls (the five-criteria contract check, the distinct test, transaction price and the variable-consideration constraint, the significant-financing-component assessment, allocation methodology, the principal-versus-agent call, the over-time-versus-point-in-time determination, and the contract-modification outcome) and the detective controls (contract-balance reconciliation, performance-obligation roll-forward, channel-stuffing detection, bill-and-hold legitimacy checks, side-letter monitoring). The three LLM stages are COSO 2013 controlled, with a confidence threshold, escalation to a revenue-accounting reviewer and decision logging, and the LLM never determines an accounting outcome without human acceptance.
Retention follows the longest applicable rule: 7 years for PCAOB AS 1215 issuer audits, 6 years for UK HMRC records, and 6-10 years across EU Member States, with IFRS 15 and ASC 606 requiring retention through the statute-of-limitations and audit-evidence period. The Agent applies that rule globally and tags each entry with its retention class. Revenue contract data and counterparty information is processed under the relevant US, UK and EU data-protection laws. Customer contract terms are commercially sensitive and carry heightened protection, so the Agent applies role-based access control, encryption at rest and in transit, and a complete audit log of access events.
§203 StGB-relevant data is encrypted end-to-end and never passed to AI models in plain text.
Process Documentation Contribution
Assessment
Prerequisites
- Cloud revenue recognition system or ERP module with API access: Workday Revenue Management, SAP S/4HANA Revenue Accounting and Reporting (RAR), Oracle Revenue Management Cloud Service, Zuora RevPro, NetSuite Advanced Revenue Management, Sage Intacct Contract and Revenue Management, Aptitude RevStream - with full per-contract record access including performance obligation registry, transaction price components, allocation calculations, contract balance positions
- Contract repository with digitised contracts plus clause-extraction capability: Conga Contract Lifecycle Management, Salesforce CPQ and Revenue Cloud, DocuSign CLM, Ironclad, Agiloft - with executed agreement plus master services agreement plus statement of work plus side letter visibility, plus contract modification trail
- Defined methodology for over-time progress measurement (input methods cost-to-cost or labour hours, output methods milestones or units produced/delivered) per contract type with historical input cost-vs-actual variance analysis
- Standalone selling price (SSP) repository per product/service line with refresh cadence, supporting allocation under IFRS 15.74 and ASC 606-10-32-31 - observable SSP, adjusted market assessment approach, expected cost plus margin approach, residual approach where applicable
- Historical contract data for variable consideration estimation (volume rebates, performance bonuses, refund/return rates, sales-based royalties, milestone payments) - minimum 24 months for expected value method, longer for sales-based royalties under specific exception
- Big-4 audit firm engagement with PCAOB evidence requirements under AS 2201, AS 2401, AS 2110 and AS 3101 (Deloitte ASM, PwC Halo, EY Helix, KPMG Clara) plus a statutory auditor with ISA UK 240 and 540 evidence requirements; integrated with revenue close cycle for automated evidence loading
- WORM-compliant archive for jurisdictional retention rules: US IRS 7 years per PCAOB AS 1215, SEC 17a-4 6 years for issuer audits, UK HMRC 6 years per Finance Act, EU 6-10 years per Member State, IFRS 15 requires retention through statute of limitations plus audit evidence period - Amazon S3 Object Lock, Azure Blob Immutable Storage, Google Cloud Storage Bucket Lock
Infrastructure Contribution
The Revenue Recognition Agent demonstrates the pattern for judgement-intensive agents: a high human share, but with structured decision preparation rather than delegated judgement. Its contract-extraction LLM infrastructure is reused by the Lease Accounting Agent, the Contract Compliance Agent and the Tax Provision Agent; its over-time progress-measurement engine is reused by every agent with over-time satisfaction, including the Lease Accounting and Long-term Construction Agents; and its LLM disclosure-note generation is reused for the major IFRS and US GAAP notes. The seven judgement-intensive decision points provide reference architecture for other judgement-heavy agents such as the Goodwill Impairment and Business Combination agents. It feeds the SOX-Compliance Agent with PCAOB AS 2201 and AS 2401 evidence, the Tax Provision Agent with deferred-tax revenue-timing differences for ASC 740 and IAS 12, the Statutory Reporting Agent with revenue disclosures, the Investor Relations Agent with disaggregation and remaining-performance-obligation data, and the Anti-Fraud Agent with channel-stuffing and bill-and-hold signals. It consumes executed contracts and their modifications from the Contract Lifecycle Management Agent, counterparty credit standing from the Customer Master Data Agent, the standalone-selling-price registry from the Pricing Agent, billing and milestone schedules from the Sales Operations Agent, and invoiced amounts and collection patterns from the Order-to-Cash Agent.
What this assessment contains: 9 slides for your leadership team
Personalised with your numbers. Generated in 2 minutes directly in your browser. No upload, no login.
- 1
Title slide - Process name, decision points, automation potential
- 2
Executive summary - FTE freed, cost per transaction before/after, break-even date, cost of waiting
- 3
Current state - Transaction volume, error costs, growth scenario with FTE comparison
- 4
Solution architecture - Human - rules engine - AI agent with specific decision points
- 5
Governance - EU AI Act, GoBD/statutory, audit trail - with traffic light status
- 6
Risk analysis - 5 risks with likelihood, impact and mitigation
- 7
Roadmap - 3-phase plan with concrete calendar dates and Go/No-Go
- 8
Business case - 3-scenario comparison (do nothing/hire/automate) plus 3×3 sensitivity matrix
- 9
Discussion proposal - Concrete next steps with timeline and responsibilities
Includes: 3-scenario comparison
Do nothing vs. new hire vs. automation - with your salary level, your error rate and your growth plan. The one slide your CFO wants to see first.
Show calculation methodology
Hourly rate: Annual salary (your input) × 1.3 employer burden ÷ 1,720 annual work hours
Savings: Transactions × 12 × automation rate × minutes/transaction × hourly rate × economic factor
Quality ROI: Error reduction × transactions × 12 × EUR 260/error (APQC Open Standards Benchmarking)
FTE: Saved hours ÷ 1,720 annual work hours
Break-Even: Benchmark investment ÷ monthly combined savings (efficiency + quality)
New hire: Annual salary × 1.3 + EUR 12,000 recruiting per FTE
All data stays in your browser. Nothing is transmitted to any server.
Revenue Recognition Agent
Initial assessment for your leadership team
A thorough initial assessment in 2 minutes - with your numbers, your risk profile and industry benchmarks. No vendor logo, no sales pitch.
All data stays in your browser. Nothing is transmitted.
Related Pages
Related Agents
Accruals Agent
Automate period-end accruals - prepaid expenses, deferred income and reversal.
Frequently Asked Questions
IFRS 15 versus ASC 606 - how does the Agent reconcile differences for dual-reporting entities and what triggers Big-4 audit qualification?
Variable consideration constraint - how does the Agent estimate variable consideration and apply the IFRS 15 'highly probable' / ASC 606 'probable' constraint, and what triggers a SEC AAER?
Performance obligation distinct test - how does the Agent identify separate performance obligations and what makes this the most-frequent restatement area?
Principal versus agent assessment - how does the Agent determine gross versus net presentation and what is the cross-jurisdictional auditor focus?
Significant financing component - how does the Agent assess whether timing of payment provides significant financing benefit and what is the practical expedient?
Contract modifications - how does the Agent determine separate contract / termination and new contract / cumulative catch-up adjustment treatment?
How does the Agent integrate with Workday Revenue, SAP S/4HANA RAR, Oracle Revenue Management Cloud, Zuora RevPro, and NetSuite for cross-jurisdictional revenue recognition?
What Happens Next?
30 minutes
Initial call
We analyse your process and identify the optimal starting point.
1 week
Discover
Mapping your decision logic. Rule sets documented, Decision Layer designed.
3-4 weeks
Build
Production agent in your infrastructure. Governance, audit trail, cert-ready from day 1.
12-18 months
Self-sufficient
Full access to source code, prompts and rule versions. No vendor lock-in.
Implement This Agent?
We assess your finance process landscape and show how this agent fits your infrastructure.