FedACH Services

FedACH Services are the Federal Reserve Banks’ services for processing U.S. Automated Clearing House credit and debit entries. FedACH receives ACH files from financial institutions or their agents, edits and sorts entries, distributes them to receiving institutions or the other ACH operator, and settles processed items through designated accounts on the books of the Federal Reserve Banks.

FedACH is an ACH operator service, not a consumer payment app, a bank account, or the organization that writes the industry-wide ACH rules. Consumers and businesses normally access ACH through a bank, credit union, employer, biller, government agency, or payment provider.

Key Takeaways

• The Federal Reserve Banks provide FedACH Services; The Clearing House provides the other U.S. ACH operator service through Electronic Payments Network (EPN).
• The operators exchange entries so an originating institution using one operator can reach a receiving institution using the other.
• Nacha administers the private ACH Operating Rules; it does not process payments.
• FedACH processes files and entries in scheduled windows. It is not a continuously available instant-payment rail.
• Same Day ACH accelerates eligible ACH processing and settlement but still uses scheduled batches and retains ACH return and exception processes.
• FedACH settlement uses a financial institution’s designated Federal Reserve settlement account or an approved correspondent’s account.
• File receipt, file acceptance, settlement, customer posting, funds availability, and return status are separate events.
• A returned entry and a reversal are different. A reversal is limited to qualifying erroneous entries and is not a general cancellation right.
• Current deadlines, holidays, eligibility rules, and institution cutoffs should be checked before relying on a payment date.

What FedACH Does

FedACH provides the operator layer between originating and receiving financial institutions. Its core origination and receipt services support:

1. receiving ACH files from sending banks, sending points, agents, or the other ACH operator;
2. applying file, batch, and entry edits required by the service and applicable rules;
3. sorting entries by destination routing information, settlement date, and selected delivery options;
4. distributing files to receiving points or exchanging entries with EPN;
5. assigning or applying settlement dates under the current rules and processing schedule;
6. debiting and crediting designated settlement accounts at scheduled settlement times;
7. processing returns, notifications of change, reversals, and other eligible ACH records; and
8. producing file, item, settlement, exception, and risk-management information for enrolled institutions.

The wider FedACH product suite also includes optional risk, anomaly-notification, reporting, information-file, international ACH, and exception-resolution services. Those tools support payment operations, but they do not replace customer authorization, participant responsibilities, fraud controls, sanctions screening, or reconciliation.

FedACH does not itself:

• hold the ordinary customer deposit account;
• originate payroll or bill instructions for a customer;
• decide whether an ACH debit was properly authorized;
• guarantee that routing and account data identify the intended receiver;
• make Same Day ACH an instant or irrevocable payment;
• eliminate ACH returns, reversals, notifications of change, or disputes; or
• prove customer posting merely because the operator accepted a file.

Parties and Records

A processor or another ACH operator can act as an institution’s agent for transmission or receipt. Outsourcing does not remove the sending or receiving institution’s responsibilities under its agreements, applicable ACH rules, Operating Circular 4, or law.

How a FedACH Entry Moves

    flowchart TD
	    A["Originator creates an ACH credit or authorized debit"] --> B["ODFI validates the instruction and releases an ACH file"]
	    B --> C["FedACH receives and edits the file, batches, and entries"]
	    C --> D["FedACH sorts entries by receiving institution and settlement date"]
	    D --> E["FedACH distributes directly or exchanges entries with EPN"]
	    E --> F["RDFI receives the entry and posts or returns it"]
	    F --> G["Federal Reserve settlement accounts are debited and credited on schedule"]
	    G --> H["Institutions reconcile settlement, customer posting, and exceptions"]

The exact order of customer posting and interbank settlement can depend on the entry, schedule, rule, and institution. The diagram shows the evidence chain, not a guarantee that every customer interface updates at one fixed moment.

A typical forward-entry process is:

1. An Originator creates an ACH instruction and supplies the required payment and authorization data to its ODFI or processor.
2. The ODFI applies customer, file, exposure, fraud, format, and release controls.
3. The sending point transmits and releases the file to FedACH by the applicable deadline.
4. FedACH checks the file, batches, and entries and reports accepted or rejected processing states.
5. FedACH sorts entries for direct distribution to receiving points or inter-operator exchange with EPN.
6. The RDFI receives the entry and applies account validation, posting, availability, return, and exception processes.
7. The Federal Reserve Banks debit and credit designated settlement accounts at the scheduled settlement time.
8. Participants reconcile the original file, operator reports, settlement accounts, customer accounts, returns, and business records.

An operator rejection before processing is different from an RDFI return after receipt. Neither should be inferred from a generic status such as “failed” without the file, batch, trace, date, and reason information.

Intra-FedACH and Inter-Operator Entries

An entry is intra-FedACH when the operator can receive it from the sending side and distribute it to the receiving side through FedACH for that processing flow.

An entry is inter-operator when FedACH and EPN exchange it because the originating and receiving endpoints use different operators. Operating Circular 4 permits a bank to designate another ACH operator as its agent for applicable transmission or receipt arrangements. The two-operator structure provides network reach without turning FedACH and EPN into one service.

