The gap between “sent” and “available to spend” is where treasury confusion starts. It is usually a timing issue, not a software failure. ACH processing time is not one number. Track five distinct stages: submission, settlement, posting, funds availability, and ledger reconciliation. Each has its own milestone, and completing one does not confirm the next.
For each entry, record when each stage occurs. That gives fund leaders a clearer basis for managing cash, confirming payment status, and explaining differences between bank balances and ledger records. The practical focus is on how the stages fit together and what each timestamp tells you.
ACH Processing Times at a Glance
Quote a timeline only after you name the payment type, the cutoff the file met, and the banking-day calendar at both institutions. Nacha's ACH payments fact sheet reports that approximately 80% of ACH payments settle in one banking day or less, combining regular and Same Day ACH processing. A same-day or next-day result is the common case. It is not a promise.
Each entry runs on its own clock: submission, settlement, posting, and availability. Those milestones do not share one timestamp. The network operates through the banking day, settles more than once, and generally does not settle on weekends or Federal Reserve holidays. Miss the last window, or land on a closed day, and the file waits for the next eligible cycle. Same Day ACH is also limited by a per-payment cap that has risen in stages since the product launched. Entries above that cap stay on the standard schedule.
| Payment type | Typical settlement | Funds availability | Key condition |
|---|---|---|---|
| Standard ACH credit | Same day, next banking day, or up to two banking days later at the sender's option | Set by the receiving bank's posting schedule | Sender chooses the settlement date |
| Standard ACH debit | Same day or next banking day | Set by the receiving bank's posting schedule | Cannot carry a settlement date more than one banking day ahead |
| Same Day ACH payment | Within the same banking day, in one of three settlement windows | Same banking day, subject to the receiving bank's local-time deadline | Eligible payments up to the network's per-payment cap for same-day entries |
| Submitted on a weekend or Federal Reserve holiday | No settlement that day | Begins on the next banking day | Moves to the next eligible processing cycle |
Read the row that matches the entry before you speak to a borrower, an investor, or a board. Credits can be dated further out than debits. A standard debit cannot carry a settlement date more than one banking day ahead. A Same Day entry settles inside the banking day you submit, then still follows the receiving bank's posting schedule before the balance is spendable.
I would not publish one turnaround time until those three checks are done. Get the payment type, the deadline, and both calendars right, and the date holds. Skip one and the cash position is a guess.
Why Settlement Does Not Mean Usable Funds
A deposit slip from the teller line isn't cash in your pocket. The bank has accepted the deposit. You still can't spend it until it posts, clears, and becomes available. ACH works the same way, at network scale, and settlement and usable cash can land hours apart, or a full banking day apart.

