29.3 Incoming pain.001 - Our Bank Role as ASI

Outbound Network Resolution

After identifying the Our Bank Role as ASI and completing field-level validations, the network resolution rule is evaluated to determine the outbound payment type and network code.

The MT101 channel is used to evaluate the network rule and resolve the resulting outbound payment network.

Date Derivation / Validation

Once the outbound network and payment type are resolved, the activation date is derived using the Requested Execution Date, currency, amount, customer details, and resolved network parameters.

The final Instruction/Activation Date is determined based on the rules for the specific outbound network type.

If the activation date is later than the processing branch date, the transaction is marked as Future Valued.

Agreement Validation

The MT101 Inbound Agreement (PXD101IM) maintenance is reused for agreement validation.

The derived customer number and Requested Execution Date are used to validate the agreement with Party Type as Ordering Customer.

If a valid agreement exists, the Sender BIC is checked against the allowed sender list.

If no valid (Open/Authorized) agreement is found or the Sender BIC is not allowed, the transaction is moved to the Business Override Queue (BO).

This validation applies only if the transaction is not future dated.

Cutoff Check

If the activation date is the same as today, the received date and time is compared against the cutoff hour/minute maintained in the Inbound Agreement Validation (PXD101IM).

If the cutoff time is met, the value date and activation date are rederived, and the transaction is marked as Future Dated.

Future Dated Transaction

If the transaction is future dated, it is moved to the Future Valued Queue (PQSFUVQU). The transaction status is set to Future Dated, and the Queue Code is updated to FV.

Sanction Check

After successful agreement validation, the outbound pain.001 credit transaction is sent for sanctions screening.

If the response is Seized or Rejected, the transaction status is updated accordingly, and it is not processed further. This validation is performed only for future dated transactions.

MIS/UDF Derivation

For non-future dated transactions, the derived network code is set, and the outbound is booked based on pain.001 data.

MIS/UDF values are populated as per the configured MIS Group/UDF Group for the source code or network code.

Transaction Field Mapping

CBPRPlus

If the resolved network is CBPRPlus, an outbound SWIFT CBPRPlus pacs.008 transaction is created from the incoming pain.001 message after processing.

The pacs.008 transaction is displayed in the Cross Border Outbound FI-to-FI Customer Credit Transfer View (PSDOCBVW) screen.

The CBPRPlus pacs.008 payment processor is initiated for further processing.

TARGET2

If the resolved network is TARGET2, an outbound TARGET2 pacs.008 transaction is created from the incoming pain.001 message after processing.

The pacs.008 transaction appears on the TARGET2 Outbound FI-to-FI Customer Credit Transfer View (PSDOT2CV) screen.

The TARGET2 pacs.008 payment processor is initiated for further processing.

Book Transfer

If the resolved network is Book Transfer, a Book Transfer transaction is created from the incoming pain.001 message after processing.

The transaction is displayed on the Outbound Book Transfer View (PBDOVIEW) screen.

The Book Transfer payment processor is initiated for further processing.