Blog article
See all stories »

SEPA: The Future is Integration Management

It’s not quite so fashionable to talk about SEPA these days. After all – aren’t we all wishing the rules and solutions were are all defined and implemented? But there’s still a fundamental challenge that banks (and corporate treasuries) face: integration among both legacy formats and legacy systems. Payments hubs are still often discussed as a solution, but the stark reality is that even after several years of industry discussion, few banks have implemented a payments hub to address SEPA.

Integration Frameworks
Don’t get me wrong, I still believe in the value of a hub. The centralization of processing to ‘break down the silos’ is still a major issue as banks strive for efficiency and cost savings. However, the effort involved to implement a hub strategy is considerable and can make these projects very daunting (especially if no application is replaced). One approach that is gaining more traction is the payments framework as a means of managing the flow of SEPA transactions between new and legacy components. This enables banks to start on a technology renewal path in a phased approach, with or without a hub. A big-bang replacement of payment processing is no longer required as flows can be migrated in phases by reconfiguring the integrated workflows as new systems and payment schemes become available.


Comments: (2)

Barry Kislingbury
Barry Kislingbury - ACI Worldwide - London 16 August, 2010, 14:20Be the first to give this comment the thumbs up 0 likes

Hubs versus engines is an interesting topic and one that traditional engine vendors also seem to find confusing - or help make confusing!  In my experience ‘engine’ suppliers seldom think of the requirements to integrate the engine into the enterprise, and this is where the cost and complexity comes from.  Only a very few can afford this approach now days, if any.  This is why they have all jumped on the ‘hub’ band wagon which is much more attractive.  A payment hub does consider the integration, workflow and management needs of payments flows, but it does not do all the processing, often continuing to use the legacy applications strengths, but normalizing the process and centralizing the management using new technology.  But it is much more that a pure integration play or framework (which means you have to build everything) as the hub must understand payments and what needs to happen to them.  The hub is therefore much easier to implement in a phased manner than an engine or a framework, and success can be measured. 

As for SEPA, until an end date set, the majority of the industry will continue to wait and see, which I also don't see as a reason banks are not upgrading their payments.  In fact we are seeing a growing number of banks realising that they need to upgrade and that real payment hubs offer a viable way forward to big engine projects.

A Finextra member
A Finextra member 17 August, 2010, 16:47Be the first to give this comment the thumbs up 0 likes

I completely agree that bank take up of systems to address SEPA has been disappointingly slow and a phased process to migrate from legacy systems to a standard approach offered by the SEPA rulebook can help banks to make the jump.

Currently many banks are playing the waiting game on who takes the first step to make the changes and test the new approach, but this can’t go on. Banks must be more proactive and make some decisions regarding deadlines for migration. A bank with a system which fully supports SEPA will have a superb opportunity to capture a large portion of the market as corporates will migrate first to whichever bank enables SEPA payments.

In addition, the four corner model outlined in the SEPA rulebook needs to be more flexible and should include corporates and solution providers. Take up will be a lot quicker, if corporates can submit directly to ACHs through payments solutions.

We’re already seeing corporates looking for tailored payment solutions in preparation for SEPA Direct Debit (SDD). To this end, it will be corporates that will drive SDD as they will be ready to handle the changes.