Each payment runs on a funds-available clock, and the milestones stay in order. The originator submits the file. The operator processes and settles it between institutions. The receiving bank posts the entry. The funds become available to the account holder. The ledger reconciles after that. Settlement is the second milestone. Usable cash is the fourth. Treasury reports that collapse those stages into one "paid" flag are why a cash forecast can look settled while the money still isn't deployable.
The local-time rule turns the gap into a scheduling fact. Nacha's Same Day ACH local-time guidance requires credits from the first processing window to be available to the receiver by 1:30 p.m. in the receiving institution's local time, and credits from the second window by 5:00 p.m. local time. Because the first window's credits must be available by 1:30 p.m. local time and the second window's by 5:00 p.m. local time, two borrowers receiving credits from different windows can see their money become usable at noticeably different times of day, even though each payment follows the same submit, settle, post, and availability sequence.
Some institutions go the other way and advance direct-deposit funds before final settlement. That is a service decision on their side, which is why settlement and availability should never share a field in your system.
A payment isn't complete when the file leaves your office. It's complete when the last milestone is confirmed.
Card payouts move on a different rail. If one cash position has to cover both, this walkthrough of how card payouts reach your bank belongs in its own sequence. Track submit, settle, post, and availability as separate states so a card credit is not booked as if it followed your ACH clock.
Same Day Windows, Cutoffs and Non-Banking Days
A loan payment file leaves your desk at 2:50 p.m. Eastern on a Friday. Window 2 closed five minutes earlier. That file does not settle at 5:00 p.m. It waits for the next eligible cycle, and a non-business day pushes the settlement date again. Treat every Same Day ACH item as its own clock: submission, settlement, posting, and availability are separate marks, not one turnaround time.
Three settlement opportunities run each business day. The transmission deadline is the mark you control.
| Window | Transmission deadline (ET) | Settlement (ET) | Credits available to receiver |
|---|---|---|---|
| Window 1 | 10:30 a.m. | 1:00 p.m. | By 1:30 p.m. local time |
| Window 2 | 2:45 p.m. | 5:00 p.m. | By 5:00 p.m. local time |
| Window 3 | Originating bank's file deadline | 6:00 p.m. | Receiving bank's availability time |
Nacha's Same Day ACH rules set settlement at 1:00 p.m., 5:00 p.m., and 6:00 p.m. Eastern, with transmission deadlines of 10:30 a.m. and 2:45 p.m. Eastern for the first two windows, and they permit Same Day ACH payments of up to $1 million. International ACH transactions and entries above the applicable limit stay out.
The third window settles at 6:00 p.m. ET. Ask your originating bank for its file transmission deadline, and ask what availability timing the receiving bank applies to that window, before you route a payment there.
Converting the deadlines to your own clock
Published cutoffs are Eastern. A fund releasing files from Chicago has to finish by 9:30 a.m. local for the first window. A team in Denver has to finish by 8:30 a.m. local. That conversion, not the network rule, is what teams miss.
Practical rule: Set an internal release deadline ahead of every transmission cutoff, sized to how long your batch needs for validation and approvals. If validation takes 40 minutes, release 40 minutes early and treat your number as the real deadline.
A payment released after the operator deadline, or on a non-business day, generally moves to the next eligible processing cycle. That changes the settlement date itself. I would keep queue latency and settlement latency in separate fields. Two hours in your approval queue is an internal control problem you can fix. An operator settling the file a day later is a calendar problem. One blended timestamp hides both.
Add pre-cutoff validation and alerts for files approaching the deadline. A warning at 20 minutes out costs nothing. A re-dated investor distribution costs credibility with the people the fund exists to serve.
Choosing Same Day or Standard ACH
A loan payoff that must clear before a closing, and an investor distribution that only needs to land on a known date, are not the same clock. Same Day ACH is one set of milestones. Standard ACH is another: submission, settlement, posting, and the moment the cash is usable.
Nacha's Same Day ACH program data reports 1.4 billion Same Day ACH payments in 2025, and first-quarter 2026 volume reached 403 million payments, up 23.6% year over year, with value up 22.1% to $1.1 trillion. Volume at that scale means same-day is ordinary processing, not a rescue button. It still only applies when the file makes a same-day submission window, and settlement is not the same mark as usable funds. Recent rule changes are expected to make some standard ACH credits available earlier on the settlement date. For a scheduled credit that only has to be usable that morning, standard ACH can close most of the speed gap same-day used to hold.

Five questions before you choose a window
- Is this a late-day correction or a genuine emergency disbursement? Routine recurring items rarely qualify.
- Does a missed cutoff create a material consequence for a borrower, an investor, or a closing date?
- Is the amount within the Same Day ACH per-payment cap?
- Can your team reconcile the extra same-day entries before the close, or will they roll into tomorrow's work?
- Would a standard credit meet the required availability time under current bank practice?
Two of those answers usually settle the choice. I would reserve same-day for the case where a later settlement date harms a borrower, an investor, or a closing. Treating "same day" as a quality grade just adds entries your close has to absorb. If you are still weighing how electronic checks and ACH differ in clearing behavior, this comparison of eCheck versus ACH is a reasonable next read, because the instrument you pick changes the timing assumptions more than the network label does.
Debit Returns and the Longer Exception Clock
Settlement is one milestone on an ACH debit. The return window is another, and it is measured in weeks, not in the banking day the funds first hit the account.
Credits and debits do not share a forward calendar. A credit can carry a settlement date further into the future than a debit can. An authorized recurring borrower debit and an outbound investor credit should not sit in the same timing model, even when both leave in the same file. Submission, settlement, posting, and availability already diverge. A later return splits them again.
Debits carry most of the recurring collection work. Nacha reported that debits represented 56% of ACH Network volume in the second quarter of 2023. For a fund collecting monthly loan payments by authorization, a return can arrive weeks after the original settlement date, so debit records need to be kept for that full period.
Why the exception clock is not a queue
For a consumer account, Nacha's limitation and warranty claims rules let the receiving institution return an unauthorized debit so that the return reaches the originating institution no later than the opening of business on the banking day after the 60th calendar day following the original entry's settlement date. The return also requires a Written Statement of Unauthorized Debit.
| Scenario | Timeline | Records to keep |
|---|---|---|
| Unauthorized consumer debit | Return available to the originator by opening of business on the banking day after the 60th calendar day following settlement | Original settlement date, authorization evidence, return reason, and Written Statement of Unauthorized Debit |
| Corresponding non-consumer return | Two-day timeframe under Nacha rules | Return reason and originating entry record |
A daily rejected-payment queue covers entries that failed today. A 60-day window covers an allegation about an entry that settled about two months ago. The first belongs with operations that clear today's file. The second belongs with whoever can still produce the authorization and the Written Statement of Unauthorized Debit after the month has closed.
Keep the original settlement date, the authorization record, the return reason code, and the supporting statement through the monthly close, the quarterly board report, and the next season of statements. If any piece is gone, you cannot tell whether the cash you posted is still yours. Retain that record set for the full return window. When you map the workflows, ACH reversal rules separate a reversal you initiate from a return the receiving bank sends back. Those are different clocks, and only one of them can reopen a settled debit weeks later.
Tracing a Loan Payment and an Investor Distribution
Rules are easier to trust when you watch them move money. Consider three transactions in one week for a fund that releases files against Eastern Time deadlines.
Friday debit, Monday settlement. A borrower's monthly loan payment is pulled by ACH on Friday for next-day settlement. The next banking day is Monday, so the ledger should show the payment received Monday, and interest accrual should stop on the settlement date, not on the Friday submission date. Post it Friday and you've overstated interest income for a weekend and possibly pushed a delinquency status onto an account that was never late.
Wednesday afternoon distribution. An investor distribution is released Wednesday at 3:10 p.m. ET, after the second window's transmission deadline has closed. It moves to the next eligible cycle, so Wednesday's cash forecast must exclude it. Treasury teams that already spent that liquidity in a projection spend Thursday explaining the variance instead.
Same-day construction draw. A draw sent by Same Day ACH at 2:00 p.m. ET settles in the afternoon window, and the receiving church's bank must make the funds available by its local-time deadline. For a church two time zones west, that deadline arrives at a different wall-clock hour than it does for the treasurer. The settlement is identical. The borrower's experience is not.

