MVTREASURY — Trade, Treasury & Liquidity Infrastructure
Add dealing, trade finance, payments, liquidity and governed AI to your bank — without replacing the core banking platform you already run.
MVTREASURY books every treasury, trade and payment event in its own double-entry ledger, moves money in your core only through one idempotent gateway, and proves at the end of every day that the two agree.
What's included
One platform for the desks that sit around your core — dealing, trade, payments and liquidity — with the controls regulators expect built in rather than bolted on.
AI operations plane
The agents do the reading, matching and scoring that fill a treasury operations day. None of them can post, release, settle or honour — they propose, and the right human queue accepts or rejects. Every decision becomes a label that measures the model.
Agents run in a separate plane under a service identity that can only draft. Their database role writes only AI tables, a build gate refuses any agent import that could reach a money path, and a model-risk approver who is never the developer signs off each version. Model cards, validation sets and monitors are generated for every agent.
Agent metrics are measured on held-out synthetic evaluation data. Each Bank's model risk committee validates on its own data before production.
Value to the bank
A core replacement takes years and puts every customer account at risk. MVTREASURY brings modern treasury, trade and liquidity capability to the teams that need it now, while the core carries on doing what it already does well.
Coexistence with core banking
MVTREASURY sits beside your core banking platform, not in place of it. The core keeps customer accounts and the general ledger. MVTREASURY keeps the treasury, trade and payment sub-ledgers — and the two are reconciled automatically every day.
Swipe sideways to see the full diagram →
Every money call to the core becomes an outbox command, delivered after the business transaction commits. A slow or unavailable core can never hold a lock in MVTREASURY — a build gate fails if any code tries.
Each call carries MVTREASURY's own idempotency key as the core's client reference, so a retry after a timeout finds the original booking rather than making a second one. A definitive refusal opens an exception case for operations.
Internal accounts and GL codes map to the core's own identifiers per legal entity, with templates by currency. An unmapped internal account stops with a clear configuration error instead of posting to the wrong place.
Movements come back by event bridge, file topic, Kafka consumer or a signed push from your middleware. An event confirms the movement MVTREASURY already recorded — it does not add a second one — and a crash only causes a re-read.
The day's journals are summarised per GL code and currency and posted to the core with entry counts, debit and credit totals and a SHA-256 digest, which the core echoes back. A three-way reconciliation then matches core movements, journals and statements, and names every break.
How it works
Standards & deployment
Request for Demo
We will walk your treasury, trade and operations teams through a full day — deal to settlement, LC to honour, QR to capture — and show the end-of-day proof against your core.
MVTREASURY is software licensed to regulated institutions, which remain responsible for their own regulatory obligations.