Nine months since the launch of SEPA, Oracle has finally released patch for SEPA Credit Transfer (SCT) for much demanded need for European EBS customer.

High Points of SEPA Project

Lets recap some of high points of SEPA project.

• Objective: Harmonize electronic payment schemes according ISO 20022 rules.
• Countries: Euro zone countries
• Transactions: Only Euro transactions.
• Period: From January 1, 2008.The goal of EPC is to make SEPA mandatory from 2011

SEPA support at Oracle

• Oracle plan is support in major product(EBS,Fusion, Enterprise) lines
• Oracle plan is to support only two types of SEPA messages in most of these products:
  • Customer Credit Transfer Initiation
  • Customer Direct Debit Initiation
    • For Availability of these functionality , check out documentation of respective products.

SEPA@ EBS

Oracle EBS functionality for SEPA messages customer credit transfer initiation (pain.001.001.02) is based on the ISO20022 format. ISO20022 format have these benefits;

• Batch booking
• Grouping : This reduce the number of transmitted files
• Remittance message
• End to end id . This will ease reconciliation and referencing

SEPA messages with Oracle EBS Release dates for 11.5.10 and 12

These are summary of different SWIFT message.

Fig 1: SEPA swift Message

Out of these list Oracle EBS supports for both Customer Credit Transfer(pain.001.001.02 ) as well as Customer Direct Debit (pain.008.001.01)

Here are the summary of information for SEPA out-of-box Functionality in EBS.

Fig 2: Oracle Support for SEPA

SEPA availability in EBS

The SEPA Credit Transfer Initiation Message is available for R11.5.10 via Patch 6741280.Customer using 11.5.10 can get the functionality enable by applying patch.

Wrapping up

• The SEPA out-of-box functionality will be released as patches
• Jan 2008 – Jan 2010 is a official transition period
• Extensive test is required with bank when you are utilizing this functionality.

Will keep you posted for any updates.:)

Similar Post

• THE SINGLE EURO PAYMENTS AREA (SEPA)
• A bit on SEPA – IBAN & BIC

Oracle white paper

• Note:738361.1 :Supporting SEPA Credit Transfer in Oracle Payables for Oracle Applications Release 11.5.10

SEPA in system context have things which is really important.

1. IBAN Code
2. BIC Validation
3. SEPA customer credit transfer, based on the ISO20022 format (XML)

So lets see why IBAN and BIC is so important.Take a note, SEPA schemes use BIC and IBAN codes to uniquely identify bank accounts

IBAN (International Bank Account Number)

The IBAN is provided by the bank servicing the account.

It should not contain any spaces when it is stored electronically. When printed on paper, however, it is usually expressed in groups of four characters, the last group being of variable length.

It consists of:

• The ISO code (two letters) of the country in which the bank account is held and a two-digit check number;
• The domestic Basic Bank Account Number (BBAN) (up to 30 alphanumeric characters).

Total IBAN length may not exceed 34 characters.

BIC (Bank Identifier Code)

The BIC is the unique identifier for banks within the European Union.The BIC is regulated by ISO 9362

It consists of 8 or 11 characters, which include:

• A bank code (four characters)
• A country code (two characters)
• A location code (two characters)
• if applicable, a branch code (three characters)

Similar Post

• THE SINGLE EURO PAYMENTS AREA (SEPA)
• A bit on SEPA – IBAN & BIC

Banks and their corporate customers are about to enter an era of profound global business change.

In January 2008, foundations were laid for a Single Euro Payments Area (SEPA) – a process that aims to deliver harmony in all financial transactions across Europe, and create the conditions for much greater standardization in the movement of money across the world. With this note, lets take a insight view of SEPA.

“The Single Euro Payments Area (SEPA) will be the area where citizens, companies and other economic actors will be able to make and receive payments in Euros, within Europe, whether between or within national boundaries under the same basic conditions, rights and obligations, regardless of their location.”

What is all the fuss about SEPA?

As its well known, Europe has had a common currency and monetary policy since the Euro was introduced in 1999 and Since 1 January 2002, consumers have been making cash Euro payments everywhere in the Eurozone.However, non-cash payments between countries – mainly credit transfers, and credit and debit cards have been expensive and complicated to transact, and a barrier to European monetary integration. There is currently no robust mechanism for a direct debit
between countries.

