How FedACH Works for Embedded Finance (September 2026)

Your payroll runs on it. So does direct deposit, bill pay, and most recurring money movement in the U.S. FedACH is the Federal Reserve's automated clearing house service, and if you're building financial workflows into software, knowing how it works, how its processing schedule runs, and how the settlement chain affects your visibility is the kind of thing that saves you from diagnosing a "missing" payment at the worst possible moment.

TLDR:

• FedACH is the Federal Reserve's ACH service, processing payroll, direct deposit, and bill pay across the entire U.S. banking system in batches
• Same Day ACH has three daily settlement windows; missing the 4:45 p.m. ET cutoff on a Friday means your payment waits until Monday
• Most "FedACH down" reports reflect missed cutoff windows, not outages; check the Federal Reserve Financial Services status page first
• Validate routing numbers in the Federal Reserve's E-Payments Directory before sending; a valid ABA number does not confirm ACH enrollment
• Unit is a registered Federal Reserve service provider, processing money movement directly with the Fed on behalf of its partner banks

What FedACH Is

FedACH is the automated clearing house service operated by the Federal Reserve Banks, functioning as one of two ACH operators in the United States. It processes electronic credit and debit transfers between depository institutions on behalf of banks, businesses, and government agencies.

When a paycheck arrives via direct deposit or a mortgage payment gets pulled from a checking account, FedACH is often the infrastructure moving it. As described by the Federal Reserve, direct deposits of payroll, Social Security benefits, and tax refunds are typical ACH credit transfers, while direct debits of mortgages and utility bills are typical ACH debit transfers.

FedACH is a named service, not a generic term for ACH in the US. The other ACH operator is a private-sector network run by The Clearing House. Both are fully interoperable, meaning a payment can originate through one operator and land at a bank connected through the other.

How FedACH Fits Into the Broader ACH Network

The U.S. ACH network runs on two operators: FedACH and the Electronic Payments Network (EPN), run by The Clearing House. EPN handles roughly half of commercial ACH volume.

The scale flowing through this structure is worth noting. According to Nacha, the ACH Network processed 35.2 billion payments valued at $93 trillion in 2025, a 7.9% increase over 2024.

Because both operators are fully interoperable, a payment initiated through FedACH can settle at a bank whose primary connection runs through EPN, and vice versa. For a platform, FedACH participation gives you reach across the entire U.S. banking system regardless of which operator the receiving bank uses.

A Brief History of FedACH

Per the Federal Reserve's historical record, ACH payments were first introduced in the 1970s by the Federal Reserve System and the banking industry as a more efficient alternative to cash and checks. Volumes were low initially, and the Fed processed far more ACH payments than private-sector operators.

Over the following decades, ACH became the backbone of recurring U.S. payments: payroll, consumer bills, government transfers. The Fed continues to operate its ACH service today at a scale the original architects of the 1970s system could not have anticipated.

How a FedACH Payment Works Step by Step

Every FedACH payment moves through the same sequence, regardless of whether it's a payroll deposit or a utility debit.

1. The originating bank (ODFI) submits a batch file to FedACH containing one or more payment instructions.
2. FedACH sorts the file and routes each transaction to the appropriate receiving bank (RDFI).
3. The RDFI receives the file and credits or debits its customers' accounts accordingly.
4. FedACH settles the transaction by debiting the ODFI's Federal Reserve account and crediting the RDFI's.

Two things to note about this model. First, FedACH processes payments in batches, not in real time. Transactions accumulate and move together on a schedule, which is why ACH has defined processing windows, not continuous settlement. Second, FedACH tracks all transactions within a specific window and settles them together.

The ODFI and RDFI never interact directly. FedACH sits between them as the clearing intermediary, giving the network nationwide reach without requiring bilateral agreements between every pair of banks in the country.

FedACH Processing Schedule and Settlement Windows

FedACH runs on a fixed schedule. Knowing the windows matters if you're building payroll, disbursements, or any time-sensitive money movement.

For Same Day ACH, there are three submission windows, per Nacha's current Same Day ACH schedule:

Next Day ACH settles at 8:30 a.m. ET on the following business day. No ACH processing occurs on Federal Reserve holidays or weekends. Miss a cutoff on a Friday afternoon, and the payment waits until Monday.

FedACH Status and How to Check It

If you think a payment is stuck, the first place to check is the Federal Reserve Financial Services status page. It shows real-time service status across all Fed payment services, including FedACH. Green means all systems are running. Any degraded or disrupted status will appear there before it shows up anywhere else.

