2.2.8 EU Regulation - Customer Identifier Changes

Defaulting Customer Identifier for Outbound Transactions in Compliance with REGULATION (EU) 2023/1113

• To comply with REGULATION (EU) 2023/1113, the system now supports defaulting customer identifier(s) from customer records in Core systems for outbound transactions initiated in Generic Wires, SCT, and SCT Inst.
• Customer Identifier details are fetched from the Core Account system during transaction or bulk file processing if the debtor identifier is not already present.
• A new system parameter, DEFAULT_CUST_IDENTIFIER, is introduced to enable this feature.
• The existing ECA Interface screen (Function ID: PMDINECA) is used to maintain REST API details of the Core system, with Interface Type set to Account Inquiry.
• Out-of-the-box support is available for the FCUBS API /CustomerAccDetailService/CustomerAccDetail/QueryCustacctDetail using the latest FCUBS version.

For outbound transactions, the following identification logic is applied based on customer type:

Corporate/Bank Type Customers: The identifier is chosen as BIC, LEI, or Other Organization ID.

Individual Customers: The identifier is chosen as Private Other ID, or a combination of Birth Date, City of Birth, and Country of Birth.

The following transaction screens are covered by this logic:

• SCT Outbound Transaction Input (Function ID: PADOTONL)
• SCT Instant Outbound Transaction Input (Function ID: PFDOTONL)
• Generic Wires Customer Transfer screens

Transactions submitted without a debtor identifier are routed to the Repair queue. Bulk file batches without debtor identifiers are moved to the PE queue, where they can only be cancelled.