Revenue Recognition Schedule
What It Is
A revenue recognition schedule describes how a deferred amount becomes earned over time. Its dated entries connect the original deferred accounting result to later fiscal recognition. Staff can inspect the plan and its progress without treating every future month as an immediate ledger movement. The schedule belongs to the posting that created it, and recognition connects its entries to the fiscal system work that releases the deferred amount.
What It Is Not
A schedule is not the fiscal calendar, the recurring batch schedule or a payment plan. Those objects answer different questions about periods, intake timing and collection. A dated recognition entry is not yet a posted subledger entry merely because its date has arrived. Fiscal close performs recognition. A correction schedule is also distinct from editing an originating schedule in place: the correction records its own effect on the remaining deferred amount.
How It Is Used
A posted document with applicable deferral behavior creates a plan using the available strategy and line facts. Staff can inspect the line’s revenue view to see its schedules, dated entries and current balances. Subsequent memos and other corrections can create related schedules that adjust future recognition. Cash accounting uses a different originating event from accrual accounting, so the schedule must be interpreted alongside the accounting method and document relationship.
Fiscal close collects eligible due amounts into system accounting work. That process can include earlier dated entries that were booked late, making the schedule’s date and the recognition period distinct pieces of context. Reopening a period takes back the selected recognition while preserving the system accounting history. Ordinary unposting instead affects the schedules owned by the posting being removed. These paths are explained by their capabilities and should not be collapsed into one generic reset operation.
Its Facets
Dated entries divide the scheduled amount and carry rounding treatment. Recognition period describes the span selected by the applicable strategy and fallback facts. Splits describe amounts released to other accounts alongside recognition. Correction facets describe related schedules for memos, refunds and write-offs, including effective-date treatment and remaining unrecognised amounts.
Status and currency help staff distinguish planned, recognised and void accounting amounts. The fiscal system-batch facet connects recognition to period-close entries. Reporting exposes scheduled entries with their account, customer and current-posting context. These facets explain the object broadly; the schedule-generation and recognition capabilities remain the single home for calculations, limits and safeguards.
How It Relates
Posting owns originating and correction schedules. Subledger Entry records each recognition result created by fiscal close. Batch provides both the original transaction collection and the system collection used for recognition. Products supply deferral configuration, while Books and Month-end Close supply fiscal context and orchestration. Revenue reporting reads the resulting schedule facts without redefining them.
What It Could Become
The product should make the distinction between planned release, actual recognition and later correction easy to understand in one revenue view. It should resolve the tax-inclusive schedule disagreement before design relies on those totals. Effective-date fallback behavior and cash-basis origins also need focused acceptance evidence so the planned experience can explain them confidently.