The problem it solves.
To turn a client's bank statements into accounting records, firms currently choose between two risks. Cloud tools require uploading the statements, including a complete transaction history, account numbers, balances and every counterparty, to be processed and retained on a third party's servers.
Offline converters avoid the upload but produce spreadsheets nobody can verify. A dropped row, a misread digit or a mis-signed debit looks completely normal in the output, and surfaces months later as a reconciliation difference, if it surfaces at all.
Enclave does the work on your own machine and proves the arithmetic before releasing a single figure. Every statement must satisfy opening + Σ = closing, and every row must agree with its running balance.
Anything the arithmetic cannot prove is blocked and reported at the moment it happens. The books are checked as they are made, from data that never left the building.
What comes out is ready to post: CSV and XLSX for Excel, bank-import files for Xero, Sage, QuickBooks and FreeAgent, journals for accounts production, and MTD-ready figures for bridging software.
Read. Prove. Export. Or stop.
Four steps, in that order, every time. A figure that will not prove never reaches your software.
Ingest anywhere
Statements from banks, brokers and exchanges, parsed on your laptop, your server, or in a browser tab. Your data never leaves your machine.
Prove everything
Every released figure carries a proof receipt: the arithmetic that produced it, replayable to the penny. Same input, same bytes.
Export ready
Proved figures leave as files your software already accepts: bank-import CSV for Xero, Sage, QuickBooks and FreeAgent, journals for accounts production, MTD figures for bridging software, and XLSX for the working papers.
No guessing
An unresolvable digit, an unevidenced rate, a statement that doesn't tie: Enclave stops, names the statement and the row, and exports nothing until it is resolved.
It lands where you already work.
Every export carries the proof receipts behind it, so any figure can be traced back to the statement line that produced it.
Xero · Sage · QuickBooks · FreeAgent
Bank-import CSV in each package's own column layout, plus QBO and OFX where a statement import is expected. Chart of accounts imported from Xero or Sage so categories post to the codes you already use.
IRIS · CCH · TaxCalc
Trial balance and journal CSV for the accounts production suite, with a nominal breakdown per account and per period.
MTD bridging software
VAT boxes 1 to 9 and ITSA quarterly figures as CSV, read into recognised bridging software, which is what HMRC accepts as a digital link. Nothing is submitted from here.
CSV · XLSX · PDF
A plain CSV for anything with an importer, a formatted XLSX for the spreadsheet a client will open, and a PDF pack with statements, receipts and exceptions for the file.
Two statements. One transfer.
Money that leaves Barclays on Tuesday and lands on Kraken on Thursday is one transfer. Enclave reconstructs the graph of your accounts from statements alone, with no feeds, no consents and no credentials, and matches every leg to its counter-leg. Anything unmatched is marked HELD until the missing statement arrives.
Your statements stayon your machine.
Every document is read where it already lives. There is nowhere to upload it to.