Applications
Financial messaging is an operational data source, not just a transport format. This page separates what we have built and shown from what the same data makes possible.
Demonstrated
Each of these has published work behind it: a worked example, a benchmark or a documented pipeline. The links go to it.
Postal address structuring and remediation
Converting loosely formatted party data in ISO 20022 and legacy MT into structured or hybrid addresses, with uncertain results routed to review rather than guessed. TxFlow Workbench is the application; its launch and a vendor benchmark are published.
Payment exceptions and investigations
Reconstructing what happened across the messages, the lifecycle and the counterparties, and proposing a resolution for a person to decide on. TxAgent is the product; the worked case is a missing cover payment, resolved end to end, and the approach is written up.
Analytics on financial messaging data
Parsed and enriched messages landed in a warehouse where they can be queried. The route is documented rather than described: a streaming pipeline from Pub/Sub through TxFlow into BigQuery, with the reasoning behind it published separately.
Possible on the same data
These are not products we deliver today. They are applications the same structured data supports, described with the mechanism that would make each one work. Where we have written about one, the link goes to the argument, not to a case study. There is no case study. Treat anything below as a conversation to have, not a capability to buy.
Sanctions screening and AML
Screening quality depends on the quality of party data, and party data arrives as free text. Structuring it is the obvious lever, and the structuring can be run as a parallel job, leaving the messages actually sent to the market untouched, which is what makes it approachable without a systems migration. Set out in ISO 20022 address structuration.
Compliance and risk reporting
Aggregating message data at party and company level is what turns individual transactions into risk factors and reportable positions. The granularity of ISO 20022 is also what makes targeted anonymisation and cross-institution exchange tractable.
Treasury and liquidity
Timing and flow data, meaning when a payment moved, through which correspondent and with what delay, is the input to cash-flow forecasting and intraday liquidity. See five reasons to adopt ISO 20022.
Front office and client intelligence
Counterparty behaviour is visible in payment flows before it is visible anywhere else, which is the argument for reading back-office data in the front office. See front to back to front and the road to data riches.
If one of these is yours
The useful conversation starts from a specific problem and representative data of your own, not from this list.