BBVA SEPA XML Guide: Payment Field Requirements and Rejection Fixes

The BBVA profile is intentionally narrow: it controls the credit-transfer XML shape and payroll category behavior, but it does not contain bank-specific validator rules or published-field assertions beyond those settings. That distinction matters when a portal rejects a file: first correct the verified generated shape, then obtain the exact portal error rather than inventing a BBVA-only rule.

What this BBVA profile actually does

A practical rejection-triage sequence

1. Confirm the product. If the portal is BBVA Confirming, stop: this profile does not model that product. A technically valid credit-transfer file is not evidence of Confirming compatibility.
2. Confirm the XML baseline. For a BBVA credit transfer, select BBVA so the output uses pain.001.001.03, TRF, MIXD, and default batch booking rather than generic settings.
3. Confirm payroll intent. Use Salary Mode only for payroll. It changes the category purpose written for the credit-transfer group; do not use it just because payments happen in a batch.
4. Use the actual bank response. This profile has no BBVA-specific mandatory, removed, ignored, or fixed-value validation rules beyond the generated settings above. Preserve the rejection text and validate the file before making targeted changes.

Prepare Excel for a clean credit-transfer file

Keep recipient name, recipient IBAN, amount, remittance, and optional address parts in separate columns. Then map them to the converter and select BBVA. The generator builds the payment-information group, aggregates count and control sum, and writes the SEPA service level; this avoids brittle edits to the XML header or payment category in Excel.

<PmtInf>
  <PmtMtd>TRF</PmtMtd>
  <BtchBookg>true</BtchBookg>
  <PmtTpInf><SvcLvl><Cd>SEPA</Cd></SvcLvl>...</PmtTpInf>
</PmtInf>