My Oracle Support Banner

SEPA Insta Network Rule Not Considered From 2nd Txn When Pain001 File Contains More Than One Txn (Doc ID 3017191.1)

Last updated on MAY 28, 2024

Applies to:

Oracle Banking Payments - Version 14.7.0.0.0 and later
Information in this document applies to any platform.

Symptoms

On : 14.7.0.3.0 version, Implementation Support

ACTUAL BEHAVIOR
---------------
SEPA insta network rule not considered from 2nd txn when pain001 file contains more than one txn


ISSUE:
----------
1) System did not validated the IBAN and BIC combination for sepa instant.

2) 2nd transaction, even when iban and BIC are belongs to same, then system generated SEPACT network.

 

EXPECTED BEHAVIOR
-----------------------
1) System should validated the IBAN and BIC combination for sepa instant when IBAN validation check in enabled at network level.

2) 2nd transaction should also generate sepa instant network as it is satisfying the network rule condition


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Upload pain001 with 2 or more transaction for sepa insta (one txn has where creditor BIC and IBAN not matched, 2nd txn has valid).

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.