The operator path can affect:

• transmission and distribution records;
• investigation ownership;
• file delivery and exception timing;
• operator-specific fees and service options; and
• which reports show each processing stage.

It normally does not create a different consumer-facing payment product. A payroll deposit remains an ACH credit whether it stays within one operator or crosses between operators.

File Status, Settlement, and Posting

The ACH trace number, file ID, batch controls, company ID, settlement date, and account record help connect these events. A confirmation screen or bank statement may not identify FedACH by name, so the financial institution’s operator reports can be necessary for a complete investigation.

How FedACH Settlement Works

Before using FedACH for sending or receiving items, a financial institution designates a settlement account on the books of a Federal Reserve Bank. The institution can designate its own account or, with the required agreement, a correspondent bank’s account.

Under Operating Circular 4, the account holder authorizes the Reserve Bank to make scheduled debits and credits associated with ACH items. In simplified form:

• credit items sent by a bank create a debit to its designated settlement account;
• debit items sent by a bank create a credit to its designated settlement account;
• credit items received by a bank create a credit to its designated settlement account; and
• debit items received by a bank create a debit to its designated settlement account.

Actual settlement reporting can aggregate many entries and include returns, government items, fees, adjustments, and correspondent relationships. Operations teams should reconcile the operator’s settlement summaries to the Federal Reserve account statement and then to customer-account and general-ledger records.

An institution remains responsible for its FedACH transactions even when it uses a correspondent settlement account. Designating the correspondent does not turn that correspondent into the ODFI or RDFI for the underlying entry.

Standard and Same Day ACH Timing

FedACH uses scheduled transmission, distribution, and settlement windows. A customer-facing cutoff can be earlier than the operator’s deadline because the ODFI needs time for validation, approvals, file creation, risk review, and transmission.

The effective entry date supplied in the ACH file and the settlement date applied under operator rules are related but not identical. A future date, missed deadline, ineligible entry, weekend, holiday, correction, or operator handling rule can change when settlement occurs.

Same Day ACH allows eligible entries received by a same-day deadline to be processed and settled on the current processing day. As of this article’s review date, the Federal Reserve’s FedACH SameDay page identifies these main exclusions:

• international ACH transactions using the IAT code;
• automated enrollment entries using the ENR code;
• transactions above $1 million; and
• entries received too late or carrying a future effective entry date.

Eligibility does not guarantee same-day customer availability or successful completion. An entry can still be rejected, returned, delayed by an institution’s earlier cutoff, or affected by account and compliance controls.

The published FedACH Processing Schedule is the controlling operational reference for Federal Reserve transmission deadlines, target distributions, and settlement times. Use its current version rather than copying times from an old procedure or assuming the same schedule applies on weekends and Federal Reserve holidays.

Returns, Reversals, and Notifications of Change

ACH exception records have different meanings:

• A return sends an entry back through an ACH operator using an applicable return reason and timeframe.
• A reversal is a new entry used only to correct a qualifying erroneous or duplicate entry under the applicable rules.
• A notification of change (NOC) tells the originating side that specified account or routing information should be corrected for future entries.
• A dishonored return or related contested record can arise when a participant challenges the handling of a return under the rules.
• An exception case can support communication or research without itself changing settlement or customer posting.

A return can occur after the original entry settled and appeared in a customer or business record. Analysts should not treat gross originated credits or debits as durable cash merely because the first settlement date passed.

Reversals are not a recovery shortcut. Before originating one, the institution should establish that the original entry meets the applicable error criteria, preserve the original and corrective records, use the required data, and meet the current timing rules.

Worked Example: Inter-Operator Payroll File

Assume an employer sends a payroll file through its bank to FedACH. The file contains 800 ACH credits totaling $1,920,000:

The initial file control totals are:

1510 + 287 + 3 = 800 entries
2$1,230,000 + $682,500 + $7,500 = $1,920,000

After the three returns, the amount remaining posted in this simplified example is:

1$1,920,000 - $7,500 = $1,912,500

The employer should not record the entire file as successfully paid based only on FedACH file acceptance. Its payroll reconciliation should match:

1. the approved payroll register to the originated file;
2. file totals to the FedACH acknowledgement;
3. direct and inter-operator distributions to operator reports;
4. settlement totals to the bank and Federal Reserve settlement records available to the participant;
5. employee account outcomes and returns to trace numbers; and
6. the corrected payment for each closed account to independently verified instructions.

If the bank does not receive an expected acknowledgement, it should investigate the file ID and release status before retransmitting. Resending the full payroll file without duplicate controls could pay hundreds of employees twice.

FedACH Compared With Other Payment Systems

Same Day ACH is a faster ACH option within scheduled processing. It should not be labeled FedNow, RTP, a wire, or a continuous real-time payment.

Risks and Controls

