Revenue recognition decides when a sale shows up in your financial statements, and Accounting Standards Codification (ASC) Topic 606 changed the answer for private companies. The standard holds them to the same discipline public companies already work under.
ASC 606 sets out five steps for recognizing revenue. This guide covers what the standard requires, where private companies get stuck implementing it, and how the five steps play out on real contracts.
Size doesn’t exempt anyone. Whether you run a ten-person shop or a few hundred people, the contracts you sign determine when you are allowed to book the money.
What ASC 606 requires
What revenue recognition is
Revenue recognition is the accounting procedure that records expected payment for the goods and services a company provides. It puts sales transactions on the books at the right moment, and without that timing any read on an organization’s financial health is guesswork.
What changed under ASC 606
FASB issued ASC 606 in 2014, and private companies adopted it in 2019 or 2020. It replaced rules that let revenue be recorded on estimates without much regard for the cash actually received. Under the new standard you have to read the customer contract closely: what services are provided, over what period, and on what payment terms.
The parameters it sets in customer contracts
ASC 606 focuses on three aspects of a customer contract:
- Type of services provided: identifying what the customer is actually getting determines the performance obligations in the contract.
- Timing of services: the period over which revenue gets recognized, whether that is monthly, quarterly, or annually.
- Amount: the financial statements have to reflect the price of every performance obligation named in the contract.
Follow those and the accounting lines up with when goods or services are actually delivered, which gives a clear picture of a company’s performance rather than a hopeful one.
Implementing ASC 606 at a private company
The standard improves revenue reporting. It also lands hard on small finance teams, and the friction shows up in a few predictable places.
Growing out of a simple revenue cycle
A small business with a simple revenue cycle can track contracts, prices, and performance obligations without much trouble. Growth changes that. More products, longer contracts, and more variations on both mean the accounting gets harder, and the approach that worked at ten customers won’t hold at two hundred.
Finding the expertise
ASC 606 requires someone in-house who can read a complex standard and interpret contract language against it. Small companies often can’t afford to hire that person and don’t have the bandwidth to train one.
Contract reviews and repeatable process
Careful contract evaluation identifies performance obligations and allocates transaction prices. That takes accounting, legal, and sales teams talking to each other, and it has to happen the same way every time. A repeatable review process keeps revenue recognition consistent when the person who usually handles it is out.
Systems and data across periods
Most systems built before ASC 606 don’t collect what it needs: detailed history on past transactions, discounts, disputes, and customer fees. That data usually sits scattered across several operational tools with no clean integration between them. Finance teams need one place to segment and analyze transaction data, both to set the price accurately and to show compliance. Companies that make that investment tend to get better financial insight out of it, not just a checked box.
The five steps of ASC 606 revenue recognition
1. Identify the contract with a customer
Recognition starts at the contract. It can be written or oral, but it needs enforceable rights and obligations. Four criteria come into play:
- Commitment and rights: the agreement shows a commitment to perform and a right to receive consideration.
- Payment terms: the terms and conditions are agreed and identifiable.
- Collectability: there is a reasonable expectation of actually collecting the consideration.
- Commercial substance: the transaction is expected to change the entity’s future cash flows.
For a subscription business that means spelling out how often the customer receives the subscription, monthly or yearly, when they get billed for the subscription and any setup fee, and what they’ve committed to pay on what schedule. Some fees get recorded right away. Unearned revenue waits, and only gets recorded once the business has finished the work it owes.
2. Identify the performance obligations in the contract
Performance obligations are the specific promises in a contract to deliver goods or services. Where they are distinct from one another, they get accounted for separately.
A company offering a yearly software subscription, a one-time setup fee, and a charge for custom integration has three separate performance obligations, tracked independently.
Finding them takes accounting, legal, and sales in the same conversation, so everyone agrees on what is being delivered, what it costs, and when it arrives. A central financial data platform keeps that information in one place instead of across four inboxes.
3. Determine the transaction price
The transaction price is what the company expects to collect for the goods or services. Working it out means pulling together past transactions, discounts, disputes, and fees, all of which differ by customer. That data usually lives in operational systems that don’t talk to each other, which is exactly why a single home for transaction data matters so much here.
4. Allocate the transaction price to the performance obligations
With several obligations in one contract, the price has to be divided among them. FASB’s guidance covers estimating the standalone price of each obligation, distributing discounts across them, and handling changes to contract terms. The result is that each distinct obligation carries its own share of revenue.
5. Recognize revenue as each obligation is satisfied
Revenue lands when the company completes the work, and that can stretch across accounting periods. A one-year agreement recognizes revenue gradually over twelve months as the obligations are met.
Doing this at any scale takes both an understanding of your own transactions and a system that can carry the accounting. Financial data platforms and automation tools handle the mechanics, and they give finance better material for planning strategies as a side effect.
How the five steps look in practice
Example 1: a SaaS company
A SaaS company sells a subscription product with an annual fee. Under ASC 606 it has to identify what it promised in the contract: monthly revenue, access to the software, and ongoing customer support.
- Identify the contract: it exists once the customer agrees to pay the annual subscription and the company agrees to provide the software and support.
- Identify the performance obligations: two distinct ones, software access and ongoing customer support.
- Determine the transaction price: the annual subscription fee the customer agreed to.
- Allocate the transaction price: split between the two obligations based on their standalone selling prices.
- Recognize revenue: across the subscription period, as the company provides access and support.
Example 2: a construction company
A construction firm contracted to erect a commercial building is providing design, materials, and labor under one agreement.
- Identify the contract: it exists once both parties agree on the specifics of the project.
- Identify the performance obligations: design services, supplying materials, and executing the labor.
- Determine the transaction price: the total amount agreed for the contract.
- Allocate the transaction price: distributed across the obligations by their relative standalone selling prices.
- Recognize revenue: design revenue as the work is done, materials and labor revenue as those parts of the project are completed, so the books track the project’s actual progress.
Different industries, same five steps. What changes is how much contract detail and transaction data you have to marshal to get through them, which is where automation tools and finance platforms earn their keep.
What ASC 606 means for warranties
Warranties come with product sales, and ASC 606 has specific rules for the revenue attached to them. The nature of the warranty determines the treatment.
- Warranties as separate performance obligations: a warranty that gives the customer assurance beyond what the standard product or service already provides counts as its own performance obligation. Part of the transaction price gets allocated to it, and revenue is recognized accordingly.
- Standalone selling price: to allocate the price you need the warranty’s standalone value, either from observable standalone sales of similar warranties or from expected cost plus a margin.
- Recognition over the warranty period: revenue is recognized as the company meets its obligations under the warranty terms. Additional costs to fulfill it, such as repairs or replacements, can affect the timing and the amount.
- Effect on deferred revenue: a warranty period often runs past the initial sale, so companies must add this to their deferred revenue calculations and recognize revenue as the warranty service is delivered.
Getting these right keeps warranty revenue compliant, and companies often have to change their accounting systems to handle the requirements.
Practical expedients under ASC 606
ASC 606 allows practical expedients that relieve specific requirements and simplify implementation, which matters most for companies with limited resources. The common ones:
- Portfolio approach: apply the standard to groups of similar contracts with similar characteristics rather than one at a time, which simplifies both pricing and allocation.
- Sales taxes: exclude sales taxes from the transaction price where third parties collect them.
- Incremental costs of obtaining a contract: recognize certain incremental costs as an expense when incurred instead of capitalizing them.
- Costs of obtaining a contract with a customer: a practical expedient is available for accounting for certain costs incurred to win the contract.
Work out which ones apply to your situation and write down why you chose them. The documentation is what makes the choice defensible when someone asks about it two years later.
Recommended Reading