In the whole EU the SEPA change in Feb. 2014 will be divided in three different types of change:
- change the number system from the account system to IBAN and BIC
- change the bank-communication from DTAUS to XML (ISO20022)
- change to the SEPA MSatic.The goal of the work contracted under this appendix is to analyze, implement, test, deploy and complete the project “SEPA Application”.
The changes are driven by law and in Germany, where more than 80% from the daily direct debits works, is the pressure to change very high.
Vericos and their customer decided to develop an encapsulated new software system. This system will be responsible to store and administer the declared data set from a SEPA mandate.
SEPA MS in main only support the interface between the insurance applications and itself (invoke by call about WEB SERVICE). The SEPA MS will be reactive and need an event (function no. and invoke no.), with data, to start working.
The interface between the insurance applications and the SEPA MS was XML based and the connector from the SEPA MS was designed like web service architecture.
The SEPA MS has to explain the interface, the expected datasets per XML and answered datasets. Every function will be declared and will get a description for integration.
The most rules and requirements for the functions are given by European or German law. Integration functionality is grounded by the business practice from German insurance companies.
The SEPA MS will know three types of invoking:
- Call by WEB SERVICE from other applications – the main use from the system
- Volume Interface Logic – Batch calls which will work with thousands of records
- HTML Interface for single usage – this will use for tests and a seldom usage by customer
In addition there are a lot of different rules, which are administered in the master data (creditor). They have to be interpreted by the function or at the beginning of the function. The different Rules are divided as followed:
- Outline Rules
- Data Rules