Preface

FDM.Preface:1 - The working problem

Financial work connects institutional relations with resources, records and possible future events. A borrower can have an obligation before a reporting system displays it. A displayed receivable can be disputed or already discharged. Money in a related company’s account can be relevant to an exposure analysis while remaining unavailable for the borrower’s next payment.

The language helps the practitioner recover these relations for a particular use. It does not attempt to replace every financial discipline. Its branch is financial domain modeling: establish the financial subjects, meanings, event conditions and effect claims that a decision, service or connected model needs. The resulting account can be a small table, a diagram or a software model; the carrier does not determine whether its claims are warranted.

Consider a loan with an advance of 100 and one contractual payment of 105 on day 30. A scoring method, its implemented calculator and one produced score are distinct. An applicable decision arrangement can use the score; an agreement can create rights and obligations under its actual formation conditions; funding can make proceeds available; later performance can satisfy only part of what is due. Following those differences explains what a score might contribute and where that contribution could fail.

FDM.Preface:2 - How the methods connect

FDM.1 recovers a financial position and distinguishes it from its descriptions. FDM.2 chooses the parties and grouping needed by the question. Either can provide an already sufficient answer. A lender explaining which entity owes an amount does not have to model an entire service.

FDM.3 uses adequate parties and terms to derive contractual events. A schedule describes what those terms require under their conditions. Scenario assumptions can produce an expected or conditional flow account; actual occurrences produce a performance account. FDM.4 establishes the effect of an actual event or action and can return a remaining obligation, a discrepancy or an unresolved institutional question.

FDM.5 follows a service output through its use to the participant’s intended financial result. It requests a position or effect model when that connection is unclear. Conversely, an accurately modeled financial change can raise the question of whose result it serves. These connections select the next needed result; they do not require all five methods for every use.

There is also a connection within the modeler’s present work. While interpreting a payment under contractual terms, the modeler can be deriving a remaining obligation and thereby constructing an account of the borrower’s position. Use B.1.5.EW — Recover How Constituent Actions Enact Encompassing Work when it is unclear how the present operation performs the encompassing work or which capability is missing. FDM.4:5.2 shows why correct subtraction can leave that work undone. A banking transfer being modeled is a separate occurrence, even when the modeler observes it while working.

FDM.Preface:3 - Connect models by the financial question

Suppose a lending model stores “loan amount = 100” for the principal, while a payment model requires the amount payable at maturity. Equal-looking field names do not establish an adequate correspondence.

FDM.1 and FDM.2 identify the same lender, borrower and contract. FDM.3 supplies the terms: principal 100, contractual maturity payment 105 in the stated currency on day 30. SIE.4 can now establish a qualified correspondence: the principal field supplies the principal input; the maturity amount follows from the applicable terms. Replacing the maturity value by 100 would lose the contractual difference of 5.

SIE.5 preserves the relevant party and contract identities. SIE.6 combines the statements with their meanings, currency and time. SIE.3 asks whether the available models are sufficient for the receiving question and directs a necessary extension. The financial distinction and the general integration method have separate contributions.

For this constructed example, assume that the advance of 100 has actually occurred and is adequately established, creating the obligation to pay 105 on day 30 under the supplied terms.

FDM.4 supplies the answers about the actual advance, payment and remaining obligation; it does not rewrite the original contractual schedule as if only 60 had been due. A reporting or risk model can retain both the schedule and the observed outcome with their distinct meanings. The connection is complete when it answers the intended question adequately, including any material unresolved premise.

FIBO supplies a reusable account of financial concepts and their relationships. ACTUS supplies a different contribution: logic relating contract terms to scheduled contractual events. A system may need either or both. The example above explains their possible roles; implementing a particular correspondence requires inspecting the chosen definitions, terms, encoding and results.

FDM.Preface:4 - Parties, resources and several useful structures

A founder-group account, legal-entity account and portfolio-risk account can all be useful. They answer different questions. A common founder can matter to correlated exposures, governance or expected support; the relation alone does not identify another entity as the debtor or make its funds available.

Keep each grouping’s criterion and use explicit. Before summing balances, preserve the parties, dates, currencies, restrictions and any relation needed for the intended aggregate. A single organizational tree can be adequate for one report and inadequate for another question. SIE.5–6 supply unresolved identity and composition work.

The same discipline applies within a loan. The lender’s right, the borrower’s duty, a bank-account record, usable proceeds and equipment acquired with those proceeds are different subjects. Their relationships explain the financial service.

