|
Most Netting Centers transfer funds to and from their netting
participants at the end of the netting cycle to settle the net positions
calculated in the netting process; frequently this can be done very simply by
transferring the net position information into the company's treasury workstation
using mapped preformat codes representing the netting participant and payment
currency, while other netting centers might generate a fully-formatted SWIFT
message or other proprietary bank payment format, which requires including
complete details of the payment path. When a fully-formatted
payment is required, it is becoming increasingly important that the bank and
account information be validated prior to payment initiation, not only to make
sure the payment reaches the beneficiary without delay (an important element of
any payment process but especially so for netting in which all payments are
expected to settle on the same date), but also to keep costs to a minimum by
avoiding expensive repairs. Therefore, for all fully-formatted cross-border
payments emanating from a multilateral netting system it is essential that the
payment includes a valid Bank Identifier Code (BIC, often also referred to
as a SWIFT code) for the beneficiary bank. In Europe, the EC
(European Commission) created the Single Euro Payments Area (SEPA)
initiative with the goal of removing the barriers to movement of funds across
borders, and to thereby reduce the cost of euro payments to the level of domestic
transfer costs. SEPA requires that payment include not only a valid Bank
Identifier Code, but also a valid International Bank Account Number (IBAN)
that conforms to standards administered by the European Committee for Banking
Standards (ECBS). To enable our clients to meet SEPA
requirements for IBAN and BIC code validation in cross-border payment instructions
with the euro area, and to generally ensure that BICs used in our clients' payment
instructions are valid, EuroNetting now includes both BIC and IBAN valdation
services.
|