BillingSummary
Type CDM 7.2.0Specifies individual summaries within a billing invoice.
Attributes
All 2 declared on BillingSummary. Cardinality in amber is required.
| Name | Type | Card. | Description |
|---|---|---|---|
| summaryTransfer | Transfer | 0..1 | The settlement terms for the billing summary |
| summaryAmountType | RecordAmountTypeEnum | 1..1 | The account level for the billing summary. |
Conditions
Validation rules the model enforces on this type, in Rune. An instance that breaks one of these is invalid CDM, whatever produced it.
if summaryAmountType = RecordAmountTypeEnum -> GrandTotal
then summaryTransfer exists and summaryTransfer ->> payerReceiver is absent if summaryAmountType = RecordAmountTypeEnum -> ParentTotal
then summaryTransfer ->> payerReceiver exists
and summaryTransfer ->> payerReceiver -> payerAccountReference is absent
and summaryTransfer ->> payerReceiver -> receiverAccountReference is absent if summaryAmountType = RecordAmountTypeEnum -> AccountTotal
then summaryTransfer ->> payerReceiver -> payerAccountReference exists
and summaryTransfer ->> payerReceiver -> receiverAccountReference exists Referenced by
1 type holds a BillingSummary as an attribute.
Functions
Model functions that produce or consume this type. These are the CDM's own behaviour — the logic a correct implementation has to match.
| Function | Role | Description |
|---|---|---|
| Create_BillingSummary | returns | Creates a billing summary to be included in a Security Lending Billing Invoice. |
Open BillingSummary in the Model Browser
Walk the tree and the reference graph interactively, and switch releases to see how the type has changed. Free, no signup.