Oops! Something went wrong while submitting the form.
Get a Demo
See your data in HubiFi < 2 days
Understand how to apply ASC 606 to recognize revenue over time with clear steps and strategies for accurate financial reporting.
Deciding when to book your revenue is one of the most important judgments you'll make under ASC 606. It’s not a simple preference; the standard requires you to follow a specific framework based on how and when you deliver value to your customer. If your contract meets certain conditions, you are required to asc 606 recognize revenue over time rather than all at once. The good news is that this isn't a guessing game. The guidance provides three clear criteria to determine if your performance obligation qualifies. This article will walk you through each of these gateways, helping you understand the logic so you can make the right call confidently and ensure your financial reporting is both compliant and accurate.
Let's break down ASC 606. At its core, this is the accounting standard that guides how and when your business should recognize revenue from contracts with customers. The main goal is to make revenue reporting more consistent and comparable across different companies and industries. Think of it as a universal language for reporting your sales. The central idea is straightforward: you should record revenue when you deliver the promised goods or services to your customer, for the amount you expect to be paid.
The biggest change ASC 606 introduced was a shift in focus. Previous guidance centered on the transfer of "risks and rewards," which could be a bit vague. The new standard is all about the transfer of "control." This means revenue is recognized when your customer gains the ability to direct the use of, and get all the benefits from, a good or service. This distinction is critical because it often requires more judgment from your team to pinpoint the exact moment control changes hands. You can find a detailed breakdown in the official ASC 606 Revenue from Contracts with Customers guidance.
To apply this principle consistently, ASC 606 provides a five-step model. This framework is your roadmap for recognizing revenue correctly:
While this framework provides clarity, it also introduces complexity, especially for businesses with high-volume transactions or complex contracts. Getting it right is essential for accurate financial statements and passing audits. Understanding these steps is the first move toward mastering your revenue recognition process and making smarter strategic decisions. For more deep dives into financial operations, you can explore other articles on the HubiFi Blog.
Deciding whether to recognize revenue over time or at a single point is one of the most important judgments you'll make under ASC 606. Getting it right is crucial for accurate financial reporting and avoiding compliance headaches later. The standard doesn't leave this up to guesswork; it provides three specific criteria. If your contract with a customer meets just one of these, you can recognize revenue as you perform the work.
Think of these as three distinct gateways. Your performance obligation only needs to pass through one of them to qualify for over-time recognition. This approach helps ensure that your financial statements accurately reflect the value you're delivering to your customer as you deliver it. For businesses with complex, long-term contracts, this is a game-changer. It aligns your revenue stream with your operational efforts, giving you a clearer picture of your company's financial health. Understanding these criteria is the first step toward mastering your revenue recognition process. Let's break down what each one means in simple terms.
The first test is whether your customer receives and uses the benefits of your work as you perform it. This is common in service-based businesses. For example, if you provide monthly IT support, your customer benefits from having access to that support throughout the entire month, not just on the last day. The same goes for a subscription to a software platform; the user gets value from accessing the software each day. The core idea here is that the customer is simultaneously receiving and consuming the benefit of your performance. This is one of the most straightforward paths to justifying over-time revenue recognition.
The second criterion applies when your work creates or improves an asset that your customer controls as it's being created. The classic example is constructing a building on a customer's land. As you build, the partially completed structure is on their property, and they control it. They have the ability to direct the use of that asset. This isn't limited to physical construction. It could also apply to developing a custom feature within a customer's existing software system. Because the customer controls the underlying asset you're enhancing, you can recognize the revenue over the course of the project, reflecting the value you're adding at each stage.
The final criterion has two parts. First, the asset you're creating must not have an alternative use to you. This means it's so customized for the client that if they canceled the contract, you couldn't easily sell it to someone else. Think of building a highly specialized piece of manufacturing equipment. Second, you must have an enforceable right to payment for the work you've completed to date. This protects you from being left empty-handed if the project is terminated. If both conditions are met, you can recognize revenue over time because you are essentially transferring value that is unique to that customer and are guaranteed compensation for your efforts. Managing these complex contracts is where an automated solution can make a huge difference.
Once you’ve determined that a performance obligation is satisfied over time, your next step is to figure out how to measure your progress. This isn’t just about tracking time; it’s about choosing a method that faithfully represents the transfer of value to your customer. ASC 606 gives you two primary ways to do this: output methods and input methods.
Choosing the right approach is crucial for accurate financial reporting and compliance. The method you select should be applied consistently to similar performance obligations and should genuinely reflect your progress toward completing the contract. Let’s break down what each method entails so you can decide which one makes the most sense for your business. Getting this right ensures your financial statements are a true reflection of your performance, which is essential for everything from passing audits to making strategic decisions.
Output methods measure progress by looking at the value you’ve delivered to the customer so far. Think of it as measuring the results, not the effort. This approach focuses on direct measurements of the goods or services transferred. Common examples include tracking units produced or delivered, milestones achieved, or appraisals of results. According to guidance from financial experts, these methods are particularly effective for long-term manufacturing projects or the rollout of new services where you can clearly see the value transferred to the customer. If your project has distinct phases or deliverables, an output method like milestones achieved can be a straightforward and logical way to recognize revenue as you complete each stage.
In contrast, input methods measure progress based on the effort you’ve put in or the resources you’ve consumed. Instead of looking at the finished product, you’re looking at the ingredients. This could include metrics like costs incurred, labor hours worked, or machine hours used. This method is often a great fit when you can’t directly measure the output or when the effort expended directly corresponds to the value being transferred to the customer. For instance, in many service-based contracts, the number of hours worked is a reliable proxy for progress. Accurately tracking these inputs is critical, which is where automated revenue recognition can make a significant difference by simplifying data collection and ensuring precision.
While the rules for ASC 606 apply to all businesses, some industries find themselves using the over-time recognition method more frequently than others. It all comes down to the nature of the product or service being sold. If you deliver value to your customer over a period instead of in a single moment, you’re likely a candidate for this approach. Think of it as matching your revenue stream to your workflow. When a project spans months or even years, recognizing revenue as you complete the work gives a much more accurate picture of your company's financial health than waiting until the very end.
This method is especially common for businesses with long-term contracts, subscription models, or projects where the customer receives and consumes the benefit of the work as it's being performed. Industries like construction, professional services, and software-as-a-service (SaaS) are prime examples. For them, over-time recognition isn't just an accounting option; it's a fundamental part of reflecting their business operations accurately. If your business falls into one of these categories, getting a firm handle on this method is essential for maintaining compliance and making informed financial decisions. It helps you avoid the cash flow rollercoaster that can come from recognizing large sums of revenue all at once.
The construction industry is a classic example of where over-time revenue recognition is standard practice. When building a custom structure for a client, the project unfolds over an extended period. According to accounting guidelines, revenue can be recognized over time if the asset being created has no alternative use for your company and you have a legal right to payment for work completed so far. Imagine you're building a specialized manufacturing plant. You can't just sell it to someone else if the original client backs out. Because of this, ASC 606 allows you to recognize revenue as you hit construction milestones, which provides a steadier, more realistic view of your company's performance throughout the project's life cycle.
Many service-based businesses, from consulting firms to marketing agencies, also rely on over-time revenue recognition. This is because the customer often receives the value of the service as it's being performed. Think about a monthly retainer for IT support or a year-long public relations contract. The guidance is clear: if the customer simultaneously gets and uses the benefit of your work, you should recognize the revenue over the service period. This prevents a situation where you do work all year but only show the income in your books when the final invoice is paid, which would distort your financial reporting. Instead, you match the revenue to the period in which you earned it by providing your services.
The software and technology sector, particularly with the rise of SaaS models, frequently uses over-time recognition. When a customer pays for a yearly software subscription, they are paying for continuous access, updates, and support over that 12-month period. This ongoing delivery of value means revenue should be recognized monthly, not all at once when the customer signs up. This concept also applies to companies making special products with no alternative use, such as developing custom software for a specific enterprise client. Managing these recurring revenue streams can get complicated, which is why automated solutions with seamless integrations are so helpful for maintaining accurate, compliant financials.
So, how do you decide when to book your revenue? Under ASC 606, you have two primary options: you can recognize it all at once (at a point in time) or spread it out gradually (over time). This isn't a choice you get to make based on preference. The right method depends entirely on the nature of your contract and, most importantly, when you transfer control of a good or service to your customer. This concept of "transfer of control" is the cornerstone of the modern revenue recognition standard.
Getting this right is more than just an accounting exercise. The method you use directly shapes your financial narrative. Recognizing revenue over time can show steady, predictable growth, which is often favored by subscription-based companies. On the other hand, point-in-time recognition might result in financial reports with significant peaks and valleys, which is typical for businesses selling physical goods. Both are perfectly fine, as long as you're using the correct method for your business model. The key is to analyze your performance obligations and determine the precise moment or period that control passes to your customer. This decision is the foundation of compliant revenue recognition and ensures your financial statements accurately reflect your company's performance.
Think of it this way: the default method is recognizing revenue at a point in time. You only use the over-time method if your customer contract meets at least one of three specific criteria. As a quick refresher, you must recognize revenue over time if:
If your contract checks just one of these boxes, you are required to use the over-time method. If it meets none of them, you’ll recognize the revenue at the single point in time that control is transferred, such as upon delivery or project completion.
The method you use directly influences the story your financial statements tell. Over-time recognition typically results in a smoother, more consistent revenue stream on your income statement. This is common for SaaS businesses, long-term construction projects, and ongoing consulting services. It can make performance look more stable to investors and lenders.
In contrast, point-in-time recognition can create a "lumpy" revenue pattern. You might see large revenue spikes when big orders ship or projects are finalized, followed by quieter periods. This is standard for retailers or companies that complete one-off projects. ASC 606 requires careful judgment to pinpoint when control transfers, and this decision has a real impact on your reported earnings. Getting it right is crucial for giving stakeholders a true picture of your company's health, which is why many businesses explore our insights on the HubiFi blog to stay informed.
Putting ASC 606 into practice can feel like a major project, but breaking it down into clear steps makes it entirely manageable. The standard requires more judgment from management than older revenue rules, so having a solid framework is key. Think of it as building a strong foundation for your revenue reporting—one that can stand up to scrutiny during an audit and provide valuable business insights.
These steps will guide you through the core requirements and help you address the challenges that often come up along the way.
First, you need to pinpoint every distinct promise you’ve made to your customer in a contract. These promises are called "performance obligations." Essentially, you should record revenue when you deliver the promised goods or services. For a simple sale, this is easy—the performance obligation is the product itself. But for bundled offerings, it gets more complex. A contract for a new software system might include the license, implementation services, and a year of customer support. Each of these could be a separate performance obligation because the customer can benefit from them individually. Getting this step right is crucial, as it sets the stage for all subsequent revenue recognition.
Next, figure out the total price of the contract. This is the amount of money you expect to receive in exchange for fulfilling your promises. It sounds straightforward, but you have to account for any variables that could change the final amount. This "variable consideration" includes things like discounts, rebates, credits, or performance bonuses. You'll need to estimate these amounts based on your company's past experiences or other relevant data. For businesses with high transaction volumes, tracking these variables manually can be a huge challenge, which is where automated solutions can make a significant difference by streamlining the process.
Once you have your total transaction price, you need to divide it among the different performance obligations you identified earlier. The rules state that you must allocate the price based on each obligation's standalone selling price—that is, what you would charge for that specific good or service if you sold it separately. If you don't have a standalone price for an item, you'll have to estimate it. This step ensures that you recognize the right amount of revenue as each distinct promise is fulfilled. Properly managing these allocations often requires robust systems that can handle complex data from various sources, which is why seamless integrations are so important.
Finally, you need to create clear internal processes and checks to manage your revenue recognition consistently. This means documenting how you determine when a performance obligation is met and how you handle contract modifications. Because ASC 606 requires significant judgment, strong internal controls are your best defense in an audit. They demonstrate that your decisions are thoughtful and consistent. Implementing automated systems is one of the most effective ways to establish these controls, as they provide a clear audit trail and reduce the risk of human error. If you want to see how automation can solidify your internal controls, you can schedule a demo to explore the possibilities.
Adopting ASC 606 isn't just a box-ticking exercise; it fundamentally changes how your company's financial story is told. The standard moves away from rigid, industry-specific rules to a more universal, principle-based framework. This means you'll likely see significant changes in how and when you report revenue, which directly impacts your income statement. Beyond just the numbers, ASC 606 also introduces a new level of transparency, requiring you to share more details about your contracts and revenue streams with investors and stakeholders.
The biggest change you'll see is in the timing of your revenue. Under ASC 606, revenue is recognized when you transfer control of a good or service to your customer. This can happen either at a single "point in time" or gradually "over time." This distinction is crucial because it can smooth out or create lumpiness in your reported income. For example, a software subscription that delivers value daily is recognized over time, while a one-off product sale is recognized at the point the customer takes possession. The key is to determine when your customer truly gains the ability to use and benefit from the asset.
ASC 606 also brings a much greater demand for transparency. You can't just report the final numbers; you have to explain the "how" and "why" behind them. This means providing detailed disclosures about your contracts, performance obligations, and the significant judgments you made. For instance, you'll need to document your reasoning for choosing point-in-time or over-time recognition. This requires robust internal processes and controls to ensure consistency and accuracy. If setting this up feels overwhelming, getting expert guidance can make all the difference. You can schedule a demo with us to see how automation can simplify these complex disclosure requirements.
Getting ASC 606 right, especially for over-time recognition, starts long before you open your accounting software. It begins with your customer contracts. These documents are the bedrock of your revenue recognition process, defining what you’ve promised, how you’ll deliver it, and when your customer gains control. Without a solid handle on your contracts, you’re essentially trying to build a house on a shaky foundation. Effective contract management isn't just a legal necessity; it's a core financial function that ensures you can report revenue accurately and confidently. By treating your contracts as the strategic assets they are, you set your finance team up for success and make compliance a much smoother process.
Your contract is the single source of truth for ASC 606. It’s where you define whether you'll transfer control of a good or service all at once or over a period of time. This decision is critical because it directly determines the timing of your revenue. Ambiguous terms about deliverables, acceptance criteria, or payment schedules can create significant compliance risks and reporting headaches down the line. It's essential for your team to carefully assess control and pinpoint the exact moment it transfers to the customer. Getting this right from the outset saves you from future disputes and difficult audit conversations.
Once your contract is clear, the next step is to meticulously track your progress against each performance obligation. ASC 606 states that you can recognize revenue over time if you meet at least one of three specific criteria, such as the customer receiving benefits as you perform the work. This means you need a reliable way to measure how much of the job is done. You must choose a single method—either input or output—for each obligation and apply it consistently. This is where many businesses struggle with manual spreadsheets. An automated revenue recognition platform can connect your project management and billing data to give you a real-time, accurate measure of progress, ensuring your financials always reflect reality.
Getting ASC 606 right isn't just about understanding the rules; it's about having the right framework in place to apply them consistently. This means combining powerful technology with a knowledgeable team. When your tools and your people are aligned, compliance becomes a seamless part of your operations instead of a recurring headache. Let’s look at the two pillars of a strong ASC 606 strategy: automation and education.
If you're still wrestling with spreadsheets to manage ASC 606, you know the struggle is real. Manual tracking is not only time-consuming but also opens the door to human error, inconsistent data, and a painful audit process. This is where automated solutions come in. They handle the heavy lifting of tracking performance obligations, allocating transaction prices, and recognizing revenue according to the five-step model. An automated system ensures that every contract modification is accounted for and that your financial data is always up-to-date. This gives you the confidence to close your books faster and provides the real-time analytics needed to make smart business decisions. The right platform should also seamlessly connect with your existing ERP and CRM.
Even the most sophisticated software can't replace a well-informed team. ASC 606 is not a simple checklist; it requires significant professional judgment, especially when determining when control of an asset transfers or how to treat variable consideration. Your team needs to understand the principles behind the rules to make these calls correctly. This education shouldn't be limited to your accounting department. Your sales team, for instance, needs to understand how contract terms can impact revenue recognition down the line. Fostering this understanding across departments creates alignment and reduces compliance risks. You can find more insights on our blog, but establishing clear internal policies and regular training sessions is a critical step for any business navigating this standard.
Adopting ASC 606 isn't a "set it and forget it" task. Because it relies heavily on judgment, staying compliant means treating it as an ongoing part of your financial operations. The contracts you sign and the way you deliver services can change, and your revenue recognition methods need to keep pace. Building a solid framework from the start will make this much easier. By creating clear internal systems and knowing when to ask for help, you can handle the standard's complexities with confidence and keep your financial reporting accurate and audit-ready.
Since ASC 606 requires more management judgment, especially when determining when a customer gains control of an asset, your team needs a clear playbook. It’s essential to establish and document your internal processes for assessing contracts and performance obligations. Think of it as creating a consistent measuring stick that everyone on your team can use. This ensures that even when judgment calls are needed, they’re made consistently and in line with the standard. Regularly reviewing these processes helps you adapt to new contract types and ensures your reporting stays accurate as your business grows. You can find more helpful articles on our blog to guide your financial operations.
Let's be honest: ASC 606 can be complicated. If you're still managing revenue recognition on spreadsheets, you're likely spending too much time on manual work and opening yourself up to costly errors. As your business scales, these manual methods simply can't keep up. Instead of trying to become a revenue recognition expert overnight, consider bringing in specialists or using an automated solution. This frees you up to focus on your business, knowing your compliance is handled correctly. If you’re ready to see how automation can simplify ASC 606, you can schedule a demo with our team to walk through your specific needs.
My business is still pretty small. Do I really need to worry about ASC 606? Yes, absolutely. The ASC 606 standard applies to all companies that have contracts with customers, regardless of size. While it might seem like a lot to handle when you're focused on growth, establishing good revenue recognition habits now will save you from major headaches later. Getting it right from the start ensures your financial statements are accurate, which is crucial for securing loans, attracting investors, and making sound business decisions.
What's the single biggest difference between the old revenue rules and ASC 606? The most significant change is the shift in focus from the "transfer of risks and rewards" to the "transfer of control." The old way could be a bit fuzzy, but the new standard asks a more direct question: When does your customer gain the ability to direct the use of and get all the benefits from the good or service? Pinpointing this moment of control transfer is now the central task of revenue recognition and requires more careful judgment from your team.
What if I can't figure out the standalone selling price for one part of a bundled service? This is a common hurdle. If you don't sell a particular service on its own, you won't have a direct standalone selling price to use for allocation. In this case, ASC 606 requires you to estimate it. You can do this using a few different methods, like assessing the market for similar services or calculating your expected cost plus a margin. The key is to choose a reasonable method, apply it consistently, and document your reasoning clearly.
Why is managing our contracts so important for ASC 606 compliance? Your customer contract is the foundation for your entire revenue recognition process. It's the document that defines your promises (performance obligations), the price, and the terms of delivery. Vague or unclear contract language can create serious confusion about when control transfers to the customer, leading to reporting errors and compliance issues. Treating contract management as a core financial function ensures your accounting team has the clear information it needs to apply the rules correctly.
Can't I just use spreadsheets to handle ASC 606 compliance? While it might be possible for a business with very few, very simple transactions, relying on spreadsheets is risky and doesn't scale. As your business grows, manual tracking becomes incredibly time-consuming and prone to human error. A single formula mistake or an unlinked cell can throw off your entire financial reporting. Automated solutions remove that risk by creating a reliable, single source of truth that ensures your data is accurate and your processes are audit-ready.
Former Root, EVP of Finance/Data at multiple FinTech startups
Jason Kyle Berwanger: An accomplished two-time entrepreneur, polyglot in finance, data & tech with 15 years of expertise. Builder, practitioner, leader—pioneering multiple ERP implementations and data solutions. Catalyst behind a 6% gross margin improvement with a sub-90-day IPO at Root insurance, powered by his vision & platform. Having held virtually every role from accountant to finance systems to finance exec, he brings a rare and noteworthy perspective in rethinking the finance tooling landscape.
Copyright © 2025 HubiFi | All rights reserved.
