The implementation of the SEPA standard required a complete review of the way in which direct debits were processed: each Corporate then became responsible for their management and had to integrate new information such as the type of mandate, the Unique Reference of the Mandate and the 'SEPA Creditor Identifier.
With its qualities, NEOFI was quickly placed as an intermediary between the different IS applications to collect sampling data, control it and above all enrich it with the new expected information without affecting the application infrastructure already in place. The ease of its configuration made it possible to limit the financial and human investment generated by this new regulation.
To carry out this SEPA migration, each customer had to equip themselves with a money order library which is used to control and enrich the direct debits with new data before sending them to the bank via the banking communication platform.
However, for each client the situation is different: For one, the SaaS mode money order library expects a direct debit file in a proprietary XML format; at another, we favored an internal development which adds to the suite of 160 regulatory characters of the old sampling format produced by the ERP the new regulatory information to form a line much longer than the standard…
Without affecting the existing system, the NEOFI rules engine retrieves information whatever the format and ensures the consistency and SEPA compliance of the aggregated information.
For this, in the first case cited above, NEOFI designs an XML file as expected by the money order library which thus automatically enriches certain fields then NEOFI converts this file into SDD pain.008 format and adapts it to the specificities of each bank .
In the second case, we defined in NEOFI Link rules for reading the ''cfonb160+'' file modified by the ERP to deduce the necessary regulatory information:
· Conversion of RIB into IBAN,
· Search for the BIC by connecting NEOFI Link to the SWIFT IBAN+ directory
Then NEOFI builds the SDD direct debit file in pain.008 format and adapts it to the specificities of each bank.
While standard software publishers tend to impose their formats and working methods, the agility, malleability and ergonomics of the NEOFI rules engine allows each client to decide the best way to carry out their project:
· Total internalization of tool settings
· Work in collaboration with the publisher NEOFI
· Complete outsourcing to the publisher NEOFI
Whatever the way of managing your project, the logic of NEOFI's configuration always remains very intuitive and easily modifiable, which is why it was easy to adapt:
· Project unforeseen circumstances, such as the BIC becoming optional, requiring the addition of an IBANONLY mention to inform the bank,
· With the evolution of the SDD diagram (it has become superfluous to distinguish first and recurring),
· Has a parallel project on the 2nd presentation of unpaid direct debits.
