Download presentation
Presentation is loading. Please wait.
1
Single Euro Payments Area (SEPA)
Implementing SEPA in BaanIV environments
2
Implementing SEPA in BaanIV environments
Introduction The Single Euro Payments Area (SEPA) is the area where citizens, companies, and other economic participants can 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. The geographical scope of SEPA encompasses the 27 EU member states, Iceland,Liechtenstein, Norway, and Switzerland. SEPA is an EU-wide policy-maker-driven integration initiative in the area of payments, which is designed to achieve the completion of the EU internal market and monetary union. After the introduction of euro notes and coins in 2002, the political drivers of the SEPA initiative – EU governments, the European Commission, and the European Central Bank – focused on harmonizing the euro payments market. Integrating the multitude of national payment systems that exist today is a natural step towards making the euro a truly single and fully functioning currency. Starting february 1, 2014 all payments-to-be-done (incoming/outgoing) should be sent to the bank in the PAyment INitiation (‘PAIN’) format (incasso, btl91, clieop formats will no longer be valid) 27 February, 2019 Implementing SEPA in BaanIV environments
3
Implementing SEPA in BaanIV environments
SEPA - Concepts IBAN = International Bank Account Number. Belongs to a person/institution The IBAN always starts with the International Country Code (2 characters) Then a control number calculated from the BankId and the accountnumber (2 digits) Then the BankId Then the accountnumber. The length of the account number is set by country. If the number is too short leading zeros will be added. Bank identification. Two concepts: BIC = Bank Identification Code. The BIC is relevant for all SEPA countries BankId identifies the bank that is handling the account. The BankId differs by country: NL : the BankId = the first 4 chars of the BIC BE : the BankId = a 3 digits number DE : the BankId = the BankLeitZahl Notes on the BIC and the BankId: In some countries the BankId has always been part of the Accountnumber (Belgium, Germany). In that case determining the IBAN is easy. In the Netherlands this is not the case. NL accountnumbers should always be sent to This service determines the correct BankId by checking a table with all NL accountnumbers. Then the BIC and the IBAN are sent back In some countries the BIC is handled in a rather complex way (Germany). Determining the correct BIC should be done feeding the BankId and the accountnumber to a SEPA account converter. A good converter tool for DE is available at For other countries check 27 February, 2019 Implementing SEPA in BaanIV environments
4
SEPA & BaanIV – Software & Data
The SEPA functionality is present in servicepack 25 and higher. It should be possible to: Give in BIC (banks) and IBAN (for suppliers, customers and the own company) Maintain the XML layout (the PAIN format) of the files for incoming (incasso) and outgoing payments; the PAIN format is standard but nevertheless there’s room for specific demands of countries and/or banks Generate incoming (incasso) and outgoing payments files in the PAIN format For companies working with BaanIV on a lower servicepack level a “backported solution” can be delivered Software components related to SEPA will be adapted to fit in the existing servicepack level. During “backporting” only known customizations & developments will be taken into account. It is the responsibility of the company to see to it that the merge of the backport with other customizations & developments is done correctly. 27 February, 2019 Implementing SEPA in BaanIV environments
5
SEPA & BaanIV – QSEP converter (IBAN/BIC)
A SEPA converter tool (QSEP) has been developed for BaanIV environments. QSEP is designed to simplify the determining of IBAN/BIC codes & consists of: Queries to export data from the BaanIV environment (BankAddresses, BanksBySupplier, BanksBy Customer) The QSEP database (MS/Access) Queries to import the data into the BaanIV environment (BanksBySupplier, BanksByCustomer) QSEP steps: Export data from the BaanIV environment Import the data into the QSEP database Generate exportfiles for NL accounts to be sent to the available SEPA converter tool. This tool will determine IBAN and BIC and send the files back. Next they will be imported in QSEP For other accounts QSEP will determine BIC and IBAN on its own Export data from QSEP to be imported in BaanIV Import data into the BaanIV environment 27 February, 2019 Implementing SEPA in BaanIV environments
6
QSEP – Quint’s SEPA converter
27 February, 2019 Implementing SEPA in BaanIV environments
7
Implementing SEPA in BaanIV environments
SEPA & BaanIV – Steps Implementing SEPA in BaanIV environments consists of the following steps: Technical setup Contact 3rd party to deliver the appropriate “backport” 3rd Party will analyze the BaanIV environment to determine the exact situation of the standard software 3rd Party will prepare & deliver the backport Unpack the backport & check which components are concerned. See allcomponents.xlsx for an example. Merge the backport components with existing customizations / developments Functional setup Import BIC/IBAN codes Follow the steps described in the BaanIV SEPA Master Data Setup document Testing Test the processing of incoming/outgoing payment XML files (PAIN) 27 February, 2019 Implementing SEPA in BaanIV environments
Similar presentations
© 2025 SlidePlayer.com. Inc.
All rights reserved.