pacs.008 UETR, BAH and network profile errors
Use source lines and XML paths to repair the generating integration. A passing preflight is limited to the checks listed in the report.
Check UETR form without inventing a network profile
PACS-UETR checks a supplied UETR against the lowercase UUID version 4 form. The third group begins with 4 and the fourth begins with 8, 9, a or b. A random identifier with the same overall length is insufficient. The fictional UETR-error fixture changes the version digit to 1, locating PmtId/UETR. Duplicate UETRs within one message also raise an independent consistency issue, without consulting a global payment registry.
The ISO base preflight does not silently require UETR on every message because requirements depend on the selected version and usage context. The optional local JSON adapter can require UETR when a user has sufficient rights to provide that assertion. Its own demo is independently written and is not a CBPR+ rule library. Assertions must explicitly declare pacsVersion, requireUetr, singleTransaction and requiredBah. Unsupported keys, missing provenance or insufficient rights leave the supplied profile unexecuted.
Select document, header and network independently
The current ISO catalogue lists pacs.008.001.14. SWIFT’s MyStandards example discusses a usage guideline derived from pacs.008.001.08. That difference does not mean one document can simply be renamed into the other. Choose the version actually required by the receiving network and its release documentation. The latest general ISO catalogue is not evidence of the SWIFT production profile.
The Business Application Header is separately published. Paste standalone AppHdr XML in its own input and choose the header version independently. The lite form recognizes head.001.001.02 and head.001.001.04. It compares MsgDefIdr with the chosen pacs.008 identifier, then compares sender and receiver BICs with group instructing and instructed agents when both identifiers are present. An eight-character BIC is normalized to its XXX branch for that comparison. These are partial consistency checks, not routing authorisation.
Debtor and creditor agents may identify themselves in ways other than BIC. The checker accepts supplied clearing-member, LEI, name or other institution-identification presence and does not invent a universal requirement for a BIC. A present BIC must have the published 8 or 11 character shape. Its syntax cannot establish registration, reachability, sanctions status or the relationship between a party and a bank. Header XSD results are separately not executed unless an authorised matching schema is supplied.
Supply a profile only within its actual rights
A shared MyStandards view can help an integration team read its network requirements. Access to that view does not permit XSDHub to copy a complete guideline library into a public validator. This form instead accepts an explicitly limited local JSON assertion document. It cannot interpret compiled XSLT, arbitrary JavaScript, Schematron phases or an exported MyStandards package. A rejected package is left unexecuted, with no claim that its original rules were checked.
Prepare the small assertion document from requirements you are entitled to process, record where they came from, and keep the required notices. Select the local assertion option deliberately. A confirmation checkbox alone does not create rights: the metadata must also identify a concrete basis, publisher, exact release, validity period and date of acquisition. The resulting report fingerprints the supplied JSON, allowing your team to reproduce which limited assertions ran. That fingerprint is evidence of bytes, not a license grant or an approval of the underlying guideline.
For the provided demonstration, all assertions were independently written by XSDHub and have MIT permission in the asset notice. The demo requires UETR on one transaction for ISO version .14 and imposes no BAH requirement. Those are demonstration choices, not a statement that a production rail uses that combination. Test your exporter with an absent UETR to observe the supplied-profile error while the independent ISO-presence checks remain separately reported.
Keep an integration evidence trail
Export a JSON report after each meaningful generator change. Record the chosen document version, BAH version, local profile provenance and each layer’s status alongside your team’s authorised network test evidence. CSV is available for comparing issues across a Pro or Team batch; files that cannot be parsed have their own failure result. The shared header input applies to every document in that batch, so use separate checks when messages have different headers.
The official-schema error fixture is deliberately labelled as a teaching-subset test. Adding an unexpected element at the root proves that the supplied-schema layer can reject a structural mismatch and report a source line. It does not imply that the unmodified fictional payment has passed the complete ISO schema. Until you select a matching authorised original XSD, the tool says that layer was not executed. Full network acceptance still needs the receiving institution’s agreed process and current MyStandards reference.
Primary sources and rights boundary
ISO catalogue · ISO archive · Published Business Application Header · SWIFT MyStandards · ISO IPR · ISO terms. Rechecked 6 November 2026. ISO repository use is royalty-free under its IPR policy; reproduction carries the official-source notice and applicable contributor conditions. MyStandards public or shared reading is no permission to redistribute CBPR+ specifications. No protected library is included. XSDHub is not the official ISO site; ISO 20022 remains the authoritative source of current repository material.
No Swift readiness certification, complete CBPR+ compliance, sanctions screening, settlement execution, RMA/reachability or bank acceptance is promised. Unknown network profiles never receive complete green approval. Without sufficient concrete processing rights a supplied local profile remains unexecuted; local BYO, runtime or server-only placement does not remove restrictions.