What is camt.053? Matching bank statements to invoices
camt.053 is the ISO 20022 XML bank statement: every booking on your account with its amount, date and references. Matching uses those references, such as the invoice number or a structured payment reference, to tie each incoming payment to the open invoice it pays.
If you download a statement from your bank as a file rather than a PDF, it is probably a camt.053. This guide explains what is inside, how it compares with other formats, why some lines match and others don't, and what is still worth checking by hand.
What is inside a camt.053 file
A camt.053 statement is one XML document in three layers:
- Group header. A message ID and the time the bank created the file.
- Statement. The account IBAN, the period it covers, and the opening and closing balances.
- Entries. One per booking: the amount and currency, whether it is a credit or a debit, the booking and value dates, and a bank transaction code that says what kind of payment it was.
Under each entry sit the details that make matching possible: the end-to-end reference the payer's side sent, the other party's name and IBAN, the mandate reference of a direct debit, and the remittance information. That last field is either free text the payer typed or a structured creditor reference.
A PDF statement shows the same lines, but software can read a camt.053 field by field.
camt.053, camt.052, camt.054 and MT940
| Format | What it is | Typical use |
|---|---|---|
| camt.053 | ISO 20022 account statement, usually end of day | Daily or periodic statement with balances |
| camt.052 | ISO 20022 intraday account report | Bookings during the day |
| camt.054 | ISO 20022 debit or credit notification | Detail for individual bookings, such as a batch |
| MT940 | Older SWIFT text statement | Still offered by many banks |
MT940 carries similar information in fixed text fields with less room for references. Many banks still offer it, but ISO 20022 camt messages are replacing it, so if your bank gives you the choice, pick camt.053.
How matching works
Matching works best on references, not on amounts. Two invoices can have the same total; two references can't. In order of strength:
- A direct debit's mandate reference. When you collect by direct debit, the bank returns the mandate reference and your own end-to-end reference with each collection, so the line points straight at the customer and the invoice. The guide to SEPA Direct Debit for small businesses explains mandates.
- The end-to-end reference. Some payers' software sends the invoice number there.
- A structured reference. An RF creditor reference, or in Belgium a structured communication, is built for matching and carries check digits that catch typing errors. See Belgian structured communication explained.
- Amount, date and payer. A payment for exactly the open amount, from the right name or IBAN, near the due date, is a good guess but still a guess. Treat it as a suggestion to confirm.
Free text such as "invoice March, thanks" is the hardest case. Putting a structured reference on the invoice, for example in a payment QR code, gives the payer the right reference to copy.
Knowing who paid matters as much as knowing what was paid. The payer's IBAN is the more reliable signal, because names on statements are often shortened, written differently or belong to a parent company. Keeping each customer's bank account on file makes that step far easier.
What to check by hand
- One payment, several invoices. A customer who pays three invoices in one transfer needs the amount split across them; see matching one payment to several invoices.
- Partial and over-payments. An amount that differs from what is open, after a discount or bank fees, needs a person to decide what to do with the difference.
- Batch bookings. A bank can book several collections or transfers as one entry, with the detail per transaction underneath or in a separate camt.054. Check that each one is matched, not just the total.
- Unknown payers. A payment from a name or IBAN you don't recognize belongs on a list to chase, not on the nearest invoice.
- Returns and refunds. A returned direct debit shows up as a separate booking with a reason code; reopen the invoice it had settled.
- Outgoing payments. Debits on the statement settle your supplier bills; check them against what you expected to pay, including recurring supplier bills such as rent and subscriptions.
- The same file twice. Each statement carries a message ID. Importing a file you already imported should be refused, not booked again.
Frequently asked questions
What is the difference between camt.053 and MT940?
Both are bank statement files. MT940 is the older Swift text format; camt.053 is ISO 20022 XML with more structured fields, including room for full references and party details, which makes matching more reliable.
Where do I get a camt.053 file from my bank?
Usually from your online banking, in the account statements or downloads area, often under a name such as "XML statement" or "ISO 20022". Some banks ask you to switch the format on before you can download it. Your bank's help pages name it for your account.
Why wasn't a customer's payment matched to its invoice?
Often the payer typed free text instead of the invoice reference, paid several invoices at once, or paid an amount that differs from what is open. Check the line's remittance information, then allocate the payment yourself.
What is camt.054 used for?
camt.054 is a notification for individual bookings, often used to give the detail of a batch of direct debit collections or incoming transfers, rather than a full statement with balances.
Run your business on Apple.
Create your account on the web, then set up your workspace in the app on your iPhone, iPad or Mac.
Create your account
