13 — Treasury at group scale
Treasury, cash management and reporting for organisations where the finance function spans entities, currencies and jurisdictions.
At group scale, the problem is rarely a missing feature. It is that cash position, exposure and intercompany balances live in a dozen systems that were each correct in isolation and have never agreed at the same moment.
We build the layer that reconciles them: bank connectivity, a single cash and exposure view, intercompany netting, and reporting that ties back to the ledger rather than to an export.
Common questions
What is treasury management system integration?
Connecting bank accounts, ERP systems and trading platforms so that cash position, exposure and payment execution operate from one dataset. The difficulty is normalisation: statement formats, value dating and entity mapping differ per bank and per country, and unresolved differences surface as a position nobody trusts.
How is intercompany netting implemented?
By calculating net positions between entities on a fixed cycle, applying agreed FX rates, and settling only the net amount — with the gross positions preserved for statutory reporting. The engineering effort is in entity mapping and the audit trail, not the arithmetic.
Why do group cash positions disagree between systems?
Value dating, in-flight payments, FX rate timing and entity mapping. Each system is internally consistent and uses a different convention. A reliable group position requires those conventions to be reconciled explicitly rather than assumed away.
Next capability
Neobanks
Bring us the hard part.
Forty-five minutes with the people who would actually run the build.