camt balance mismatch: compare booked balances safely

When a balance comparison is meaningful

Start with camt.053, the bank statement. Select exactly one opening booked balance OPBD and one closing booked balance CLBD, with the same currency and subtype. An available balance such as OPAV or CLAV measures something different; an interim balance is not a replacement. Multiple balance pairs are ambiguous and remain unchecked.

The local control requires an explicit complete-period confirmation, a valid FrToDt interval, one complete page, exclusively BOOK entries and matching currency. Both balances must use calendar Dt values: the opening day is the period’s first day or the preceding day, and the closing day is the last period day. All booking dates must fall inside the period. Date-time balance boundaries are deliberately not compared in this lite scope. A skipped comparison says nothing about whether the numbers reconcile.

Use the reported direction once

Convert each balance and entry to a signed amount: CRDT is positive, DBIT negative. Opening balance plus the signed booked entries should equal the closing balance only after all the conditions above are satisfied. RvslInd identifies reversal context; it does not instruct the tool to negate CdtDbtInd again.

The fictional example has opening 1000.00 CRDT, entries 100.00 CRDT and 30.00 DBIT. Closing 1070.01 CRDT triggers CAMT-BALANCE; 1070.00 resolves this particular difference. A debit opening balance also carries its own negative sign. No conversion is made across currencies.

Why notifications and pending entries are different

camt.054 is a debit/credit notification, not a daily statement. The validator never requires a closing balance for it. PDNG, INFO and proprietary statuses prevent the statement from being treated as a complete booked set. A file extract or a page from a larger statement also cannot establish closing reconciliation. Review these conditions before changing any exported amounts.

Repair the generator and retest

1. Keep the bank-agreed message kind, namespace and version. .053 and .054 are distinct messages; .14 does not silently replace .08.
2. Read the conditions and skipped-check section. Confirm completeness only when your source export warrants it.
3. Find the reported line in the source generator. Correct the totals or export grouping using the actual booked transactions, then regenerate.
4. Run XML, authorised supplied XSD, independent business rules, plausibility and reconciliation separately. Full bank rules and authenticity remain unchecked even if these selected checks pass.

Primary sources and scope

The ISO catalogue lists distinct BankToCustomerStatement and BankToCustomerDebitCreditNotification messages at V14; the ISO archive retains V08. The official V08 message definition report is the primary reference for message and element meanings; the checks and examples here are independently written. The DK / EBICS lifecycle explains the German move to ISO V08 for account information; it does not establish every receiving bank’s profile.

Sources rechecked 6 November 2026. ISO download attempts returned maintenance HTML, so this tool publishes no unverified schema or protected bank rules. The official XSD is not executed without a local authorised package. ISO IPR and ISO terms govern repository material; bank artifacts, imports and code lists need separate rights. This guide does not establish account ownership, bank authenticity, bank acceptance or a complete national profile.