Which records and relationships can a generated schedule release contain?

A release for this workflow can be built around a plan and everything that touches it. A buyer can ask for any of the following, and scope the set in a pilot.

- **Parties and accounts:** customers, accounts or contracts that the schedule belongs to, with status and segment fields. - **Plans and instalments:** the schedule itself, with sequence, due dates, amounts, fees and status for each line. - **Payments and allocations:** money received, and how it was applied across instalments, including part-payments and overpayments. - **Policies:** deferral limits, minimum instalment sizes, approval thresholds, cut-off rules and effective dates, kept as versioned records. - **Approvals and handovers:** requests, decisions and the roles that made them. - **Communications:** reminders and notices triggered by schedule changes. - **Event log:** a time-ordered record of each action with before and after references.

The relationships matter as much as the records. Payments point to instalments, instalments to plans, plans to the policy version in force, and events to everything they changed.

Tasks, expected end states and grading rules can sit alongside this state, so the same release can seed an environment and score it.

All of it is generated. Buyers should inspect it for grounding quality and for any sign that it reproduces a real source too closely.