The International Bank Account Number (IBAN) was intended to help make cross-border euro payments more efficient. Interestingly, the establishment of the IBAN also has had the unintended consequence of limiting payment options for corporates. How is it that the establishment of a standard meant to streamline payment processing would also limit options for customers making payments? The dilemma of the IBAN revolves around the “cross-border” aspect.
Here’s what’s happened...In order to meet SEPA mandates, many corporates utilizing enterprise resource planning (ERP) systems to maintain profiles on their vendors have replaced the legacy account numbers with IBANs. But, in many ERP systems, there’s only room for one account number per vendor. So, with the legacy account number out and the IBAN in, the information needed to create payments that don't cross borders is no longer in the system. What’s a corporate to do?
The answer lies within the IBAN itself. The legacy account number is in fact concatenated within the last part of the IBAN, but deriving it is no simple task. There are numerous variations, often by country or even by bank, that make the seemingly straightforward task of IBAN decryption anything but.
Whether this is a short- or long-term issue remains to be seen. Some believe that national payment systems will begin utilizing the IBAN for their local payments, which would eliminate the dilemma altogether. This is already true in Italy where, as of January 1, 2008, the ABI (Italian Banking Association) has made the IBAN the standard of account identification for use in cross-border as well as domestic payments. If this trend continues, the need for a legacy account number will be moot. Such a move would go a long way toward allowing organizations beyond the banks to realize the efficiencies promised by SEPA.
|