As of March 3rd, The Federal Reserve is reporting a FedACH® service issue / delivery delay.
This means some ACH deposits and bank transfers may post later than normal today (Tuesday, March 3, 2026). This does not typically stop credit card payment processing. Card payments (Visa/Mastercard/AmEx/Discover) should continue to run as usual because they operate on separate networks, but it can delay the bank “send → deliver → post” process used for ACH activity.
So if you’re a merchant asking, “Why didn’t my deposit hit?” the most accurate answer is that some ACH files are delayed upstream at the FedACH delivery level, and banks may post deposits late while they wait for file delivery and then work through backlog once the flow resumes.
What FedACH is and why this matters today
ACH is the network used for bank transfers that run in batches: payroll direct deposits, vendor payments, loan drafts, subscription billing, and a lot of business-to-business money movement. Most banks don’t send ACH items directly to every other bank one at a time; they submit files to an ACH operator for processing and distribution. FedACH is one of the primary ACH operator services run by the Federal Reserve, and when the Fed reports a delivery delay, it can affect how quickly receiving banks get the files they need to post transactions.
The practical impact is straightforward: a delay in file delivery can become a delay in posting, even if the underlying transactions were initiated correctly.
What merchants will typically see when FedACH is delayed
For most small businesses, the first signal is usually a missing or late deposit compared to a normal funding pattern. Payroll is another major pain point: if your payroll provider submitted on schedule but the ACH flow is delayed, employees can see direct deposits arrive later than expected.
Vendor payments can also be affected. If you pay suppliers by ACH, they may not receive funds when expected, which can delay releases or shipments depending on their policy. On the incoming side, if you collect via ACH (invoices, membership drafts, payment plans), those pulls can stay in “processing” longer and settle later.
Importantly, ACH runs on scheduled processing windows, not a true 24/7 instant model. So delays can ripple through batches and posting timing as banks catch up.
What is not usually affected
This kind of issue is specific to ACH file delivery. In most cases, card payments still function normally because they run on different networks. If you need reliable collections today, card payments are typically the most consistent option while ACH timing is uncertain.
What to do right now
The most important thing you can do today is prevent an operational problem from turning into a duplicate-payment problem.
First, do not resubmit payroll, vendor payments, or ACH batches “just in case.” If the original file was accepted and is simply delayed in delivery/posting, a second submission can create duplicates when both eventually clear.
Instead, contact your bank, payroll provider, or payment provider and ask a very specific set of questions: whether your file was accepted, whether it is queued/delayed or rejected, whether they will auto-resubmit if needed, and what they are seeing for posting expectations at receiving banks.
Second, protect payroll communications. If payroll is scheduled to land today, communicate early with employees that there is a nationwide ACH delay being reported by the Federal Reserve and that posting may be later than usual. This reduces confusion and prevents your team from flooding managers with avoidable questions.
Third, if you’re collecting customer payments by ACH and the timing is flexible, consider delaying non-critical drafts for 24 hours to reduce the risk of returns caused by posting order issues at banks. If collections are time-sensitive, use card payments or other approved alternatives for urgent receivables.
Finally, monitor your account closely. When backlogs clear, transactions can post close together, which can increase the likelihood of overdrafts, returned items, or NSF fees for accounts running tight. If you’re close to the line, leaving a buffer (even temporarily) can help avoid fees.
What to tell customers or vendors
Keep it short, factual, and calm. Here is copy you can use as-is:
Customer-facing message:
“We’re currently seeing a nationwide ACH processing delay reported by the Federal Reserve affecting FedACH file delivery. Some bank transfers and deposits may post later than normal. Card payments are processing normally.”
Vendor-facing message:
“Our ACH payment is scheduled and has not been canceled. Due to a nationwide FedACH delay reported by the Federal Reserve, posting may be later than normal.”
Where to check updates
For the most accurate real-time status, rely on the Federal Reserve’s own service status page for FedACH updates.
If your bank also posts notices, check those as well, because posting timing and internal queues can vary by institution.
Bottom line
This is an ACH timing disruption. For merchants, that means some deposits and transfers may be late, and the practical response is to avoid duplicate submissions, prioritize payroll clarity, use card rails for urgent collections, and monitor balances until posting normalizes.
