Cash-Flow Computation Trigger

Return to Terms and Definitions

Cash-flow computation triggers identify the logical conditions that cause the FX Cash-Flow Computation Node to compute projected or derived FX Cash-Flow Obligations.

A trigger uses FX Contract State, FX Semantic Assertion, applicable transaction information, model reference, calculation context, or control command to initiate computation. The FX Cash-Flow Computation Node produces FX Cash-Flow Obligations and records the provenance of the computation.

A cash-flow computation trigger identifies the triggering information, producing or requesting Node, applicable model or rule context, computation scope, timestamp, and provenance reference.

Cash-flow computation triggers preserve the distinction between FX Contract State and FX Cash-Flow Obligation. Contract state identifies the lifecycle condition of the FX contract. FX Cash-Flow Obligations represent derived or projected monetary obligations produced from that state and related context.

Logical condition initiating computation of FX Cash-Flow Obligations.

Specialization of FX Cash-Flow Obligation from Section 9.7, Cash-Flow Computation Role from Section 7.6, Logical Assertion from Part 2, Section 8.8, and Interpretation from Part 1, Section 9.5; generalised from ACTUS cash-flow and analytical computation material in the original FX Demo Reference Architecture.

A cash-flow computation trigger does not prescribe the ACTUS library, model implementation, calculation engine, scheduler, job runner, API call, event trigger, or orchestration mechanism.

An FX Contract State established for a validated and semantically interpreted FX transaction triggers computation of projected FX Cash-Flow Obligations.