FDM.Preface:5 - Practical gain, cost and evidence

The first gain is a smaller, better defined question. A payment report may need only a corrected party reference or a distinction between due and paid. A service design may need to locate who actually uses a score. A disputed obligation may require the applicable institutional rule and evidence of the event it recognizes.

A detailed model costs time to build and maintain. Begin with an adequate existing account and deepen it where a plausible alternative changes interpretation or action. A qualified model, demonstrated non-change or precisely located unknown can be the first useful result.

Recognition and assurance have different jobs. A score presented as a benefit or an aggregate presented as available cash is a reason to examine the account. An actual financial-effect claim needs adequate support for the parties, applicable terms, occurrence and consequence it asserts. A quantitative benefit claim also needs evidence for its comparison and uncertainty. The numerical cases here are constructed under supplied terms.

FDM.Preface:6 - Source choices and alternatives

The score-and-loan and group-funding cases join two questions: which financial relation a description concerns, and what using the description can change for a participant. A tool supplier can properly deliver information while another participant makes the decision. An authorized automated arrangement can act without a mandatory intermediate change in a human’s expectation. A duty or permission is an actual institutional relation under its applicable conditions, distinguishable from descriptions of it. More client admissions are not by themselves a better outcome: suitability, legitimate refusal, participant objectives and the governing conditions can change that conclusion.

A.2.8, A.2.8.PER and A.2.9 supply the respective duty, permission and communicative-work distinctions. ADM supplies the applied administrative questions. These sources retain results that a vocabulary-only financial model could erase.

A data dictionary is a good first result when the missing answer is a term’s meaning. An event model is needed when terms must determine behavior; a service explanation is needed when the use and contribution remain unclear. Combining them is justified by the receiving question. Reconsider a model when actual terms, institutional conditions, observed behavior or a changed use defeats a relied-on distinction.

FDM.Preface:7 - Using the connected account correctly

For a connected use, establish that the parties, positions, terms and times agree where the models join; that a conditional event remains conditional; and that the evidence supports the particular use or effect being asserted. Use the relevant pattern’s substantive questions for its result. An adequate supplied result can be reused while its conditions hold.

The examples expose three consequential mistakes: an amount field substituted for its financial meaning, a group aggregate substituted for available resources and a service output substituted for the participant’s outcome. Recover the missing relation rather than adding another label. When only one such question is unresolved, the other adequate accounts remain usable.

FDM.Preface:End

FDM.1 - Recover the Financial Position Behind a Record

Type: Architectural

FDM.1:0 - Use this when

Use this pattern when someone relies on a balance, agreement, score or financial label without being able to say whose position it describes and under which terms. Begin with the party and the financial question the record is being used to answer.

The pattern governs an account of a financial position: the relevant right, obligation or other financial interest of an identified party under stated conditions and at a relevant time. It returns the warranted position and its relation to the records and resources involved.

Use an already adequate account directly. A cosmetic change to a report does not require recovering an undisputed position from the beginning.

FDM.1:1 - Problem frame

Financial systems hold statements about parties and their positions. The word “claim” can refer either to an assertion in a report or to a creditor’s right to receive something. Those meanings have different consequences. A report can assert that a lender has a right; the assertion and that right remain distinguishable.

Similarly, a loan agreement, a funded loan position, an account entry and the proceeds available to the borrower are connected without being the same subject. The receiving use determines which of these must be established.

FDM.1:2 - Problem

A record’s label and amount can make its financial interpretation appear settled. If the party, terms or time are wrong, a correctly copied number can still answer the wrong question. Treating the record as the position also prevents the practitioner from explaining a stale entry, disputed obligation or valid agreement that has not yet been funded.

FDM.1:3 - Forces

A practitioner needs an answer quickly enough to support work. Reconstructing every institution and document is excessive when an adequate established account is available. Yet a material gap cannot be supplied merely by trusting a familiar field name.

The position can be clear while its future performance is uncertain. The model must retain that difference: a right to a future payment is not an assurance that the payment will occur.

FDM.1:4 - Solution

FDM.1:4.1 - State the financial question and relevant party

Ask what someone intends to conclude from the record: who owes, who may receive, who bears a loss, what is available or another specific result. Identify the actual party whose position matters and the counterparty or other participant required to interpret it.

Resolve a material identity or grouping uncertainty through FDM.2 or SIE.5. A common trading name, group identifier or database key can help locate the party but cannot settle a disputed entity boundary.

