Questions, answered.

Capallo is the operating layer for treasury governance. It sits between your treasury team and the systems they already use (TMS, ERP, banks). Every recurring treasury decision (FX, debt, liquidity, payments) becomes a controlled workflow with policy enforcement, approval routing, evidence capture, and an audit-ready output. We are the system of record for the decision process, not the ledger or payment rail.

Any organisation where more than one legal entity moves money and more than one person should be involved in deciding. That runs from multi-entity mid-market groups through to large corporates, health systems, universities and funds operating under obligated-group or restricted-group structures. The common thread is not revenue or country. It is that treasury decisions carry material consequence while the governance still lives in spreadsheets, email threads, and an annual audit scramble. We're also a fit for advisory and accounting firms governing treasury for multiple corporate clients. See For Advisory Firms.

TMSs handle execution and reporting. They're systems of record for the transactions themselves. Capallo sits one layer up: we govern the decision before it happens. Policy checks, delegated authority, segregation of duties, evidence capture, and the audit trail are all native to the workflow, not bolted on after the fact. Capallo is designed to run alongside an existing TMS rather than replace it.

Capallo's primary production environment is hosted in AWS Sydney (ap-southeast-2). Customer workspace data stays in that region by default. We can discuss specific data residency requirements during onboarding. Full detail is on our Security page.

Not yet. We're targeting SOC 2 Type I in Q1 2027 and are evaluating compliance automation platforms to support evidence collection ahead of the audit. Current controls, encryption posture, and the full certification roadmap are documented on our Security page.

Capallo is designed to be system-of-record-agnostic and integrates through standards, not vendor-specific connectors. Live today: CSV bridge (covers any system that can export to CSV) plus the ISO 20022 CAMT.053 and SWIFT MT940 bank statement parsers, which between them cover the large majority of corporate banks via their existing statement export. On the roadmap: BAI2 for the US banks that don't emit ISO 20022; read-only TMS connectors starting with Kyriba; ERP connector for NetSuite; chat surfaces in Microsoft Teams and Slack; and an Excel add-in. The design principle: standards beat vendors on leverage. One MT940 parser unlocks every bank that emits MT940, rather than building 50 vendor-specific connectors. Happy to confirm exactly what's live and what's near-term during a conversation.

Three tiers: Standard, Group and Enterprise, set by how complex your governance is. How many entities move money, how many decision domains you enable, and who outside the company asks you to prove the policy held. Never by seat count. We're not publishing fixed numbers while in early access, because the same tier can be a very different deployment, so we size it on the first call. Full breakdown on the Pricing page.

It is specifically an advisory-firm programme. A small founding cohort of firms that deploy Capallo across their client engagements and shape how it gets built for the channel. Cohort-specific commercial terms in exchange for weekly feedback during onboarding, willingness to be referenced privately, and a committed go-live timeline. It is not a discount tier for corporates buying Capallo for their own treasury; that is a separate conversation. Charter Partner closes once the founding cohort is signed, and later firms join under standard partnership terms.

Yes, though not from a single console. Capallo deploys into each client's own environment, and your team joins each one as members for the life of the engagement. The client owns their deployment and their evidence, which is what keeps the audit trail theirs and keeps your work independent of ours. What travels between clients is your policy framework, not a shared workspace. See For Advisory Firms for the full breakdown.

Depends on the depth of your policy work and integration footprint, so we calibrate timelines on the first call. As a working target: initial workspace setup with one decision domain enabled in 1–2 weeks; policy authoring, delegated authority matrices, and a second domain layered in over the following 2–3 weeks; steady-state operation in 4–8 weeks for the first domain, with each subsequent domain rolling out faster as your team builds policy authoring fluency. We'll commit to a concrete plan with you at scoping.

Capallo is designed to coexist with your existing TMS. Your TMS keeps doing what it does (execution, position keeping, reporting). Capallo handles the decision governance layer (policy, evidence, audit trail) that TMSs don't cover deeply. The common pattern: Capallo upstream of the TMS for decisions, the TMS for execution.

Book a conversation for 45 minutes with the founder. We walk through Capallo end-to-end and figure out where it fits, whether that's bringing governance in-house on a Standard, Group or Enterprise deployment or, if you're an advisory firm, joining the Charter Partner cohort to roll Capallo out across your client engagements.