Most "FedACH down" reports on Reddit or social media reflect delayed payments, not true outages. Because FedACH processes in batch windows, a payment submitted after a cutoff simply waits for the next one. That delay can look like a system problem when it's actually expected behavior.

If the status page shows no issues but a payment still hasn't landed, contact your bank or financial infrastructure provider. They can pull the ACH trace number and determine exactly where in the settlement chain the transaction sits.

FedACH Routing Numbers and the E-Payments Directory

Every U.S. bank has an ABA routing number, but not every routing number is enrolled in FedACH. The Federal Reserve maintains the E-Payments Routing Directory, which shows which routing numbers are eligible to receive ACH transactions through FedACH.

Searching a routing number in the directory returns the institution name, its ACH participation status, and whether it accepts same-day ACH. That differs from a general ABA lookup, which confirms a bank exists but says nothing about ACH eligibility.

For anyone building disbursements or payroll, this distinction matters. A routing number that appears valid in the ABA system could still fail or return if the receiving institution isn't enrolled for ACH. Checking the E-Payments Directory before sending is the cleaner approach.

FedACH vs. Fedwire: Choosing the Right Rail

The right rail depends on four variables: size, urgency, cost, and whether reversibility matters.

FedACH fits recurring, lower-value payments where same-day or next-day settlement is acceptable. Payroll, direct deposit, and bill pay all run on ACH. The batch model keeps costs low and the schedule is predictable enough to build around.

Fedwire is for when funds need to arrive immediately, with no ambiguity. A same-day real estate closing, a large interbank settlement, a time-sensitive wire to a supplier. Settlement is immediate and generally irrevocable, with no standard recall path once it clears.

For most embedded finance workflows, FedACH handles the volume and Fedwire handles the exceptions.

Common Reasons for FedACH Delays and How They Are Resolved

Most FedACH delays trace back to a small set of root causes. Here's how to diagnose them.

• Missed cutoff window: the most common reason. A payment submitted after the 4:45 p.m. ET Same Day ACH cutoff, or after the 2:15 a.m. ET Next Day ACH origination deadline (with settlement at 8:30 a.m. ET the following business day), waits for the next available window. On Fridays, that wait extends through the weekend.
• Federal Reserve holidays: the Fed observes federal holidays, and no ACH processing runs on those dates. Payments with an effective date on a holiday roll to the next business day.
• Incorrect or unenrolled routing number: if the routing number supplied doesn't match an active FedACH participant, the payment returns. Always validate against the E-Payments Directory before sending.
• Return codes: the RDFI can reject a payment after receiving it. Common return codes include R01 (insufficient funds), R02 (account closed), and R03 (no account found). Each has a defined resolution path, usually correcting account details and resubmitting.
• Exception items: occasionally a payment gets flagged during processing for manual review. These typically resolve within one business day but can extend settlement.

If a payment is delayed and the FedACH status page shows no outage, pull the ACH trace number from your bank or infrastructure provider. That trace number lets anyone in the chain locate exactly where the transaction is sitting and whether a return is pending.

FedACH Services: Product Offerings From the Federal Reserve

The Federal Reserve offers several distinct services under the FedACH umbrella, each targeting a specific use case.

• FedACH SameDay Service processes transactions within same-day windows, settling eligible domestic payments the same business day they originate.
• FedGlobal ACH Payments extends ACH origination to select international destinations, letting U.S. institutions send cross-border payments over local clearing networks abroad.
• FedACH Risk Origination Monitoring screens outbound ACH files for anomalies before they enter the clearing cycle.
• FedDetect flags suspicious payment activity across Fed payment services.

Access runs through FedLine, the Federal Reserve's secure channel for financial institutions. Non-bank fintechs and software companies reach FedACH indirectly through a sponsor bank or a registered service provider that holds the Fed connection on their behalf.

How Embedded Finance Platforms Access FedACH

Software companies can't connect to FedACH directly. FedACH membership is reserved for depository institutions, which means fintechs and financial infrastructure providers access the network through sponsor banks and FBO accounts that hold that membership on their behalf.¹

The structural chain runs: your infrastructure, your infrastructure provider, the sponsor bank, FedACH. Each layer adds a potential point of latency or opacity. An infrastructure provider that processes money movement directly with the Federal Reserve on behalf of its bank partners collapses that chain, giving you network-level settlement data instead of a filtered view from an intermediary.

That distinction matters most when timing is contractual: real ACH trace numbers, actual settlement dates, and payment status sourced from raw network events, not estimates reconstructed from an upstream system. For teams building instant payouts, that visibility is especially critical. For payroll or disbursements, that visibility is the difference between catching a problem before your end users do and finding out after.

