Sign in
Get a Demo
Talk with an accountant.
Learn how to identify performance obligations in 5 steps, with practical tips for breaking down contracts and ensuring accurate revenue recognition.
Think of your customer contracts as a collection of building blocks. Before you can construct an accurate financial report, you need to understand what each block represents. A performance obligation is a distinct promise—a single block—to deliver a good or service. Some contracts have one simple block, while others are complex structures with many interconnected pieces. The key is learning how to tell them apart. This process is the most important step in applying the ASC 606 framework. We’ll show you how to identify performance obligations by breaking down your contracts into their core components, ensuring you recognize revenue at the right time, for the right reasons.
Let's talk about one of the most important concepts in modern accounting: the performance obligation. It might sound like complex financial jargon, but at its core, it’s a straightforward idea that sits at the heart of how and when your business recognizes revenue. Think of it as the fundamental promise—or promises—you make to a customer within a single contract. Under accounting standards like ASC 606, you can't just recognize revenue whenever you send an invoice or receive a payment. Instead, you have to earn it by fulfilling your end of the bargain.
Identifying exactly what those promises are is the first and most critical step in getting your revenue recognition right. It forces you to break down your contracts into the specific goods or services you're delivering. This process ensures your financial statements accurately reflect the value you’ve provided at any given time, keeping you compliant and giving you a much clearer picture of your company's financial health. It’s the difference between just tracking cash and truly understanding your earnings.
So, what exactly is a performance obligation? Simply put, it's a promise in a contract to provide a distinct good or service to a customer. If you sell a software subscription that includes setup and training, you might have three separate promises: the software license, the installation service, and the training sessions. Each of these could be a performance obligation. The key here is the word "distinct," which means the customer can benefit from the good or service on its own or with other readily available resources. Getting this definition right is the foundation for correctly applying the five-step revenue recognition model.
Identifying performance obligations is more than just an accounting exercise; it directly controls the timing of your revenue. According to ASC 606, you recognize revenue when (or as) you satisfy a performance obligation by transferring the promised good or service to the customer. This is a major shift from older methods that were often based on billing dates or cash collection. For example, if a customer pays you upfront for a one-year service contract, you don't recognize all that cash as revenue on day one. Instead, you recognize it over the 12 months as you fulfill your promise to provide the service. This approach provides a more accurate and transparent view of your company's financial performance, which is why mastering automated revenue recognition is so valuable for growing businesses.
Getting a handle on performance obligations is more than an accounting exercise; it’s a cornerstone of your company's financial health. When you clearly define the promises you’ve made to your customers, you create a clear path for recognizing revenue correctly. This single step has a ripple effect across your business, influencing everything from stakeholder trust to your ability to forecast growth. Misinterpreting or overlooking a performance obligation can lead to significant reporting errors and compliance headaches down the road. Let’s break down exactly why this process is so important.
Your financial reports tell your business's story, and you want it to be accurate. Correctly identifying performance obligations helps you show when you've delivered on a promise and earned the revenue. If you get this wrong, you might recognize revenue at the wrong time, creating a misleading picture of your company’s performance. This can confuse investors, worry lenders, and lead your own team to make decisions based on faulty data. Solid financial reporting builds trust and gives you a reliable view of your business, which is essential for sustainable growth. For more on building a strong financial foundation, you can find helpful Insights on our blog.
Think of ASC 606 as the official rulebook for recognizing revenue from customer contracts. It was created to make reporting more consistent and transparent across all industries. Following these guidelines isn’t optional, and a key piece is correctly identifying your performance obligations. This is step two of the five-step model for a reason—everything else builds on it. Failing to adhere to ASC 606 can result in non-compliance, which could trigger audits and damage your company’s reputation. Staying compliant protects your business and demonstrates financial integrity. At HubiFi, we specialize in helping businesses meet these standards with confidence.
When do you actually get to count your money? The answer depends entirely on your performance obligations. Each distinct promise in a contract must be identified so you can recognize revenue as you fulfill it. This process is sometimes called "unbundling." For example, if you sell a product that includes installation and a year of support, you likely have three separate promises. Recognizing all the revenue upfront would be incorrect. You have to allocate a portion of the contract price to each promise and recognize it as it’s delivered. Getting the timing right is critical for accurate forecasting and managing cash flow. If this sounds complex, you can always schedule a demo to see how automation can simplify the process.
Under ASC 606, not every item listed in a contract is a separate performance obligation. To qualify, a promise to deliver a good or service must be "distinct." Think of this as the official test to determine whether you should account for something separately or bundle it with other items. It’s a crucial step because it directly impacts how and when you recognize revenue.
So, what makes a promise distinct? It’s not just about whether you can physically separate one item from another. Instead, the guidance gives us a two-part test. A good or service is only considered distinct if it passes both of these tests. If it fails even one, you’ll need to combine it with other promises in the contract until you’ve created a bundle that does pass. Let’s walk through exactly what to look for in each test.
First, ask yourself if the customer can benefit from the good or service on its own or with other resources they can readily access. This is the "standalone value" test. Essentially, can the customer use, consume, or sell the item for an economic benefit without needing anything else from you in that same contract?
For example, if you sell a laptop, the customer can immediately benefit from it. If you also sell an optional one-year technical support package, they can benefit from that, too, using the laptop they just bought. The key is that the item doesn't depend on another undelivered item in the same contract to be useful. This is a fundamental part of identifying performance obligations correctly.
Next, you need to determine if your promise to transfer the good or service is distinct within the context of the contract. This test is about intent. Are you delivering individual items that happen to be in the same order, or are you delivering a single, combined solution where each item is just an input?
Imagine you’re hired to build a custom website. You might promise to deliver design, coding, and content. While each of these could have value on its own, in the context of the contract, they are highly integrated inputs to one combined output: the finished website. Your promise isn't to deliver code; it's to deliver a functional site. Therefore, these promises aren't separately identifiable and would be bundled into one performance obligation.
If a good or service fails either of the two tests, it’s not a distinct performance obligation. When this happens, you must combine it with other promises in the contract. You continue bundling goods or services together until you create a package that satisfies both criteria. In some cases, this might mean that everything in the contract merges into a single performance obligation.
This bundling process is essential for accurate financial reporting, but it can get complicated, especially for businesses with high-volume or complex contracts. Keeping track of these combined obligations requires clear data and reliable systems. Automating your revenue recognition can help ensure you’re grouping promises correctly and recognizing revenue at the right time for each distinct bundle.
Once you have a contract in hand, it’s time to look closely at what you’ve actually promised to deliver. This isn’t about making assumptions; it’s a methodical process of breaking down the agreement into individual goods and services. Think of it as creating a detailed checklist of your commitments. This assessment is the foundation for recognizing revenue correctly, as it forces you to see the contract from both your perspective and your customer’s. Getting this right ensures your financial reporting is accurate and reflects the true value exchange.
Your first move is to simply read the contract and list every single good or service you’ve promised to the customer. As accounting guidance from Deloitte puts it, "When a company starts a contract, it needs to look at all the goods and services it promised." This list becomes your roadmap. Each item on it must then be evaluated to see if it qualifies as a distinct performance obligation. This systematic review is a core part of maintaining ASC 606 compliance and prevents you from lumping together deliverables that should be accounted for separately.
Next, for each promised item, ask yourself: can the customer benefit from this on its own? A good or service is considered "distinct" only if the customer can use it independently or with other resources they can easily get. For example, a subscription to a software platform provides clear value by itself. However, a one-time fee for customizing that software for the customer’s specific workflow might not have standalone value; its benefit is entirely dependent on the software subscription. This step is all about looking at each promise through your customer’s eyes to determine its standalone utility.
Finally, you need to consider if a promise is separately identifiable within the contract. The goal is to figure out if you’re delivering a series of individual items or one combined solution where each piece is just an input. For example, if you sell a piece of hardware and an installation service, are they two separate deliverables? Or is the installation essential to the hardware’s function, making them one single promise? If a good or service isn't distinct on its own, you must combine it with other promises until you identify a bundle that is. This ensures your revenue recognition aligns with the actual, combined value you’re providing.
Performance obligations aren't always a single, clear-cut item. They can be straightforward promises written in a contract, unstated expectations that are part of your business practice, or even a series of services delivered over time. Understanding these different types is key to getting your revenue recognition right. Think of it this way: a promise is a promise, whether it’s written in black and white or simply understood by your customer. You can find more foundational tips on our HubiFi blog. Let's break down the three main categories you'll encounter.
This is the most straightforward type of performance obligation. An explicit promise is one that’s clearly stated in your contract with a customer. It’s the "promise" a company makes to deliver goods or services in exchange for payment. Think of a signed agreement to deliver 100 widgets, a software license with specific features outlined, or a statement of work for a three-month consulting project. These promises are easy to identify because they are documented and agreed upon by both parties. They form the foundation of your contract and are the first things you should look for when analyzing an agreement.
Sometimes, a promise isn't written down but is still part of the deal. These are called implied promises, and they arise from your standard business practices or published policies. A customer might reasonably expect something from you even if it’s not in the contract. For example, if your company has a well-known policy of providing free technical support for the first 90 days, that support becomes an implied promise. The key here is the customer's reasonable expectation. If your past actions have created a valid expectation for a good or service, you have an implied performance obligation you need to account for.
What about ongoing services? A performance obligation can also be a series of distinct goods or services that are delivered over time. Think of a monthly subscription box, a yearly cleaning contract, or a SaaS plan that provides continuous access to a platform. According to the ASC 606 guidance, if these goods or services are substantially the same and have the same pattern of transfer to the customer, they can be treated as a single performance obligation. This simplifies accounting for recurring revenue models, allowing you to recognize revenue consistently over the subscription period instead of for each individual delivery.
Complex contracts with multiple deliverables can feel like a puzzle, but they become much more manageable when you have a system. Whether you’re dealing with software licenses, installation services, ongoing support, or physical goods, the key is to break the contract down into its individual components. This process isn't just an accounting exercise; it’s fundamental to understanding the value you’re delivering to your customers and when you’re delivering it. By systematically identifying, separating, and grouping your promises, you can confidently apply the revenue recognition model and ensure your financials accurately reflect your performance.
Before you can do anything else, you need to read the contract carefully and list every single thing you’ve promised to the customer. A performance obligation is simply a "promise" a company makes to a customer to deliver goods or services. This includes both explicit promises written in the contract and implicit ones based on your business practices or specific statements. Think of it as creating an inventory of your deliverables. Does the contract include a product, a setup service, technical support, and future updates? Each of these is a potential performance obligation and needs to be on your list before you move to the next step.
Once you have your list of promises, it’s time to determine which ones are distinct. According to accounting standards, a promise is distinct if the customer can benefit from the good or service on its own and if it's separately identifiable from other promises in the contract. For each item on your list, ask yourself: Could a customer use this product without the installation service? Is the technical support a separate service, or is it integral to the software itself? This step helps you unbundle your offerings into individual units for accounting, which is a core principle of accurate financial reporting. You can find more Insights in the HubiFi Blog to guide your financial operations.
What happens when a promise isn't distinct? You group it with other items until you have a bundle that is distinct. If a good or service doesn't meet the criteria, you must combine it with other promised goods or services until you find a group that works as a single unit. For example, if you sell highly specialized machinery that requires a mandatory, complex installation service from your team, the machinery and the installation service would likely be grouped into one performance obligation. The customer can’t benefit from the machine without your specific installation, making them inseparable. This bundle then becomes the single performance obligation you'll track for revenue recognition.
Even when you have the rules down, identifying performance obligations can feel like navigating a maze. A few common misunderstandings can easily lead you astray, causing headaches during audits and skewing your financial reports. Let's clear up some of the most frequent trip-ups so you can approach your contracts with confidence and precision. Getting these details right is key to accurate revenue recognition and building a solid financial foundation for your business.
The term "distinct" seems straightforward, but in the world of ASC 606, it has a very specific, two-part definition. For a good or service to be distinct, it must pass both tests. First, the customer must be able to benefit from it on its own or with other resources they can easily get. Think of a laptop—it’s useful right out of the box. Second, the promise to provide that item must be separately identifiable from other promises in the contract. This means it isn't highly dependent on or integrated with another item. Both conditions must be met for you to correctly identify performance obligations.
It’s easy to focus only on what’s written in black and white, but performance obligations aren't just about the explicit terms in a contract. You also have to account for implied promises. These are the things your customer reasonably expects based on your company’s past actions, marketing materials, or standard industry practices. For example, if you’ve always provided free installation with a piece of equipment, that service becomes an implied promise, even if you forget to include it in the latest contract. Overlooking these unwritten expectations is a common pitfall that can lead to non-compliance and misstated revenue.
This is where many businesses get tangled up. Sometimes, two items that look separate—like a software license and an installation service—are actually a single performance obligation. The deciding factor is often the level of integration or customization. If the software requires a significant, specialized installation from you to function as promised for the client, the two are intertwined. In this case, you must bundle the promises together until you have a single, distinct deliverable. The customer can't truly benefit from one without the other, so they become one unit for revenue recognition purposes.
Identifying performance obligations sounds straightforward in theory, but it can get tricky when you're dealing with real-world contracts. Even with clear guidelines, you’ll likely run into gray areas that require careful thought and solid judgment. Knowing what to look out for ahead of time can save you from headaches down the road. Let's walk through some of the most common hurdles you might encounter.
Not all contracts are simple. In the software industry, for example, figuring out revenue can be complicated because products are unique and the landscape is always changing, which means you'll often need to make careful judgment calls. A contract might include multiple services, vague language, or clauses that modify promises over time. You might find yourself debating whether a setup fee is a separate service or just part of the initial software access. These situations require you to interpret the contract from the customer’s perspective, which isn’t always black and white. Documenting your reasoning is key to staying consistent and prepared for an audit. For more guidance, you can find helpful insights in the HubiFi blog.
While ASC 606 aims to create a universal framework, its application can look different from one industry to the next. The core principles apply to nearly every type of deal, with a few specific exceptions like insurance contracts or leases. However, industries like telecommunications, construction, and software-as-a-service (SaaS) have their own common practices that create unique challenges. For instance, a construction contract might have performance obligations that are satisfied over time, while a SaaS contract could bundle implementation, support, and software access. Understanding these industry-specific nuances is essential for accurate ASC 606 compliance. You need to apply the five-step model within the context of how your industry actually operates.
The tech and software sectors are particularly challenging due to the sheer variety of products and pricing models. Because there are so many ways to structure a deal, identifying performance obligations can be very tricky. Even contracts that seem similar on the surface might require different accounting decisions. Think about all the elements that can be included: software licenses, implementation services, data migration, technical support, and promised updates or upgrades. You have to determine if each of these is a distinct promise or part of a single, combined solution. This complexity is why many businesses turn to automated solutions that can handle various integrations with their systems and apply revenue rules consistently.
Identifying performance obligations correctly isn't just about ticking a compliance box; it's about building a reliable foundation for your financial reporting. When you get this step right, you create clarity that ripples through your entire business, from sales to accounting. Adopting a few key practices can help you handle even the most complex contracts with confidence and precision. These habits ensure you’re not just compliant, but also making smarter, data-driven decisions. Let's walk through three essential practices that will help you stay on track and avoid common pitfalls.
Your customer contracts are the ultimate source of truth for identifying performance obligations. Make it a habit to review them meticulously, not just when they’re signed, but throughout the project lifecycle. The goal is to clearly determine when your customer truly gets control of the goods or services you’ve promised. This means you have to carefully judge if the promises in a contract are separate deliverables or part of a combined package. Documenting your analysis is just as important. It creates a clear audit trail and ensures that your reasoning is consistent and defensible if questions arise later. This process is foundational to accurate revenue recognition and provides a clear picture of your financial health.
Revenue recognition isn't just a job for the finance department. To get a complete picture, you need input from sales, legal, and operations. Your sales team understands the customer's expectations and any implied promises made during negotiations. Your legal team can interpret the contractual terms, and your operations team knows the practical details of delivering the goods or services. Bringing these perspectives together helps you avoid blind spots and ensures your assessment is grounded in reality. This collaborative approach is crucial for understanding the full context of a contract, especially in industries like software where deliverables can be complex and interconnected. When your systems can communicate through seamless integrations, it makes this cross-functional teamwork even easier.
Everyone involved in the contract lifecycle should have a basic understanding of the rules. Think of ASC 606 as the official playbook for how your company recognizes revenue from customer deals. It was created to make the rules clearer and more consistent across all industries. When your team is trained on these standards, they can spot potential issues early on and apply the principles correctly from the start. This training doesn't need to turn everyone into an accountant, but it should empower them to understand how their roles impact the company's financials. Consistent training ensures everyone is speaking the same language and working toward the same goal: accurate and compliant financial reporting.
Trying to manually track performance obligations across complex contracts can feel like a never-ending puzzle. It’s time-consuming, prone to human error, and can leave your finance team scrambling at the end of every month. This is where automation comes in. By using software to handle the heavy lifting, you can streamline the entire revenue recognition process, from identifying obligations to reporting your financials. It shifts your team's focus from tedious data entry to strategic analysis, giving you a clearer picture of your company's financial health without the late-night spreadsheet sessions.
Automating revenue recognition takes the guesswork and manual effort out of the equation. Instead of pulling data from different places, an automated system continuously syncs information from your ERP, CRM, and billing platforms. This eliminates delays and reduces the risk of errors that can happen with manual tracking. The result is a faster, more efficient close process. Your finance team gets real-time visibility into outstanding performance obligations and compliance metrics, allowing them to provide accurate, up-to-date revenue insights whenever they’re needed. This frees up your team to focus on more strategic work that drives the business forward.
Adopting a new tool shouldn't mean overhauling your entire workflow. The best automated revenue recognition software is designed to connect with the business tools you already use every day. Look for a solution that offers seamless integrations with your CRM, ERP, and accounting software. This creates a unified system where data flows automatically from one platform to another, automating the entire process from the initial data capture all the way to final reporting. This connected approach ensures that your revenue data is consistent and reliable across your entire organization, without creating extra work for your team.
With automation, you no longer have to wait until the end of the month or quarter to get a clear view of your revenue. Your team can see current and accurate revenue figures at any time, which is a game-changer for making informed business decisions. This real-time visibility is also essential for maintaining compliance with standards like ASC 606. An automated system makes it much easier to monitor your performance obligations and generate the reports needed to pass an audit with confidence. If you want to see how this works in practice, you can schedule a demo to explore the features firsthand.
What's the biggest mistake companies make when identifying performance obligations? The most common trip-up is focusing only on what's written in the contract and forgetting about implied promises. If your marketing materials, past actions, or even a salesperson's verbal commitment have created a reasonable expectation for your customer, that's a performance obligation you need to account for. Another frequent mistake is misinterpreting what "distinct" means; a good or service has to be useful on its own and be separately identifiable within the contract's context to be counted as a separate obligation.
My business offers a software subscription that includes setup and ongoing support. Is that one promise or three? This is a classic scenario, and the answer depends on the specifics of your contract. You need to apply the two-part "distinct" test. Can the customer benefit from the software on its own, without your specific setup? Is the support a standard offering, or is it highly integrated with the software's core function? If the setup is complex and essential for the software to work as promised, you would likely bundle the software and setup into a single performance obligation. If the support is a standard, optional service, it might be separate.
Do verbal promises made by my sales team count as performance obligations? Yes, they absolutely can. If a salesperson's promise creates a valid expectation for the customer that they will receive an additional good or service, it becomes an implied performance obligation. This is why it's so important for your sales and finance teams to be on the same page. Training your entire team on the basics of revenue recognition helps prevent these unwritten promises from creating compliance issues down the road.
What happens if a contract is modified after it's signed? Do the performance obligations change? Contract modifications require careful assessment because they can definitely change your performance obligations. Depending on the nature of the change, you might be adding new, distinct goods or services, or you might be altering an existing promise. Each modification needs to be evaluated to see how it impacts the original contract and how the revenue associated with it should be recognized going forward.
When should I consider automating this process instead of managing it with spreadsheets? A good time to consider automation is when the complexity starts to outpace your manual systems. If your finance team is spending days instead of hours on the month-end close, if you're constantly worried about errors, or if you can't get a clear, real-time view of your revenue without a major effort, it's a strong sign. Automation is designed to handle high-volume or complex contracts consistently, giving you accuracy and visibility that spreadsheets simply can't match.
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.
