Building the proper safeguarding workflows between the Bank of Lithuania and the partner bank
Any credit or debit on the Bank of Lithuania settlement account must be attributed to specific customers so that the PI or EMI can update individual customer balances accordingly and know at all times how much funds each customer holds with the PI or EMI.
This step is not new, as CENTROlink’s customers must already do so in their current safeguarding setup on the Bank of Lithuania’s FC accounts.
The
European regulation mandates that if a customer receives a payment, and the funds corresponding to that payment are not withdrawn by the customer or used to send another payment, the PI or EMI must safeguard these funds “by the end of the next business day.”
This means that CENTROlink’s customers will need to transfer the right amount of funds from their Bank of Lithuania’s FC accounts to their partner bank safeguarding account every day and properly track and reconcile these payments to ensure the proper tracking of individual customers’ funds at any given time.
As safeguarded funds are held on a different account than the settlement account, or FC accounts in CENTROlink’s case, all customer deposits are not instantly available on the FC account to settle outgoing SCT or SCT Inst or incoming SDD.
These accounts being held at two different partner banks can make the problem even more complex as the transfer between the safeguarding and settlement accounts can take some time.
Automating the liquidity management of the settlement accounts is, therefore, critical. There are several levels of automation possible, from triggering automated cash sweeps from the safeguarding account to the settlement accounts whenever the settlement accounts balances reach a given minimum value to calculating automated cash sweep amounts based on customers' booked payment orders and current settlement accounts balances, to adding learnings from historical data to the computation.