camt signed totals: CRDT, DBIT and complete entries
Separate gross entry sums from net CRDT/DBIT totals, and compare underlying transactions only when their detail scope is complete. The report shows CAMT-ENTRY-SUM with an XML path and source line.
Gross sum and signed net answer different questions
A statement with 100.00 CRDT and 30.00 DBIT contains two entries. Its gross Sum is 130.00 and its net amount is 70.00 CRDT. The debit subtotal is 30.00, not a negative gross Sum. All arithmetic uses exact decimal integers with five fractional places; no binary floating-point tolerance or currency conversion hides differences.
The fictional failing export declares TtlNtries/Sum 130.01. Correcting that field to 130.00 resolves CAMT-ENTRY-SUM. Independently check NbOfNtries and TtlNetNtry; changing the gross total does not repair a wrong count or net direction.
Completeness determines which totals can be checked
Entry-summary comparison requires an explicit complete-period confirmation, a single complete page, booked entries and one currency. Without those conditions the summary is listed as not executed. Per-bank-transaction-code summaries are outside this lite implementation.
Underlying NtryDtls/TxDtls may be absent, grouped or incomplete. A second confirmation is required before comparing them with an entry. Every detail must supply exactly one comparable TxAmt/Amt (or direct transaction Amt), with the entry currency and known direction. A missing transaction direction inherits the entry direction. FX, charges and interest prevent this comparison; InstdAmt and CntrValAmt are not substituted for TxAmt.
Duplicates and reversals need context
Repeated NtryRef, AcctSvcrRef or transaction references produce review warnings, not automatic rejection. NOTPROVIDED and NONREF are treated as placeholders. Two identical EndToEndId values alone do not prove duplicate bookings; a reversal and its original may share a reference. The tool has no cross-file bank history and never proves authenticity. A reported CRDT/DBIT direction is applied once even when RvslInd is true.
Before and after
Before: conditional check fails
<TtlNtries><NbOfNtries>2</NbOfNtries><Sum>130.01</Sum></TtlNtries>After: this difference is resolved
<TtlNtries><NbOfNtries>2</NbOfNtries><Sum>130.00</Sum></TtlNtries>Download the fictional error · Passing rule-only example · Exact known outcomes and source locations.
Keep an audit trail in your import job
Capture which entry set your ERP summed before exporting TxsSummry. Store the chosen currency, status filter and message version with your own processing record. A subtotal from the entire bank period cannot be compared to a filtered download of three entries. If a bank export is split, assemble its complete period in your own system before confirming completeness here.
Inspect the source line for the declared Sum first, then follow the paths for the individual Ntry amounts. Credit and debit counts each describe a subset. A missing TtlDbtNtries block is not itself a failure: the tool compares only summaries actually supplied. Do not add a made-up total to make an incomplete file appear reconciled.
- Choose the document version from the bank export agreement.
- Establish whether every entry, and separately every transaction detail, is present.
- Correct the generator’s gross Sum, count or signed net at its original source.
- Download a fresh CSV or JSON report after regenerating. The report records which comparisons were skipped and which completeness confirmations you supplied.
Evidence for these amount meanings
The ISO V08 message definition report identifies the distinct TotalEntries, TotalNetEntry and TransactionAmount fields. This page explains their arithmetic in original wording; no bank implementation guide or rule code is reproduced. Currency conversion and per-bank-code summaries are beyond the comparison implemented here.
Use the official message archive for the older version selected by the receiving bank, rather than changing xmlns to match a newer download. The current catalogue was checked on 6 November 2026 and lists V14 for these two message kinds. Version selection and successful totals are separate from a schema check.
The direct ISO downloads yielded a maintenance page during this build. No unverified replacement schema is supplied. To execute XSD, bring your complete authorised package with concrete rights and notices for each import. A successful independent sum never certifies bank authenticity, an account owner, or the full bank profile. The bank-specific acceptance process remains outside this tool.
Check the regenerated file
camt.053/054 validator · Related camt repair guide · API / CLI scope