- Knowledgebase
- US ACH (Nacha)
- General
-
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
Technical details
NACHA schema is a stripped version of ISO 200222's pain.001.001.03.
ISO's pain.001.001.03 can be divided following "main parts":
- GroupHeader
- PaymentInformation
- CreditTransferTransactionInformation
- RemittanceInformation
- CreditTransferTransactionInformation
In NACHA's schema only the RemittanceInformation is present, so pain.001.001.03 (and thus ISO 20022 and CGI) and NACHA.xsd are not compatible. However, RemittanceInformation in NACHA is used as it is in pain.001.001.03 with no modifications.
Information present in NACHA's schema could be directly tranfered into pain.001.001.03 schema in exact same locations, but the file would not be schema valid in that case, as mandatory fields in GroupHeader, PaymentInformation and CreditTransferTransactionInformation would be missing. Information could, of course, be remapped into appropriate fields.
Screenshots of both schemas below, first being pain.001.001.03.xsd and second NACHA.xsd.
NACHA.xsd