FDM.1:4.2 - Recover the position from its applicable basis

Obtain the terms and institutional basis adequate for this question. Establish what right, duty or financial interest they provide, to whom, against whom where relevant, with what content, conditions and time. Use competent interpretation when an actual rule or term is unresolved.

A document can provide evidence and, under an applicable rule, its execution or another recognized act may help institute a relation. Recover that rule and event when they matter. Do not infer the existence or absence of an obligation solely from whether a database entry is present.

A.2.8 supplies the question whether an individual duty actually obtains. A permission uses A.2.8.PER.

FDM.1:4.3 - Relate descriptions and resources to the position

Identify what each source describes, the time it concerns and any limitation affecting reliance. A contract description, a servicing record and a customer’s statement can refer to the same loan while differing in date, purpose or evidential support.

Distinguish the position from resources actually available. A borrower can owe repayment while proceeds have already been spent. A lender can have a funded right to payment while the borrower cannot currently pay. A displayed balance can be evidence about these facts, but its interpretation still needs the relevant account and availability conditions.

Retain a prospective position as prospective. A score or offer can inform a decision without establishing an agreement. Conversely, applicable terms can establish duties at valid formation before disbursement. Examine the actual conditions rather than imposing one universal sequence.

FDM.1:4.4 - Return what is warranted for this use

Return the party, financial relation, content, conditions and time at enough detail to answer the question. Relate the material records to that account and name any discrepancy or missing premise.

Use FDM.3 when the receiving question needs the event and flow consequences. Use FDM.4 when an actual action may have changed the position. If the position is already sufficient for a routine report or decision, supply it without expanding the model.

FDM.1:5 - Archetypal Grounding

A lender considers advancing 100 to a borrower. In this constructed arrangement, valid formation, currency and the applicable terms are supplied: successful funding creates the stated funded position, with 105 contractually due on day 30. The model distinguishes the lender and borrower, their respective right and duty, and the proceeds made available on funding.

An earlier score of 0.72 is a produced assertion under its scoring method. Its scale and meaning must be known before it is interpreted even as a probability. The score alone establishes neither a lending decision nor the borrower’s repayment obligation.

Suppose the signed arrangement also obliges the lender, before funding, to advance the amount once a specified condition is met. That supplied term gives the practitioner a separate pre-funding duty to examine. Waiting for disbursement before recognizing every obligation would lose it. If the actual formation or term is disputed, the model returns that exact uncertainty.

Now assume that the advance of 100 has occurred and the resulting obligation to pay 105 is established. After an adequately established payment of 60, the original agreement still describes the contractual payment of 105. FDM.4 can establish the remaining 45 under the example’s application rule and absence of further fees or interest. A servicing record that still shows an unpaid 105 is now a discrepancy to investigate, not proof that the payment had no effect.

FDM.1:6 - Bias-Annotation

System designers may prefer facts represented in their own application; a contract specialist may emphasize the agreement while overlooking settlement or usable resources. Compare the accounts around the receiving financial question.

The loan is a debt example. Other financial interests require their actual relation and governing terms; do not force an ownership interest or conditional instrument into a simple lender–borrower account merely because that example is familiar.

FDM.1:7 - Conformance Checklist

For the proposed interpretation, examine whether:

1. The actual party and financial question are identifiable.
2. The right, obligation or other interest has an adequate basis, content, conditions and time.
3. Assertions and records about the position remain distinguishable from the position itself.
4. Actual resources and expected future performance are not inferred from a position alone.
5. The result supplies an adequate answer or names the particular identity, term, rule or evidence still missing.

An adequate description supports its stated interpretation. Its existence alone does not prove formation, funding or performance.

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

Treating “claim” as one unambiguous object. State whether the sentence concerns an assertion or a creditor’s right. Then relate them where the report is evidence about the right.

Making the database constitutive by default. Establish what rule, if any, gives the relevant recording act that effect. A stale or missing entry otherwise remains a recording question.

Deferring every duty until funds move. Inspect the actual formation and conditional-performance terms. A valid unfunded arrangement can already have consequences.

FDM.1:9 - Consequences

The recipient can use an amount with its financial meaning and can distinguish uncertainty about a position from uncertainty about payment. The model also makes a disagreement between records intelligible.

The cost is recovering material terms and relations that a label had concealed. Adequate existing accounts reduce that cost; unresolved institutional interpretation limits the conclusion the model can supply.

FDM.1:10 - Architectural Rationale

