TL;DR: Remaining performance obligations measure allocated transaction price for certain promised goods and services still to be transferred, within the issuer's disclosure scope. Forecast recognition from delivery and the maturity schedule. Estimate cash separately from invoices and collections, and compare companies only after aligning definitions and disclosure exclusions.
Two companies can report the same revenue and finish the year with different contracted work ahead. They can also report equally large remaining obligations while expecting radically different cash receipts. The reason is easy to see in a contract file and harder to reconstruct from a headline. A contract specifies a promised service, the timing of delivery, and how a customer pays. Those sequences have separate dates.
Consider two fictional companies selling support for industrial instruments, Rowan Systems and Tide Service. Their contracts and figures below are invented. Each uses a calendar year simply to keep the time arithmetic visible. The references establish the U.S. financial reporting concepts and illustrate how real companies describe their disclosure scope. Rowan's conclusions about accounting and cash apply only to the example assumptions.
The FASB guidance in Topic 606 addresses allocation of transaction price to remaining performance obligations and an explanation of when that price is expected to become revenue. Later amendments include disclosure exceptions in specified circumstances. A useful investor read starts with the issuer's current notes, including practical expedients, definitions and how it describes recognition timing. FASB revenue recognition amendments, Rockwell Automation annual filing.
Rowan's first calendar shows three rows
On January first Rowan starts a three-year fixed service contract at an assumed total transaction price of 360 monetary units. The contract has one service obligation fulfilled evenly over 36 months under the example's accounting assumptions. The customer pays 180 on delivery of the initial invoice at start, 90 at the beginning of year two, and 90 at the beginning of year three. All payments arrive as assumed for now.
At the first year end, 120 of revenue has been recognized and 240 of the consideration remains allocated to future performance. Cash received so far is 180. The example assumes payment and billing work as stated and no other contract asset adjustments. A contract liability of 60 represents consideration already received for services not yet delivered. The cash flowing in the next two years totals 180. The 240 of remaining expected revenue includes the 60 already collected and 180 yet to be collected under the assumed schedule.
The next calendar row begins with 90 of cash on the invoice date. Under the evenly fulfilled service, each year again delivers 120 of revenue. At year two end, revenue recognized to date totals 240, cumulative cash is 270, and the contract liability is 30. The remaining performance amount is 120 and the final cash payment is 90. A forecast that interprets the remaining amount as the cash due in the next year overstates the illustrated inflow by 30.
The last row contains the next 90 of cash, final service year revenue of 120, and a closing balance of zero for both measures. It is tempting to say the transaction price has fully turned into money only when the last service ends. In this model the final payment arrived at the start of the third year. A cash forecast and a revenue model can reconcile at termination and still diverge substantially in each intervening period.
The cash plan presumes that the invoices are paid as scheduled. Move the second collection by thirty days and the monthly cash path changes while service delivery might continue under the example terms. In a real company a missed payment can lead to a contract or collectibility reassessment, depending on the applicable facts and guidance. The analyst should state which scenario is modeled instead of changing performance recognition automatically whenever a customer pays late.
Ordinary terminology can hide these differences. A business statement may say bookings grew, invoices rose, backlog contracted or deferred revenue converted. Each can describe one piece of the contract sequence. The ability to put a figure in a specific calendar column is more useful than assuming every commercial term names an accounting balance.
Tide writes the same services with a different payment date
Tide sells the same 360 units of fixed three-year service under identical delivery assumptions. The customer pays all 360 at start. After one year, the remaining performance amount is again 240. Tide's remaining collections are zero under the assumption of full initial payment, while its contract liability is 240. The organization still owes the future work and will recognize revenue as it completes that work.
The contracts can now be compared in a way an issuer narrative rarely makes explicit. Rowan and Tide have identical future recognized revenue in this illustration. Rowan will receive more future cash because much of its consideration remains payable. Tide already holds more cash from the customer and needs to fulfill the service after collection. The time at which working capital is supported differs even if operating delivery is the same.
Add a third schedule. Tide's second customer pays 120 after each completed service year and the first payment has been invoiced but remains unpaid at year end. A receivable captures an unconditional right to the first payment under the example. That first performance has already been satisfied. The receivable may drive future cash even though it belongs outside the remaining performance amount. The collection model needs receivables as well as expected invoices for future activity.
Some deals let performance precede an unconditional right to consideration. A contract asset can record a right conditioned on something beyond the mere passage of time under the applicable framework. Imagine a multi-stage instrument project with meaningful performance recognized before reaching a milestone that triggers billing. Its contract asset and future performance disclosure answer different questions. Milestone details, payment rights and transfer patterns need separate reading in an actual filing.
The bundle might also contain more than one obligation. Suppose a company allocates 100 units to a delivered instrument and 200 to future service under its applicable policy. Delivery of the instrument can recognize its allocated 100 regardless of which payment arrives first. Remaining recognition belongs to the unsatisfied services. Assume cash terms of 210 up front and 90 later. The received amount is neither a universal measure of equipment price nor an independent estimate of service obligations. The allocation is an accounting conclusion defended by its own evidence.
The schedules tell the analyst which data cannot be recovered from an aggregate directly. A portfolio's 240 of remaining obligations could begin under equal annual service recognition, launch mostly on future dates, or arrive on delivery of defined physical units. The note's timing disclosure can narrow those alternatives. A comparison of cash flow uses payment and collection evidence wherever the issuer makes it available. When evidence is limited, ranges and labelled assumptions are better than an apparently exact payment calendar.
What belongs in a disclosed remaining obligation
A salesperson can report a renewal offer as part of a pipeline before the customer accepts it. An existing accounting contract and transfer obligation have tests of their own. A company can also use commercial backlog to include purchase commitments that it tracks differently from the Topic 606 disclosure. Start by collecting what the issuer includes, how it treats cancellations and contract duration, and what it excludes. A comparable headline needs a comparable population.
Fixed minimum amounts and usage-dependent fees can have different treatment. A software arrangement can contain a fixed subscription plus incremental charges based on later usage. The disclosure may omit some amounts under applicable rules, or an estimated variable amount may be limited by the transaction price rules. Read the accounting policy and specific note rather than treating observed next year's usage as already in the contracted remaining amount. Explaining which parts are included can matter more than refining a numerical growth assumption.
Duration offers another example. Topic 606 provides disclosure exceptions under conditions, including certain obligations in contracts with an original expected duration of one year or less, and certain circumstances involving the amount an entity has a right to invoice. An issuer's usage of these allowances shapes what readers can infer from the disclosed balance. The exact customer terms and the applicable guidance control what qualifies. A large annual renewal base can provide recurring deliveries without carrying the same reported long-duration obligation profile as multi-year contracts. FASB clarification of disclosure exceptions.
A real filing can illustrate the perimeter without supplying a peer assumption. Rockwell Automation discusses practical expedients in its 2026 annual filing under revenue recognition. Salesforce's earnings report identifies total and current remaining performance obligations and describes its own measure. Read the definitions in the cited disclosure before lining up figures from the two companies. Their terms, service patterns and reported boundaries can differ even when they use similar labels. Rockwell Automation Form 10-K, Salesforce quarterly earnings exhibit.
A customer relationship sometimes lets the company recognize a commercial probability of future renewal outside current performance obligations. An analyst can model that expectation with a separately named renewal assumption. If expected renewals are included in the remaining amount by mistake, the revenue forecast can double count them after adding new bookings. Keeping existing disclosed work and new business in separate calendar sections makes the assumptions inspectable.
The label current can also refer to several things. One issuer describes a portion expected to be recognized in the next twelve months. A balance sheet current liability has its own classification. These are different balance concepts even when they cover similar periods. Find the stated timing convention and the date it starts. A fiscal year-end or quarter-end comparison can move the window forward, removing an upcoming recognition event from one measure while leaving meaningful contracts in force.
Rebuild growth with a sensible number of unknowns
Imagine Rowan begins the period with 240 units of remaining performance obligations. During the period it recognizes 90 from those obligations and adds a new multi-year contract contributing 140 at the reporting date. The period ends with 290, assuming no other movements. Growth is 50 divided by 240, about 20.8 percent. The change of 50 combines delivery and new contracted work. Recording only the 50 obscures both operating scales.
If reporting makes sufficient data available, a reader may trace changes from currency, acquisitions, cancellations, contract modifications and newly booked agreements. Suppose currency translation increases the carrying balance by 12, and a portfolio purchase contributes 35. In an otherwise aligned version of the example, operating net additions account for the rest of the change once those other sources are removed. Carefully align reporting measures before claiming a precise organic contribution from a number derived from totals.
The maturity profile can shift even when the total increases. In one scenario of 290 closing obligations, 100 is expected to be recognized over the next twelve months and 190 later. In another, 175 is expected in the next twelve months and 115 later. A portfolio with the second mix gives stronger disclosed near-term revenue coverage, under the forecast dates and assumptions, even though the total amount is the same. Operating commitments and capital needs can differ alongside that recognition path.
A bridge with missing categories should preserve the gaps. Public disclosures may provide beginning and end balances without separating recognition of current amounts from new business that started and completed inside the period. Estimate known effects transparently and keep an explained residual rather than assigning all unknowns to bookings. The note might show how much of prior-year contract liability became recognized revenue, a related datum with a different perimeter. It can constrain a hypothesis without completing a missing rollforward.
Revenue schedules depend on delivery shape. If Rowan pauses equivalent service work for a contractual suspension, recognition may depend on the actual promise and the applicable accounting model. Some standing-ready arrangements can continue to transfer benefit through time, others may depend on completed service actions. The simple even yearly amounts used here reflect the model's assumptions. A public analysis needs the issuer's promised performance and how that company measures progress.
The asset side also matters. Advance payments can finance setup, yet future services still require people, parts and energy. An investor can compare revenue recognition against expected cost to fulfill and any associated capital needs. A larger remaining balance does not establish a specific margin. Long inflation-sensitive commitments may even create pressure if costs rise under fixed pricing. A filing's risk notes, business economics and actual operations shape a grounded margin estimate.
Cross-examine the same balance against two demand stories
In one scenario Rowan signs three-year support with a customer planning a major increase in instrument usage. The customer gains fixed access and has already ordered several machines. The growth question involves finish dates, staffing and the tenor of this committed deployment. The disclosed remaining obligations carry evidence of the future contracted service component within their definition.
In the other scenario Rowan shifts existing one-year clients onto three-year contracts, while monthly service price and instrument counts remain unchanged. Disclosed remaining obligations can rise because the contracting duration changes. That change might improve visibility and reduce renewal frequency. The inference about current usage or new customer growth is different from the first scenario. A useful analysis looks for duration, customer count and unit-level data instead of deriving all business behavior from one reported balance.
Timing around a reporting date can do something similar. An agreement signed just before the cut-off raises eligible future allocations in that snapshot. Another signed the next morning belongs to a later period, subject to facts and applicable policy. A reader comparing quarters can investigate seasonality and deal cadence with disclosed context. Treating every abrupt change as a durable demand acceleration projects the timing of individual events beyond what the evidence supports.
Forecasts can make the choice visible. A simple two-column model records expected recognition from existing disclosed obligations and recognition from agreements that are still to be secured. Any forecast of usage or short agreements omitted from the initial perimeter sits in a labelled line. Calculate expected cash separately from invoice terms and opening receivables where evidence is available. A delay in cash from the same amount of work is a known scenario, as is on-time cash against slower delivery.
A workbook also identifies assumptions about customer retention and fulfillment costs. If a company's share of upfront payments rises, cash flow may improve before earnings under otherwise equivalent services. When the operator sees older advance contracts approaching delivery, it can plan for the work without expecting an identical second inflow. This is an internally consistent interpretation of strong recognized sales and little new cash in a given month.
Margin and duration deserve separate tests. A high future allocation can reflect a long period of thin-margin maintenance. More immediate shorter commitments can yield greater cash generation after costs. Each forecast requires its own assumptions about what the company delivers and what it must spend. Under uncertainty, the analyst can give a forecast range by delivery and cost rather than promise what a booked amount alone cannot establish.
Change one assumption at a time on the last calendar
Rowan's analyst sets up a later delivery case. Assume 30 of the initially expected year-two recognition moves to year three because a performance period is contractually rescheduled. Keep total consideration, and collection timing fixed only where the revised agreement supports that assumption. In a simplified case where just 30 of the original 120 shifts, the year-two roll becomes 90 and year three becomes 150. The payer still contributes the stated 90 each year under the assumed billing terms. Revenue timing has moved through the recognition columns while cash stays on the collection calendar.
A cash-delay scenario keeps the performance schedule as originally written. Suppose an invoice for 90 at the start of year two is collected only at the start of year three, alongside the scheduled year-three payment. The cash reported in the two years becomes zero and 180 for that agreement, assuming the two receipts clear. Services still contribute 120 in each year in this narrow example, with the appropriate interim balance reflecting actual invoice rights and performance. This version aims to show the difference in working capital exposure. If late payment changes collectibility or the contract terms, a real analysis revisits the accounting assumptions.
A credit loss scenario asks a third question. If the customer begins to lose the ability to pay, accounting and cash outlook require evidence about credit, enforceable terms, future performance and the treatment of recorded receivables. An analyst who projects the uncollected amount from the performance disclosure alone would overlook any unpaid previously recognized receivables. Keep the existing-asset and future-service exposures visible and consult the issuer's applicable policies. A vulnerable customer can affect both without the two measures becoming interchangeable.
The remaining revenue schedule may also have concentrations. A company with 290 units of performance spanning a dozen unrelated contracts has a different sensitivity to renegotiation than one with most of it at a single customer. Look for disclosed contract concentrations, material terms and risk commentary where available. If facts are sparse, model explicit volume and delivery scenarios rather than infer diversification from the visibility of one total.
One final check applies to time. The reported balances are evidence as of the filing's period end. Contracts concluded later can change the outlook between that date and publication. Keeping a subsequent-event or management-commentary column distinct allows a reader to locate it without reopening the historical measurement. A forecast dated today can reflect later confirmed information while still recording the old balance accurately.
The changes above can be indexed with a reference to the existing promise and the reason one calendar moved. Distinguish a customer amendment whose terms are known from a hypothetical sensitivity in which the analyst moves a recognition date. The same numerical effect can derive from a documented change or an arbitrary modeling exercise, and it deserves a different confidence label. This distinction also helps the next analyst remove superseded scenarios when audited delivery results arrive. They can compare the original allowance for slippage, actual service performance and receipt timing without changing what they previously knew on the reporting date.
Close the file with three dates
End a review by recording the reporting date, recognition horizon, and key dates or conditions for collection. Next to each amount write which agreements it describes. If the issuer reports the total and a near-term portion, keep the indicated timing and its perimeter. If a commercial backlog measure is used alongside, connect the two only where the company supplies enough evidence for a bridge.
Rowan's example begins with revenue of 120 and cash of 180. Its first year-end performance balance of 240 survives into the next delivery calendars. A reader can reconcile the advanced 60, the remaining cash of 180 and the future revenue of 240 because every receipt belongs to a date and definition. Tide arrives at the same performance headline with a different cash future. Knowing why makes the two reports comparable in the dimensions that actually match.
The decision sheet finally states what would change the conclusion. Earlier collection affects the cash forecast. Slower transfer changes the recognition path. Contract duration and disclosure policy can move the starting balance. New agreements affect each calendar in their own terms. This record preserves the analytical work even when next quarter's headline rises or falls for several reasons at once.
Sources
- FASB Accounting Standards Update 2016-20, technical corrections and improvements to Topic 606 including remaining performance obligation disclosures.
- Rockwell Automation 2026 annual report, revenue recognition policy and practical expedients.
- Salesforce quarterly earnings exhibit, remaining performance obligation presentation.