-
Glossary
-
XML / ISO 20022 Standard
-
ISO 20022 Messages
-
XML Schema
- Miscellaneous
- Attribute
- Closing Tag
- Comment
- Content
- Cvc-complex-type
- Cvc-elt
- Cvc-id
- Cvc-identity-constraint
- Cvc-minexclusive-valid
- Cvc-mininclusive-valid
- Cvc-type
- Cvc-totaldigits-valid
- Cvc-attribute
- Cvc-datatype-valid
- Maximum Length
- Cvc-enumeration-valid
- Cvc-fractiondigits-valid
- Cvc-length-valid
- Cvc-maxexclusive-valid
- Cvc-maxinclusive-valid
- Cvc-maxlength-valid
- Cvc-minlength-valid
- Cvc-pattern-valid
- Element Value
- Encoding
- Length
- Mandatory element
- Missing
- Missing Tag
- Missing Child Element
- MIXD
- Root
- Unsupported Characters
- UTF-8
- Value
- Wrong Declaration
-
EPC SEPA
-
CGI-MP
-
US ACH (Nacha)
-
SWIFT MT
-
Finvoice
-
Bank-Specific
-
XMLdation Service Guides
-
Studio Guide
-
Simulator
Postal Address formats: unstructured and structured
Postal Address formats
Postal Address can be in structured or unstructured format. In the structured format the Postal Address must contain mandatory fields Country and Town Name. The fields Street Name and Postal Code are optional. The unstructured format only contains optional fields Country, Address Line 1 and 2.
If the Postal Address does not contain any mandatory elements required for the structured format, it is considered to be in the unstructured format.
Some example cases
Street Name | Postal Code | Town Name | Country | Address Line1 | Address Line 2 | Format and used fields |
included | included | included | included | included | included |
structured:
|
included | included | included | included |
unstructured:
|
||
included | included | included | included |
structured:
|
||
included |
unstructured:
|
Changes in the future
Until November 2025, Postal Address will be permitted in both structured or unstructured format. After that only structured format will be permitted. However there will be a years grace period and on November 2026 the unstructured addresses will be rejected by Swift and local RTGS.