Invalid Pain.001 messages

The following table describes the invalid batch messages for the bad batch scenarios covered by the sample application.

Table 1. Invalid batch test messages
Test message	Description
pain.001.001.03_invalidBatAmount.xml	The value of CtrlSum in the GrpHdr does not match the sum of the transfer values.
pain.001.001.03_invalidTxnCount.xml	The value of NbOfTxs in the GrpHdr does not match the total number of transfers.
pain.001.001.03_invalidTxn.xml	One transfer has an invalid InstdAmt currency. It is set to USA instead of USD.

The following figure shows the batch records for all of the invalid batch test messages.

The batch objects are in an alert state, so they also appear on the all alerts screen as shown in the following figure.

All of the batch objects have the same state transition history. The following figure shows a sample state history for a batch object.

Figure 3. Invalid batch: sample state history

Each batch object has its own validation failure reason, which is shown on the errors tab of the batch details. The following figures have the different validation failure reasons for the invalid batch test messages:

Invalid Batch Error: Transaction Count shows an error with the transaction count.
Invalid Batch Error: Amount shows an amount error.
Invalid Batch Error: One Invalid Transaction shows a batch with an invalid transaction.

In the sample application, the only option for handling the invalid batches is for the operator to cancel each batch with a command. When canceling batches, a second operator must approve the cancellation. A batch is canceled in the same manner as described in UglyPaymentRequestFailsParse.103.

Figure 4. Invalid batch error: transaction count

Figure 6. Invalid batch error: one invalid transaction