The financial position is the central subject because it is what the record is commonly used to infer. Beginning with the receiving question limits the reconstruction to distinctions that matter.

A dictionary-only account is sufficient when the issue is a shared term and the actual position is already known. It is inadequate when an individual party’s right or duty remains unsettled. Starting instead with the complete financial-service chain can impose unnecessary work on a narrow position question.

FDM.1:11 - SoTA-Echoing

The practice question is how to give a financial record a warranted interpretation. The method uses FPF’s distinction between an actual institutional relation and claims about it to interpret financial records. This changes §§4.2–4.3: establish the applicable relation and then connect the descriptions and resources.

FIBO is useful for financial concepts and relations that a local label obscures. It supplies reusable meaning rather than evidence that this particular party has this particular right. At the effort of clarifying one disputed label, a position account can expose a missing formation or time premise that a field renaming would retain.

Reopen the interpretation when actual terms, party identity or event evidence changes the position being described.

FDM.1:12 - Relations

FDM.2 resolves the party or group boundary; FDM.3 derives contractual behavior; FDM.4 establishes actual changes. FDM.5 uses an adequate position model when tracing a service’s contribution.

A.2.8 governs the individual-duty question, A.2.8.PER the permission question and A.2.9 communicative work where its occurrence matters. ADM.2–4 supply the corresponding administrative participant, effectivity and account questions. SIE supplies general identity and correspondence methods without replacing the financial terms.

FDM.1:End

FDM.2 - Choose Party and Group Boundaries for Financial Modeling

Type: Architectural

FDM.2:0 - Use this when

Use this pattern when a financial question crosses companies, accounts, funds or groups and the chosen boundary could change the answer. A founder’s portfolio and a reporting group can include different entities; identify separately which party must make the payment.

The pattern governs the party and grouping account used for a financial question. It returns identified underlying parties and positions, a grouping criterion and the aggregation or support relations warranted for that use.

Use an adequate established boundary directly. A different display arrangement alone need not reopen an undisputed debtor or reporting subject.

FDM.2:1 - Problem frame

One fund tracks investments by individual legal entity. Another groups startups associated with the same founders. Both views can support useful work, yet a shared founder does not automatically combine their obligations or accounts.

The question determines the relevant relation. Payment feasibility concerns the debtor’s timely usable resources. A portfolio analysis can concern shared exposures without any support between entities. A reporting aggregate follows its applicable inclusion and elimination rules. The model must retain these differences while allowing the useful views to connect.

FDM.2:2 - Problem

A convenient group key is often used as if it settled control, liability, support and resource availability together. Adding the members’ balances then conceals the very restriction that changes the financial answer.

Forcing every question into separate-entity accounts has a different cost: it can miss correlated exposure or an actual support arrangement. The practitioner needs the boundary warranted by this question, with enough underlying structure to prevent an aggregate from acquiring another meaning.

FDM.2:3 - Forces

An aggregate makes comparison manageable. Its simplicity is useful only while the omitted distinctions do not change the intended conclusion. The relevant membership and support conditions can also change over time.

Some relations establish a duty or power; others support a prediction of voluntary action. Both may matter, but treating an expectation as committed funding gives the prediction an unwarranted institutional effect.

FDM.2:4 - Solution

FDM.2:4.1 - Start with the financial consequence being examined

State whose payment, position, exposure, control or report is at issue and the relevant time. Identify the actual entities and accounts involved before selecting a group label.

For a payment, find the party that bears the obligation. For a portfolio question, identify the investments or exposures being compared. For a required report, obtain the applicable reporting boundary from the responsible practice. Use SIE.5 when the entities themselves or their continuity are disputed.

FDM.2:4.2 - State why these members belong together

State the question the grouping serves and its inclusion criterion. The criterion may concern a common founder, control, contractual support or inclusion in the consolidated accounts under the applicable reporting rule. Establish membership at the time relevant to that question. Preserve the underlying positions when a group view is produced.

Different criteria can produce overlapping groups. Keep them connected when the receiving use needs them. A single hierarchy need not carry every financial relation.

FDM.2:4.3 - Recover what connects the positions

For a proposed support or resource-availability conclusion, inspect the actual connecting relation. A guarantee, committed facility, permitted transfer, control relationship and expected voluntary payment answer different questions.

Establish the relevant parties, content, limits, conditions and timing. A guarantee can give the creditor a further conditional claim without placing cash in the primary debtor’s account now. Permission to transfer does not establish a transfer obligation. A support commitment does not establish timely performance. Control can matter while restrictions still prevent a particular use of funds.

