CAMT.053 import not working? Here's how to fix it

Why a CAMT.053 import fails

CAMT.053 (ISO 20022) is a strictly defined XML format. Accounting packages validate the file before they accept it, and differ in how strict they are. A file that imports without problems in one package may be rejected in another. Below we cover the most common causes and their solutions.

Cause 1: wrong CAMT.053 version

There are several versions of CAMT.053, such as camt.053.001.02 up to and including camt.053.001.08. Each version has its own XML namespace. Not every package supports every version: SnelStart, for example, often reads only older versions such as 001.02 and refuses a newer file in 001.08.

Solution: check which version your package expects and deliver that version. StatementBridge can generate a matching CAMT.053 version, so the file aligns with the requirements of your software.

Cause 2: Moneybird is a strict importer

Moneybird places strict requirements on a CAMT.053 file. Among other things, it expects a correct booking status <Sts><Cd>BOOK</Cd></Sts> and structured fields for amount, date and counterparty. A self-made or manually edited file often lacks this structure and is then rejected without a clear message.

Solution: do not edit the XML file manually. Let StatementBridge build the CAMT.053 file with all required fields and the correct booking status, so that the file meets Moneybird's requirements.

Cause 3: IBAN does not match the linked account

Accounting packages link a CAMT.053 file to a bank account based on the IBAN in the file. If this IBAN differs from the account in your administration, you get a message such as “Bank account not found” — even though the rest of the file is correct.

Solution: make sure the IBAN in the file matches exactly the IBAN of the linked account. If the source has no real IBAN (credit card, PSP, foreign currency), use a fictitious IBAN and set the same IBAN in your accounting.

Cause 4: wrong character encoding or XML errors

Special characters such as accents and umlauts can cause import errors if the file is not saved as UTF-8. An incomplete or damaged XML structure (for example after manual editing in a text editor) also leads to parsing errors.

Solution: use a correctly encoded file. StatementBridge generates valid UTF-8 XML with a closed, validatable structure, so that special characters and the structure cause no problems.

Cause 5: wrong journal

If you import the statement into the wrong bank or cash journal, the transactions end up on the wrong account or the package refuses the import because the currency or IBAN does not match the journal.

Solution: when importing, deliberately choose the correct journal that belongs to the IBAN and currency of the statement. For credit cards, PSPs and foreign currency, use a separate journal with its own (fictitious) IBAN.

Overview: problem and solution

Problem	Cause	Solution
Version not supported	Package only reads older version (e.g. SnelStart, 001.02)	Generate the correct CAMT.053 version with StatementBridge
File is rejected	Strict importer (Moneybird) misses required fields or status BOOK	Let StatementBridge build a complete, structured file
“Bank account not found”	IBAN does not match the linked account	Make the IBAN identical or use a fictitious IBAN
Special characters or parsing error	Wrong encoding or damaged XML	Use a valid UTF-8 file from StatementBridge
Transactions in the wrong place	Wrong journal chosen during import	Choose the journal that matches the IBAN and currency

How StatementBridge creates a clean CAMT.053 file

Instead of editing an existing file, StatementBridge rebuilds the CAMT.053 file from scratch from your source data (CSV, Excel, PDF or another statement). The result is a valid, package-friendly file: the correct version, a closed XML structure, correct UTF-8 encoding, the booking status BOOK and structured fields for amount, date, description and counterparty. You simply enter the correct IBAN and download a file that imports directly.