Integrations
Bank feeds for ERPClaw: your transactions, in your books
The shipped path is statement file import: download a file from your bank, hand it over in a sentence, and the lines match themselves to open invoices and payments. It works with the four formats banks actually export, and it is free, like the rest of ERPClaw.
The four formats your bank already exports
No connector account, no monthly fee, no third party between your bank and your books. The format is detected for you.
OFX
The common download from US and Canadian banks
CAMT.053
The ISO 20022 statement most European banks issue
MT940
The SWIFT format used across Europe, the Middle East, and Asia
BAI2
The cash-management format US commercial banks provide
Matching does the boring half
A deposit that clears an outstanding invoice pairs with that invoice. A withdrawal that settles a bill pairs with that payment. The lines the engine is confident about are matched in one pass, and standing match rules let your recurring lines, payouts, fees, subscriptions, categorise themselves. What is left is the short list a human should actually look at.
Ask "how does the checking account reconcile as of the end of January?" and you get the picture at a cutoff, from the books, in plain language. That is the AI-native difference: the request is the interface, and deterministic accounting code does the posting.
Multi-currency, the honest version
Payments are where multi-currency is real and validated in ERPClaw: an invoice raised in a supported currency is settled in that same currency, and the books stay clean because no silent conversion ever happens inside a transaction. Cross-currency conversion at posting time is deliberately not what ERPClaw does; that discipline is what keeps a self-run ledger defensible.
Common questions
How do I get bank transactions into ERPClaw today?
Download a statement file from your bank in OFX, CAMT.053, MT940, or BAI2 and hand it to ERPClaw. The lines import, match themselves to open invoices and payments where the engine is confident, and queue the rest for your review. This is shipped and documented.
Does re-importing the same statement create duplicates?
No. Every line carries its own identifier from the bank, and lines already on the books are skipped on the way in, so an interrupted download can be run again safely.
Can ERPClaw learn my recurring transactions?
Yes. Match rules let recurring lines categorise themselves, for example anything with STRIPE in the description mapping to your Stripe payout account, with priorities deciding which rule wins.
Is there a live bank connection instead of files?
Yes. Live feeds are connected per business so the setup matches your bank; ask through the form at the bottom of this page and we set yours up. Statement file import needs no setup at all and works today.
What about payments in other currencies?
Payments in the currencies ERPClaw supports settle and reconcile cleanly, with each invoice paid in its own currency. ERPClaw deliberately does not convert currencies inside a transaction; an invoice is settled in the currency it was raised in.
What does this cost?
Nothing. ERPClaw is free forever, self-hosted, and the statement import is part of it.
We set this up for you, one business at a time.
Live bank feeds are connected per business so the setup matches your bank. Leave your email and we set yours up. Statement file import needs no setup at all: it works today, free.