SEPA File Checker

Amount or IBAN in the wrong format

Last updated: 28 October 2026

An amount written as 25,00 or an IBAN with spaces looks fine to a person, but the XML schema rejects it. Banks then refuse the file with CH16 or FF01. Upload the file below to see which values have the wrong notation and which can be converted automatically.

Check your file for amounts and IBANs in the wrong format

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
Format error (XSD)
Where
InstdAmt, CtrlSum, IBAN
Repair
Automatic when unambiguous, otherwise reported

What the error message looks like

Validators and banks report notation errors in English, regardless of where your software comes from. You see them in the bank portal when uploading, in the status file pain.002, or in the validation step of your accounting software.

The messages quote the value that failed, which makes them easy to trace: libxml2 says that '25,00' “is not a valid value of the atomic type”, Xerces that it “is not a valid value for 'decimal'”. For an IBAN the message refers to the pattern the value does not match.

XML schema validator (libxml2, for example xmllint and many online validators)

22: Element '{urn:iso:std:iso:20022:tech:xsd:pain.008.001.08}InstdAmt': '25,00' is not a valid value of the atomic type '{urn:iso:std:iso:20022:tech:xsd:pain.008.001.08}ActiveOrHistoricCurrencyAndAmount_SimpleType'.
26: Element '{urn:iso:std:iso:20022:tech:xsd:pain.008.001.08}IBAN': [facet 'pattern'] The value 'nl91 abna 0417 1643 00' is not accepted by the pattern '[A-Z]{2,2}[0-9]{2,2}[a-zA-Z0-9]{1,30}'.

Java validators (Xerces)

cvc-datatype-valid.1.2.1: '25,00' is not a valid value for 'decimal'.
cvc-pattern-valid: Value 'nl91 abna 0417 1643 00' is not facet-valid with respect to pattern '[A-Z]{2,2}[0-9]{2,2}[a-zA-Z0-9]{1,30}' for type 'IBAN2007Identifier'.

.NET validators

The 'urn:iso:std:iso:20022:tech:xsd:pain.008.001.08:InstdAmt' element is invalid - The value '25,00' is invalid according to its datatype 'urn:iso:std:iso:20022:tech:xsd:pain.008.001.08:ActiveOrHistoricCurrencyAndAmount_SimpleType' - The string '25,00' is not a valid Decimal value.

Your bank (status report pain.002)

  • CH16 ElementContentFormallyIncorrect
  • FF01 InvalidFileFormat

In the status report, banks put the reason in the Rsn/Cd field. Online banking often shows a translation of it. CH16 means the content of a field is formally incorrect; FF01 that the file format is invalid.

Our check

  • The value of <InstdAmt> (amount) has the wrong data type.
  • The value of <IBAN> does not have the required format.

Cause

In a SEPA file an amount has a decimal point, no thousands separator and at most two decimals, and the currency is EUR. 25.00 is correct; 25,00 and 1.250,00 are not.

The decimals need attention. The ISO schema technically allows up to five, so 25.005 passes a schema check. The SEPA rules of the EPC allow two.

An IBAN must be written without spaces and in capitals. The spaced form used on paper, such as nl91 abna 0417 1643 00, does not match the pattern [A-Z]{2,2}[0-9]{2,2}[a-zA-Z0-9]{1,30}. A BIC has 8 or 11 characters. An IBAN whose check digits are wrong is a different error: the notation is fine, but the number itself is not.

How to fix it by hand

Notation errors are easy to fix by hand, but they tend to recur.

  1. Replace the comma with a point in every InstdAmt field and in CtrlSum, and remove any thousands separators.
  2. Remove the spaces from every IBAN and write it in capitals.
  3. Check that no amount has more than two decimals; decide yourself how to round it.
  4. Preferably set up the export in your software correctly, so the next file has the right notation from the start.

Before

<InstdAmt Ccy="EUR">25,00</InstdAmt>
...
<DbtrAcct>
  <Id>
    <IBAN>nl91 abna 0417 1643 00</IBAN>
  </Id>
</DbtrAcct>

After

<InstdAmt Ccy="EUR">25.00</InstdAmt>
...
<DbtrAcct>
  <Id>
    <IBAN>NL91ABNA0417164300</IBAN>
  </Id>
</DbtrAcct>

In the example the amount 25,00 becomes 25.00 and the IBAN is written as one block in capitals. Only the notation changes.

How the tool repairs it

The check names each field with the wrong notation, for example “The value of <InstdAmt> (amount) has the wrong data type.” An unambiguous notation is converted automatically: the change report then says “Amount 25,00 converted to 25.00.” IBANs with spaces or lower case are normalised in the same step. If the notation of an amount is unclear, the tool does not guess and leaves the decision to you.

Amounts with more than two decimals are reported (“Amount has more than 2 decimals; SEPA allows at most 2 decimals.”) but deliberately not rounded, because rounding changes the amount you collect or pay. If an IBAN's check digits are wrong, the tool reports it and asks you for the correct IBAN.

What the repair writes in the change report:

  • Amount 25,00 converted to 25.00.

The tool does not decide which amount was meant. Ambiguous notations and amounts with too many decimals are left to you.

Related pages

Frequently asked questions

Why does my bank reject 25,00?

SEPA files use a decimal point. 25,00 does not match the amount type in the schema; write 25.00.

25.005 passes my validator. Is it allowed?

The ISO schema allows up to five decimals, the SEPA rules only two. The tool reports it but does not round, because that would change the amount.

May an IBAN contain spaces?

Not in the file. Write it without spaces and in capitals, for example NL91ABNA0417164300.

Does the tool correct a wrong IBAN?

It normalises spaces and lower case. If the check digits are wrong, it reports that and asks you for the correct IBAN.

Sources

Check file