Questions, answered.

Capallo checks every payment, from every company in your group, against the group's own rules before it reaches the bank. It reads the payment file your ERP already produces, holds the lines that break a rule (a new bank account, a subsidiary over its limit, an approver who isn't allowed to approve), lets the rest go on time, and records every approval with the rules and figures it was checked against. The same checks run on transfers between your own companies and on loans. Capallo never holds or moves money; it is the record of the decision, not the ledger or the payment rail.

Mid-sized groups, usually ten or more companies across several countries, where more than one company pays its own suppliers and the group's limits and approval rules live in a policy document rather than in the systems the payments go through. Usually that's a CFO or financial controller who releases payments across several companies. We're also a fit for advisory, accounting and tax firms that set up payment approvals or intercompany loans for clients like that. See For Advisory Firms.

Yes, that's what it's built for. Each company's ERP keeps making its payment file as it does now. Before the file goes to the bank, Capallo checks it against the group's approval rules: the run has to be approved by someone allowed to approve that amount, and any line going to a new or changed bank account is held until someone checks it. The rest go on time, and every approval across the group lands in one record. Payments keyed straight into a bank portal are matched afterwards from the bank statement, and any debit without a decision is raised for someone to explain. Capallo leaves the route to the bank as it is. If you want one system that sends every payment for you, that's a payment hub, and Capallo isn't one.

Put them into Capallo once: who may approve what, and up to how much. From then on each company's payment files, and transfers between your companies, are checked against them before the money moves. Anything above a person's limit goes to someone who holds the authority, and nobody can approve beyond their own. When one file pays from several companies, each company's finance lead reviews the lines drawn on it. Each approval is recorded with the version of the rules it was checked against, so after the policy changes you can still show which rules applied to a payment last March.

Yes. You can require every transfer between your companies to say what it is before the money moves: a loan, a repayment, equity, an invoice payment, a dividend or a cash pool movement. A loan across a border needs its agreement on record, its interest basis and its repayment terms, its rate is checked against the band you set, and an interest free one needs a written reason. Loans made through Capallo keep a running balance as advances and repayments go through. Capallo doesn't price loans, calculate interest or write the transfer pricing file; that stays with you and your tax adviser.

Many TMSs have approval rules built in for the payments that go through them. Capallo is for the payments that don't: supplier files that go from the ERP straight to the bank or its portal, often at the smaller or newly bought companies. It reads the file those companies already make and leaves the route to the bank as it is. If every payment in your group already goes through a TMS with its rules switched on, Capallo probably isn't your first buy.

Partly. Capallo also holds a payment to a new or changed bank account until someone other than the person who changed it has checked it. It doesn't check who owns the account against outside data, which is what payee check services like Eftsure do, so if you use one, keep it. What Capallo adds is the group: each company's payments checked against the group's limits and approval rules, transfers between your own companies recorded as what they are, and one record of every approval across all of it.

Only to take out what it holds. If nothing is held, the file goes to the bank exactly as your ERP produced it. If a payment is held, Capallo cuts it out, corrects the file's totals and checks the new file against the approved payments before it's released. Every other payment stays exactly as it was.

Those don't pass through Capallo before they go, so it catches them afterwards from the bank statement: every debit is matched to a decision or raised as an exception for someone to explain.

Capallo currently runs on Render in Frankfurt, Germany, and evidence files are stored with Cloudflare R2 in its EU jurisdiction. Both encrypt data at rest. We can discuss specific data residency requirements during onboarding, before any real data goes in. 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: payment files in ISO 20022 pain.001 and Australian ABA (Direct Entry); bank statements in ISO 20022 CAMT.053, SWIFT MT940 and CSV, with ready mappings for verified bank layouts and a mapping editor for the rest; and a CSV bridge for any system that can export to CSV. Between them they cover the large majority of corporate banks via their existing exports. 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 many of your companies make payments, what you switch on beyond payments, and who outside the company asks you to prove the rules 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.

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.

Book a conversation for 30 minutes with the founder. We walk through Capallo on a real payment run and work out where it fits for your group, or for your clients if you're an adviser. You can also try the interactive demo first, with no login.