Validation overview

One of the primary objects of the SEPA component is the validation framework map.

The validation framework map is designed to simplify the calling of validation steps that are provided by IBM and the optional integration of custom validation steps. This map orchestrates the validation flow and enables the logging to debug validation flow.

This validation framework map will take in any UNIFI 20022 formatted XML message and validate the set of rules published by the EPC. Default setting for UNIFI validation is OFF. In the updated configuration (input card 3 renamed to config), use the following parameters:

enableUNIFI - set to true to enable UNIFI validation, or false to disable it
allowUnstrAddr - set to true to allow unstructured formatted addresses only, or false to restrict to structured format and hybrid addresses only

Example:

enableUNIFI:false;allowUnstrAddr:false - disables UNIFI validation and disallows unstructured addresses

The validation framework is completely operated by the call of one map, sepvalid, which is discussed in detail in the following section.

It should be noted that no matter what the SEPA message type, the validation framework map passes correct data.

In order for a SEPA message to pass through the validation framework without error, the following conditions must be met:
  • the XML must be well-formed
  • all published applicable UNIFI rules must be followed
  • all published applicable SEPA IGs and rulebooks must be enforced
  • XML must validate against the published UNIFI/SEPA schemas

Optionally, the validation framework allows for validation of a message against an original SEPA message, where appropriate. The SEPA implementation guides have rules that require the original payment information to be validated in the current data document. Specifically, the contents of the Original Transaction Reference must match the original transaction information. For example the pacs004 return refund and pacs002 reject, for both credit transfer transactions and direct debit collections. The pacs007 direct debit reversal also has this requirement. For all of these cases, the original message is the pacs008 FI to FI customer transfer, or the pacs003 FI to FI customer direct debit.