Sign in
Get a Demo
Talk with an accountant.
Get clear, actionable steps for over time revenue recognition. Learn key ASC 606 criteria, common challenges, and best practices for accurate reporting.
How you recognize revenue tells a story about your company’s financial stability and operational efficiency. It’s more than just a compliance requirement; it’s a critical piece of information for investors, lenders, and your own leadership team. A financial story filled with unpredictable spikes and dips can make forecasting and strategic planning incredibly difficult. The over time revenue recognition method helps you tell a much clearer and more consistent story. By aligning your reported income with the actual work you perform, you create a predictable and transparent financial picture that builds trust and enables better decision-making. This guide explains how to implement this method correctly to strengthen your financial narrative.
Think of over time revenue recognition as a way to account for money earned from long-term projects or services. Instead of booking all the revenue at once when a contract is signed or when the final product is delivered, you recognize it in stages as you complete the work. This method paints a much more accurate picture of your company's financial performance, especially if your business involves lengthy contracts.
Under the ASC 606 standard, revenue is recognized over time if your work meets certain conditions. For example, if your customer continuously receives benefits while you perform a service—like with a monthly software subscription or a year-long consulting gig—you should recognize that revenue gradually. The same applies if your work creates or improves an asset that the customer controls as it's being built, such as constructing a new office building on land they own. This approach ensures your financial statements reflect the value you're delivering at each stage of the contract, not just at the beginning or end. It moves accounting from a simple transaction-based model to one that truly represents the ongoing transfer of value. For more details on accounting standards, you can find great articles with additional insights in the HubiFi blog.
The main difference between recognizing revenue "over time" versus at a "point in time" comes down to one key concept: the transfer of control. Under ASC 606, revenue is recognized when your customer gets control of the promised good or service. This means the customer can direct the use of the asset and receive most of its remaining benefits. This is a shift from older accounting rules that focused more on when the risks and rewards of ownership were transferred. For a simple transaction, like selling a laptop, control transfers at a single point in time—when the customer walks out of the store with it. But for a complex, multi-year service contract, control transfers gradually over the life of the agreement.
Choosing between over time and point-in-time recognition isn't just an accounting detail; it has a major impact on your business. Deciding when control of a good or service transfers to the customer is a significant change from older accounting rules. This choice directly affects how and when you report revenue, which can alter your financial statements from one period to the next. Getting it right is crucial for compliance, but it also influences key business metrics, investor perceptions, and even internal decisions like sales commissions. Accurate revenue recognition requires clean, connected data, which is why seamless integrations with HubiFi are so important for pulling information from your CRM, ERP, and other systems into one reliable source.
Deciding whether to recognize revenue over time or at a single point isn't a judgment call—it's a structured decision based on specific accounting standards. Under ASC 606, you can recognize revenue over time if your contract with a customer meets at least one of three criteria. Think of it as a checklist. If you can tick just one of these boxes, you're set to spread revenue recognition across the life of the contract.
This approach is designed to more accurately reflect how your business delivers value. For many companies, especially those in service, construction, or subscription-based industries, value isn't handed over in a single moment. It's a continuous process of fulfilling your promises to the customer. The ASC 606 framework ensures that your financial statements mirror this reality, providing a clearer picture of your company's performance as it happens. Understanding these three criteria is the first step to ensuring your revenue recognition practices are compliant and accurately represent your business operations. Let's walk through each one so you can confidently determine which applies to your contracts.
The core of over time revenue recognition rests on three distinct scenarios laid out by ASC 606. Your contract only needs to satisfy one of these to qualify. This isn't about finding the "best fit"; it's about identifying if any of them apply. The three ASC 606 criteria focus on how and when the customer receives the benefit of your work. They ask you to look at whether the customer is getting value as you perform, if you're enhancing an asset they already control, or if you're creating something unique for them that you couldn't sell to anyone else.
This first criterion is perhaps the most straightforward. It applies when your customer simultaneously receives and consumes the benefits of your work as you perform it. Think of services like a monthly cleaning contract, a SaaS subscription, or a consulting engagement. The customer gets the value—a clean office, access to software, or expert advice—continuously throughout the contract period. A great litmus test is to ask: If you stopped partway through, could another company step in and finish the job without having to substantially redo the work you've already completed? If the answer is yes, your customer has been receiving value all along.
The second criterion comes into play when your work creates or enhances an asset that the customer controls as the asset is being created or enhanced. The key word here is "control." The customer must have control over the work-in-progress, not just the final product. The most common example is construction. If you're hired to build an extension on a client's existing warehouse, they control the warehouse (the asset) throughout the entire project. As you build, you are enhancing an asset they already control, so you would recognize the revenue over the course of the construction project.
This final criterion is a two-parter, and you must meet both conditions. First, the asset you're creating must have no alternative use to you. This means the product or service is so customized for the customer that you couldn't easily turn around and sell it to someone else without significant rework or a major loss. Think of manufacturing a highly specialized piece of machinery for a client's unique production line. Second, you must have an enforceable right to payment for the work you've completed to date, even if the customer cancels the contract. If both of these conditions are met, you can recognize revenue over time.
So, you’ve confirmed that your contract qualifies for over time revenue recognition. The next logical question is: how exactly do you measure your progress? This isn’t about guesswork; it’s a critical step to ensure your financial statements accurately show the value you’re delivering to your customer as it happens.
Under ASC 606, you have two primary approaches for this: input methods and output methods. Think of it as measuring the effort you put in versus the results the customer gets. The right choice depends on which method best reflects how you transfer control of the goods or services to your customer. Choosing the right one and applying it consistently is fundamental to staying compliant and maintaining clear, reliable financials. Let’s break down what each of these methods looks like so you can decide which approach fits your business.
Input methods measure progress based on the resources and effort you’ve put into fulfilling a performance obligation. Essentially, you’re looking at your "inputs" to determine how much of the job is done. Common examples include costs incurred, labor hours worked, machine hours used, or materials consumed. This approach is most effective when there’s a direct correlation between the effort you expend and the value the customer receives. For instance, if you’re a consultant billing for a long-term project, tracking labor hours is a very logical way to measure the service delivered over the contract term. You can find more insights on managing financial operations like this on our blog.
In contrast, output methods measure progress based on the value transferred to the customer. Instead of focusing on your effort, this approach looks at the tangible results or "outputs." This could mean tracking units produced or delivered, celebrating project milestones, or using appraisals to survey the work completed. Output methods are a great fit when the deliverables are distinct and easily quantifiable. For example, if you’re building a custom software application in three phases, recognizing revenue as each milestone is approved by the client is a clear way to follow ASC 606 guidelines and track progress.
Here’s the most important rule: be consistent. Once you select a method for a specific performance obligation, you need to apply it consistently throughout the contract. You can’t use an input method one quarter and switch to an output method the next simply because it yields a more favorable result. The goal is to choose the single method that most faithfully depicts the transfer of value to your customer and stick with it. This decision should be documented as part of your accounting policy and applied uniformly to similar contracts. Getting this right is key to accurate reporting, which is why many businesses use automated systems to enforce these rules. If you're curious how that works, you can schedule a demo with our team.
While the principles of over time revenue recognition can apply to any business, some industries rely on this model more than others due to the nature of their contracts and deliverables. If your business operates in one of these sectors, understanding the nuances of ASC 606 is not just good practice—it's essential for accurate financial reporting and compliance. These industries often involve long-term projects, continuous services, or custom-built assets where value is clearly transferred to the customer over the duration of the contract, not just at the final handover. Let's look at a few key examples to see how this plays out in the real world.
Construction is the classic example of over time revenue recognition. When a company builds an office building or a bridge, the customer gains control of the asset as it's being created on their land. It wouldn't make sense to wait until the entire project is finished to recognize the revenue. Instead, construction companies typically use the percentage-of-completion method. They calculate revenue based on the costs incurred to date versus the total estimated project costs. This approach provides a more accurate picture of the company's financial performance throughout the life of a long-term project, reflecting the value being delivered incrementally.
If you run a subscription-based business, like a SaaS company or a managed IT service, you're delivering value to your customers continuously. A customer paying a monthly fee for software access receives the benefit of that service every single day of the month. Therefore, you should recognize that revenue over the subscription period. The same logic applies to long-term consulting gigs, annual maintenance agreements, or any contract where services are performed and consumed simultaneously over an extended period. This model is central to the modern service economy and a key focus of ASC 606 compliance.
Developing custom software or executing a complex IT implementation for a specific client often falls under the over time model. Because the work is highly specialized for one customer, the resulting asset has no alternative use for your business. As you build and implement the solution, the customer is typically involved in the process and controls the asset as it develops. The shift to a principles-based framework under ASC 606 requires tech companies to carefully identify performance obligations and track progress. Managing this requires systems that can handle complex data, which is why seamless data integrations are so critical for accurate reporting.
Think about a company that manufactures a highly specialized piece of machinery for a factory or a custom-designed component for an aerospace company. If the product is built to unique specifications and the contract ensures the manufacturer has the right to payment for work completed, revenue is recognized over time. This is because the asset being created has no real value to any other customer, and the value is transferred as it's being built. This method requires detailed tracking of project costs and progress, demanding a robust accounting process to ensure financial statements are presented fairly and accurately.
Applying the over time revenue recognition model seems straightforward in theory, but putting it into practice can feel like assembling furniture with vague instructions. You know what the end result should be, but the steps to get there are filled with potential pitfalls. The shift to the principles-based framework of ASC 606 means you have to use more judgment, which can create complexity and risk if not handled carefully. Getting it right requires a solid understanding of your contracts, clear internal processes, and systems that can keep up.
Many businesses stumble when trying to apply this model. The most common hurdles aren't just about accounting rules; they're about how your entire business operates. From how you structure your contracts to the software you use, every piece plays a role. We're going to walk through the four biggest challenges you're likely to face: identifying your specific promises to customers, dealing with fluctuating prices, deciphering complex agreements, and making sure your data is accurate and accessible. Tackling these head-on will help you build a reliable and audit-proof revenue recognition process.
A performance obligation is essentially a promise you make to a customer in a contract. The challenge is that one contract can contain several distinct promises. Under ASC 606, you have to identify each one so you can recognize revenue as it’s fulfilled. For a business offering a software subscription bundled with implementation services and ongoing support, are you delivering one continuous service or three separate ones? The answer determines how and when you recognize the revenue for each part. This requires careful judgment, as the standard focuses on principles rather than rigid rules, making it a tricky area for many companies, especially in the tech and service industries.
Variable consideration is any part of a transaction price that can change, such as discounts, rebates, credits, or performance bonuses. If your contract includes these elements, you have to estimate the total amount you expect to receive. The tricky part is that ASC 606 requires you to only recognize this revenue if it’s "probable that a significant reversal" won't happen later. This creates a delicate balance. You need to make a reasonable estimate based on historical data and future expectations without overstating your revenue. For businesses with usage-based pricing or long-term projects with incentive payments, this forecasting can be a major headache.
Your customer contracts are the source of truth for revenue recognition, but they are often far from simple. Modern agreements can be layered with custom terms, non-standard clauses, and modifications that change the scope or price midway through the project. Each detail can impact how you recognize revenue. For example, a termination for convenience clause might affect whether an asset has an alternative use. A deep, consistent understanding of your contracts across your sales, legal, and finance teams is critical. Without it, you risk misinterpreting your obligations and recognizing revenue incorrectly, creating compliance issues down the road.
Accurate over time recognition depends on having good data, and that data often lives in different systems. Your CRM holds the contract details, your billing platform tracks payments, and your project management software measures progress. Manually pulling information from these disconnected sources is time-consuming and prone to human error. To measure progress accurately, you need a seamless flow of information. This is why having strong system integrations is so important. When your tools can talk to each other, you can automate data collection and calculations, ensuring your revenue figures are timely, accurate, and always ready for an audit.
Choosing to recognize revenue over time isn't just a box-ticking exercise for your accounting team; it’s a strategic decision that fundamentally shapes your company's financial narrative. This method directly influences how investors, lenders, and internal stakeholders perceive your performance and stability. For businesses with long-term contracts or subscription models, it provides a much more accurate, real-time reflection of how you deliver value to your customers. Getting it right is about more than just compliance—it’s about creating a clear and consistent financial picture that you can use for strategic planning and forecasting. This approach touches every major financial statement, so understanding its specific effects is crucial for maintaining accurate records, passing audits with confidence, and making the best possible decisions for your business's future.
When you recognize revenue over time, you’re essentially smoothing out your income. Instead of showing large revenue spikes only when a project is completed, you report it steadily as the work progresses. This gives a more stable and realistic view of your company's performance. Under ASC 606, you also have to account for variable consideration—things like performance bonuses, incentives, or discounts. You'll need to estimate this amount and include it in the transaction price, but only if it's probable that you won't have to reverse that revenue later. This approach provides a more predictable income stream on your statement, which stakeholders love to see.
Adopting over time recognition introduces a few key accounts to your balance sheet. You’ll start seeing terms like "contract assets" and "contract liabilities." A contract asset represents the value of performance you've completed but don't have an unconditional right to bill for yet. Think of it as earned but unbilled revenue. On the flip side, a contract liability is for payments you've received from a customer before you've completed the work—essentially, deferred revenue. These classifications are important because they directly affect your liquidity ratios and the overall assessment of your company's financial position and health.
It’s crucial to remember that revenue recognition and cash flow are two different things. Recognizing revenue over time often means your income statement shows revenue before the cash actually hits your bank account. This can create a mismatch between your reported profitability and your actual cash on hand. While your income statement might look healthy and stable, your cash flow statement tells the real story of your company's ability to generate and use cash. Stakeholders will look closely at both to understand your operational efficiency and true financial stability, so it's important to manage both effectively.
Transparency is a cornerstone of ASC 606. The standard requires you to provide detailed disclosures in your financial statements so that anyone reading them can understand the nature, amount, timing, and uncertainty of your revenue. This means clearly explaining your contracts with customers and the significant judgments you made in your accounting. While it might seem like extra work, these disclosures build trust with investors and lenders. They offer a clear window into your financial performance and the risks associated with your revenue streams, which is something our automated solutions are designed to simplify.
Adopting over time revenue recognition is more than a box-ticking exercise for compliance; it’s about building a reliable system that supports your company’s growth. Getting it right from the start prevents major headaches, like financial restatements or audit failures. A smooth implementation hinges on a few core principles: creating strong internal processes, getting every team on the same page, defining your policies clearly, and using the right tools for the job. By focusing on these four areas, you can create a revenue recognition framework that is accurate, auditable, and scalable. It’s about turning a complex accounting standard into a straightforward, repeatable part of your financial operations. This proactive approach not only ensures compliance but also gives you clearer visibility into your company’s financial health, allowing you to make better strategic decisions. It transforms a regulatory requirement into a strategic asset that provides a true picture of your performance over time, which is invaluable for forecasting, budgeting, and communicating with investors. Ultimately, a well-executed implementation builds trust with stakeholders and sets a solid foundation for sustainable financial management as your business scales.
Think of internal controls as the guardrails for your revenue recognition process. They are the checks and balances that ensure your data is accurate and your process is sound. For your accounting team, strong controls provide confidence that the numbers coming out of your system are correct and haven't been arbitrarily changed. This involves documenting everything, from how you identify performance obligations to how you measure progress. It also means establishing clear change management protocols. Who has the authority to adjust revenue schedules? How are those changes tracked and approved? Having these rules in place is critical for passing audits and maintaining the integrity of your financial reporting.
Revenue recognition isn't just an accounting issue—it’s a business-wide function. The terms your sales team negotiates, the language your legal team puts in contracts, and the way your product team defines deliverables all have a direct impact on how and when you can recognize revenue. That’s why it’s essential to train these cross-functional teams on the basics of ASC 606. When your sales team understands how contract terms affect revenue, they can structure deals that are both customer-friendly and compliant. When everyone speaks the same language, you can avoid last-minute surprises and ensure the entire customer lifecycle, from sale to delivery, aligns with your revenue recognition policies. You can find more helpful articles on our HubiFi blog.
Consistency is key when it comes to ASC 606. You need a clear, documented playbook for how your team identifies performance obligations and handles things like variable consideration—such as bonuses, refunds, or other incentives. ASC 606 requires you to estimate this variable income, but only to the extent that a significant reversal is not probable later on. Creating firm policies removes the guesswork. Your team should have a go-to guide for interpreting different contract types and applying the rules consistently every time. This ensures that your revenue is recognized accurately and defensibly, no matter who is managing the contract.
As your business grows, managing over time revenue recognition on spreadsheets becomes unsustainable. It’s not just inefficient; it’s a huge risk for manual errors. Investing in an automated revenue recognition system early on is one of the best things you can do for scalability and accuracy. The right technology can automate complex calculations, manage revenue schedules, and provide real-time financial data. It also ensures that your methods are applied consistently across all contracts. By connecting with your other business systems, a dedicated platform can pull the necessary data automatically, giving you a complete and accurate picture of your revenue. Explore how HubiFi integrations can streamline this process for your business.
Getting over time revenue recognition right is a game-changer for financial accuracy, but a few common slip-ups can cause major headaches. Knowing what to watch for is the first step in keeping your books clean and your audits smooth. Let’s walk through the most frequent mistakes so you can steer clear of them.
It’s easy to assume that certain services, like implementation, automatically qualify for over time revenue recognition. However, this assumption can lead to significant reporting errors. You have to carefully check if your service meets at least one of the three specific criteria under ASC 606. Forgetting to do this due diligence is one of the quickest ways to misstate your revenue. Take the time to analyze each contract against the criteria to ensure you’re applying the standard correctly from the start. This rigor prevents having to make painful corrections down the line.
Determining the Standalone Selling Price (SSP) for different performance obligations can be tricky, and it’s an area where inconsistencies often appear. If your team uses different methods to calculate SSP or allocate revenue across contracts, you’ll end up with reporting discrepancies. It’s essential to establish a clear, consistent methodology and apply it uniformly. Having a solid framework ensures your financial statements are comparable and reliable over time. This is where automated revenue recognition tools can be a lifesaver, enforcing consistency across the board.
ASC 606 is all about consistency and transparency. If you can’t show an auditor why you made certain decisions, you’re going to have a problem. Inadequate documentation is a huge red flag during audits and can undermine the credibility of your financial reporting. Be sure to document everything: your contract analysis, how you identified performance obligations, your SSP calculations, and the method you chose for measuring progress. This paper trail is your best defense and proves you’ve made judgments in good faith and in line with compliance standards.
Contracts change. Customers add services, adjust scope, or change timelines. Each of these modifications can complicate revenue recognition. A common mistake is failing to properly account for these changes as they happen. When a contract is modified, you need to revisit the five-step revenue recognition process to see what’s impacted. Mishandling a modification can throw off your entire revenue schedule for that contract. For a deeper look at this, check out our guide to subscription business challenges under ASC 606.
Can I use different methods to measure progress for different types of contracts? Yes, you absolutely can. The rule is to be consistent for similar types of contracts. For example, you might use labor hours (an input method) for your long-term consulting projects but use project milestones (an output method) for your custom software development work. The goal is to pick the single method that most accurately shows how you transfer value to the customer for a specific service and then apply that same method to all similar contracts.
What happens if my customer cancels a long-term contract halfway through? This is precisely why having a well-structured contract is so important. If your agreement includes an enforceable right to payment for work you've already completed, you can recognize the revenue for that portion of the project. This clause ensures you are compensated for the value you've delivered, even if the customer decides to terminate the agreement before it's finished.
Why is it so important for my sales team to understand revenue recognition? Your sales team is on the front lines, structuring the deals that your finance team has to account for later. If they negotiate non-standard payment terms or bundle services in a way that creates multiple, complex performance obligations, it can cause major accounting challenges. When your sales team understands the basics, they can help structure contracts that are both appealing to the customer and compliant from the start, which saves everyone time and reduces risk.
My business is small. Does over time revenue recognition still apply to me? Yes, it does. The ASC 606 standard applies to all businesses—public, private, and non-profit—that have contracts with customers. While your contracts might be simpler than those of a large corporation, the principles for determining how and when to recognize revenue are the same. If you provide services over a period of time, you still need to evaluate your contracts against the three criteria to ensure you're reporting revenue correctly.
What’s the difference between a contract asset and accounts receivable? Think of it in terms of your right to get paid. A contract asset is revenue you've earned by doing the work, but you don't yet have an unconditional right to send an invoice for it. For instance, you've completed 25% of a project, but the contract states you can only bill at the 50% milestone. That earned 25% is a contract asset. Once you hit that milestone and send the invoice, it converts to accounts receivable because you now have an unconditional right to that cash.
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.
Meet with an expert in revenue recognition and order-to-cash accounting and automate revenue close.
*Or watch 2 minute demo here.
Power your high-volume business's revenue compliance and reporting needs with one platform.
