Beruflich Dokumente
Kultur Dokumente
3. SEPA V5 updates
4. Mapping the attributes for SEPA messaging
Group Header
Payment Information
Credit transfer transaction information
2.
The Payment Instruction Creation Program (PICP) is enhanced to group the payments within the Payment
Instruction files based on fixed parameters. It includes stamping a logical group ID on each of the payment.
The BIC and IBAN validations are handled in the Oracle Cash Management application.
For Batch Booking, Manual and Automatic reconciliation logic is enhanced to include reconciliation
based on the payment groups described above.
Seeded XML Publisher Templates
Two new XML Publisher Templates
IBY_SEPA_CREDIT_INIT_TEMPLATE_STR_REM and IBY_SEPA_CREDIT_INIT_TEMPLATE
are seeded for SEPA Credit Transfer Initiation message with Structured and Unstructured remittances.
Seeded Formats
Two new Formats
IBY_SEPA_Credit_Init_Format_Strd and IBY_SEPA_Credit_Init_Format_UnStrd are seeded for SEPA
Credit Transfer Initiation containing Structured and Unstructured remittances.
Seeded Payment Process Profiles
Two new Payment Process Profiles
IBY_SEPA_MIXD_ST and IBY_SEPA_MIXD are seeded to support SEPA Credit Transfer Initiation
containing Structured and Unstructured remittances.
Predefined Validations attached to SEPA Credit Transfer Payment Format
For a payment to be sent to a bank in SEPA format there are some basic conditions and validations that
must be met. The validation architecture in Oracle Payments is used to ensure a payment included in the
SEPA format satisfies the conditions. This in turn ensures straight through processing (STP).
The following data is validated:
The transaction currency is in Euro. This has been ensured by including EUR as the only valid
currency for seeded Payment Process Profiles.
The Bank charge bearer is SLEV.
The Payer address fields are entered.
The IBAN of internal bank account and supplier bank account is present.
The BIC code for internal and the supplier bank branch is present.
The initiating party name and identification are present.
3. SEPA V5 updates
As per SEPA V5 guidelines, there are changes prescribed in the usage rules for some of the data elements.
These changes are mainly related to the xml tags to be populated in the output file. The following changes
are included as part of SEPA implementation:
Group Header:
Grouping - Grouping Mode is no more required to be populated. Therefore, the grouping mode is
removed in the payment output file.
Batch Booking The batch booking is populated in the Payment Information Block.
Initiating Party - The identification of the initiating party is passed under Other in Organisation
Identification.
Number of Transactions The number of payment transactions included in the payment information block
is populated in the payment output file.
Control Sum The sum of payments included in each payment information block is populated.
Debtor and ultimate debtor: The identification of the debtor is mapped to BIC of the internal bank branch.
The identification of ultimate debtor party is passed under Other in Organisation Identification in the
payment output file.
Credit Transfer Transaction Information block:
Creditor and ultimate creditor: The identification of creditor and ultimate creditor is passed under Other in
Organisation Identification in the payment output file.
Group Header
This is the first block in the SCT message. The Group Header consists of the elements like: SCT Message
Identification, CreationDateTime, BatchBooking, NumberOfTransactions, Grouping, Initiating Party etc.
The mapping of the data elements is described below.
SCT Message Identification The Payment Instruction Reference Number is mapped to this
field. This is system generated.
Creation Date and Time This is the system generated date and time stamp.
Number of Transactions This is the count of number of payments in the output file.
Control Sum The Absolute total of payment amounts is mapped to this data element.
Initiating Party The name and identification of Initiating Party are required as per SEPA
guidelines. The mapping for Name and Identification is described below:
- Name: The Legal entity is mapped to the Name.
- Identification: The identification in populated in the following order
- 1. Tax Registration Number if available, else
- 2. Legal Entity Registration Number.
- The identification is populated in <Othr> tag under the Organisation Identification.
Control Sum The sum of payments included in each payment information block is populated.
Category Purpose When the value for the Payment Function is PAYABLES_DISB the
value SUPP is passed for this data element.
Requested Execution Date The Payment Date is mapped to this data element.
Debtor The name, address and identification of debtor are required elements for SEPA core
payments. . The mapping for name, address and identification is described below:
- Name: The Legal entity is mapped to the Name.
- Address: The Legal entity address is mapped to the Address.
- Identification: The BIC of internal bank branch is populated in identification.
Debtor Account The Identification and Currency of the debtor account is required as per SEPA
guidelines. The mapping for these elements is:
- Identification: IBAN of the internal bank account is passed for this element.
- Currency: Currency of the internal bank account is passed for this element.
Debtor Agent The BIC of the bank branch of internal bank account is mapped to this element.
Ultimate Debtor The name and identification of ultimate debtor are required as per SEPA
guidelines.
- Name: This is mapped to the Invoice Legal Entity if it is same for all the invoices selected
for payment else a hard coded value Multiple Ultimate Debtor is passed.
- Identification: If the Invoice legal entity is the same for all the invoices selected for payment,
then Tax registration number is populated in the <Othr> tag under the Organisation
Identification. If it is not present, the Legal entity registration number is populated in the
<Othr> tag under the Organisation Identification.
If the Invoice legal entity is different on the invoices selected for payment, then a hard coded
value Multiple Ultimate Debtor is passed in the <Othr> tag under the Organisation
Identification.
Charges Bearer A hard coded value SLEV is passed for this data element. This is as per the
requirement in SEPA guidelines.
Payment Identification The Instruction Identification and End to End identification are
required as part of SEPA core payments.
The Payment reference number is mapped to both instruction identification and end to end
identification.
Payment Type Information This data element is populated in payment information block as
described in the usage rules of SEPA guidelines.
Instructed Amount The Payment Amount and Payment Currency are mapped to this data
element.
Charge Bearer This data element is populated in payment information block as described in
the usage rules of SEPA guidelines.
Ultimate Debtor - This data element is populated in payment information block as described
in the usage rules of SEPA guidelines.
Creditor Agent The BIC of the Remit to Bank Account is mapped to this data element.
Creditor The Name, Address and Identification are required for creditor. The mapping for
these elements is:
- Name: This is mapped to Supplier Name.
- Address: This is mapped to the address of Supplier Site, Address line 1 and 2 are
supported per the requirement of SEPA guidelines.
Identification: The identification of supplier is provided in the following order as given
below:
1. If Tax Registration Number is available it is populated in the tag <Othr> under the
Organisation Identification
2. If the Tax Registration Number is not present, the identification is populated in
<Othr> under the Organisation Identification in the following order:
o Legal entity registration number or
o Supplier number or
o Party number or
o First party reference
Ultimate Creditor The ultimate creditor is mapped to the Remit to Supplier. If Remit to
Supplier information is not available, then it is mapped to the Supplier. The mapping is
same as for creditor.
Creditor account The IBAN of the Remit to Bank Account is mapped to this element.
Payment purpose The Payment Reason is mapped to this element.
Remittance information The remittance information can be either Structured Remittance or
Unstructured Remittance. SEPA guidelines prescribe a 140 characters limit for the
remittance information including the tag size.
o Structured remittance - The Creditor reference and Creditor reference type are required as
data elements in SEPA core payments.
- Creditor Reference Type:
Code: SCOR (Structured Communication Reference) is the value prescribed to
be passed for this data element. Therefore a hard coded value SCOR is passed
for this field.
- Creditor Reference: The Invoice Number is passed for Creditor Reference.
Change Record
Date
Description of Change
Created document.
Oracle Corporation
Author and Date
Patruni Suresh, November 2011
Copyright Information
Copyright 2011, 2012 Oracle. All rights reserved.
Disclaimer
This document in any form, software or printed matter, contains proprietary information that is the exclusive
property of Oracle. Your access to and use of this confidential material is subject to the terms and conditions of your
Oracle Software License and Service Agreement, which has been executed and with which you agree to comply.
This document and information contained herein may not be disclosed, copied, reproduced or distributed to anyone
outside Oracle without prior written consent of Oracle. This document is not part of your license agreement nor can
it be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates.
This document is for informational purposes only and is intended solely to assist you in planning for the
implementation and upgrade of the product features described. It is not a commitment to deliver any material, code,
or functionality, and should not be relied upon in making purchasing decisions. The development, release, and
timing of any features or functionality described in this document remains at the sole discretion of Oracle.
Due to the nature of the product architecture, it may not be possible to safely include all features described in this
document without risking significant destabilization of the code.
Trademark Information
Oracle, JD Edwards, PeopleSoft, and Siebel are registered trademarks of Oracle Corporation and/or its affiliates.
Other names may be trademarks of their respective owners.
Update Date dd-mon-yyyy
Expire Date dd-mon-yyyy (ignore after this date)