When a bank sends ACH entries for a business or another originator, the bank can face settlement, credit, fraud and operational exposure before the underlying activity is complete. Originator exposure controls connect customer underwriting with the amount and timing of entries the bank is willing to release.
The originating bank stands behind the entries it sends
An originating depository financial institution transmits ACH entries into the network under its agreements and the applicable rules. If an originator cannot fund a credit file, sends unauthorized debits or generates returns and claims, the bank may face financial, compliance and operational consequences.
The exposure is not limited to one file's face value. Timing across processing windows and settlement dates, return rights, reversals and related customer activity can create a larger or longer-lived position than a simple daily total suggests.
Underwriting establishes the expected activity
Before enabling origination, the bank evaluates the customer's business, ownership, financial capacity, purpose for using ACH and control environment. It identifies expected Standard Entry Class codes, debit and credit activity, volumes, values, settlement timing, counterparties and any third-party sender or service provider.
The review also considers fraud, authorization, sanctions, return and reputation risks. A legitimate business model can still require tighter controls when activity is volatile, delayed-settlement exposure is high or the bank has limited evidence of the customer's operating history.
Limits connect approved risk with unsettled activity
The bank sets approved limits that may distinguish a file cap, a daily origination amount and the cumulative value still outstanding across settlement dates. Credit and debit entries can create different exposures, so the measurement should reflect how and when funds become final rather than treating every entry identically.
Limits are tied to the originator and any relevant group or processor relationship. They include owners, approval authority and review dates so a temporary accommodation does not silently become the customer's permanent operating capacity.
Files are monitored before release
Origination-monitoring tools compare submitted batches with approved limits and expected patterns. An unusual amount, new entry type, rapid volume increase or limit exceedance can cause a file to be pended or rejected until an authorized reviewer understands the activity and available funding.
Depending on risk, the bank may require prefunding, collected balances, collateral, reserves, delayed release or dual approval. These measures are proportionate protections, not substitutes for validating the customer's authority and the legitimacy of the underlying entries.
Ongoing review adjusts controls as evidence changes
The bank compares actual activity with the approved profile and reviews returns, unauthorized claims, exceptions, account balances, financial condition and control changes. Material changes can require new underwriting, revised limits or suspension before losses accumulate.
Limit exceptions are documented with a reason, duration, conditions and approving authority. Repeated urgent overrides can indicate that the profile is outdated or that the relationship is operating outside risk appetite, rather than proving that the limit should always be raised.
Read the primary material
Banking Explained prioritizes regulators, official publications and first-party announcements.