Settled volume
$4.82B
+12.4%
SOC 2 Type II · ISO 27001
Know what your books say before month end
Cirrus reconciles every processor, bank and ledger you use, continuously. Breaks surface in seconds instead of at close, and the audit trail is written as it happens.
Settled volume
$4.82B
- 41s
- Median reconciliation lag
- 38
- Source formats supported
- 99.99%
- Platform uptime
Reconciliation lag
41s
-63.8%
Unmatched breaks
12
-71.2%
Ledgers connected
38
+8.6%
The problem
Close takes eleven days because nothing agrees
Every processor reports differently, every bank settles on its own schedule, and the ledger is reconciled once a month by someone with a spreadsheet. By the time a break is found, nobody remembers the transaction that caused it.
Cirrus does the matching continuously and deterministically. The result is not a faster close so much as the absence of one — the books are already right on the last day of the month.
Breaks surfaced in seconds, not at close
Rules you can read, version and test
Every match and override attributable
The ledger as it stood on any past date
Unmatched breaks, by month
12this month
Sample data
Product
Six things that make close a non-event
None of them is machine learning. Financial reconciliation needs to be explainable to an auditor, which means it needs to be deterministic.
Continuous reconciliation
Matching runs on arrival, not overnight. A break is surfaced in seconds, while the counterparty still remembers the transaction.
One normalised schema
Thirty-eight source formats collapse into a single ledger model, so a query written once works across every processor you use.
Deterministic matching
Rules you can read, version and test, rather than a model that scores. When a match is wrong you can see exactly which rule did it.
Immutable audit trail
Every match, override and adjustment is append-only and attributable. Nothing in the history can be edited, including by us.
Streaming exports
Push the reconciled ledger into your warehouse continuously, or pull it as of any point in time.
Point-in-time queries
Ask what the books said on a date, as they were understood on that date, not as they have since been corrected.
Security
Controls your auditor can test
Every control below maps to a clause and produces exportable evidence, because an assertion in a PDF is not a control.
SOC 2 CC6.1
Least privilege by default
A new user can read nothing. Access is granted per ledger and expires unless it is renewed.
SOC 2 CC7.2
Every read is logged
Not just writes. Who looked at which ledger, when, and from where, retained for seven years.
ISO 27001 A.10
Encrypted with your keys
Bring your own KMS key. Revoke it and the data is unreadable, including to us, within the hour.
GDPR Art. 44
Data residency
EU, UK, US or Australia. Data does not leave the region you pick, including backups and logs.
SOC 2 Type II
Evidence, not assertions
Control evidence is exportable on demand, so your auditor tests the system rather than reading our description of it.
SOX 404
Segregation of duties
The person who creates an adjustment cannot approve it. Enforced in the data model, not in a policy document.
Questions
What finance teams ask first
Most processors and banks are a credential and a callback, so under an hour. A custom or in-house ledger is a file format we map for you, which is typically two or three days including the test cycle you will want to run against historical data.
Contact
See it against your own data
Thirty minutes with an engineer and a sample of your ledger. We will show you the breaks you have today, or tell you that you have none — which does happen, and we will say so.
Sales
sales@cirrus.finance
Security
security@cirrus.finance
Trust centre
trust.cirrus.finance
Offices
London · New York · Singapore