1Tool

Blog · 30 July 2026

Import bank statements instead of typing them: CAMT and finAPI support in 1Tool

Import bank statements instead of typing them: CAMT and finAPI support in 1Tool

A bank statement, a list of open invoices and the job of matching the two by hand – anyone who knows this from everyday accounting knows how much time it takes and how easily allocation errors creep in. 1Tool offers two ways to automate this reconciliation: importing bank statements in CAMT format and connecting to finAPI with automatic invoice matching.

CAMT import: load bank statements directly

For banks that provide their customers with statements in CAMT format, 1Tool supports direct import. Specifically, camt.053 in versions v02 and v08 is supported, as well as camt.054 – the format for debit and credit notifications. Instead of typing a bank statement line by line or transferring it from a PDF, you simply upload the CAMT file provided by your bank to 1Tool. This option is particularly suitable for banks that do not offer a direct API connection but do provide a standardised statement export.

finAPI integration: automatic matching with open invoices

If a finAPI connection is available, 1Tool goes one step further: bank transactions are imported via finAPI and automatically matched with existing invoices. An overview shows the last ten invoices linked in this way – including a direct link to the respective contact, so that if questions arise you land straight in the right customer record. Because this automatic matching exposes sensitive payment data, access to transaction matching is permission-based – not every user in the system sees this view automatically, only those who have been granted access.

CAMT or finAPI – which option suits you?

Both approaches pursue the same goal but differ in how they work. CAMT import is the right choice if your bank does not offer a direct programming interface but does provide standardised statement files – the import then takes place as needed, for example once a week or once a month. The finAPI integration is ideal if you want invoice matching to run as continuously and automatically as possible in the background, without downloading and uploading each file individually. In practice, the two approaches are not mutually exclusive – many companies use whichever option fits each bank.

Frequently asked questions

Which CAMT formats does 1Tool support?
1Tool supports camt.053 in versions v02 and v08 for the classic bank statement as well as camt.054 for debit and credit notifications. What is the difference between CAMT import and finAPI?
CAMT import processes a statement file provided by your bank, which you upload manually. The finAPI integration imports bank transactions automatically and matches them directly with open invoices – including an overview of the most recently linked invoices. Can every employee automatically see which invoices have been matched?
No. Access to transaction matching is permission-based, so you decide which users are allowed to see this view. Would you like to automate bank statement reconciliation instead of matching payments manually?

Book a demo

Read more