Which record layers should a reseller name when asking what a release can contain?

When asking what a release could contain, a reseller can use this list to confirm that each layer your customers expect has been named.

- **Schedule headers** with product type, frequency, term and governing policy reference. - **Instalment lines** split into principal, interest, fees and a status for each due date. - **Payment events**, including partial, late, duplicate and reversed payments, linked to instalment lines. - **Amendment requests** with requester role, reason code, effective date and the channel used. - **Approval decisions** naming the approver role, the policy clause applied and any conditions attached. - **Side-effect records** such as notices, arrears flags, fee postings and reconciliation tasks. - **Calendar tables** covering public holidays, cut-off times and month-end rules for the relevant region. - **Task definitions** with starting state, permitted actions and an expected end state for grading.