Transaction

Go up to Terms and Definitions

Discussion

A Transaction represents a recordable business event or proposed business event involving one or more parties, obligations, rights, values, assets, instruments, services, or settlement expectations.

In a financial system, a Transaction provides the business context for validation, interpretation, state management, settlement, audit, provenance, evidence, and review. A Transaction may describe an agreed financial event, a proposed financial event, an instruction, an order, a transfer, a contract event, or another governed business interaction, depending on the applicable domain profile.

The Financial Systems Archetype treats a Transaction as a conceptual business item, not as a message, file, database record, API payload, or runtime event. Later, logical and implementation profiles define the information structures, endpoints, services, and artefacts that represent or process transactions.

Definition

recordable business event or proposed business event involving parties, obligations, rights, values, assets, instruments, services, or settlement expectations

Source

Generalised from financial-system transaction concepts used by the Financial System and Foreign Exchange Domain material in the FX Demo Reference Architecture.

Note

A Transaction is not a message, file, an_application_programming_interface_api_provides_an_implementation_interface_through_which_software_components_systems_services_applications_tools_or_users_request_provide_exchange_or_control_information_or_behaviour payload, database row, DDS sample, event stream record, or deployment artefact. Those artefacts may represent, carry, store, or process transaction information.

Example

An FX forward transaction records an agreement between counterparties to exchange specified currencies at a specified rate on a specified settlement date.