FDM.3 - Derive Events and Conditional Flows from Financial Contract Terms

Type: Architectural

FDM.3:0 - Use this when

Use this pattern when a financial instrument’s amount or due-date field cannot answer what happens under its terms. The question may concern payment timing, a conditional draw, repayment, a guarantee or another event that changes the required flows.

The pattern governs an event and flow model of the relevant arrangement. It returns contractual events under stated terms, any scenarios needed for the question and their relation to observed performance.

Use an adequate existing schedule directly when its conditions match the question. A new diagram is unnecessary if the contractual behavior is already clear.

FDM.3:1 - Problem frame

“Loan amount 100” does not say whether 100 is the advance, current principal or payment due. A repayment amount may depend on elapsed time, a reference value, an option or prior events. Its date may depend on a calendar rule rather than a number typed into a report.

Contractual behavior and actual performance also differ. An amount due can remain unpaid. A forecast of receipts requires assumptions about performance even when the contractual schedule is certain.

FDM.3:2 - Problem

A flat list of amounts and dates can conceal the conditions that produce them. Treating the resulting schedule as an unconditional cash forecast then imports an unsupported performance assumption.

A model of every possible contingency would be costly and often impossible. The working problem is to recover the contractual logic and the conditional outcomes that can change the present use.

FDM.3:3 - Forces

Contract terms can be precise while required inputs remain uncertain. An amount linked to a future reference value may be contractually well defined without being numerically known today.

Simplification is useful when it preserves the receiving answer. It becomes misleading when it erases an exercise condition, timing rule or priority of events that changes the amount or obligation.

FDM.3:4 - Solution

FDM.3:4.1 - Recover the arrangement and intended question

Identify the relevant parties, instrument or arrangement, version of the terms and time from which the model starts. Use FDM.1 or FDM.2 for missing positions or boundaries.

State the needed answer: the contractual schedule, an adverse funding scenario, the consequence of an option or another specific question. Reuse existing terms and schedules to the extent that their scope and assumptions match.

FDM.3:4.2 - Extract the terms that determine the events

Recover the event conditions and their consequences from the applicable arrangement. For each relevant event, establish who acts or pays, to whom, what amount or quantity is determined, in which currency and at what time. Include calculation, calendar, exercise, notice or settlement rules when they can change the answer.

Identify the state from which an event is evaluated. Outstanding principal, accrued amounts or a prior exercise can matter. Preserve the rule that updates this state after an event; an amount calculated from an outdated principal can be wrong even when its formula is correctly implemented.

Ask the responsible specialist about a missing or disputed term. A software default can represent an explicit modeling assumption, but it cannot silently establish the actual contract’s meaning.

FDM.3:4.3 - Derive and inspect contractual behavior

Work through the relevant events in their applicable order. Apply the terms and state changes to derive the schedule or conditional branches. Keep terms, supplied input values and derived amounts distinguishable enough to inspect.

A simple fixed-payment loan can be modeled in two rows. An instrument with contingent payments may require branches or an executable model. Where an event’s order or date can change the result, inspect that boundary case explicitly. Choose the representation from the behavior the question needs.

Check that the resulting flows agree with the terms under representative conditions. A calculation can be mechanically correct while using the wrong meaning for “amount”, the wrong party or an inappropriate initial state.

FDM.3:4.4 - Add scenarios and performance without replacing the contract

For a scenario, state the additional assumptions: market values, exercise, default, recovery or another condition relevant to the use. Derive the resulting conditional flows. If a probability or expectation is needed, obtain an adequate basis for it and retain its conditions.

Keep the contractual schedule available alongside expected or scenario flows. An expectation is an account across possible outcomes under a model; it is not another amount that every counterparty must pay. Likewise, an observed payment belongs to the actual-performance account. FDM.4 establishes its effect on remaining positions.

A financial choice or valuation may need discounting, risk treatment or comparison with alternatives. Supply the qualified flows to the relevant financial method; the event model alone does not select those decision rules.

FDM.3:4.5 - Return the usable event model and its limits

Return the contractual or conditional flows, relevant parties, time rules and assumptions at the detail the receiving use needs. Name a missing term or uncertain input where it changes the answer.

Return a range, conditional branches or an unresolved amount when the available terms and inputs do not determine one value. Reopen the model when terms, relevant state, a relied-on scenario premise or the intended use changes.