When support is merely expected, preserve it as a scenario assumption with the reason for that expectation. A risk account may reasonably consider it; an account of cash already available needs the stronger fact it claims.

FDM.2:4.4 - Build the warranted aggregate

Combine only amounts whose meaning, time, currency and inclusion rule are adequate for the receiving use. Preserve restrictions and conditional relations that can change the result. Apply the relevant reporting or specialist rule where valuation, conversion, netting or elimination is required; the group label does not supply those rules.

For a payment question, derive the debtor’s usable funds at the payment time after other relevant receipts and obligations. For a risk question, retain the exposures and dependencies needed to understand adverse scenarios. Do not silently use the risk aggregate as the payment-feasibility balance.

FDM.2:4.5 - Return the boundary and its financial meaning

Return the relevant parties, membership rule, positions and justified aggregate or support conclusion. State what remains unresolved where it affects use: an entity identity, support condition, restriction, payment time or aggregation rule.

Use SIE.6 to combine the relevant claims into a qualified answer once their financial meanings are established. Its result can retain several claims or report conflict, non-comparability or an unresolved premise. FDM.3 develops conditional support flows; FDM.4 establishes the effects of an actual transfer. A sufficient ordinary boundary can be used without constructing every other group view.

FDM.2:5 - Archetypal Grounding

X must pay 100 on day 7. Its unrestricted cash available on that date, after all other receipts and obligations but before this payment, is 20. Y holds 150 in its own account. They share a founder. These are supplied facts of a constructed case.

The founder-group view can show both members and their balances. It does not settle X’s ability to pay. X has an 80 shortfall under the stated cash premise.

Suppose a duly established support arrangement requires Y to transfer 80 to X, with conditions that make it due before day 7. The model now contains a support obligation whose timely performance could close the gap. Until adequate evidence establishes the transfer or another means of timely availability, “support committed” remains different from “funds available”.

If the arrangement instead provides only a guarantee exercisable after X fails to pay, the creditor may have a further route under those supplied terms. X still lacks day-7 cash in the facts given. FDM.3 models the guarantee’s actual trigger and timing; the model must not describe it as an earlier transfer.

If Y has no support commitment but the founder is expected to arrange a voluntary transfer, keep that event in the scenario that assumes it. For a portfolio-risk question, common dependence on that founder or on the same market can justify examining the members together even when no transfer is possible.

FDM.2:6 - Bias-Annotation

An investor may view a founder group as one economic story; a reporting system may prefer one legal identifier. Test both against the actual consequence being claimed.

Evidence of past voluntary support can inform an expectation. It does not by itself establish a present obligation or remove the possibility that support will arrive too late.

FDM.2:7 - Conformance Checklist

For the boundary’s stated use, examine whether:

1. The financial question, relevant time and underlying parties are clear.
2. Group membership follows an identified criterion adequate for that question.
3. Liability, control, support, permission and expected behavior remain distinct where their differences matter.
4. An aggregate retains the necessary time, currency, restrictions and applicable composition rule.
5. A claim of available funding has adequate support for timely usability, and unresolved premises remain visible.

A correct membership list establishes the group under its criterion. It does not establish every financial conclusion someone might draw from that group.

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

Funding X by summing X and Y. Recover the relation and event that make Y’s resources usable for X’s payment.

Reading a guarantee as cash in advance. Use the actual trigger, beneficiary and payment conditions. The guarantee may answer a recovery question while leaving the immediate funding question open.

Rejecting a useful risk group because its members are separate debtors. Keep the debtor accounts and model the shared exposure for the risk use that needs it.

FDM.2:9 - Consequences

The user can compare group views without erasing the party that bears an obligation or the conditions of support. This exposes both false funding comfort and overlooked shared exposure.

The model can require more than one structure. Maintaining those structures is justified by their uses; unused groupings add cost without improving the financial answer.

FDM.2:10 - Architectural Rationale

The method begins with the consequence because there is no single group boundary that settles every financial question. It retains underlying positions so that aggregation can be interpreted and revised.

A single reporting tree is adequate when its rule and the receiving use match. Separate-entity accounts suffice for an isolated debtor question. Several connected views become useful when support, exposure and reporting differ. Their connection uses SIE’s existing identity and composition methods, with the financial relations supplied here.

FDM.2:11 - SoTA-Echoing

The practice question is which party and group account makes a financial consequence intelligible. For financial groupings, the method adapts C.32.MWA’s idea that several useful structures need not coincide. SIE.5–6 supply identity and composition methods.

