EPN is The Clearing House's private ACH operator. Learn how it clears ACH files, exchanges entries with FedACH, supports settlement, and differs from RTP and wires.
The Electronic Payments Network (EPN) is the private-sector Automated Clearing House operator owned and operated by The Clearing House. EPN receives batched ACH credit and debit files from participating financial institutions, sorts and distributes the entries, exchanges entries with the Federal Reserve Banks’ FedACH service when necessary, and supports settlement between the institutions. EPN is an operator within the U.S. ACH Network, not an instant-payment network or a consumer payment app.
An ACH operator is the central processing layer between originating and receiving financial institutions. EPN’s core operator functions include:
The operator handles files and interbank processing. The ODFI remains responsible for the Originators and entries it submits, while the RDFI posts or returns entries for Receiver accounts under the applicable rules.
flowchart LR
A["Originator creates authorized ACH entry"] --> B["ODFI submits file to EPN"]
B --> C{"Which operator reaches the RDFI?"}
C -->|EPN| D["EPN sorts and distributes entry"]
C -->|FedACH| E["EPN exchanges entry with FedACH"]
E --> F["FedACH distributes entry"]
D --> G["RDFI posts or returns entry"]
F --> G
G --> H["Receiver account"]
G -. "return, NOC, or other exception" .-> C
The operator path is usually invisible to the payer and recipient. What they see is a bank-account debit or credit, a status in a banking interface, or an exception from their financial institution.
| Participant | Role in the flow | Evidence to retain |
|---|---|---|
| Originator | Creates the credit or authorized debit | Authorization, payroll or invoice record, source instruction |
| ODFI | Accepts entries and submits the ACH file | Origination agreement, file-control totals, exposure approval, acknowledgement |
| EPN | Sorts, distributes, exchanges, and supports settlement of entries | Operator file receipt, processing report, settlement and exception files |
| FedACH | Receives or sends entries when the destination uses the other operator | Inter-operator exchange and processing records |
| RDFI | Receives entries and posts or returns them | Account posting, return reason, notification of change |
| Receiver | Owns or controls the account being credited or debited | Account statement, receipt, debit authorization where applicable |
A third-party sender or processor can create or transmit files for another participant. Outsourcing the file operation does not erase the ODFI’s or Originator’s responsibilities under contracts, EPN rules, Nacha rules, and applicable law.
An entry is intra-EPN when both the originating and receiving financial-institution endpoints are handled through EPN for that processing flow. EPN can receive, sort, and distribute the entry without exchanging it with FedACH.
An entry is inter-operator when EPN receives it from an ODFI but the destination RDFI is reached through FedACH, or when FedACH sends an entry for an EPN participant. The operators exchange the relevant files so the ACH Network can reach participating U.S. depository institutions across operator boundaries.
The distinction can affect operational cutoffs, file delivery, reports, and investigation paths. It should not be interpreted as a different type of payment for the Receiver. Both paths remain ACH entries subject to the applicable network rules.
| Stage | What happens | What remains uncertain |
|---|---|---|
| File acceptance | Operator accepts a submitted file for processing | Individual entries may still fail edits or later be returned |
| Clearing and distribution | Entries are sorted and delivered to the appropriate operator or RDFI | Interbank obligations may not yet have settled |
| Settlement | Financial-institution positions are debited and credited under the settlement arrangement | Receiver account posting and availability can still require confirmation |
| RDFI posting | Entry is applied to the Receiver’s account | Some entries remain subject to return, dispute, hold, or correction processes |
| Funds availability | Receiver can use the credited funds under applicable rules and account terms | Availability does not eliminate every later legal or operational exception |
| Reconciliation | Participants compare source, operator, settlement, account, and ledger records | Unmatched items require investigation and resolution |
Calling every stage “processed” hides material differences. A treasury analyst should identify the exact file, entry, settlement date, posting status, and return status.
Assume an employer sends a payroll file through its ODFI containing 10,000 equal ACH credits of $1,800 each:
1File control amount = 10,000 x $1,800 = $18,000,000
The ODFI submits the file to EPN. Based on destination routing:
7,400 entries go directly from EPN to EPN-receiving institutions.2,600 entries are exchanged to FedACH for delivery to FedACH-receiving institutions.The routing split is:
1Intra-EPN share = 7,400 / 10,000 x 100 = 74%
2Inter-operator share = 2,600 / 10,000 x 100 = 26%
Suppose 20 credits are later returned because the destination accounts are closed or invalid. Each credit is $1,800, so returned principal is:
1Returned principal = 20 x $1,800 = $36,000
2Net posted principal = $18,000,000 - $36,000 = $17,964,000
The entry return rate is:
1Return rate = 20 / 10,000 x 100 = 0.20%
The employer should not treat EPN’s acceptance of the $18 million file as proof that every employee was paid. A complete reconciliation connects the employer’s payroll register, ODFI file acknowledgement, operator reports, settlement debit, RDFI returns, corrected employee instructions, and general-ledger postings.
The example uses equal payments to make the arithmetic transparent. Real payroll files contain different amounts, and a returned count cannot be converted into returned dollars without entry-level data.
EPN processes ACH entries in scheduled batch windows. Eligible entries can use Same Day ACH, while other entries use standard schedules based on effective dates, submission deadlines, and operator rules.
| Feature | Standard ACH | Same Day ACH |
|---|---|---|
| Processing model | Scheduled batch processing | Scheduled same-banking-day windows |
| Eligibility | Broad ACH use under applicable rules | Subject to current eligibility, amount, format, and deadline rules |
| Settlement | Based on the applicable future or next-day schedule | Same banking day when properly submitted and accepted |
| Returns | Applicable return processes remain | Applicable return processes remain |
| Comparison with instant payments | Not continuous real-time settlement | Faster ACH, but still not a 24/7 instant-payment rail |
The Clearing House publishes current EPN processing schedules, including intra-EPN and inter-operator deadlines. Those times can change. Operational teams should use the current schedule and their institution’s earlier customer cutoff rather than copying a time from an undated summary.
EPN is governed by The Clearing House’s EPN Membership and Operating Rules. The Clearing House states that these rules incorporate the Nacha Operating Rules and include EPN-specific provisions and modifications for EPN participants and operations.
The rule layers can include:
An institution should identify which rule created a deadline or obligation instead of attributing every requirement to “EPN” or “Nacha.” A private operating rule also does not replace a consumer or commercial right established by law.
| System or organization | Main role | Processing model | Common use |
|---|---|---|---|
| EPN | Private ACH operator run by The Clearing House | Scheduled batch ACH | Payroll, bill payments, business payments, account transfers |
| FedACH Services | Federal Reserve Banks’ ACH operator service | Scheduled batch ACH | Same broad ACH entry types through participating institutions |
| RTP Network | The Clearing House’s instant-payment network | Individual, continuous settlement using prefunded positions | Immediate account-to-account credit payments |
| CHIPS | Private U.S. large-value payment system run by The Clearing House | Liquidity-saving clearing and settlement with intraday finality | Domestic and cross-border U.S. dollar bank payments |
| Nacha | ACH Network rule administrator | Governance rather than payment processing | Industry-wide ACH rules and participant responsibilities |
The Clearing House operates EPN, RTP, and CHIPS, but they are separate services with different messages, rules, operating schedules, settlement models, and use cases. A payment should not be called “an EPN transaction” merely because a bank also participates in another Clearing House network.
The Clearing House offers services around EPN processing. One example is the Universal Payment Identification Code (UPIC), an identifier that can be shared to receive ACH credits through EPN without disclosing the underlying deposit-account number to the payer. The Clearing House describes UPIC as credit-only; it should not be used to initiate ACH debits.
EPN also offers participant tools for file transmission, reporting, routing, notifications of change, returns, and risk monitoring. These services support operations but do not replace authorization, customer due diligence, fraud controls, sanctions screening, or reconciliation at the participating institution.
A duplicated file can create thousands of incorrect credits or debits. ODFIs should verify file identifiers, record counts, debit and credit totals, effective dates, sequence numbers, and duplicate indicators before release. Recovery controls must prevent a retransmission after a timeout from becoming a second financial file.
Invalid or stale routing and account information can cause rejects, returns, misdirected entries, or notifications of change. Institutions should control routing data and independently verify changed customer instructions.
ODFIs need sufficient balances, credit, collateral, or prefunding under their arrangements. A valid file does not create settlement liquidity. Institutions should reconcile operator settlement totals to their settlement-account entries and monitor unusual concentrations.
ACH debits can be returned for insufficient funds, invalid accounts, or authorization-related reasons. ODFIs should monitor Originators and third-party senders by return category and trend, not only by total volume.
Missing a customer, EPN, or inter-operator cutoff can shift the processing date. Contingency plans should identify alternate transmission methods, decision authority, file-reconstruction controls, and reconciliation after recovery.
Secure operator connectivity does not prove that the originating company’s email, payroll system, bank credentials, or beneficiary master data are secure. Dual approval, least privilege, anomaly monitoring, callback verification, and protected logs remain necessary.
Consumers and business end users should start with their own bank, credit union, payroll provider, or biller. They usually do not have direct access to operator records or the contractual standing to instruct EPN.
This article provides general financial education, not payment-processing, legal, regulatory, security, or compliance advice. Institutions should use current EPN and Nacha rules, operator schedules, contracts, and applicable law for operational decisions.