A contract asset is revenue a company has already earned by delivering goods or services to a customer, but which it cannot yet invoice because the same contract requires it to finish additional work first. It sits on the balance sheet as its own line item, separate from accounts receivable, because the right to be paid is still conditional on the company’s own future performance rather than on the passage of time. Contract assets became a formal reporting category under ASC 606, the revenue recognition standard issued by the Financial Accounting Standards Board, and its international counterpart, IFRS 15.
When a Contract Asset Shows Up
Recognition happens at a specific moment: the company transfers control of a promised good or service, but the contract prevents it from billing until something else occurs beyond a calendar date. That “something else” is almost always another piece of work the company itself still has to complete.
The test is the nature of the condition attached to payment. If the company must hit a milestone, pass an inspection, or deliver a second component before it earns the right to invoice, the earned amount is a contract asset. If the only thing standing between the company and payment is a due date, the amount is a receivable. This distinction tells readers of the financial statements how much reported revenue is genuinely at the company’s mercy, still dependent on execution, versus how much is simply waiting in the mail.
Contract Asset vs. Accounts Receivable
Both represent money the company expects to collect, and both come from work already recognized as revenue. The difference is what has to happen next.
An account receivable is unconditional. The company has done everything it owes the customer, and the only remaining event is payment on the agreed date. A contract asset is conditional. The company has done part of what it owes, has recognized revenue for that part, but still has performance obligations left under the same agreement before it can send a bill.
Before ASC 606, many companies labeled any earned-but-unbilled amount an “unbilled receivable.” The standard draws a sharper line. Some companies still use the older term in their notes, but it should map to either a contract asset or a receivable depending on whether the right to payment is conditional or unconditional.
Contract Asset vs. Contract Liability
Contract assets and contract liabilities are mirror images. A contract asset appears when the company has delivered value ahead of billing. A contract liability, traditionally called deferred revenue, appears when the customer has paid or owes payment before the company delivers. A software company collecting an annual subscription fee upfront holds a contract liability that shrinks each month as it fulfills the service.
Under ASC 606, the two must be netted on a contract-by-contract basis. A single contract shows up on the balance sheet as either a net contract asset or a net contract liability, never both. If a company has delivered a $200,000 component under a contract (creating a contract asset) and also received a $150,000 advance for another component under that same contract (creating a contract liability), it reports a net $50,000 contract asset for that agreement.1FASB Staff Educational Paper. Topic 606 Presentation and Disclosure of Retainage for Construction Contractors
The netting rule stops at the contract line. A company can absolutely report contract assets from some agreements and contract liabilities from others on the same balance sheet. What it cannot do is show both sides for a single contract, which would inflate total assets and total liabilities and mislead lenders and analysts.1FASB Staff Educational Paper. Topic 606 Presentation and Disclosure of Retainage for Construction Contractors
Examples Across Industries
Large construction projects produce contract assets frequently. A builder finishes the foundation of a commercial building and the completed work has real value, but the contract may prohibit invoicing until the framing phase is also done. The value of the foundation work sits as a contract asset until the framing milestone triggers billing rights.
Bundled technology deals create the same pattern. A vendor ships specialized servers to a client on day one while the related software installation takes several more weeks. Revenue for the servers is recognized at delivery because the customer controls the hardware, but the contract bars invoicing until the software is fully functional. During the installation period, the server revenue is a contract asset.
Professional services firms hit this in phased engagements. An accounting firm running a two-part advisory project may complete the diagnostic phase and recognize its revenue, yet the contract states that billing occurs only after the implementation phase wraps up. The diagnostic revenue is a contract asset until that second phase is finished.
How and When It Converts to a Receivable
A contract asset turns into an account receivable the moment the right to payment becomes unconditional. The trigger is typically an event spelled out in the contract: the customer accepts the final deliverable, the project passes a milestone inspection, or the last piece of equipment is installed. Once that event occurs, the company removes the contract asset from its balance sheet and records a receivable in its place.
Retainage in Construction
Long-term construction contracts commonly withhold a percentage of each progress payment, called retainage, until the project is complete. Whether that balance belongs in the contract asset column or the receivable column depends on what condition is still attached.
If retainage is held back until the builder finishes a future phase or passes a final inspection, the amount stays as a contract asset because payment still depends on the company’s own performance. If the project is substantially complete and the only remaining condition is the passage of time before the holdback is released, retainage shifts to a receivable. Retainage balances often run five to ten percent of each progress billing, so classifying them as receivables too early overstates the company’s unconditional claims to cash and can mislead lenders about liquidity.
Presentation on the Balance Sheet
Contract assets appear as their own line, distinct from accounts receivable. That separation is the whole point of the category: it lets readers see how much of the company’s recognized revenue is still tied to future performance instead of blending it into the receivables pool.
On a classified balance sheet, contract assets are split between current and non-current. Balances expected to convert to a receivable within a year of the reporting date are current; balances tied to a multi-year project with a later billing trigger are non-current. The split is a judgment call based on the contract’s payment schedule and the expected timing of the remaining performance obligations.
Credit-Loss Testing
Contract assets are subject to the current expected credit loss (CECL) model under ASC 326. CECL requires companies to estimate losses over the full life of the asset, starting from the moment it lands on the balance sheet as a contract asset, running through its life as a receivable, and continuing until the cash is collected or the balance is written off. The estimate draws on historical loss experience with similar assets, current economic conditions, and reasonable forecasts.2Federal Reserve Board. Frequently Asked Questions on the New Accounting Standard on Financial Instruments Credit Losses
In practice, most companies apply the same credit-loss methodology to contract assets that they use for receivables. If a receivable from the same customer is already delinquent, that fact should feed into the loss estimate on any related contract asset. The size of the reserve varies widely by industry and by customer, so a contract asset owed by a well-capitalized government agency carries a much smaller allowance than one tied to a startup with no payment history.
The Tax Timing Problem
Recognizing a contract asset can pull tax liability forward. Section 451(b) of the Internal Revenue Code, added by the Tax Cuts and Jobs Act, requires accrual-method taxpayers to include an item in taxable income no later than the year they recognize it as revenue on their financial statements.3Office of the Law Revision Counsel. 26 U.S. Code 451 – General Rule for Taxable Year of Inclusion
For a contract with multiple performance obligations, the tax treatment tracks the allocation used in the financial statements. If forty percent of a contract’s total price is allocated to a first deliverable and recognized as revenue upon delivery, the IRS treats that forty percent as includable in gross income for that tax year, even though no invoice has gone out and no cash has arrived.3Office of the Law Revision Counsel. 26 U.S. Code 451 – General Rule for Taxable Year of Inclusion
The practical effect is a cash-flow squeeze. A business can owe taxes on revenue it has recognized but has not yet billed or collected. Companies carrying large contract asset balances — construction firms, defense contractors, and enterprise software vendors are the usual examples — need to forecast this timing mismatch and plan for it, because the tax bill will arrive on the financial-statement clock, not the invoicing clock.