This changes §§4.1–4.4: choose the boundary by the consequence, retain the members’ positions and examine support separately. At the effort of naming the debtor and the support relation, it can expose a payment shortfall that a founder-group total hides. A larger organizational model is useful only when another material relation needs it.

The X–Y example demonstrates the difference between grouping entities and establishing support under its supplied conditions. Reopen the boundary when actual membership, support terms, restrictions or the receiving financial question changes.

FDM.2:12 - Relations

FDM.1 supplies positions, FDM.3 their conditional flows and FDM.4 actual changes. FDM.5 uses the relevant participant boundary when examining a service result.

SIE.5 supplies unresolved identity work and SIE.6 composition. Use C.32.MWA when a financial-practice architecture question spans several structures, starting from representative performed work or a prospective use case. The relevant accounting, legal or financial practice supplies a disputed reporting, liability or aggregation rule.

FDM.2:End

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

FDM.4 - Establish What a Financial Action Changed

Type: Architectural

FDM.4:0 - Use this when

Use this pattern when someone says a financial action is complete but the resulting position is uncertain. Approval, a sent instruction, a system posting and settlement can support different claims.

The pattern governs an account of an actual action or event’s financial effect. It returns a supported change, supported non-change or a specific unresolved effect, including the remaining position where that matters.

Use an adequate established effect account directly. Reconstructing an uncontested payment from every source adds no value when the receiving use already has sufficient evidence.

FDM.4:1 - Problem frame

A lending decision can authorize a next step without funding a borrower. An agreement can create a duty before funding. A payment instruction can be accepted for processing while the recipient still lacks usable funds. A payment can discharge only part of an obligation.

The financial question concerns the effect that actually obtains under the applicable arrangement. Its answer needs both the relevant institutional or contractual rule and adequate evidence of the event that satisfies its conditions.

FDM.4:2 - Problem

A local completion label can be used to infer a wider result. That inference can leave a debt overstated, a payment falsely treated as available or a proposed agreement treated as effective.

The opposite error is to require physical cash movement for every financial change. Waiver, valid modification or another recognized act can change a position under its applicable rule. The method must recover the actual effect mechanism rather than select it from the action’s label.

FDM.4:3 - Forces

Operational systems need timely completion signals. Their signals have scopes and can arrive before or after the effect relevant to another participant. Several dates may therefore be useful.

Evidence can disagree because of timing, identity or meaning as well as an actual failed action. Resolving the discrepancy requires enough context to distinguish those explanations, without turning every routine completion into a full investigation.

FDM.4:4 - Solution

FDM.4:4.1 - Name the claimed change and prior position

State what is supposed to have changed, for which party, under which arrangement and at what relevant time. Recover the prior position to the extent needed to explain the effect. FDM.1 supplies a missing position account; FDM.2 resolves an uncertain party boundary.

Distinguish a changed permission, duty, usable resource, recorded statement and business outcome. If a message says only “approved”, establish what its sender actually approved before treating it as evidence of another result.

FDM.4:4.2 - Recover the rule that gives the event its effect

Obtain the applicable terms or institutional rule. Identify the event or action the rule recognizes, the actor and authority where required, the conditions and the effective time. Some effects require a communicative act; others depend on performance or another recognized occurrence.

A.2.8, A.2.8.PER and A.2.9 supply the respective duty, permission and communicative-work questions. Use the relevant specialist for disputed local terms. A record can be constitutive if the applicable rule gives the recording act that role.

FDM.4:4.3 - Establish what actually occurred

Inspect the evidence relevant to that rule and effect. Match the parties, arrangement, amount and occurrence. Distinguish an instruction from its execution and a provider’s local result from the recipient’s result where those differences matter.

Retain the dates needed to interpret the action: occurrence, effective date, posting or actual availability can differ. Obtain only the dates that can change the present answer. Evidence sufficient for “instruction received” may be insufficient for “recipient can use the funds”.

If sources disagree, first compare their subjects, dates and meanings. Then investigate the remaining factual discrepancy. Do not select a source as decisive merely because its application is the most familiar one.

FDM.4:4.4 - Derive the effect and remaining position

Apply the recovered rule to the established occurrence. State what changed and when. For a partial payment, use the applicable allocation rule to determine which amounts are satisfied and what remains. Preserve other interest, fees or conditions only where the actual arrangement requires them.

