4:52 p.m. on the Last Day of the Quarter
Ridgeline Property Management must pay 1,900 vendor credits totaling $4.3 million today, March 31, to close its quarter. The file includes a $1.8 million payment to a general contractor and a $450,000 payment to a roofing supplier. Ridgeline's ERP export finishes at 4:52 p.m. ET, and its ODFI, which does support Same Day ACH, calls to ask what can still be done. Separately, Ridgeline wants to fund the run with a $900,000 same-day debit against a tenant's operating account at another bank; that debit settles, and at 3:00 p.m. Ridgeline realizes the file mapping selected the wrong tenant account.
1. What can still settle today, and what cannot?
Read the worked answer
Two independent failures, and fixing one does not fix the other.
Timing. Same Day ACH runs three submission windows with processing deadlines of approximately 10:30 a.m., 2:45 p.m. and 4:45 p.m. ET. A 4:52 p.m. release misses the last window, so nothing in this file can settle today as a Same Day entry. The operator will handle it as a next-day file with an effective date of the next banking day. Ridgeline's quarter-close deadline is not something the network recognizes, and an effective date cannot be back-dated to the day the file was intended to go.
Eligibility. The $1.8 million contractor payment was never eligible regardless of timing: the per-entry Same Day ACH limit is $1,000,000, and an entry over the limit is rejected rather than settled same-day. The $450,000 roofing payment is within the limit and would have been eligible had the file been released before 4:45.
So the honest answer to the caller is: not today, and not the contractor payment same-day at all.
2. Ridgeline proposes sending three $600,000 entries to the same contractor to fit under the cap. Any issue?
Read the worked answer
Yes - that is structuring to evade the per-entry limit, and the ODFI should refuse it.
The cap applies to each entry, and $1.8 million owed on one contract to one payee is a single payment. Deliberately slicing it into pieces sized to stay under the threshold defeats the control the limit exists to impose, and it is exactly the pattern that ODFI monitoring and examiners are built to flag. It also creates duplicate-payment risk: three same-day entries to one account is a dispute waiting to happen the moment one of them is returned or the payee's clerk counts only one.
The legitimate options are straightforward: release the contractor payment as a next-day entry; stage the payment across settlement dates because the contract actually calls for staged billing; use a wire or another rail for the large amount; or pay part today under the cap and the remainder tomorrow on a documented schedule. Each of those follows the underlying payment terms rather than gaming a threshold.
3. The $900,000 same-day debit settled to the wrong tenant. What are the options?
Read the worked answer
Not a return, and not a simple recall.
The entry was authorized by Ridgeline and correctly posted by the RDFI. The RDFI has no reason to send it back, and there is no "we picked the wrong account" return code.
The only network mechanism is a Reversal, and it is narrowly confined: permitted error types are wrong dollar amount, wrong DFI account number, and duplicate; the Originator must notify the ODFI promptly, because reversals must move within a short window measured in banking days from settlement; the Originator must indemnify the ODFI in writing; and - the part clients always miss - the RDFI can only debit the receiver's account to the extent the funds are still there. A tenant who watched $900,000 arrive and moved it out is a failed reversal.
Practical sequence: notify the ODFI immediately, transmit the reversal within the permitted window with the correct reversal code and the Originator's written request and indemnity, and in parallel ask the RDFI, as a courtesy outside the Rules, to place a hold on the balance. Then fix the mapping that selected the wrong account, because the second occurrence will not be treated as an error.