FDM.3:5 - Archetypal Grounding

In the constructed loan, a lender advances 100 and the borrower owes one payment of 105 on day 30. Valid formation, currency and the fixed payment terms are supplied. The model can begin with:

The signs describe each party’s perspective. The second row is contractual; actual receipt still requires performance.

For illustration, suppose a separate performance model assumes an 80% probability of payment of 105 and a 20% probability of payment of only 60, both on day 30. Its expected receipt is 0.8 × 105 + 0.2 × 60 = 96. These probabilities are supplied assumptions, not an interpretation of an unexplained score. The expected amount is neither the contractual amount nor a discounted value.

If the actual payment is 60, retain that observation separately. Under the example’s supplied application rule and absence of additional fees or interest, FDM.4 can establish 45 remaining due. The contractual schedule does not become “60 due” merely because only 60 was paid.

Now consider a conditional support arrangement for X. The terms require a payment of 80 only after a specified failure and valid demand. Its event model must preserve those conditions and the actual payment timing rule. It cannot supply 80 of unconditional day-7 funding merely because that amount appears in the document. If the rule does not establish when funds can arrive, the timing result remains unresolved.

FDM.3:6 - Bias-Annotation

A precise formula can attract more confidence than its inputs deserve. Keep the source and uncertainty of performance assumptions visible, especially when a score has been converted into a probability.

A familiar simple loan can also bias the interpretation of another instrument. Use its actual terms; a repeated software field name does not establish the same event behavior.

FDM.3:7 - Conformance Checklist

For the intended flow use, examine whether:

1. The arrangement, parties, relevant terms and initial state are identified.
2. Event conditions, amounts, currencies, timing and state updates follow the applicable terms or explicit assumptions.
3. The representation retains the branches and ordering that can change the answer.
4. Contractual, scenario, expected and actual flows remain distinguishable.
5. Missing terms and uncertain inputs are exposed where they affect the result.
6. A valuation or decision claim uses the further method and evidence it requires.

A generated schedule demonstrates the calculation under its inputs. It does not establish valid formation, future performance or financial suitability.

FDM.3:8 - Common Anti-Patterns and How to Avoid Them

Using principal as the maturity payment. Recover the amount’s contractual meaning and derive the payment from the terms.

Treating a schedule as a receipt forecast. State the performance assumptions and retain the contractual obligation separately.

Applying an undocumented default. Establish whether the chosen convention belongs to the actual arrangement. If it is only a scenario assumption, say so where it changes the flow.

FDM.3:9 - Consequences

The user can explain where an amount or date comes from and can compare contractual requirements with conditional and actual outcomes. The result can feed funding, risk, reporting or service work.

The model may reveal that a previously definite number depends on an unresolved term or uncertain input. That limits reliance while giving the recipient a precise next question. Greater instrument complexity increases construction and maintenance effort.

FDM.3:10 - Architectural Rationale

Events and their conditions are central because an instrument’s financial behavior depends on how the arrangement responds over time. A flat amount-and-date record can be sufficient for a simple fixed obligation; it needs extension when conditions alter that obligation.

Separating contractual behavior from performance keeps both interpretable. A single blended “forecast cash flow” can be useful to its intended decision, but its construction must retain the contractual and scenario meanings needed to explain or revise it.

FDM.3:11 - SoTA-Echoing

The practice question is how to turn financial terms into inspectable event behavior. The selected line adopts ACTUS’s distinction between terms and the scheduled contractual events derived from them. It changes §§4.2–4.3 by making conditions, state and event consequences explicit. Actual use of a particular ACTUS contract type requires checking its specification and encoding.

At comparable first-case effort, deriving two qualified event rows is more useful than mapping an unexplained “loan amount” into a cash-flow field. An executable model is preferable when the relevant branching and repeated calculations justify its cost.

FDM.4 supplies the separate actual-effect question. Reopen the event model when terms, initial state, event ordering or a material scenario assumption changes.

FDM.3:12 - Relations

FDM.1–2 supply adequate positions and party boundaries. FDM.4 establishes actual events and their effects; FDM.5 uses the flows relevant to a participant’s service result.

SIE.3–6 supply general model construction and connection. Management Accounting, MA.4 reconciles operating, reporting and cash accounts; MA.5 uses the relevant conditional flows in its forecast. The responsible financial practice supplies any additional valuation or choice method.

FDM.3:End