Keep the calculation answerable to that interpretation. If you can perform the arithmetic but cannot explain how it establishes the financial position, use B.1.5.EW to locate the missing operation in the encompassing work. An unresolved contractual interpretation may need a qualified colleague’s contribution; a computational correction addresses a different failure.

When the evidence establishes that the required event did not occur, return the supported non-change for that effect. When the rule or occurrence is unresolved, return the exact missing premise. An unresolved result is not proof of either performance or failure.

Relate the records to the resulting position. A necessary correction belongs in the appropriate account through its responsible process; do not silently rewrite history to make sources appear consistent. Use ADM.4 when the participants’ accounts require a broader comparison.

FDM.4:4.5 - Return the result needed by the next user

Supply the supported effect, time, remaining position and limits. Name the next responsible question when a rule, occurrence or correction still needs resolution.

FDM.3 uses the resulting state for later events. FDM.5 uses the effect when examining a participant’s service result. A demonstrated financial change can be useful even when its longer-term benefit is not yet known.

FDM.4:5 - Archetypal Grounding

FDM.4:5.1 - A payment, an instruction and a modification

In the constructed loan, 105 is due on day 30. Adequate evidence establishes a payment of 60 by the borrower to the lender. The supplied application rule applies all 60 to that due amount; there are no additional fees or interest. The resulting unpaid amount is 45.

A servicing report still showing 105 unpaid disagrees with that established effect. The model returns the 45 position and the report discrepancy. It retains the original 105 contractual schedule and the actual 60 payment as distinct statements, rather than editing either into the other.

Now suppose the available evidence instead establishes only that the borrower sent a payment instruction for 60. The evidence does not yet establish the event that the supplied terms recognize as payment. The claimed reduction to 45 remains unresolved. The next question is whether that event occurred, not whether subtraction was performed correctly.

A separate pre-funding example has different effect conditions. A valid modification, made by the competent parties under supplied terms, changes a lender’s conditional advance obligation before any money moves. The model follows that rule and its actual occurrence. It does not wait for disbursement to recognize every change.

These examples demonstrate reasoning under their supplied premises. Another instrument’s payment-allocation, formation or modification rule can produce a different result.

FDM.4:5.2 - Deriving the position through an interpreted calculation

Consider a variant in which receipt of 60 is established, but the supplied terms classify it as refundable cash collateral. The terms leave the borrower’s loan obligation of 105 unchanged. Subtracting 60 from 105 still produces 45 arithmetically, but does not describe the remaining loan obligation under these terms. The account instead retains the obligation of 105 and the separate collateral position.

While applying the contractual classification, the modeler is deriving the financial effect and constructing the position account. What the larger account must explain determines what the local calculation may claim. The earlier repayment example permits the subtraction; this collateral example does not. The banking receipt supplies an occurrence to interpret, rather than becoming part of the modeler’s act of interpretation.

Someone who can calculate but cannot interpret the collateral terms needs to learn to interpret them or obtain an adequate interpretation from an appropriate specialist. Once the interpretation is adequate, the account can proceed without a fresh investigation of the already established receipt. If the terms later provide that collateral is applied to the debt, establish the event and effect under that changed condition before updating the obligation.

FDM.4:6 - Bias-Annotation

A service team may equate its own successful step with the recipient’s result. A financial reporter may give the latest posting more authority than its evidential meaning supports. Recover the effect and its rule before judging either account.

When the available sources cannot establish whether the event occurred, retain that uncertainty.

FDM.4:7 - Conformance Checklist

For the effect being asserted, examine whether:

1. The affected party, prior position, claimed change and relevant time are clear.
2. The applicable rule and its action, authority or occurrence conditions are established where required.
3. Evidence supports the actual event at the scope claimed.
4. The derived effect and any residual obligation follow the applicable terms.
5. Records, effective relations and resource availability remain distinct where their differences matter.
6. The result distinguishes supported change, supported non-change and unresolved effect.

A calculation can verify the consequence of supplied premises. It cannot establish the missing event or institutional rule.

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

Closing the obligation from a sent instruction. Establish the event the applicable arrangement recognizes as performance.

Treating all postings as either constitutive or merely descriptive. Recover the actual rule and the role of the recording act in that arrangement.

Using one date for every consequence. Retain distinct occurrence, effect or availability dates when they change the receiving answer.

FDM.4:9 - Consequences

The practitioner can explain what a financial action actually changed and what remains. Local system success no longer automatically becomes a broader completion claim.

The work can expose a missing rule, uncertain event or account correction. Resolving it may require another participant or specialist.

