Your ACH Payment Says Complete. Is It?

A bill-payment screen changes from Pending to Complete.

The word is reassuring. It is also incomplete without one more question:

Complete for whom?

The company may mean it accepted the instruction. Its bank may mean the ACH file passed validation. An ACH operator may have processed the entry for a settlement window. The receiving bank may have posted it to an account. The customer may mean the balance changed.

Those are related events. They are not the same event.

ACH moves instructions between financial institutions through operators such as FedACH. The work follows transmission, distribution, and settlement schedules. Same Day ACH has multiple processing windows; other eligible entries settle on a later banking day. A product can update its screen before or after any one of those boundaries depending on the promise it has chosen to make.

Settlement is an important boundary because funds are exchanged between institutions. It still does not mean that every ACH payment has become unchangeable.

Returns are part of the rail, not evidence that the rail malfunctioned. An entry may return because an account is closed, has insufficient funds, contains invalid information, or was not authorized. Different reasons carry different deadlines. Some returns move quickly after settlement; certain unauthorized consumer debits can be returned on a much longer timeline.

That later return does not erase the original event. It adds another financial event that sends the obligation back through the network.

This is why a single status such as complete can become dangerous inside a payment system. It compresses several questions into one label:

• Did we record the customer’s instruction?
• Did our bank or processor accept it?
• Did the ACH operator process it?
• Did interbank settlement occur?
• Did the receiving bank post it?
• Can it still return?

The customer interface may not need to display all six. The underlying system still needs to know which answer it has.

A more honest product might distinguish scheduled, submitted, settled, and returned. The exact vocabulary depends on the use case and what evidence the provider exposes. What matters is that the application does not present its own progress as proof of the entire network’s state.

There is no universal moment when the word complete becomes safe for every participant. A payroll recipient cares when funds are available. A biller cares whether the debit remains good. A bank cares about settlement and its return obligations. An operations team cares whether its ledger agrees with external reports.

The screen may need one word. The system underneath needs the whole sentence.

Further Reading

• Federal Reserve Financial Services, FedACH Processing Schedule
• Nacha, Limitation on Warranty Claims
• Nacha, What Is ACH?