Field guide
AI for treasury & payments
Cash visibility, liquidity forecasting and payment operations, built on ISO 20022 data, bank APIs and instant rails.
Treasury spent the last decade getting visibility; the next constraint is speed. Instant rails give you seconds to release or hold a payment, ISO 20022 finally delivers structured data worth mining, and the forecast the CFO acts on has to update itself when the cash actually moves. The engineering sits between the ERP, the banks and the models, not inside any one of them.
This guide covers the treasury and payments stack as we build it: intraday liquidity and 13-week forecasting that refresh from bank feeds, payment repair and orchestration that cut failure rates before release, virtual accounts and in-house bank structures, verification-of-payee controls, and the API connectivity that replaces portal downloads and file batches.
Current signals
- With the ISO 20022 coexistence period closed in late 2025, treasury teams are mining structured remittance data for reconciliation and exception handling instead of re-keying references.
- SEPA Instant is fully in force: euro-area PSPs had to receive instant credit transfers by January 2025 and send them, with Verification of Payee, by October 2025.
- Bank connectivity is moving from file batches and portal downloads to APIs for balances and payment initiation; the treasury workstation increasingly reads positions in near real time.
- Rolling 13-week cash forecasts now refresh from ERP and bank feeds as data arrives, with treasurers reviewing variance and scenarios rather than assembling spreadsheets.
In this guide
Running SEPA Instant as an operating model
SEPA Instant is a 24/7 liquidity and controls problem wearing a payments badge. Prefunding, 10-second budgets, and real-time risk for the always-on rail.
ReadPayment orchestration and smart routing
Routing each transaction across acquirers by approval odds, cost, and FX turns payments into a decision problem. What the layer does and when it pays.
Stablecoin settlement for corporate treasury
GENIUS and MiCA turned stablecoins into regulated settlement rails. Where they fit in a treasury stack, and the accounting and custody traps that remain.
Bank connectivity: APIs versus files
Premium bank APIs have not retired SFTP, EBICS, or SWIFT FileAct. How to split treasury flows across channels by latency, control, and volume.
Verification of Payee: surviving the rollout
EU VoP is live for euro-area PSPs since October 2025. What the name-check actually demands from matching engines, corporate bulk files, and master data.
Virtual accounts and the in-house bank
Virtual accounts centralise cash while keeping entity-level attribution. Where they beat physical accounts, and where they add a layer of complexity.
Automating FX exposure management
Most FX automation fails at the exposure data, not the hedging. How to build the register, netting, and policy checks before letting AI near a trade ticket.
Intraday liquidity forecasting in practice
End-of-day cash forecasts miss the hours when funding problems actually happen. How to nowcast intraday positions and wire every forecast to an action.
Payment repair automation that clears the queue
Repair queues grow because exceptions outpace the people working them. How a rules-plus-ML repair layer classifies failures, enriches data, and raises STP.
ISO 20022 data after the migration
The CBPR+ cutover ended in November 2025. The returns now come from using structured payment data for reconciliation, exceptions, and analytics.
Working on something similar?
Tell us about your data and the workflow around it, and we will give you a straight read.
Book a 30-min intro call