Institution route · Corporates and treasury
The buffer looked adequate on the fifteenth.
Cash forecasting says the group is comfortable. Then a receivable slips, an intercompany settlement takes three days instead of one, a committed line turns out to be uncommitted, and the currency you were naturally hedged in moves against the entity that actually holds the debt.
SAA computes the group picture beside your existing treasury stack: liquidity under stress, currency and rate exposure by entity, counterparty and bank concentration, and the operational leakage that turns into a cash number later. Every result ships with its inputs, assumptions and replay path, so the audit committee can re-open it a year from now and get the same answer.
Founder-direct intake · NDA before data · review-grade evidence
Data handling comes before product claims. For treasury teams, the first diligence question is where payment, position and counterparty data physically sits while it is being computed.
Four treasury pressures that appear only when the page is joined.
Each line is familiar on its own. The exposure appears when treasury, control and operations meet.
Liquidity is fine until the calendar disagrees.
Pain. The buffer is measured as a monthly average while payroll, tax, coupon and a supplier prepayment land in the same ten days, in three currencies, in two entities that cannot lend to each other without a tax question.
Model the group cash position day by day under stress. Intercompany constraints are stated, not assumed, and the resulting buffer is shown per entity rather than in aggregate.
The bank you are exposed to is not the bank you think.
Pain. Deposits look diversified until the same custodian, clearing route or parent group appears behind three of them. Committed and uncommitted lines are recorded in the same column.
Aggregate counterparty and bank exposure to the real entity level. Committed and uncommitted capacity are separated, with a largest-institution unavailable scenario over thirty days.
Operational leakage arrives as a cash number one quarter late.
Pain. Duplicate vendors, auto-renewed contracts, threshold splitting and missed early-payment discounts rarely look like one incident. All of it is money.
Map the leakage as structural patterns with an owner and an amount. The controller sees where working capital is going before year-end review does.
The number has to survive the committee, twice.
Pain. The treasury figure that justified a hedge, a facility or a write-down will be asked about again, after the data vintage has moved and the analyst has changed roles.
Seal every result with its inputs and its assumptions. The same question re-run in twelve months returns the same answer, verifiable by your own auditor without our involvement.
Treasury evidence pack
One treasury number, two media, one seal.
The screen and the committee pack show the same review-only result: liquidity buffer, FX exposure, counterparty concentration, date and canonical hash.
Screen shown is a review-only surface · figures are illustrative
Six workflows for corporate finance teams.
Designed for the group treasurer, CFO, controller, internal audit and audit committee.
Stress the group cash position
Day-level liquidity under adverse scenarios, by entity and currency, with committed and uncommitted capacity separated.
Size the currency and rate exposure
Transaction and translation exposure by entity, hedge coverage, refinancing wall and covenant headroom under stress.
See the counterparty concentration
Bank, custodian and clearing exposure resolved to the real institution, with a single-name unavailability scenario.
Review the corporate investment book
Deposits, money-market funds, bills and treasury-held securities reviewed as a portfolio: tails, liquidity ladder, concentration.
Find the leakage and name the owner
Duplicate payments, threshold splitting, auto-renewals, missed discounts, approval bottlenecks and rework, each with owner and amount.
Hand the committee a file it can verify
Assumptions, boundaries, sources and replay instruction, ready for internal audit and the audit committee.
Treasury Validator
If part of the treasury is on-chain, it is still treasury.
Accounting tools report the balance. They do not answer how many months the liquid part covers, what can be sold without moving the price, or what happens when an unlock, a drawdown and payroll land in the same month.
KOKON
Where the money and the time actually go.
The loss inside a group is rarely dramatic. It is the same vendor entered twice under two spellings and paid twice; purchases split just below approval threshold; a contract that renewed because the notice window closed on a Friday; a process where waiting time exceeds working time by a factor of four.
A payment your systems initiated is still your payment.
Automation now initiates and executes payments. The control framework was written for people.
Know Your Agent
An automated actor does not steal, it drifts: it retries a failed payment forty-seven times and settles three of them, splits an amount into identical fragments, applies a superseded policy version or reuses one approval token across sixty transactions.
Review automated payment activity
Automated payment activity is reviewed for machine signatures with the same discipline and the same boundary as human-conduct review.
Evidence first, authority stays inside
The output supports treasury, controller and internal-audit review. Payment authority and determination stay with the company.
Evidence, not testimonials.
The route returns numbers, sources, owner, replay path and cannot-claim boundary.
DRCET protocol
Open method for checking whether a fast risk engine returns the Monte Carlo answer, with deterministic numbers and replayable evidence.
See methodology →Determinism protocol and replay packs
Every report is tied to source, version, hash and replay instruction instead of a static slide.
See control posture →Independence Charter
No replacement claim, no hidden endorsement claim, no stronger claim than the evidence can replay.
Read charter →Four questions worth asking any provider, including us.
Our answers are on this page. Ask the same of anyone else in the room.
Can the number be reproduced?
Can someone who does not trust the vendor reproduce the result without access to the vendor’s code?
Where does our data sit?
Where does payment and position data physically sit while it is being computed?
What happens when evidence is insufficient?
Does the system estimate anyway, or does it refuse and show why?
Do we see disagreement?
When the model disagrees with itself, does the committee see the disagreement or only the average?
Founder-direct intake
Bring one treasury or control workflow.
One entity, one currency pair, one payment ledger, one quarter. We return the route, the owner, the evidence and the boundary of what may be claimed, before anything goes into production use.