For each of those three, four values must land in the ledger separately: the requested effective date, the transmission timestamp, the settlement date, and the availability date. Drop one and the mismatch has a predictable home. Without the transmission timestamp, a missed cutoff looks like a bank error. Without the availability date, the cash forecast borrows money the fund can't spend yet. Without the settlement date, interest accrual and delinquency both anchor to the wrong day.
If a borrower calls about a payment that "should have posted," the first question is not whether it posted. It's which of the four dates they're actually looking at.
Recording ACH Timing and Confirming It Before the Next Run
A treasurer releases Thursday's investor distributions at 4:10 p.m. The operator cutoff was 4:00. The file is still in the queue, and it will not settle on the date anyone typed into the request. If the ledger stores one payment date, that miss looks identical to a completed transfer, and Friday's cash meeting starts from money the fund cannot spend.

Treat each ACH item as its own clock. Submission, the cutoff that applied, settlement, posting, and availability are separate milestones. Collapse them and no report will split them apart later.
Six records to keep
- Five dates and a status. Store the requested effective date, the submission timestamp, the operator cutoff applied, the settlement date, and the funds-available date, plus returned status. A single "payment date" column erases the trail you will need when a borrower or investor asks which day the money moved.
- Cutoffs on the releasing team's own clock, with one maintained calendar for banking days and Federal Reserve holidays. Two calendars in circulation is the same as none.
- A pre-cutoff check that flags files approaching a deadline and requires a human acknowledgment. It is the cheapest control in the routine, and the one funds most often skip.
- Lifecycle states, not flags. Move each entry through initiated, submitted, accepted, settled, funds-available, returned, and reversed. Post a loan payment only at the state your written policy names, so interest and delinquency do not start a day early.
- A daily reconciliation comparing originating records against operator acknowledgments, settlement reports, bank postings, and return files. A break found at month-end is a break found after that week's cash has already been spoken for.
- A named owner for every exception, with the original authorization and settlement date on the case file. The person investigating should not have to rebuild the history from email.
The submission timestamp and the cutoff tell you whether the delay sat in your queue or at the operator. The named posting state stops a loan credit before the funds are available. The daily match still has time to move cash inside the same week.
Software can carry the repeatable parts of states, tie-out, and exceptions. CEFCore's automation covers daily interest accrual, month-end close procedures, automated tie-out verification, and approval workflows, and its operations tools include batch processing and exception management. A fund that stays on spreadsheets can keep the same control if the five dates live in five columns and one person owns the reconciliation.
Settlement dates are only as clean as the close that consumes them. A monthly bookkeeping services provider working from reconciled bank data will finish faster than one rebuilding deposits from statements. Recording the availability date in the general ledger, not only in the payment file, is what lets general ledger and cash balances agree at close without a manual bridge entry.
The pre-run confirmation list
Before the next payment run, confirm the window deadlines and the holiday calendar for the coming month. Confirm which payment types settle same day, next day, and later. Confirm the loan posting rule your policy names. Confirm the debit return window and the records you retain for it. Confirm that reconciliation runs daily rather than at close.
Name one owner for the timing table and put a review date on the calendar. Recheck the Same Day ACH per-payment cap against Nacha's current guidance every year. Caps on this network have not stayed fixed.
CEFCore gives church extension funds one place to run loan records, investor account information, and the general ledger cash position that depends on both. Daily accrual, month-end close, and automated tie-out sit in that same workflow. If your team is still matching ACH activity across spreadsheets and bank portals, visit CEFCore to see how the platform handles batch processing, exception management, and month-end tie-out for funds like yours.