• Unauthorized debit risk: an Originator can submit a debit without valid or retained authorization.
• File duplication: retransmitting an uncertain file can duplicate every entry in the batch.
• File integrity: incorrect counts, hash totals, dates, or record sequences can cause rejection or misprocessing.
• Exposure and settlement risk: a participant or correspondent can lack capacity to settle originated entries and later returns.
• Routing and account risk: stale or fraudulent instructions can misdirect payroll, supplier, or refund credits.
• Return risk: settled entries can later return, changing cash, receivable, payroll, and customer outcomes.
• Cutoff risk: missing an institution or operator deadline can shift the settlement date.
• Agent risk: a processor can mix files, misuse credentials, apply the wrong participant profile, or fail to release a transmitted file.
• Cyber risk: compromised credentials or source systems can create technically valid but unauthorized files.
• Reconciliation risk: file, entry, settlement, customer-account, and business systems can use inconsistent dates and identifiers.

Useful controls include dual approval, independent verification of account changes, file and batch totals, unique file IDs, duplicate detection, exposure limits, originator monitoring, strong access controls, encrypted transmission, status-aware retries, return-rate monitoring, protected logs, contingency testing, and daily end-to-end reconciliation.

FedACH anomaly notifications and monitoring tools can add useful signals, but their specific behavior matters. For example, a notification product can alert an institution without stopping the underlying items. Institutions should not describe every risk service as a payment block.

Common Mistakes

• Calling FedACH the entire U.S. ACH Network.
• Calling Nacha an ACH operator or saying it processed a payment.
• Treating FedACH and EPN as different consumer payment products.
• Assuming a transmitted file was released and accepted.
• Treating file acceptance as proof of entry distribution, settlement, or customer posting.
• Calling Same Day ACH instant, continuous, or irrevocable.
• Ignoring the difference between effective entry date and settlement date.
• Assuming Federal Reserve settlement prevents a later ACH return.
• Using a reversal as a general cancellation mechanism.
• Treating an NOC as a value transfer or automatic correction of the original entry.
• Assuming a processor replaces the ODFI’s or RDFI’s responsibilities.
• Using an old processing schedule for current deadlines.

How to Investigate a FedACH Entry

1. Confirm that FedACH processed or exchanged the entry rather than assuming the operator from a bank statement.
2. Obtain the file ID, trace number, batch information, company ID, SEC code, amount, direction, effective entry date, and settlement date.
3. Identify the Originator, ODFI, RDFI, sending and receiving points, processors, other operator, and settlement-account relationship.
4. Separate file transmission, release, receipt, edits, distribution, settlement, account posting, and availability.
5. Review rejects, returns, reversals, NOCs, exception cases, and operator exchanges using their own timestamps and reason codes.
6. Trace uncertain files before resubmission to prevent duplicate batches.
7. Reconcile operator settlement summaries to designated Federal Reserve settlement-account entries and internal ledgers.
8. Match the entry to authorization, payroll, invoice, benefit, tax, or customer-account evidence.
9. Check the current FedACH schedule, Operating Circular 4, Nacha rules, institution agreements, and applicable law.
10. Escalate fraud, consumer-protection, sanctions, liability, or compliance questions to the relevant institution or qualified professional.

Official Resources

• Federal Reserve Financial Services: FedACH Services describes current origination, receipt, Same Day ACH, risk, reporting, information, and exception services.
• FedACH Origination and Receipt explains scheduled file delivery, sorting, routing, status, and settlement information available to participants.
• FedACH Processing Schedule publishes current transmission deadlines, target distribution times, settlement schedules, and operational footnotes.
• FedACH SameDay Service describes current eligibility, amount, date, and deadline conditions for same-day processing.
• Federal Reserve Operating Circulars links the current version of Operating Circular 4 and related circulars.
• Operating Circular 4, effective January 5, 2026 governs Federal Reserve processing and settlement of commercial ACH credit and debit items. Check the operating-circulars page for a later effective version.
• Nacha ACH Guide: How ACH Works explains the two ACH operators and the participant flow.
• Federal Reserve E-Payments Routing Directory provides service-specific institution routing information.

Official operator records do not by themselves establish whether a customer authorized an entry, whether a debit is legally valid, or which party bears a loss. Use the actual account, authorization, participant, and transaction evidence for a specific case.

FAQs

Related Terms

• ACH: U.S. batch payment network in which FedACH provides operator services.
• Electronic Payments Network (EPN): Other U.S. ACH operator, provided by The Clearing House.
• Nacha: Private administrator of the common ACH Operating Rules.
• ODFI: Financial institution that submits ACH entries to an operator.
• RDFI: Financial institution that receives ACH entries for customer accounts.
• Direct Deposit: Common ACH credit used for payroll and benefits.
• Electronic Funds Transfer: Broader category that includes ACH and other electronic transfers.
• Routing Number: Institution identifier used with service-specific routing records.
• Reconciliation: Matching files, operator reports, settlement accounts, customer entries, and business records.

Educational Use

This article provides general financial education. It is not payment-operation, accounting, legal, regulatory, cybersecurity, sanctions, fraud-recovery, compliance, or transaction-specific advice. Use current FedACH schedules, Federal Reserve operating circulars, Nacha rules, institution agreements, and qualified professional guidance for an actual payment.