|
Carruba urged attendees to develop a comprehensive contract with their corporate customers. He said the contract should include provisions for assigning liability and a host of other issues such as hardware and software, image quality, eligible items, receipt of files, deposit and file limits, deadlines, method of presentment and availability of funds. It should also contain warranties and indemnification provisions, clauses that clearly spell out what the customer will guarantee to the bank in the imaging process.
All too often, Carrubba said, banks resort to grabbing a boilerplate agreement off the Internet, or using one from another bank. Many of these contracts don’t offer the protection a bank needs with RDC, potentially opening it up to big losses, he added.
Since image quality will be determined by the type of scanner used, customers should not be allowed to purchase the least expensive scanner in the marketplace, Carrubba added. This is likely to happen if the agreement fails to require the customer to use hardware that’s certified by the solutions provider, he said.
The agreement should also define the point when a bank acknowledges receipt of a file from a customer, Carrubba said. But such acknowledgement should not mean that a bank acknowledges that the file contains no errors or that the bank is responsible for the information in the file, he added. The agreement should state that credit given for the file is provisional and that the customer secures the bank for any loss sustained by the bank for acceptance of the file, he said.
Carrubba also advised banks to gird their systems for fraud. “A financial institution should not offer RDC to every customer that wants it,” he said. “There needs to be some type of due diligence on that customer to make sure they qualify for the service.”
(For more on RDC, see “Making the Case for Remote Deposit Capture” in the May/June 2006 issue of BAI Payments Strategies.)
|