Remaining performance obligation

Remaining performance obligation, or RPO, is the transaction price allocated to performance obligations that are unsatisfied or partly unsatisfied at the reporting date. The disclosure pairs that aggregate amount with either suitable quantitative time bands or qualitative information about expected recognition. ASC 606-10-50-13 defines those two parts.

RPO is not total contract value. Revenue already recognized is outside the remaining amount. Consideration outside transaction price is also outside it. The disclosed population can omit qualifying obligations from contracts whose original expected duration is one year or less, right-to-invoice arrangements, and specified variable consideration. Fixed consideration cannot use the variable-consideration exemptions. ASC 606-10-50-14 through 50-15 requires an entity to identify applied exemptions and explain excluded obligations or consideration. The local text includes pending amendments, so the effective-date status belongs in the source record.

A controlled rollforward can begin with opening RPO and add new or acquired consideration. It can then reflect contract modifications, revenue recognized, cancellations, and currency effects to reach ending RPO. The timing bands must sum to that ending population when the entity gives a quantitative schedule. This bridge is a review control; Topic 606 does not prescribe that exact rollforward format.

Management backlog can include different contracts, cancellation assumptions, unexercised options, or measures outside transaction price. RPO therefore does not guarantee future revenue, cash collection, margin, or unchanged timing. Define and reconcile both populations before comparing them.

Study the Cedar Trail RPO bridge, then complete the independent Northstar practice.