Revenue Recognition Schedule

What It Models

A revenue plan separates initial deferral from later earning. Posting generates dated release amounts, and fiscal accounting turns due releases into ledger entries. Corrections can generate negative plans for the portion still deferred.

Identity and Attributes

Generation identity allows an original plan and a later replacement to coexist. The attribute rows distinguish persisted release amounts from transient generation settings and read-time positions; neither a header total nor a truncation-method column exists.

Relationships

The originating posting owns the plan. Fiscal system entries reference released plan entries, while product setup and document context supply the original deferral inputs.

Invariants

Generation and fiscal persistence enforce the safeguards listed in the invariant rows. Retiring an Open plan does not itself undo earlier recognition, and schedule-level retirement leaves entry statuses unchanged.

How It Is Stored and Shared

Batch Management stores plans and dated entries. Invoice-line inspection and the deferred-revenue query expose their positions under separate permissions. Fiscal close invokes recognition in-process; workspace export includes surviving plans and entries.

Open Design Questions

Tax-inclusive schedule generation remains inconsistent with the net deferred credit. Product must also resolve recognition already released when the originating posting is removed and prove the empty-weight correction fallback.