The payment cleared in seconds. Three days later, the books were still wrong.
Funds can move rapidly while invoice data, approval records, remittance information and accounting entries remain fragmented across multiple systems. Faster settlement does not necessarily make finance faster; it can simply shift the bottleneck from the payment desk to the reconciliation queue.
I think of the process as having two clocks. The payment clock tracks how quickly money moves. The close clock measures how quickly the business can explain, record and reconcile that movement.
A company has not truly improved its payment operation if it shortens the payment clock but makes the close clock more difficult to manage.
Separate the payment from the record
Every payment follows two paths: the movement of funds and the movement of information through approval, accounting and reconciliation.
The Federal Reserve distinguishes between clearing and settlement. Clearing covers payment information and related processing, while settlement involves debiting and crediting accounts. The two steps are connected, but they are not identical.
That distinction became especially clear while I was running Tyler Petroleum. We used different payment providers for different vendors, creating unnecessary costs and delays. The challenge was not only the time required to move money. Each additional system created another place where payment information had to be captured, matched and interpreted.
The key question is not simply, “How quickly can we send this?” It is, “What will finance need to know once it has been sent?”
That question matters even more as businesses adopt additional payment methods. A 2025 Federal Reserve Financial Services survey summary found that 92% of businesses use some form of faster payment, including Same Day ACH and digital wallets. The same summary said businesses continue to cite cost, security concerns and insufficient timeliness among their leading payment challenges.
Measure both clocks before changing the rail
Before switching payment methods or introducing automation, map the full workflow: invoice approval, payment initiation, settlement, remittance delivery, accounting entry, reconciliation and exception resolution.
Track both clocks: the time required for a payment to settle and the time finance needs to identify it, match it to the correct invoice and resolve any exception. If settlement improves from one day to a few seconds but an unmatched transaction still takes three days to resolve, the company has increased payment speed—not financial visibility.
Assign an owner to every stage, particularly the point where the process can fail. That is one of the most important payment controls. If the response to an unmatched payment is simply that “accounts payable will find it later,” the workflow is not ready.
Choose the payment method by the business need
Payment timing and data requirements vary by situation. A payroll correction late on a Friday may warrant a faster method, while a routine invoice due the following week may not.
Before changing the payment method, ask three questions:
The right payment method aligns with the urgency of the transaction, the approval process, the accounting workflow, the cash forecast and the exception plan.
Run the five-payment test before you scale
Before expanding a new payment method, test it against five scenarios:
If the team cannot explain all five cases, the process is not ready to scale. Real finance work is defined by payment exceptions, not by the one payment that works as planned.
Design reconciliation before launch
Reconciliation should be designed before a payment project goes live.
Require one usable identifier to follow the transaction from approval through settlement and into the accounting system. Define a daily exception queue. Set a deadline for resolving unmatched items. Keep an audit trail that connects the original approval, the actual payment and any correction.
Nacha has noted that many payment back offices still rely on manual intervention for exception handling, returns and reconciliation. Automation can reduce repetitive work, but it does not remove the need for judgment. A system that can send a payment in seconds but cannot explain it is only partially controlled.
Before approving the project, ask whether the business can identify every payment’s purpose, assign responsibility for unmatched transactions and distinguish timing differences from actual errors at close. If the answer is no, slow down the rollout. The goal is not maximum payment speed. It is knowing what happened after the money moved.
Faster payments are useful. Faster confusion is not.
The payment went through in seconds. The books were still wrong three days later.
Money can move quickly while invoice data, approval history, remittance details and accounting records remain scattered across different systems. Faster settlement does not automatically create a faster finance operation. It can move the bottleneck downstream, from the payment desk to the reconciliation queue.
I think about this in terms of two clocks. The payment clock measures how quickly money moves. The close clock measures how quickly the business can explain and reconcile that movement.
