The ASC 606 How-To Guide: Revenue Recognition in Five Steps

Why ASC 606 Doesn’t Have to Be Your Nightmare

If you’re reading this, chances are someone mentioned ASC 606 and you felt that familiar knot in your stomach. Maybe it was your investor, your auditor, or that conversation with your CPA that left you more confused than when you started. Here’s the thing – ASC 606 isn’t actually designed to make your life miserable. It’s designed to create consistency and transparency in how businesses recognize revenue.

At Alajian Group, we’ve guided hundreds of businesses through ASC 606 implementation, from tech startups to established enterprises. What we’ve learned is that once you understand the framework – really understand it – it becomes a powerful tool for accurate financial reporting rather than a compliance burden.

Let’s break down ASC 606 into five manageable steps that you can actually implement in your business.

Our Values in Revenue Recognition

Precision We ensure your revenue recognition follows ASC 606 standards exactly, protecting you from audit issues.

Clarity Complex accounting standards made simple through practical, step-by-step guidance.

Compliance Full ASC 606 and GAAP compliance that stands up to investor scrutiny and audit requirements.

Confidence Peace of mind knowing your financial statements accurately reflect your business performance.

What Exactly Is ASC 606?

ASC 606 stands for Accounting Standards Codification Topic 606. It’s the current standard for revenue recognition that replaced older, industry-specific guidance with one unified approach. Think of it as the universal language for when and how businesses should recognize revenue from customer contracts.

Here’s why it matters: before ASC 606, a software company, a construction company, and a consulting firm might all handle similar transactions completely differently. ASC 606 creates consistency across industries while still accommodating the unique aspects of different business models.

Who Needs to Follow ASC 606?

Public Companies: Required by law – no exceptions.

Private Companies Seeking Investment: Most sophisticated investors expect ASC 606 compliance.

Companies with Complex Revenue Streams: Multiple products, services, or subscription models.

Businesses Preparing for Sale or Audit: Clean, compliant books are essential for due diligence.

Growing Companies: Better to implement it right from the start than fix it later.

The Five-Step ASC 606 Framework

Think of ASC 606 as a roadmap. Each step builds on the previous one, and skipping steps or rushing through them creates problems down the line. Here’s how to navigate each step successfully:

Step 1: Identify the Contract with a Customer

This sounds simple, but it’s where many businesses stumble. A contract isn’t just a signed document – it’s any agreement where both parties have enforceable rights and obligations.

What Makes a Valid Contract Under ASC 606:

Approved Agreement: Both parties have agreed to the terms (written, verbal, or implied by business practice).

Identifiable Rights: Each party’s rights regarding goods or services are clear.

Clear Payment Terms: How much, when, and how payment will be made.

Commercial Substance: The contract changes the risk, timing, or amount of future cash flows.

Probable Collection: You’re likely to collect the payment you’re entitled to receive.

Real-World Examples:

SaaS Company: Your standard subscription agreement, even if signed electronically, qualifies as a contract.

Consulting Firm: A signed statement of work detailing deliverables, timeline, and fees.

E-commerce Business: Your terms of service combined with a customer’s purchase order.

Red Flags to Watch For:

• Contracts where collection is uncertain
• Agreements missing key commercial terms
• Deals that are essentially free trials disguised as sales

Step 2: Identify the Performance Obligations in the Contract

A performance obligation is simply a promise to deliver something of value to your customer. The key question: what distinct goods or services are you promising to provide?

What Makes Something “Distinct”:

Standalone Value: The customer can benefit from the good or service on its own.

Separately Identifiable: It’s not highly integrated with other promises in the contract.

Common Performance Obligation Scenarios:

Software + Implementation: If you’re selling software with setup services, these are typically two distinct performance obligations.

Product + Warranty: Standard warranties are usually not distinct, but extended service contracts often are.

Training + Software: Professional training delivered separately from software access counts as a distinct obligation.

Bundled Services: Must evaluate whether each service provides standalone value.

Practical Tips:

• List every promise you make to customers
• Ask: “Could the customer get value from this separately?”
• Consider how you price and sell these items individually
• Document your analysis – auditors will ask

Step 3: Determine the Transaction Price

This is the total amount you expect to receive from the customer. Sounds straightforward, but there are several complicating factors to consider.

Components of Transaction Price:

Fixed Consideration: The base price stated in the contract.

Variable Consideration: Bonuses, penalties, discounts, rebates, or usage-based fees.

Non-Cash Consideration: Goods, services, or other non-monetary payments.

Consideration Paid to Customer: Any amounts you pay back to the customer.

Handling Variable Consideration:

You can only include variable consideration in the transaction price if it’s “highly probable” that you won’t have to reverse the revenue later. This is where many companies get conservative – and rightfully so.

Examples of Variable Consideration:

• Performance Bonuses: Only include if achievement is highly probable.
• Volume Discounts: Estimate based on expected purchase volumes.
• Usage-Based Pricing: Recognize as usage occurs, not based on estimates.
• Refund Rights: Reduce transaction price by expected refunds.

Step 4: Allocate the Transaction Price

When you have multiple performance obligations, you need to divvy up the total transaction price among them. The goal is to allocate based on standalone selling prices – what you’d charge for each item separately.

The Allocation Process:

Determine Standalone Selling Prices: What would you charge for each performance obligation separately?

Calculate Allocation Percentages: Each obligation’s standalone price divided by the total.

Apply Percentages to Transaction Price: Multiply each percentage by the total transaction price.

Methods for Determining Standalone Selling Prices:

Observable Prices: What you actually charge when selling items separately.

Adjusted Market Assessment: What competitors charge for similar goods or services.