FDM.4:10 - Architectural Rationale

The method joins a governing rule with an actual occurrence because neither alone establishes the particular effect. A generic term describes what would happen; an event description becomes financially meaningful through the applicable conditions.

A transaction log is sufficient when it already supplies adequate evidence for a settled effect rule. A broad business-outcome inquiry is unnecessary for a narrow residual-balance question. The wider inquiry becomes useful when someone claims the financial change itself established the participant’s benefit.

FDM.4:11 - SoTA-Echoing

The practice question is how to distinguish an actual financial effect from a decision, message or record. The method applies FPF’s duty, permission and communicative-work distinctions to financial actions, with ADM.3 and ADM.9–10 supplying effectivity, usable provision and fulfillment questions.

This changes §§4.2–4.4: recover the effect rule, establish the occurrence and derive the remaining position. At the effort of examining one completion claim, it can distinguish “60 instructed” from “60 paid”, which a status-only reading conflates. More extensive investigation is justified when the unresolved premise changes the receiving use.

Actual local rules and event evidence govern an actual result. Reopen the account when either changes or when a later use requires a broader effect claim.

FDM.4:12 - Relations

FDM.1–2 supply positions and parties. FDM.3 supplies contractual event logic and consumes the resulting actual state. FDM.5 uses the supported effect in a service-contribution account.

ADM.3, ADM.7–10 and the relevant financial practice supply effectivity, evidence, permission, usable provision and fulfillment questions at their own scope. A.2.8, A.2.8.PER and A.2.9 govern the underlying institutional distinctions.

FDM.4:End

FDM.5 - Trace a Financial Service to a Participant’s Result

Type: Architectural

FDM.5:0 - Use this when

Use this pattern when a score, report, advice, interface or transaction service is called a financial benefit without explaining the receiving use. Begin with the participant and the result the service is supposed to help them obtain.

The pattern governs an explanation of a financial service’s contribution. It returns the relevant output, use, financial effect and participant result, with the support and uncertainty appropriate to the claim being made.

Use an adequate existing contribution account directly. A routine service need not be redesigned merely to describe its established result.

FDM.5:1 - Problem frame

A scoring team can improve predictive accuracy while leaving lending decisions unchanged. An admission tool can produce accurate client information while a separate arrangement determines permission to use a service. A payment provider can complete its own processing while the recipient still lacks usable funds.

Each output can be useful. Its contribution depends on a receiving participant, an actual or proposed use and the financial result that use can affect. The tool developer, decision maker, service provider and beneficiary need not be the same participant.

FDM.5:2 - Problem

Output quality is often used as evidence of an entire financial result. This hides an unused output, missing decision, failed provision or adverse consequence for another participant.

Expanding the service boundary to every eventual business outcome is also unhelpful. It can make a provider responsible for results it neither decides nor supplies. The working problem is to explain the relevant contribution and its limits at enough scope to support the current decision.

FDM.5:3 - Forces

A service needs a recognizable useful result. Different participants can want different results, and a throughput measure may not express their shared interest. A legitimate refusal can be preferable to another admission.

Longer-term outcomes depend on more conditions than the service controls. A useful model can name those conditions without claiming either sole causation or complete ignorance about the service’s contribution.

FDM.5:4 - Solution

FDM.5:4.1 - Name the participant and intended result

Identify the participant whose result is at issue and what would improve for them: access to usable funds, a warranted lending decision, timely payment, a better understood exposure or another concrete gain. Establish the horizon and comparison the present question needs.

When several participants matter, retain their differing objectives and consequences. A lender’s result and a borrower’s result need not be identical. Use the responsible financial or management practice to settle a disputed objective or choice criterion.

FDM.5:4.2 - Locate the output and its actual receiver

Identify the service output and who uses it. Separate the method, its implementation, one performed use and the produced result where their differences affect the account. A score is one output of a scoring arrangement; it is not the arrangement itself.

Ask the receiving participant how the output enters their work. A human or an authorized automated arrangement can use it. There is no mandatory intermediate change in a human’s private expectation. Conversely, delivering data to an application does not establish that it influenced the relevant action.

A supplier can properly deliver information to another actor. Give that supplier’s contribution its actual scope instead of redefining every upstream tool as if it directly provided the final financial outcome.

FDM.5:4.3 - Follow the use through the financial effect

Identify the decision or action the output can change and the financial relation or resource consequence that action can establish. Use FDM.1–4 where the position, terms or actual effect is unclear.