Accounting

Construction site with crane and scaffolding illustrating output-based revenue recognition tied to project milestones

The Revenue Recognition Principle: Time-Based vs. Output-Based Recognition Under IFRS 15

The revenue recognition principle is not merely a compliance exercise buried in the notes to the financial statements. It is a statement about how a company creates value. It must prove that value transfer with evidence a board, an auditor, or an acquirer will trust. The five-step model under IFRS 15 and ASC 606 ends with its most consequential step. That step asks a deceptively simple question. Does the customer receive value over time, or does the company deliver a specific output before revenue counts? The answer shapes everything downstream, from accounts receivable and covenant compliance to how investors read the growth story.

Controlled plume launch symbolizing the momentum and risk of choosing the right ASC 606 milestone method for revenue recognition.

ASC 606 Milestone Method: Choosing Between Time, Output, and Percentage of Completion

Revenue recognition timing is rarely the technical afterthought many finance functions treat it as. Under ASC 606, once a contract qualifies for recognition over time, the harder question begins. Does the pattern of value delivery track the calendar, or does it track discrete deliverables and milestones? The ASC 606 milestone method and the percentage of completion method ASC 606 permits are not interchangeable defaults. Each reflects a different theory of how a customer receives value. Choosing the wrong one distorts the story a company tells investors, lenders, and its own board.

Mountain road guardrail at sunset symbolizing risk control and boundaries in principal vs agent revenue recognition under ASC 606

Principal vs Agent Revenue Recognition: What Control Really Means Under ASC 606

Every growing company eventually faces a version of the same question: gross revenue or net revenue? Gross means reporting the full amount billed to the customer. Net means reporting only the margin retained after paying a partner. That choice sits inside one of the more consequential judgments calls in ASC 606, the principal vs agent revenue recognition determination. It shapes how investors read growth. It shapes how boards evaluate strategy. And it shapes how auditors sign off on the numbers a company puts in front of the market.

Financial growth charts and graphs with pen, representing variable consideration and revenue forecasting

ASC 606 Variable Consideration: A CFO’s Guide to Estimating What You Cannot Yet Know

Every early-stage company forecast revenue as though the best case were the only case. Then reality sets in. Customers cancel, dispute, renegotiate, and return. ASC 606 variable consideration is the accounting discipline built for that gap between the invoice and the truth. Across two and a half decades in the CFO chair, I have come to see it differently. It is less a technical footnote. It is more a test of whether finance truly understands the business it reports on.

Young child learning counting with a colorful wooden abacus

Audit Readiness: Building Financial Systems That Explain Themselves

Audit readiness is often mistaken for a formatting exercise. Many assume clean spreadsheets and a working familiarity with GAAP can resolve it on their own. More than two decades of finance leadership across cybersecurity, SaaS, gaming, logistics, digital marketing, medical devices, and nonprofit organizations point to a different picture. Audit readiness is a test of systems, habits, and culture. It is not a test of arithmetic. Companies rarely stumble over a complex technical error buried in the ledger. They stumble because of gaps in process. A revenue policy nobody wrote down. An accrual with no supporting schedule. Equity records out of sync with a board approval. Documentation assembled the week before auditors arrived, instead of maintained continuously.