Expected Cost Plus Margin: Your costs plus a reasonable profit margin.

Residual Approach: Only used when standalone selling price is highly uncertain.

Real Example:

You sell software ($100 standalone), implementation ($50 standalone), and training ($25 standalone) as a bundle for $150.

• Total standalone prices: $175
• Software allocation: ($100 ÷ $175) × $150 = $85.71
• Implementation allocation: ($50 ÷ $175) × $150 = $42.86
• Training allocation: ($25 ÷ $175) × $150 = $21.43

Step 5: Recognize Revenue When Performance Obligations Are Satisfied

This is where the rubber meets the road. Revenue recognition happens when you satisfy performance obligations – meaning when you actually deliver value to the customer.

Two Ways Performance Obligations Can Be Satisfied:

Over Time: You recognize revenue as you perform.

At a Point in Time: You recognize revenue when control transfers to the customer.

Performance Obligations Satisfied Over Time:

• Customer receives and consumes benefits as you perform (like monthly SaaS subscriptions)
• Customer controls the asset as you create it (like custom software development)
• You’re creating something with no alternative use and have a right to payment (like custom manufacturing)

Performance Obligations Satisfied at a Point in Time:

• Physical goods typically transfer control at delivery
• Software licenses often transfer at delivery or activation
• Services completed and delivered in full

Measuring Progress for Over-Time Recognition:

Output Methods: Based on value delivered to customer (milestones, units produced, etc.)

Input Methods: Based on your efforts or inputs (costs incurred, time elapsed, etc.)

Choose the method that best depicts your performance pattern.

Common ASC 606 Implementation Challenges

Challenge 1: Complex Bundled Offerings

Many businesses sell combinations of products and services. The key is properly identifying what’s distinct and allocating revenue appropriately.

Challenge 2: Contract Modifications

When customers change their orders, you need to determine if it’s a separate contract or a modification of the existing contract.

Challenge 3: Variable Consideration

Estimating bonuses, penalties, and discounts requires judgment and careful documentation.

Challenge 4: Systems and Processes

ASC 606 often requires more detailed tracking and reporting than companies currently have in place.

Technology Solutions for ASC 606 Compliance

Entry-Level Solutions:

• QuickBooks with revenue recognition add-ons
• Excel-based tracking (only for very simple businesses)

Mid-Market Solutions:

• NetSuite with Advanced Revenue Recognition
• Sage Intacct revenue recognition module

Enterprise Solutions:

• Workday Financial Management
• SAP Revenue Accounting and Reporting
• Oracle Revenue Management Cloud

Red Flags That Signal You Need Professional Help

Your Revenue Recognition Keeps Changing: If you’re constantly adjusting prior period revenue, you likely have process issues.

Auditor Questions: If your auditors are asking detailed questions about your revenue recognition approach.

Investor Concerns: Sophisticated investors will scrutinize your revenue recognition practices.

Complex Contracts: Multi-element deals, variable pricing, or long-term contracts require expertise.

System Limitations: If your current systems can’t handle the complexity of ASC 606 calculations.

Our ASC 606 Implementation Services

Initial Assessment & Gap Analysis We review your current revenue recognition practices and identify areas needing attention.

Five-Step Framework Implementation Step-by-step guidance through each phase of ASC 606 compliance.

Policy & Procedure Development Documented revenue recognition policies that meet audit standards.

System Selection & Setup Help choosing and implementing technology solutions that support ASC 606.

Staff Training & Education Ensuring your team understands the new processes and requirements.

Ongoing Compliance Support Monthly reviews and updates to maintain compliance as your business evolves.

Your ASC 606 Implementation Roadmap

Phase 1: Assessment (Weeks 1-2)

• Document current revenue streams
• Identify contracts and performance obligations
• Assess system capabilities

Phase 2: Design (Weeks 3-4)

• Develop revenue recognition policies
• Design new processes and controls
• Select appropriate technology tools

Phase 3: Implementation (Weeks 5-8)

• Configure systems and processes
• Train staff on new procedures
• Test with sample transactions

Phase 4: Go-Live (Week 9)

• Process first period under new standards
• Monitor and adjust as needed
• Document lessons learned

Phase 5: Optimization (Ongoing)

• Refine processes based on experience
• Update for new transaction types
• Maintain compliance as business evolves

FAQs

Do I need to follow ASC 606 if I’m a private company? While not legally required for all private companies, ASC 606 is expected by most investors, lenders, and auditors. It’s becoming the de facto standard.

Can I implement ASC 606 gradually? ASC 606 should be implemented comprehensively. However, you can prioritize your most significant revenue streams first.

What if my contracts don’t clearly identify performance obligations? This is common. You may need to revise contract templates and clarify terms with existing customers.

How do I handle contract modifications under ASC 606? It depends on whether the modification adds distinct goods/services at standalone selling prices. Each situation requires specific analysis.

What documentation do auditors expect for ASC 606? Detailed policies, transaction-level support for the five-step analysis, and evidence of consistent application across similar transactions.

How does ASC 606 affect my financial statements? It may change the timing of revenue recognition, requiring adjustments to opening balances and potentially impacting loan covenants.

Ready to Implement ASC 606 the Right Way?

ASC 606 doesn’t have to be overwhelming. With the right approach, proper planning, and expert guidance, you can implement compliant revenue recognition that actually provides better insight into your business performance.

The key is starting with a solid understanding of the five-step framework and then building processes and systems that support consistent application. Don’t try to do it alone – the stakes are too high, and the complexity too great.

At Alajian Group, we’ve helped businesses across industries successfully implement ASC 606. We know the pitfalls to avoid, the shortcuts that backfire, and the best practices that actually work in the real world.