The right to invoice practical expedient, codified at ASC 606-10-55-18, lets a company recognize revenue equal to the amount it has the right to bill a customer, provided that amount corresponds directly to the value the customer has received so far.1Financial Accounting Standards Board. Revenue from Contracts with Customers It applies only to performance obligations satisfied over time, and it works as a shortcut around the transaction-price, allocation, and progress-measurement steps of ASC 606’s five-step model. If your billing pattern already tracks the value you’re delivering, the standard lets you skip the more elaborate math that would produce the same answer.
The Direct Correspondence Test
The codification imposes a single criterion: the entity must have a right to consideration in an amount that “corresponds directly with the value to the customer of the entity’s performance completed to date.”1Financial Accounting Standards Board. Revenue from Contracts with Customers The standard’s own example is a service contract that bills a fixed amount for each hour of service provided. Each invoice maps precisely to the value delivered during that billing period, so no separate progress measurement is needed.
Direct correspondence takes judgment. A negotiated payment schedule doesn’t automatically mean invoiced amounts reflect value transferred. Market prices or standalone selling prices of the delivered services can serve as evidence, but they’re not the only evidence available. The real question is whether the dollar amount on each invoice genuinely reflects what the customer got during that period, not simply what the contract requires the customer to pay at that point.
Certain features inside a contract can undermine the analysis. A large upfront payment or a back-end rebate may signal that period-by-period invoices don’t match period-by-period value. When those features exist, you need to weigh their size against the total arrangement before concluding that direct correspondence holds.
Contracts That Qualify
The strongest candidates are service contracts with fixed per-hour or per-unit billing. A consulting firm that bills $250 per hour and invoices monthly based on hours worked has invoices that, by definition, reflect the value delivered that month. Fixed monthly fees for ongoing services follow the same logic when the scope is essentially identical each month, such as a $10,000 managed-services contract billed ratably.
Usage-based contracts billed at a fixed rate per unit of consumption also commonly qualify. A cloud-hosting provider billing $0.05 per gigabyte of storage used, invoiced monthly against actual usage, has invoiced amounts that correspond directly to value received.
Contracts That Don’t Qualify
A substantial upfront payment followed by reduced periodic charges fails the test. If a customer pays $500,000 at signing for a five-year engagement and $2,000 per month afterward, the upfront payment doesn’t correspond to value delivered at inception, and direct correspondence breaks down.
Tiered or volume-discount pricing creates a similar problem. When the per-unit rate drops as consumption rises, the invoiced amount in any given period may not reflect the standalone value of the services delivered in that period. Contracts with heavy back-end payments tied to a final deliverable, while most of the work happens earlier, also fail the criterion.
One firm boundary: the expedient applies only to performance obligations satisfied over time. A contract to deliver a single piece of equipment on a specific date involves a point-in-time transfer and doesn’t qualify regardless of how the billing is structured.
What the Shortcut Actually Saves You
Without the expedient, an entity satisfying a performance obligation over time has to determine the total transaction price, allocate it across obligations using relative standalone selling prices, and apply a progress measure each reporting period. For a multi-year contract with variable fees, that means estimating total consideration at inception, re-estimating each period, and adjusting cumulative revenue accordingly.
With the expedient, revenue each period simply equals the amount the entity has a right to invoice. The entry debits Accounts Receivable and credits Revenue for the invoiced amount. No separate allocation, no cumulative catch-up adjustments, no need to estimate total contract value upfront. For entities with hundreds or thousands of similar service contracts, that’s where the real time savings accumulate.
FASB’s Transition Resource Group described the mechanism as a combined shortcut through Steps 3, 4, and 5: the entity doesn’t have to determine the transaction price separately, allocate it, or build a progress model.2Financial Accounting Standards Board. Practical Expedient for Measuring Progress toward Complete Satisfaction of a Performance Obligation It just recognizes revenue in the invoiced amount.
Interaction With Variable Consideration
Usage-based contracts often involve variable consideration because the total the entity will receive depends on the customer’s future consumption. Under the general model, the entity would estimate the variable amount and potentially constrain the estimate before allocating it. The right to invoice expedient can eliminate that exercise entirely for qualifying contracts, because revenue is recognized as usage occurs rather than by projecting total fees upfront.
When the expedient doesn’t apply, because of tiered pricing, minimum commitments, or other complications, the entity may still qualify for the variable consideration allocation exception under ASC 606-10-32-40. That exception permits variable amounts to be allocated entirely to a specific performance obligation, or to a distinct period within a series, when the variable payment relates specifically to the entity’s efforts in that period and the allocation is consistent with the standard’s allocation objective. For many software-as-a-service arrangements structured as a series of distinct services, one of these two simplifications is usually available.
Disclosure Relief
The expedient also lightens disclosure. ASC 606-10-50-14(b) provides that an entity using the right to invoice expedient doesn’t have to disclose the aggregate transaction price allocated to remaining performance obligations or the expected timing of that revenue recognition.2Financial Accounting Standards Board. Practical Expedient for Measuring Progress toward Complete Satisfaction of a Performance Obligation That “backlog” disclosure can be onerous for entities with large service-contract portfolios. If revenue tracks invoicing, the remaining-obligation schedule would add little insight anyway.
What you still owe: a statement in the summary of significant accounting policies that you’ve elected the expedient, along with a description of the types of contracts you apply it to.
Don’t Confuse It With the One-Year Financing Expedient
The right to invoice expedient is frequently mixed up with a separate practical expedient at ASC 606-10-32-18. That one addresses the significant financing component, meaning the requirement to adjust the transaction price for the time value of money when a substantial gap exists between performance and payment. Under ASC 606-10-32-18, an entity can skip the financing adjustment if it expects the gap between transferring goods or services and receiving payment to be one year or less.1Financial Accounting Standards Board. Revenue from Contracts with Customers
These are different tools for different problems. The one-year expedient at ASC 606-10-32-18 sits in Step 3 and governs whether to impute interest when payment timing doesn’t match delivery timing. The right to invoice expedient at ASC 606-10-55-18 governs how to measure progress and recognize revenue for over-time obligations. A contract might qualify for both, one, or neither, depending on its structure. Applying the wrong expedient to the wrong problem can lead to a material misstatement in revenue.