Find your XML standard.

Choose by the document you have

Begin with the message root and the job that produced it. A payment instruction, a bank statement and an invoice can all contain amounts and account identifiers, yet describe different events. Choose pain.001 for customer credit-transfer instructions; use the camt tool for the statement or notification returned by a bank. A pacs message belongs to a separate interbank workflow.

For tax audit exports, country and version are part of the format. A Portuguese SAF-T file cannot be assessed with the Romanian D406 structure merely because both contain ledger entries. Select the matching country card, then compare the declared format version with the exact scope shown on its validator. Keep an older export separate when its profile is unsupported.

Orders and logistics are similarly distinct: an Order expresses a purchase request; DespatchAdvice describes a dispatch. A matching order reference can connect them, but neither proves physical receipt. Use the appropriate existing tool and supply order context only when the selected check explicitly requests it.

Read each result by layer. Local independent rules may run without a supplied schema, while XSD validation remains not executed. Where authorised local schemas are supported, preserve their dependencies and provenance rather than substituting a similarly named file. Country filters narrow this directory; they do not establish legal applicability or a bank’s acceptance policy.

If you do not recognise a document, inspect its root, namespace and producer documentation before choosing a card. Generic XML syntax checking is a useful first step; a schema check adds structure only for the schema actually supplied. This directory introduces no new format conversion or automatic selection of legal obligations.