Status Report (pain.002) input files

List of trigger codes

The format of a trigger code is following:

ERR{ ReasonCode }{R type} for example ERRAC01RJCT

The full list of availabe trigger codes below:

Special cases

The XMLdation Simulator tool always generates one pain.002 status report file per one input file. This functionality creates a limitation in the following scenario:

Assume e.g. an SCT payment file, which has an incorrect account number on batch level and contains an invalid BIC on transaction level. The simultaneous presence of these two errors in one and the same message file can manifest itself in two different ways: either they are found in one and the same batch or they appear in different batches. In Rabobank production environment, both situations will always generate two separate pain.002 files, one reporting the error on batch level and one reporting the error on transaction level. 

The simulator will generate the following output for the above described cases:

• The Batch error and Transaction error are included in the same batch – Only the error on batch level will be reported in the generated pain.002 file
• The Batch error and Transaction error are included in different batches – Bothe the error on batch level and the error on transaction level will be reported, but within the same pain.002 message

This situation in Rabobank production environment can only be simulated for both cases by presenting the error on a batch level and the error on a transaction level in two separate input SCT or SDD files.