Productivity
Schedule revenue recognition
Contracts split into performance obligations, recognised over the right period.
Fill it in
The agreements to schedule.
Across obligations at standalone selling price.
What recognises when.
Your prompt
Build the recognition schedule for the contracts in . Identify the performance obligations first, and be strict. A contract that bundles a platform, an implementation and support is often three obligations, and treating it as one moves revenue into the wrong period in a way an auditor will find. Allocate the transaction price across obligations at standalone selling price, and show how you derived each one. That derivation is the part that gets challenged. Handle the wrinkles explicitly: a discount that applies to only part of the bundle, a ramp, a usage component, and a renewal option that is a material right. Produce the deferred revenue waterfall by month, so the balance ties. Document the judgements. Where reasonable people would differ, say so.
Continue and pick your folderOpens with everything above already filled in.
Why this works
A contract bundling a platform, an implementation and support is usually three performance obligations, and treating it as one moves revenue into the wrong period in a way an auditor finds. This identifies them strictly and shows how each standalone price was derived.