Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-18 22:51:26 UTC · snapshot created 2026-11-18 22:54:45 UTC · last check 2026-11-18 23:35:10 UTC

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.

Specify the requested result, such as the contractual schedule, an adverse funding scenario or the consequence of an option. To find the borrower’s next required payment, establish its obligation and the applicable event conditions. To find what it has already discharged, use evidence of performance. For its ability to pay, establish usable funds by the due date. Reuse adequate terms and schedules under their stated assumptions.

FDM.3:4.2 - Construct the event rules from the operative terms

Use the operative terms and supported interpretations. FDM.1 can supply them when needed. For an event relevant to the question, identify the actor or payer, any recipient, the quantity and currency where applicable, and the relevant time.

Read each material clause as a condition with a consequence. An installment can fall due on a date even though the obligation already exists. An election clause specifies an available action and the effect of a valid exercise. A floating-rate clause specifies the observation setting the rate and when it applies. An allocation clause determines how an actual or assumed receipt changes principal and interest.

Establish how to recognize the condition, calculate the consequence and carry the resulting state forward. If payments first satisfy accrued interest, calculate interest to the receipt’s effective boundary, allocate the receipt and carry the remaining principal into the next accrual interval. A field showing “payment = 1,000” leaves that allocation open.

FDM.3:4.2.1 - Match or adapt an available model

Assess a suitable available model against the operative rules. Check whether the candidate model represents the repayment rules and events in this agreement. When several model types could fit and their differences could affect this use, compare their behavior under the terms of the agreement. Principal payable only at maturity, fixed principal installments and equal total installments require different calculations. An optional prepayment is another distinct event. Use the actual terms to determine which the loan requires or permits.

Check whether the model’s definitions and event rules express the required allocation, calendar and exercise conditions. Use a fit directly, extend a separable missing behavior when the rest remains valid, or report what the model cannot support. A software default can support a conditional scenario if stated. Use the agreement to establish its actual terms. SIE.3 helps decide whether the model suffices and SIE.4 helps connect different representations.

For an ACTUS implementation, inspect the selected contract type’s schedule, state initialization, payoff and transition rules, together with the dictionary and implementation edition. Supply the operative terms, supported starting state and any external inputs the model needs. Compare its events with the agreement-based derivation in this case. A successful sample run establishes what that sample executed. Applying the model to another contract needs a correspondence for that contract.

FDM.3:4.2.2 - Construct enough state and preserve the different dates

Work back from the next calculation to identify the required state. Simple interest on unpaid principal needs that principal, the rate and the start of the interval still to accrue. Carry any accrued unpaid interest separately. An exercised option may change which events remain possible. Other instruments can require other state.

Initialize the state at the requested starting time from supported history or an adequate opening account. After a repayment, the original principal may give a wrong forecast. After a rate change, today’s rate may give a wrong amount for an earlier interval. Use the intervening event or an adequate opening value. If neither is available, identify the later quantities that remain conditional.

Generate recurring dates from the specified anchor, interval and end condition. Preserve a short final period or end-of-month rule where the agreement requires it. Then determine which dates the business-day convention changes. The date used to calculate interest, the date on which payment is due and the date on which a transfer actually settles can differ. Notice and observation dates can add further relevant boundaries.

When a rate or principal changes, split the accrual interval at the effective boundary and apply each value during its interval. If events coincide, use the order supported by the terms or a qualified interpretation. Calculate each event from the state its rule requires. A spreadsheet row order needs a financial basis before it can determine the result.

FDM.3:4.3 - Derive and inspect contractual behavior

Work through the relevant events in their applicable order. Keep the operative terms, supplied input values and derived amounts distinguishable enough to inspect.

For a simple-interest interval with constant principal P and annual rate r, the constructed case below uses P × r × d / 365, where d is its specified actual-day count. Other conventions require their own supplied calculation. Keep the rule that selects the dates beside the arithmetic.

At an event, bring any required accrual to the applicable boundary. Determine the amount payable or noncash consequence, then apply the rule for the next state. For a receipt C allocated to interest first, compute payable interest I, apply the smaller of C and I to it and apply any permitted remainder to principal. If C < I, carry unpaid interest forward as the terms require. Use the arrangement’s rules for rounding, excess receipts and other allocations. Where capitalization is specified, add the eligible interest to principal without a cash payment.

At the due date, derive what is payable. A forecast may assume that the borrower pays it. To report an actual discharge, use FDM.4 with evidence of the event the terms recognize. Keep outstanding principal and interest until discharge or another effective change is established. A forecasting engine that clears its balance at scheduled maturity establishes only the state of that forecast.

Give the receiving user the starting position, operative rule, event condition, dates, amount and next state needed to reconstruct the result. A short table can suffice. An executable model can help with repeated or interacting calculations. Where users must inspect its result, show how a representative event answers their financial question.

Check derived flows and state changes against the terms under conditions representative of the claimed use. Examine a relevant boundary when the date, event order, exercise or allocation can change the result. Correct arithmetic still depends on the party, meaning of the amount and starting state. Use a simple two-row account for a fixed-payment loan when it suffices. Add branches or an executable model for behavior the question needs.

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

For a scenario, state the assumptions that affect the result, such as market values, option exercise, default or recovery. Derive the conditional flows. A probability or expectation needs a basis appropriate to the claim, including explicitly supplied weights for a conditional calculation.

Preserve contractual flows alongside scenarios or expectations when the receiving use needs those different amounts. Expected receipts combine possible outcomes under a model. Actual receipts require evidence of performance. Use FDM.4 to establish their effect on the remaining position.

For a financing choice, valuation or funding question, supply the qualified flows to the method that needs them. Use FIN.10 to compare financing terms and FIN.2 to relate dated amounts to usable funds. Discounting, risk treatment and rules for choosing an alternative require their respective grounds.

FDM.3:4.5 - Return and adapt the model for its receiving use

Return the contractual or conditional flows with the parties, timing rules and assumptions the question needs. An unknown future market value can leave a usable formula. Competing readings of a term may give different formulas or dates. When no single value is established, give the supported range, conditional branches or precise unresolved amount.

Distinguish an observation, exercise of an existing right, an amendment and correction of a record. A new market fixing gives an input to an existing rule. An effective amendment may change the rule. A late bank confirmation can establish a receipt that occurred earlier. Update the state, rule or evidence that actually changed.

For a valid prospective amendment, preserve established history and apply the revised rule from its effective boundary. Recompute dependent later events. If effectivity or treatment of prior accrual is unresolved, qualify the affected amount and obtain an interpretation when it is needed. Use ADM.3 and ADM.10 for the temporal or performance question.

Revisit the affected calculation when the relevant state, scenario premise or intended use changes. Use FDM.4 for the established effects needed to update actual state. Use FDM.5 for a question about how the model contributed to a service result. Preserve the basis of an opening value or changed rule when a later user needs it.