pain.001 Validator

UETR (Unique End-to-End Transaction Reference), if present, must be a valid UUID version 4 (format: xxxxxxxx-xxxx-4xxx-yxxx-xxxxxxxxxxxx).

Why pain.001 files fail rule PAIN00111-FMT-001 (ERROR) and how to fix it: UETR (Unique End-to-End Transaction Reference), if present, must be a valid UUID version 4 (format: xxxxxxxx-xxxx-4xxx-yxxx-xxxxxxxxxxxx).

What this rule checks

UETR (Unique End-to-End Transaction Reference), if present, must be a valid UUID version 4 (format: xxxxxxxx-xxxx-4xxx-yxxx-xxxxxxxxxxxx).

Applies to pain.001.001.11. Severity: ERROR.

Why your file is rejected

Banks validate this rule server-side after the XSD schema check. When it fails, the whole file is typically rejected — even if every other transaction is correct — so a single violation blocks the entire batch.

How to fix it

This is a computed consistency check (a total or a transaction count). Recompute the value directly from the transactions in your file and make the header match exactly. Accumulate monetary amounts as integer minor units (cents) to avoid floating-point drift, then format with the correct number of decimals.

Verify before you send

Upload your pain.001 file to the validator below to confirm this rule — and every other business rule and XSD constraint — passes before your bank sees it.

UETR (Unique End-to-End Transaction Reference), if present, must be a valid UUID version 4 (format: xxxxxxxx-xxxx-4xxx-yxxx-xxxxxxxxxxxx). — pain.001 PAIN00111-FMT-001 — Ifriqa