Professional Services

Financial reports and revenue charts illustrating ASC 606 revenue recognition analysis

Performance Obligations Under ASC 606 Explained

Performance obligations sit at the center of that question. Getting the classification wrong can turn a strong bookings quarter into a messy audit conversation. This article explains how companies define performance obligations and why the distinction carries strategic weight beyond compliance. It also covers how the concept plays out across common bundled contracts involving software, hardware, warranties, and services.

Boxed toy train product illustrating bundled contract accounting under ASC 606

ASC 606 Revenue Recognition for Bundled Discount Contracts

A single line on an invoice rarely tells the full story of value delivered. Nowhere is that truer than in bundled contracts. ASC 606 revenue recognition governs how finance teams separate hardware, software, licenses, and services sold together for one price. Getting it wrong can distort margin analysis, mislead the board, and complicate a fundraising or M&A process. For growth-stage companies structuring a bundled discount across products and services, the discipline matters. Identifying performance obligations, estimating standalone selling price, and allocating transaction price is not an academic exercise. It shapes forecasting accuracy and investor trust.

Retail discount and sale signage illustrating accounting for sales discounts under ASC 606

Accounting for Sales Discounts Under ASC 606: What Finance Leaders Get Wrong

Accounting for sales discounts is not a pricing footnote. Under ASC 606, a discount, rebate, or coupon changes the transaction price itself. That shift changes recognized revenue, gross margin, and the story a board or investor reads into the numbers. A ten percent discount on $10M in ARR is $1M in revenue. It either belongs on the income statement now, or it does not. Getting that determination wrong is one of the more common sources of restatements in growth-stage companies.

Large boulder blocking a mountain road, representing a bottleneck in the contract review process

Working with Lawyers Under Pressure: A Practical Guide to Legal Risk Triage

Working with lawyers under deadline pressure is one of the most persistent friction points in growing companies. Most of that friction comes from confusion about priority, not from the legal work itself. When every contract, hire, and financing document arrives on counsel’s desk with equal urgency, review slows down. It settles to the pace of the most cautious lawyer in the room. The fix is not to push lawyers to move faster. It is to give legal teams a structure that tells them where genuine risk lives. That structure lets speed and diligence stop competing with each other.

Server room data center representing vendor-hosted infrastructure in software license revenue recognition

Software License Revenue Recognition Under ASC 606: A CFO’s Guide to License Accounting

Software license revenue recognition is rarely the semantic exercise it appears to be on the surface. It is the mechanism by which a company tells the market, its board, and its auditors what it actually sold. Under ASC 606, the right-to-use versus right-to-access distinction determines the recognition pattern. That single choice decides whether revenue lands on delivery or unfolds across the life of the contract. License accounting frameworks built across companies from early-stage software builds to a publicly listed gaming enterprise reveal the same pattern. Long after the parties sign the contract, this classification decision ripples through forecasting, valuation, and audit outcomes.

Steel bridge under construction, symbolizing long-term projects tracked with the percentage of completion method

The Percentage of Completion Method: A Practitioner’s Guide to PoC Accounting Under ASC 606

Revenue is the story a company talks about performance. For professional services firms running long, multi-period engagements, that story can drift from reality fast. The percentage of completion method is the mechanism that keeps it honest. I have built and defended PoC accounting across cybersecurity, professional services, and consumer products businesses. Over time, I have come to see it less as a compliance exercise and more as a discipline. It forces finance, delivery, and leadership to agree on what progress actually means before the number ever reaches the board.

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.

Interlocking metal pulleys and gears symbolizing legal support as a strategic lever for startup growth

Legal Support for Startups: Turning a Cost Center into a Growth Lever

Most founders treat legal support for startups as a reactive function, summoned when a deal needs closing or a problem needs cleaning up. The founders who scale with intention treat it differently. They fold legal thinking into the operating rhythm of the company from the earliest days. It strengthens governance, protects intellectual property, and keeps the business ready for whatever opportunity or scrutiny arrives next.

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.