Getting Help with 'SEPA' Questions

What is 'SEPA'?

The Single Euro Payments Area (SEPA) is a self-regulatory initiative for the European banking industry championed by the European Commission (EC) and the European Central Bank (ECB). The aim of the SEPA initiative is to improve the efficiency of cross border payments and the economies of scale by developing common standards, procedures, and infrastructure. The SEPA territory currently consists of 33 European countries -- the 28 EU states, together with Iceland, Liechtenstein, Monaco, Norway and Switzerland.

Part of that infrastructure includes two new SEPA instruments that were introduced in 2008:

  • SEPA Credit Transfer (a Payables transaction in Oracle EBS)
  • SEPA Core Direct Debit (a Receivables transaction in Oracle EBS)

A SEPA Credit Transfer (SCT) is an outgoing payment instrument for the execution of credit transfers in Euro between customer payment accounts located in SEPA.

SEPA Credit Transfers are executed on behalf of an Originator holding a payment account with an Originator Bank in favor of a Beneficiary holding a payment account at a Beneficiary Bank.

In R12 of Oracle applications, the current SEPA credit transfer implementation is based on Version 5 of the "SEPA Credit Transfer Scheme Customer-To-Bank Implementation Guidelines" and the "SEPA Credit Transfer Scheme Rulebook" issued by European Payments Council (EPC). These guidelines define the rules to be applied to the UNIFI (ISO20022) XML message standards for the implementation of the SEPA Credit Transfers in the customer-to-bank space. This format is compliant with SEPA Credit Transfer version 6.

A SEPA Core Direct Debit (SDD) is an incoming payment instrument used for making domestic and cross-border payments within the 33 countries of SEPA, wherein the debtor (payer) authorizes the creditor (payee) to collect the payment from his bank account. The payment can be a fixed amount like a mortgage payment, or variable amounts such as those of invoices.

The "SEPA Core Direct Debit" scheme replaces various country-specific direct debit schemes currently prevailing within the SEPA zone. SDD is based on the ISO20022 XML messaging standards, version 5.0 of the "SEPA Core Direct Debit Scheme Rulebook", and "SEPA Direct Debit Core Scheme Customer-to-Bank Implementation Guidelines". This format is also compliant with SEPA Core Direct Debit version 6.

EU Regulation #260/2012 established the technical and business requirements for both instruments in euro. The regulation is referred to as the "SEPA end-date regulation", and also defines the deadlines for the migration to the new SEPA instruments:

  • Euro Member States: February 1, 2014
  • Non-Euro Member States: October 31, 2016.

Oracle and SEPA

Within the Oracle E-Business Suite of applications, Oracle Payables (AP), Oracle Receivables (AR), and Oracle Payments (IBY) provide SEPA transaction capabilities for the following releases, as noted:

  • Release 11.5.10.x -  AP & AR
  • Release 12.0.x - AP & AR & IBY
  • Release 12.1.x - AP & AR & IBY
  • Release 12.2.x - AP & AR & IBY


To assist our customers in migrating, using, and troubleshooting SEPA functionality, a number of resource documents related to SEPA are available on My Oracle Support (MOS), including:

R11i: AP: White Paper - SEPA Credit Transfer V5 support in Oracle Payables, Doc ID 1404743.1
R11i: AR: White Paper - SEPA Core Direct Debit v5.0 support in Oracle Receivables, Doc ID 1410159.1
R12: IBY: White Paper - SEPA Credit Transfer v5 support in Oracle Payments, Doc ID 1404007.1
R12: IBY: White Paper - SEPA Core Direct Debit v5 support in Oracle Payments, Doc ID 1420049.1
R11i/R12: AP/AR/IBY: Get Help Setting Up, Using, and Troubleshooting SEPA Payments in Oracle, Doc ID 1594441.2
R11i/R12: Single European Payments Area (SEPA) - UPDATES, Doc ID 1541718.1
R11i/R12: FAQs for Single European Payments Area (SEPA), Doc ID 791226.1



I whish there would be a step-by-step instruction on how to setup SEPA for both SCT and SDD.



Posted by guest on November 27, 2013 at 05:39 AM EST #

Thanks for your valued feedback. I was able to locate the following documents that might help you:

1) R12: IBY: White Paper - SEPA Core Direct Debit v5 support in Oracle Payments (Doc ID 1420049.1)

This whitepaper provides information on various features introduced in the Oracle Payments module in Oracle E-Business Suite Release 12 to support SEPA Direct Debit, and describes user considerations related to implementing and using these features, including the setup and transactions flow of SEPA Direct Debit in EBS R12.

2) R12: IBY: White Paper - SEPA Credit Transfer v5 support in Oracle Payments (Doc ID 1404007.1)

This white paper describes the SEPA Credit Transfer V5 functionality supported in Oracle Payments for E-Business Suite Release 12.
EPC has released Version 5 of these guidelines which are effective from 19 November 2011. There are changes prescribed in the usage rules for various data elements in the new guidelines. In addition, some new data elements are also prescribed to be supported as part of SEPA core payments. This document describes the SEPA core implementation solution including the changes prescribed in V5 of SEPA guidelines.

Hope that is of some use, if not, please do come back with comments on what is missing and i'll feed that back to the team that creates the content on SEPA.

Kind regards

Posted by SamanthaF on November 28, 2013 at 04:02 AM EST #

Hi Sam,

thanks for your info.

And yes I have reviewed all the recommended notes. As you say they describe new features. But they do not give setup instructions.
I would appreciate a step-by-step instruction for SCT and SDD to get the full SEPA process running.

Thanks and regards


Posted by guest on December 03, 2013 at 01:55 AM EST #

OK no problem let me pass on your comments to our team that handles the SEPA content and we will see what we can do for you! Drop me your email address to so the team can contact you directly if they need more direction.

Kind regards

Posted by SamanthaF on December 03, 2013 at 03:42 AM EST #

We are implementing SEPA in one of our customer accounts and were told to apply patch set version 6 to environment to make everything work.

Unfortunately there is an error in Account Receivables that we have found through regression testing. This is causing significant issues as we now have to apply patch set version 7 and this means a big increase in regression testing and further liaison with HSBC bank.

We really need to find someone within Oracle who can organise an update to Patch Version 6 to fix the AR problem. Is this something you can help with?

Posted by Steve Priestnall on December 10, 2013 at 05:43 AM EST #

Hi Steve

Can you provide further details on the issue? which patch set 6/7 you are referring to?


Posted by guest on December 12, 2013 at 12:55 PM EST #

Information that is not in the documentation:
If you are using normal Direct Debit and now are moving to SEPA, you have to setup new payment system accounts, one per OU, and you have to setup new Payees because only one FCPP can be attached. However, since you can assign an OU only once to a Payee this means that you also need a new Payment System.
Or do I get wrong?

Posted by guest on January 07, 2014 at 10:06 AM EST #

We've implemented sepa for Oracle financials AR (version 11) and are having a problem with 8 DD requests out of 530. the message appearing is 'Customer bank is invalid with current transaction date', this is reference APP-12178.
We cannot find any differences in setup, has anyoen come across this or the criteria behind this message (I could not find any detail behind how the message is produced).

Posted by guest on January 09, 2014 at 11:01 AM EST #

Please direct any functional/technical questions to the relevant community: or


Posted by SamanthaF on January 10, 2014 at 06:44 AM EST #

Post a Comment:
  • HTML Syntax: NOT allowed

Welcome to the EBS Support Blog where Oracle insiders share news and information about EBS products including new releases, tips and tricks, troubleshooting guides, upcoming webcasts and links to EBS Communities.

Stay Connected



« July 2016