I worry we may have weaknesses in our cash ordering process, that we don't have the right access levels for those that place orders or that employees may be ordering too much. How can I place limits on the amounts individuals are allowed to order from the Fed?
What if an employee allows a business to have a larger ACH origination limit than is authorized? Is there a way, outside of the operations area, to double check that the established caps are being used?
Let's say an employee in a rush to go home submits an ACH batch with the 9-digit routing transit number mistakenly entered into the credit dollar amount field. Can I enforce double checks before the file enters the ACH network?
If we miss a check return window, we could end up responsible for a loss if the depositor withdraws the money before the check clears. Is there a way to accelerate check receipt and thus the return process?
I worry I won't be as fast as the check fraudster. Is there a way to accelerate our check deposits and as a result potentially receive any returns more quickly?
What if fraudsters try to send ACH transactions to an account known to have been compromised and subsequently closed? Is there an easy way to be alerted to such attempts?
We don't want to be caught off guard by a large incoming ACH debit. Can we be alerted?
Not all ACH originators are equally credit worthy. I want to closely manage ACH origination risk. How can I track and control originators' activity in near-real time?
We know ACH originators can sometimes initiate more than we intend to allow, either by mistake, over the course of multiple days in a row or through several different entry points such as online banking systems and a separate payroll processor. Is there a way for us to control our originator's combined activity on our RTN before it enters the ACH network?