SEPA File Checker

Control sum incorrect: CtrlSum or NbOfTxs does not match

Last updated: 28 October 2026

Your bank rejects the file or a batch with AM10 or AM18: the control sum or the number of transactions in the header does not match the payments in the file. An ordinary schema validator does not notice this. Upload the file below to compare the totals with the transactions it actually contains.

Check whether the control sum and number of transactions in your file match

Choose file

Checking is free. Repair if needed: €14.95 excl. VAT per file.

Our server checks your file in memory only, never saves it to disk and deletes it after 30 minutes at the latest.

See how it works

Error
Totals error (AM10, AM18)
Where
Group header and each batch: NbOfTxs, CtrlSum
Repair
Automatic: both totals recalculated

What the error message looks like

Banks report this error with a reason code and an English description, not with a schema message. You find it in the bank portal after uploading, in the status file pain.002, or in the software that imported that status file.

There is no validator message here: for the schema, NbOfTxs and CtrlSum only have to be a number and an amount, and a validator adds nothing up.

Your bank (status report pain.002)

  • AM10 InvalidControlSum
  • AM18 InvalidNumberOfTransactions

In the status report, banks put the reason in the Rsn/Cd field. Online banking often shows a translation of it. AM10 means the control sum does not match the amounts, AM18 that the number of transactions is wrong; the bank rejects the file or the batch concerned.

Our check

  • Group header: NbOfTxs is 3, but the file contains 2 transactions.
  • Group header: CtrlSum is 65.00, but the amounts add up to 75.00.

Cause

Every SEPA file states its own totals. In the group header, GrpHdr/NbOfTxs is the number of transactions in the whole file and GrpHdr/CtrlSum the sum of all amounts (InstdAmt). Each batch (PmtInf) can carry the same two fields, and there they apply to that batch only.

The figures stop matching when the file is changed after it was created. Typical cases: a transaction was deleted by hand; two files were merged into one; the data was exported from a spreadsheet that rounded the amounts; or the software counted cancelled items that never ended up in the file.

In the example the header announces three transactions totalling 65.00, while the file holds two direct debits of 25.00 and 50.00, so 75.00. Either figure alone is enough for a rejection.

How to fix it by hand

You can correct the totals in a text editor. Work carefully: one wrong digit and the bank rejects it again.

  1. Count the <DrctDbtTxInf> blocks in the file; for credit transfers count <CdtTrfTxInf>.
  2. Add up all InstdAmt values and write the result with a decimal point and two decimals, for example 75.00.
  3. Enter the count in NbOfTxs and the sum in CtrlSum in the group header.
  4. If the batches also have NbOfTxs or CtrlSum, correct them per batch with the transactions of that batch only.

Before

<GrpHdr>
  <MsgId>INC-2030-03-001</MsgId>
  <CreDtTm>2030-03-01T09:30:00</CreDtTm>
  <NbOfTxs>3</NbOfTxs>
  <CtrlSum>65.00</CtrlSum>
  ...
</GrpHdr>
<!-- 2 transactions: 25.00 + 50.00 -->

After

<GrpHdr>
  <MsgId>INC-2030-03-001</MsgId>
  <CreDtTm>2030-03-01T09:30:00</CreDtTm>
  <NbOfTxs>2</NbOfTxs>
  <CtrlSum>75.00</CtrlSum>
  ...
</GrpHdr>

After the correction the header states two transactions and 75.00, exactly what the transaction blocks contain. The transactions themselves are left untouched.

How the tool repairs it

The check counts the transactions and adds up the amounts, then compares the result with the header and every batch. You get a plain message such as “Group header: NbOfTxs is 3, but the file contains 2 transactions.”

The repair recalculates both values, at file level and at batch level, and records each change in the change report. After the repair the tool verifies that the number of transactions and the total amount are the same as those of the transactions in your original file, so nothing is added or lost along the way.

What the repair writes in the change report:

  • Group header: NbOfTxs corrected from 3 to 2.
  • Group header: CtrlSum corrected from 65.00 to 75.00.

If the amounts themselves are unclear, for example because of an ambiguous notation, the tool does not guess a total. It reports the amounts first; see invalid amount or IBAN format.

Related pages

Frequently asked questions

What does AM10 mean?

AM10 (InvalidControlSum) means that CtrlSum does not equal the sum of the amounts in the file or batch. Its counterpart AM18 is about NbOfTxs.

Why did my XML validator not find this error?

Because the file is valid according to the schema. A validator checks that CtrlSum is an amount, not that it is the right amount.

Does the repair change any of my payments?

No. Only the totals are recalculated. Afterwards the tool checks that count and total amount match the transactions of the original file.

Sources

Check file