From statement line to low point.

No. Headroom reads balances and transactions, forecasts them and proposes actions. A payment or a transfer is prepared inside Headroom, goes through your approval chain, and leaves as a file or an instruction that your own bank portal executes. We never hold your funds, and we never hold credentials to your bank portal.

Headroom starts from the real balances, adds known movements from your ERP (invoices, payment runs, payroll calendars) and fills the gaps with a model trained on your own history. The result is a median line and a band between the 10th and 90th percentile. The band widens with the horizon, because uncertainty does. The accuracy report shows how often actual cash stayed inside it.

Headroom connects through SWIFT, EBICS, Open Banking APIs and statement files, and reads ERP data through each system's API. The Integrations page lists the banks and systems we show as examples, such as Commerzbank, HSBC, NetSuite and SAP. If your bank can send you a CAMT.053 or MT940 statement, it can be connected, even if it is not listed.

Most groups see their first consolidated position within three days. A forecast you can trust takes about three weeks, once Headroom has learned how you pay and get paid.

Yes. Access is granted by role, entity and, if you like, by account. A regional controller can see only the entities they are responsible for, and a viewer can see balances but not payment drafts. Every change in access is written to the audit log with the person who made it.

You write rules as sentences: "Payments above €50,000 need two approvers", "New beneficiaries need the treasurer". Preparers and approvers can never be the same person on one payment. The chain, the times and the people involved are saved with each payment and can be exported for your auditors.

Data is stored in Frankfurt by default, or in London on request, and encrypted in transit and at rest. Only the people you give access to can read it; our staff need a time-limited request, approved by you, to see anything in your workspace. A report on our controls is available under NDA, and a data-processing agreement is part of every contract.

Plans are set by how far ahead you forecast: 13, 26 or 52 weeks. Accounts and entities scale by plan, and extra entities, accounts and the board pack can be added month by month. Viewers are always free.

Yes. We can run a read-only pilot on a few of your accounts before you commit. You see your own consolidated position and your own forecast, and you decide at the end whether to keep it. Nothing is changed in your banks or your ERP during the pilot.

The account is marked stale, drawn in grey and excluded from alerts that rely on fresh data, so a dead connection never looks like a quiet account. The owner receives a message that says which account, since when, and what to do next. Most connections recover on their own within the next cycle.