Therefore, The Single Euro Payments Area (SEPA) project is designed to eliminate national differences in payment instruments and processing infrastructures in Europe,and harmonies fees for cross-border and domestic Euro transactions.

SEPA Journey

It all started in the year 2002 as an initiative to transform European banking Infrastructure by creation of a European Payments Council (EPC). The purpose of such initiative was to define new rules and frameworks and simplify cross border complex payments process across Europe. This project aimed at achieving harmony between national and international payments in non-cash mode. European banking industry used to face severe losses in the process of cross border transactions. This led the banks to create the EPC.

SEPA aims at providing a common platform for all the associated members to make and receive payments in a single currency (i.e. euro) within Europe irrespective of their base location. SEPA project involves key members like European Commission (EC) and European Central Bank (ECB) supported by the European Payment Council (EPC).

About European Payments Council (EPC)

It is a European governing body, which consists of more than 50 banking institutions formed to standardize the payments mechanisms in Europe. It is the decision-making and coordinating body, which is responsible for issues related to payment systems in the European Banking industry.

Mission SEPA

• It aims to provide a single area for all payments across Europe.
• Single Account, single card mechanisms irrespective of country

SEPA Project

As per website note, SEPA implementation schedule was split into three (overlapping) phases from a banking perspective:

• Design Phase (January 2004 -June 2006)
  • Establishment of the rules, practices and standards for new payment instruments.
• Implementation Phase (June 2006 –November 2009)
  • The banks design and test new product offerings under SEPA
  • Participating countries have to set up national implementation and migration bodies to ensure smooth roll out of the SEPA infrastructure
  • Launched in January 2008:
  • SCT (SEPA Credit Transfer)
  • SCF (SEPA Cards Framework)
  • Scheduled for launch at end of 2009:
  • SDD (SEPA Direct Debit).
• Migration Phase (January 2008 – December 2010)
  • The cross-over period between the old and new instruments, ensuring a gradual market-driven migration to SEPA
  • This phase includes set-up of PEACHs (Pan-European Automated Clearing House).

Therefore this third phase is more meaningful to corporate who are running there accounting system in ERP and they must be make sure they should not impacted by product limitation and avoid penalties as there is Europe wide mandatory requirement for non-compliance. These penalties would be leveled for each individual payment, which would be substantial across 16 countries.

SEPA Consist of:

• The single currency
• A single set of euro payment instruments – credit transfers, direct debits and card payments
• Efficient processing infrastructures for euro payments
• Common technical standards & business practices
• A harmonized legal basis
• Ongoing development of new customer-oriented services

SEPA coverage area

As SEPA will be introduced on a phased basis. Thirty-one countries are currently committed to SEPA: the 27 EU member states, the three other European Economic Area countries (Norway, Iceland and Liechtenstein) and Switzerland.[source Website]

Currently only 16 counties under coverage area.

• Austria
• Belgium
• Germany
• Spain
• Finland
• France
• Greece
• Ireland
• Italy
• Luxembourg
• Netherlands
• Poland
• Portugal
• Sweden
• Slovenia
• United Kingdom

What are the different payment Instrument that cover in SEPA

There are four types of payment Instrument

1. SEPA Credit Transfer
2. SEPA Direct Debit
3. SEPA Card
4. SEPA Cash

Standardization -Addressing the SEPA schemes Requirements

The SEPA payment platform supports different schemes for both credit transfers and direct debits.

New schemes have been developed for credit transfers and direct debits that describe the technical and functional protocol for exchanging credit transfers and direct debits between two banks using formats and procedures. The formats are based on the ISO 20022 XML standard developed by SWIFT.

SEPA requires common information (‘data elements’) for SCTs and SDDs, outlined in the SEPA Credit Transfer Rulebook and SEPA Direct Debit Scheme Rulebook respectively.

SEPA within ERP

SEPA will make it possible for ERP systems to be better integrated and to communicate better with the bank.

SEPA@Oracle

SEPA support is required in Oracle in these products;

• EBS 11.5.10, 12, 12+
• Fusion

Out of these EBS support started a few days back, which will be discussed in other post.

Possible changes with SEPA

• Euro BankAccounts :
• Cash Management Structures
• Banking Interfaces

Further References

• SEPA Vision
• Making SEPA a reality
• Roadmap towards SEPA