Under ASC 606, the difference between contract assets and accounts receivable comes down to one question: is the company’s right to be paid unconditional, or does something other than the passage of time still stand in the way? An account receivable is unconditional. The work is done, the customer has accepted it, and the only thing left is the payment date. A contract asset is conditional. Revenue has been earned and recorded, but the company cannot yet invoice because a milestone, an inspection, another deliverable, or some other contractual gate has not been cleared.
That single distinction drives balance sheet presentation, impairment analysis, how lenders value the asset, and, for many companies, when the revenue becomes taxable.
What Makes a Receivable Unconditional
ASC 606-10-45-4 defines a receivable as a right to consideration that is unconditional, meaning only the passage of time stands between the company and payment becoming due.1Financial Accounting Standards Board. Revenue from Contracts with Customers (Topic 606) Once the product has shipped, the service has been performed, and the customer has accepted delivery, the claim is locked in. The seller issues an invoice, and the only remaining variable is whether the customer pays on time.
Because performance risk has been eliminated, the balance behaves like a near-cash asset. Finance teams track it through aging schedules, and asset-based lenders will advance against it. If the customer refuses to pay, the company can pursue collection on strong legal footing because its own side of the bargain is complete.
What Makes a Contract Asset Conditional
ASC 606-10-45-3 requires a company to present a contract asset when it has transferred goods or services but its right to payment depends on something other than the passage of time.1Financial Accounting Standards Board. Revenue from Contracts with Customers (Topic 606) The company has done work, recognized revenue for that work, but cannot yet bill because the contract holds the invoice back until some further condition is satisfied.
Take a manufacturer building custom equipment under a contract that calls for payment only after final testing. As work progresses, the manufacturer recognizes revenue based on the percentage completed, but no invoice can go out until the equipment passes inspection. That recognized revenue sits on the balance sheet as a contract asset. If the project is cancelled before inspection, whether the manufacturer recovers the balance depends entirely on the termination provisions. Contracts with termination-for-convenience clauses typically require the customer to pay for completed work; without that language, the balance can be lost.
Embedded performance risk is what separates the two categories in the eyes of investors and lenders. A large or rising contract asset balance signals that a meaningful portion of recognized revenue still needs something to happen before it becomes an enforceable claim.
How a Contract Asset Becomes a Receivable
Reclassification happens when the condition blocking the right to invoice is satisfied. At that point, the right to payment becomes unconditional and the balance moves from one line to the other. The journal entry is simple: debit accounts receivable, credit contract asset. No new revenue is recognized, because the revenue was already booked when the work was performed.
The trigger varies with the contract. In a multi-deliverable arrangement where a manufacturer sells both equipment and installation, revenue recognized on the equipment might remain a contract asset until installation is complete, because the contract ties payment to both deliverables. When installation wraps and the customer accepts the full package, the balance shifts to receivables.
Getting the timing right matters. Moving balances into receivables before the conditions are truly met overstates the strength of current assets, and auditors focus heavily on the cutoff between the two categories at period-end. That is especially true for companies with long-duration contracts where billing milestones do not line up neatly with reporting dates.
Multiple Performance Obligations and Variable Pricing
When a contract contains multiple distinct performance obligations, each one has its own revenue trigger and its own potential to create a contract asset. A software company that licenses a product and provides implementation services might satisfy the license obligation on day one but recognize implementation revenue over several months. If the contract ties payment to completion of implementation, both the license revenue and the in-progress implementation revenue sit as contract assets until implementation is finished. Misidentifying the performance obligations or their billing triggers is where most misclassification errors start.
Variable pricing adds another layer. Performance bonuses, volume discounts, late-delivery penalties, and rebates all count as variable consideration. Under ASC 606, a company includes variable consideration in the transaction price only when it is probable that doing so will not lead to a significant reversal of cumulative revenue once the uncertainty resolves.1Financial Accounting Standards Board. Revenue from Contracts with Customers (Topic 606) The “probable” threshold generally means about 75 percent likelihood.
That constraint feeds directly into contract asset balances. If a construction company expects a $200,000 performance bonus but cannot yet conclude with sufficient confidence that the target will be met, it must exclude that amount from revenue and from the contract asset. As evidence accumulates, the company gradually includes it. The result is a contract asset balance that moves not only with work completed but also with management’s assessment of variable outcomes. Rising contract assets paired with heavy variable consideration disclosures can signal aggressive estimation.
Netting Against Contract Liabilities
p>Contract liabilities are the mirror image of contract assets. A contract liability arises when a customer pays before the company has performed the corresponding work.1Financial Accounting Standards Board. Revenue from Contracts with Customers (Topic 606) Older statements often call the same item “deferred revenue.” Either way, the obligation is to deliver goods or services, not to return cash.
The presentation rule that trips up many readers of financial statements: contract assets and contract liabilities from the same contract are netted into a single line at the contract level. A contract that produces a $50,000 contract asset and a $30,000 contract liability shows up as a net $20,000 contract asset. Netting applies even when the asset and liability relate to different performance obligations inside that contract, and when contracts are combined under ASC 606’s combination criteria, the netting applies to the combined contract as a whole. Companies cannot pick which pieces to net and which to show gross.
On the balance sheet itself, contract assets and accounts receivable must appear as separate line items. Balances expected to convert to cash within a year or the normal operating cycle sit in current assets; multi-year projects with deferred billing milestones can push contract assets into the non-current section.
Impairment Under CECL and the ASU 2025-05 Expedient
Both contract assets and accounts receivable fall under ASC 326, the Current Expected Credit Loss framework, which requires companies to estimate lifetime expected credit losses when the asset is first recorded rather than waiting for a loss event. For receivables the risk is straightforward credit risk. For contract assets, the analysis carries a second layer because the company must also finish its own performance before the billing right materializes. A customer’s deteriorating credit is a problem either way; an unfinished deliverable adds exposure that pure receivables do not carry.
ASU 2025-05, effective for annual reporting periods beginning after December 15, 2025, introduces a practical expedient for current accounts receivable and current contract assets arising from ASC 606 transactions.2Financial Accounting Standards Board. ASU 2025-05 Financial Instruments – Credit Losses (Topic 326) Under the expedient, a company may assume that current conditions at the balance sheet date will not change for the remaining life of the asset. Historical loss information still has to be adjusted to reflect current conditions, but the forward-looking economic forecasting that many preparers found burdensome relative to the short duration of these assets is no longer required.
Non-public companies get an additional option: they can elect an accounting policy that considers actual collections occurring after the balance sheet date but before the financial statements are issued. Under this election, the company first removes any receivable or contract asset balances that were actually collected after period-end, then applies the practical expedient to what remains.2Financial Accounting Standards Board. ASU 2025-05 Financial Instruments – Credit Losses (Topic 326) For smaller companies where a handful of large invoices can swing the allowance calculation, the change is significant. It eliminates the situation where a company records a credit loss allowance on a balance that has already been collected by the time the statements are finalized.
Tax Consequences Under IRC 451(b)
Classification as a contract asset versus a receivable also matters for tax. IRC Section 451(b) requires accrual-method taxpayers with an applicable financial statement to include an item of gross income no later than when that item is recognized as revenue in their financial statements.3Office of the Law Revision Counsel. 26 USC 451 – General Rule for Taxable Year of Inclusion In practice, the earlier of the traditional all-events test or the financial statement recognition date controls when income becomes taxable.
An applicable financial statement includes SEC filings like 10-Ks, audited statements used for credit or shareholder reporting, and statements filed with other federal agencies.3Office of the Law Revision Counsel. 26 USC 451 – General Rule for Taxable Year of Inclusion For companies that have one, ASC 606’s accelerated revenue recognition patterns flow straight through to taxable income. Revenue sitting as a contract asset under a percentage-of-completion approach can be taxable even though no invoice has been issued and no cash has been received.
The IRS does allow a reduction to the recognized amount for consideration the taxpayer would not have an enforceable right to recover if the customer terminated the contract on the last day of the tax year.4Internal Revenue Service. Accounting Periods and Methods (Publication 538) That softens the blow for contract assets tied to cancellable arrangements, but it requires a contract-by-contract analysis. Special methods, including the completed-contract method for certain long-term contracts under IRC Sections 453 through 460, are carved out of the 451(b) conformity rule, so companies eligible for them can continue deferring taxable income even when their GAAP financials show earlier recognition.3Office of the Law Revision Counsel. 26 USC 451 – General Rule for Taxable Year of Inclusion Companies with large contract asset balances and no matching cash inflow need to plan for the working capital hit of paying tax on revenue they have not yet billed.