ValidateFin

pain.001.001.03 — NbOfTxs mismatch

A pain.001 that miscounts itself: NbOfTxs declares one transaction while the file actually carries two. Like CtrlSum, the count is checked both on the payment batch and on the file header.

pain.001.001.03 — Invalid

A pain.001 that miscounts itself: NbOfTxs declares one transaction while the file actually carries two. Like CtrlSum, the count is checked both on the payment batch and on the file header.

SEPA Credit Transfer (pain.001) pain.001.001.03 ISO 20022Expected result: Invalid — 2 errors

What this file shows

A pain.001 that miscounts itself: NbOfTxs declares one transaction while the file actually carries two. Like CtrlSum, the count is checked both on the payment batch and on the file header.

Transactions2
SchemeSEPA
Date in the file2026-02-25

The defects it carries

  • NbOfTxsPmtInf NbOfTxs mismatch: a payment batch declares 1 but contains 2 transactions.
  • NbOfTxsNbOfTxs mismatch: header declares 1 but found 2 transactions.

Quoted verbatim from the validator, not paraphrased.

Last verified: License: CC-BY-4.0
Download the file Open the matching validator

Every party, IBAN and amount below is fictitious. The IBANs are structurally valid — they pass the mod-97 check — but they belong to no real account.

File content

<?xml version="1.0" encoding="UTF-8"?>
<!--
  ValidateFin sample file - SEPA Credit Transfer, pain.001.001.03.
  Expected validation result: INVALID - exactly one error.
  Deliberate defect: NbOfTxs declares 1 transaction but the file carries 2.

  All parties and account numbers are fictitious.
  Reference page: https://validatefin.com/en/resources/samples/sepa-pain001-invalid-nbtxs
  License: CC-BY-4.0
-->
<Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain.001.001.03"
          xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <CstmrCdtTrfInitn>
    <GrpHdr>
      <MsgId>MSG-ERR-NBTXS-001</MsgId>
      <CreDtTm>2026-02-23T10:00:00</CreDtTm>
      <NbOfTxs>1</NbOfTxs>
      <!-- CtrlSum correct pour 2 transactions -->
      <CtrlSum>800.00</CtrlSum>
      <InitgPty>
        <Nm>Societe Test NbOfTxs</Nm>
      </InitgPty>
    </GrpHdr>
    <PmtInf>
      <PmtInfId>PMT-ERR-NBTXS-001</PmtInfId>
      <PmtMtd>TRF</PmtMtd>
      <!-- NbOfTxs incorrect : declare 1, mais 2 transactions ci-dessous -->
      <NbOfTxs>1</NbOfTxs>
      <CtrlSum>800.00</CtrlSum>
      <PmtTpInf>
        <SvcLvl>
          <Cd>SEPA</Cd>
        </SvcLvl>
      </PmtTpInf>
      <ReqdExctnDt>2026-02-25</ReqdExctnDt>
      <Dbtr>
        <Nm>Societe Test NbOfTxs</Nm>
      </Dbtr>
      <DbtrAcct>
        <Id>
          <IBAN>FR7630006000011234567890189</IBAN>
        </Id>
      </DbtrAcct>
      <DbtrAgt>
        <FinInstnId>
          <BIC>BNPAFRPP</BIC>
        </FinInstnId>
      </DbtrAgt>
      <CdtTrfTxInf>
        <PmtId>
          <EndToEndId>E2E-NBTXS-001</EndToEndId>
        </PmtId>
        <Amt>
          <InstdAmt Ccy="EUR">500.00</InstdAmt>
        </Amt>
        <CdtrAgt>
          <FinInstnId>
            <BIC>SOGEFRPP</BIC>
          </FinInstnId>
        </CdtrAgt>
        <Cdtr>
          <Nm>Premier Creancier</Nm>
        </Cdtr>
        <CdtrAcct>
          <Id>
            <IBAN>FR0430003000209876543210093</IBAN>
          </Id>
        </CdtrAcct>
        <RmtInf>
          <Ustrd>Paiement 1</Ustrd>
        </RmtInf>
      </CdtTrfTxInf>
      <CdtTrfTxInf>
        <PmtId>
          <EndToEndId>E2E-NBTXS-002</EndToEndId>
        </PmtId>
        <Amt>
          <InstdAmt Ccy="EUR">300.00</InstdAmt>
        </Amt>
        <CdtrAgt>
          <FinInstnId>
            <BIC>CMCIFRPP</BIC>
          </FinInstnId>
        </CdtrAgt>
        <Cdtr>
          <Nm>Deuxieme Creancier</Nm>
        </Cdtr>
        <CdtrAcct>
          <Id>
            <IBAN>FR3314508600001234567890150</IBAN>
          </Id>
        </CdtrAcct>
        <RmtInf>
          <Ustrd>Paiement 2</Ustrd>
        </RmtInf>
      </CdtTrfTxInf>
    </PmtInf>
  </CstmrCdtTrfInitn>
</Document>

How we know these results hold

Every file in this library is run through the site's own validator on each build. The expected result stated above is asserted by an automated test — if a file stopped matching what this page claims, the build would fail. Two inherited fixtures were repaired this way before publication: three IBANs failed the mod-97 check and several names used characters outside the basic SEPA character set.

SEPA Credit Transfer (pain.001)

All sample fileshttps://validatefin.com/samples/sepa-pain001-invalid-nbtxs.xml