How Unit Connects Directly to FedACH on Behalf of Banks

Unit is a registered Federal Reserve service provider, which means we process payments directly with the Fed on behalf of our partner banks.¹ There is no intermediary layer between our infrastructure and FedACH. That connection is why we can return real ACH trace numbers, actual settlement dates, and network-level payment status through the API, not estimates reconstructed from an upstream system.

For teams building payroll, disbursements for fund management, or any time-sensitive money movement, that proximity is the difference between knowing where a payment is and guessing. The closer your infrastructure sits to the actual rails, the more visibility and control flows down to you. Teams focused on building and monetizing money movement will find that proximity critical. With Unit, your team sees what the Federal Reserve sees.

Final Thoughts on FedACH Processing, Schedules, and How to Access the Network

FedACH touches nearly every recurring payment in the U.S., so understanding its structure matters whether you're diagnosing a delay or assessing infrastructure. Knowing the cutoff windows, how to read the E-Payments Directory, and what return codes signal will save your team real time. The more directly your infrastructure connects to those rails, the better your visibility into what's actually happening with a payment. Talk to our team if you want to see what that looks like firsthand.

FAQ

What is FedACH and how does it differ from ACH broadly?

FedACH is the automated clearing house service operated by the Federal Reserve Banks, and one of two ACH operators in the U.S., alongside the Electronic Payments Network run by The Clearing House. ACH is the network; FedACH is a specific operator within it. Both are fully interoperable, so a payment originating through FedACH can settle at a bank whose primary connection runs through the other operator.

What does "FedACH down" actually mean, and how do you check FedACH status?

In most cases, "FedACH down" reports reflect delayed payments, not true outages. FedACH processes in batch windows, so a payment submitted after a cutoff simply waits for the next one, and that wait can resemble a system failure. To check real FedACH status, go to the Federal Reserve Financial Services status page, which shows live service health across all Fed payment systems. If the status page shows no issues but a payment hasn't settled, pull the ACH trace number from your bank or infrastructure provider to locate exactly where in the settlement chain the transaction sits.

FedACH vs Fedwire: Which Rail Should I Use for Embedded Finance Payouts?

FedACH fits recurring, lower-value payments where same-day or next-day settlement is acceptable, such as payroll, direct deposit, and bill pay. Fedwire is the right choice when funds need to arrive immediately and settlement must be final: large-value transfers, time-critical wires, or situations where reversibility is not an option. For most embedded finance workflows, FedACH handles the volume and Fedwire handles the exceptions.

How do software companies access FedACH without a banking license?

FedACH membership is reserved for depository institutions, so fintechs and software companies reach the network through a sponsor bank or a registered Federal Reserve service provider that holds the Fed connection on their behalf. The structural chain runs from your infrastructure through your provider, through the sponsor bank, to FedACH. Unit is a registered Federal Reserve service provider and processes ACH payments directly with the Fed on behalf of its partner banks, so platforms building on Unit get real ACH trace numbers, actual settlement dates, and network-level payment status through the API, not estimates filtered through an intermediary.

Can I build instant payouts for marketplace sellers using FedACH, or do I need a different rail?

Same Day ACH through FedACH supports three settlement windows per day, with the latest cutoff at 4:45 p.m. ET settling by 6:00 p.m. ET, fast enough for many payout use cases but not truly instant. For instant payouts, the faster path is embedded accounts: when your sellers hold accounts on the same banking infrastructure as your platform, payouts move as book transfers between accounts at the same bank, which are instantaneous and carry no per-transaction cost. That architecture requires a financial infrastructure layer that supports both the platform and end-user accounts on a shared ledger, which is how Unit's instant payout use case works for marketplace and vertical SaaS programs.

The content in this article is provided for general informational and educational purposes only and should not be construed as legal, tax, accounting, or regulatory advice. Unit does not warrant or guarantee the accuracy, completeness, adequacy, or currency of the information provided, and the content may not reflect all considerations relevant to a particular business, product, or use case. References to regulatory frameworks, processing schedules, or network rules are provided for educational context only and are subject to change without notice.

Requirements may vary based on product structure, jurisdiction, bank partner, program design, and other factors. Nothing in this article creates or implies a client relationship between Unit and the reader. Readers should consult their own legal, compliance, tax, financial, or other professional advisors before making any business, product, or operational decisions, as applicable.

¹ Unit is a financial technology company and is not a bank. Banking services are provided by Unit's bank partner(s), Members FDIC. Accounts are held at Unit's bank partner(s), not by Unit. Unit provides technology infrastructure and program management services to enable clients to offer financial products.