Does my camt.053 bank statement balance, and why won't it import?

1. Your camt.053 statement

A .xml or .camt download from your bank, or its text pasted below. Several statements in one file are fine.

Check statement Load a clean example Load an example with errors Clear

Choose a file or paste the XML, then click Check statement.

Result

The rules, and what they leave out

• Structure: a Document containing BkToCstmrStmt, with one Stmt per account and day, each holding an Acct, balances (Bal with type OPBD and CLBD) and Ntry entries.
• Balance: opening plus booked entries must equal the closing balance, compared exactly; credits count plus, debits minus, reversals the other way; pending and information entries are left out. Each statement must open where the previous one for the same account closed.
• Entries: an amount with a currency, CRDT or DBIT, a real booking date, and, for batch entries, transaction lines that add up to the entry.
• Declared totals: the entry counts and sums in TxsSummry must match what the statement holds.
• Never changed: the file. Problems are reported with their line number; nothing is guessed or repaired.
• Not checked: that the balances match your bank, that the file came from your bank, full XSD schema validity, digital signatures, bank-specific extensions, or what any one importer will accept. Element names are read from memory of the public camt.053 message and vary by bank and version; confirm against your bank's implementation guide.

Common questions

Why does my camt.053 file fail to import, or not reconcile?

The usual causes are an XML file that is not well formed (a cut-off download, an unescaped & in a name), a statement whose opening balance plus booked entries does not equal the closing balance, an entry with no booking date or no credit/debit indicator, a batch entry whose transaction lines do not add up to the entry amount, and a statement that does not open where the previous one closed. This tool reads every statement in the file and gives a line number for each.

How does the balance check work?

For each Stmt it adds the booked entries (CRDT as plus, DBIT as minus, and the opposite when RvslInd is true) to the opening balance (OPBD) and compares the result to the closing balance (CLBD). Pending and information entries are left out. A difference means an entry is missing, repeated or has the wrong sign. It also checks that each statement opens where the previous one for the same account closed. Amounts are compared exactly, not as floating point.

What is the difference between camt.053, camt.052 and camt.054?

camt.053 is the end-of-day statement with opening and closing balances. camt.052 is an intraday account report and camt.054 is a debit/credit notification; neither carries a closing balance to check, so the tool says which one you gave it instead of reporting a broken statement.

Can I convert camt.053 to CSV?

Yes. Download a CSV with one row per entry: account, statement, booking and value date, signed amount, currency, status, reversal flag, end-to-end id, bank reference, type code, counterparty name and account, and the remittance text. Choose a period or a comma as the decimal mark.

Does it fix the file?

Only two things that can be proved from the file itself: an amount written with a comma is rewritten with a period, and a bare ampersand character inside a name or description is escaped the way XML requires, which is the usual reason a whole file is refused as not well formed. A wrong total, a missing entry or a repeat cannot be proved from the file alone, so those are reported with their line number and left untouched; correct the source with your bank.

Does it read MT940?

No. MT940 is the older SWIFT text format. If you drop one in, the tool says so; use the MT940 statement check for it.

Is my statement uploaded anywhere?

No. It is read in your browser tab and a test in the code asserts there are no network calls. A statement holds account numbers and counterparties, so do not paste one into a tool that uploads it.