An EDI payment is a computer-to-computer transaction that moves money between two businesses while carrying structured remittance data in the same message, so the receiver’s accounting software can automatically match the funds to the invoices they pay. The money itself usually travels over the ACH network. What makes it an EDI payment, rather than a plain bank transfer, is the standardized electronic document traveling alongside the dollars.1X12. X12 Home
What Separates an EDI Payment From a Regular ACH Transfer
A standard ACH transfer moves funds but tells the receiver almost nothing about what the payment covers. A basic Corporate Credit or Debit (CCD) entry carries only a single addenda record. EDI payments use the Corporate Trade Exchange (CTX) format instead, which supports up to 9,999 addenda records in a single transaction.2ACH Guide for Developers. ACH File Details Those addenda records carry a full ANSI ASC X12 or UN/EDIFACT message, which means one CTX entry can settle dozens of invoices at once and tell the receiver exactly how to apply every dollar.
That matters because it eliminates the most labor-intensive task in accounts receivable: cash application. When $47,000 lands with no detail, someone has to work out which invoices it covers. When the same amount arrives as a CTX entry with structured remittance advice, the receiver’s software reads it and closes the matching invoices on its own. Same-day ACH is available for transactions up to $1 million, with three settlement windows each business day.3Nacha. Same Day ACH
What an EDI Payment Message Looks Like Inside
Every EDI payment follows a rigid structure so that different software systems can read it without confusion. The message is built from segments (lines of data) and elements (individual data points like a date or dollar amount), all wrapped in envelopes that identify the sender, the receiver, and the transaction type.
Each message opens with an ST (Transaction Set Header) segment and closes with an SE (Transaction Set Trailer) that confirms how many segments the message contains.4Oracle Corporation. Transaction Sets (ST/SE) Between those bookends sit trading partner identifiers, a Beginning Segment for Payment Order (BPR) that specifies the payment amount and method, and one or more remittance detail loops listing each invoice being paid, the original amount, any discounts taken, and the net applied. The outer envelope uses ISA and GS segments that function like digital addresses, routing the message to the correct trading partner.5Summit Community Care. Required ISA/IEA and GS/GE Settings in EDI Claims
The Standards Behind EDI Payments
In the United States, the dominant standard is ANSI ASC X12, maintained by a nonprofit accredited by the American National Standards Institute for more than 40 years.1X12. X12 Home The transaction set used for payments is the 820 Payment Order/Remittance Advice. An 820 can instruct a financial institution to make a payment, send remittance detail so the receiver knows what the payment covers, or do both at once.6Department of Housing and Urban Development (HUD). Transaction Set 820 – Payment Order/Remittance Advice
Across borders, UN/EDIFACT plays the equivalent role. Maintained by the United Nations Economic Commission for Europe, it covers administration, commerce, and transport data and is widely used outside North America.7UNECE. Introducing UN/EDIFACT
The payments industry is also converging on ISO 20022, an XML-based messaging standard built to carry richer data than older formats. The Federal Reserve implemented ISO 20022 for the Fedwire Funds Service on July 14, 2025.8Federal Reserve Financial Services. Fedwire Funds Service to Implement ISO 20022 on July 14 SWIFT’s coexistence period for cross-border payments ended on November 22, 2025, after which only ISO 20022 messages are delivered.9SWIFT. ISO 20022 in Bytes for Payments – One Month to Go None of this eliminates X12 for domestic B2B transactions. It does mean the payment rails underneath EDI are carrying more structured data than before, and banks and trading partners will progressively incorporate ISO 20022 elements into EDI workflows.
How a Payment Moves From Send to Settlement
Once trading partners are set up, the day-to-day flow is largely hands-off. The sender’s ERP system generates a formatted EDI file, typically an 820, with the payment amount, bank routing instructions, and remittance detail for every invoice being settled. The file is wrapped in the ISA/GS envelope and transmitted through a secure gateway to the trading partner or a clearinghouse.
When the file arrives, the receiver’s system returns a 997 Functional Acknowledgment. The 997 confirms that the file was received and that its segments and elements conform to the agreed standard. It does not confirm that the business content is accurate, only that the system could read the structure.10Defense Logistics Agency (DLA). DLMS Implementation Convention (IC) 997 Functional Acknowledgment The receiver’s accounting software then extracts the remittance data, matches it against outstanding invoices, and closes them automatically.
The money itself rides the ACH network. Historically these payments settled in batches on the next business day. Same-day ACH compressed that: transactions up to $1 million can now settle the same day they are submitted, across three settlement windows.3Nacha. Same Day ACH The legal framework governing when a payment becomes final and irrevocable is Uniform Commercial Code Article 4A, which addresses acceptance, payment dates, and the obligations of each bank in the chain.11Legal Information Institute (LII) / Cornell Law School. UCC – Article 4A – Funds Transfer
What Setting Up EDI Payments Involves
Getting EDI payments running between two companies takes legal agreements, technical configuration, and bank coordination. The effort is front-loaded; the automation comes after.
Trading Partner Agreement
Before any transaction, both sides formalize a Trading Partner Agreement. The TPA defines the technical specifications each side will use, assigns liability when data errors occur, and specifies communication protocols. Transactions depend on a properly completed TPA and successful testing before a partner is approved to go live.12Commonwealth of Pennsylvania. Trading Partners
Identifiers and Protocols
Each party needs unique ISA and GS identifiers that act as digital addresses so each transmission reaches the right company.5Summit Community Care. Required ISA/IEA and GS/GE Settings in EDI Claims The two companies also agree on a secure communication method. AS2 and SFTP are the most common choices. AS4, a newer protocol built on web services, adds standardized exception handling, non-repudiation receipts, and built-in encryption that some organizations prefer for sensitive data.13Oracle Documentation. Enabling AS4-Based Message Exchange
Mapping and Bank Authorization
Technical teams map EDI fields to the company’s ERP software so incoming payment data imports correctly. Mapping is where most implementation delays happen, because every company’s chart of accounts and invoice numbering scheme is different. The bank also needs authorization forms with routing and account numbers for the ACH side of the transaction.
Cost Shape
Costs vary with the delivery model. Cloud-based managed services charge lower upfront fees but bill per document. Value Added Networks (VANs) charge monthly subscription fees and per-transaction fees on top of any setup. In-house solutions carry the largest upfront investment in software, mapping, and testing but can reduce per-transaction costs at high volume. Bank authorization fees exist as well but are modest compared to software and integration work.
When Something Goes Wrong
The 997 only checks syntax. When the receiver’s application digs into the business content and finds problems like a mismatched invoice number or an invalid account code, it responds with an 824 Application Advice. The 824 reports whether the transaction was accepted, rejected, or accepted with changes, and includes error codes so the sender knows what to fix.14HUD.gov. Transaction Set 824 – Application Advice
When actual money moves to the wrong place, UCC Article 4A assigns liability based on whether each party followed the agreed security procedures. If a payment goes to the wrong beneficiary, is sent for the wrong amount, or is an accidental duplicate, and the sender can prove it followed the security procedure while the receiving bank did not, the sender is not obligated to pay the erroneous order. The receiving bank can try to recover the funds from the unintended beneficiary under the law of mistake and restitution.15Legal Information Institute (LII) / Cornell Law School. UCC 4A-205 – Erroneous Payment Orders
There is a hard deadline in that framework. Once a sender receives notice that an erroneous payment was accepted or its account debited, it has no more than 90 days to discover the error and notify the bank. Miss that window and liability shifts to the sender for any losses the bank can prove resulted from the delay.15Legal Information Institute (LII) / Cornell Law School. UCC 4A-205 – Erroneous Payment Orders Where a bank fails to execute a payment order or executes it improperly, the bank is liable to the sender for expenses, incidental costs, and interest losses. Consequential damages beyond that are only recoverable if the parties have an express written agreement allowing them.16Legal Information Institute (LII) / Cornell Law School. UCC 4A-305 – Liability for Late or Improper Execution
One boundary to note: healthcare EDI carries extra obligations. Covered entities conducting standard electronic transactions must use X12 Version 5010 and protect PHI under 45 CFR Part 162.17eCFR. 45 CFR Part 162 – Administrative Requirements Non-healthcare businesses are not bound by HIPAA, but trading partner agreements usually impose similar security obligations contractually.
Records the IRS Expects You to Keep
Companies using EDI must meet specific IRS requirements for retaining electronic records. Under Revenue Procedure 98-25, machine-sensible records must be kept at least until the statute of limitations for assessment expires for each relevant tax year, and longer for records tied to fixed assets or certain insurance calculations.18Internal Revenue Service (IRS). Requirements for Retaining Machine-Sensible Records (Rev. Proc. 98-25)
The IRS also requires an audit trail connecting EDI records to the company’s books and from the books to the tax return. If EDI records lack detail that would have appeared on paper, like product descriptions or vendor names, the company must supplement them with files such as product code lists or vendor master data. Documentation of the business processes that create, modify, and maintain the records, including field definitions and record layouts, is required as well.18Internal Revenue Service (IRS). Requirements for Retaining Machine-Sensible Records (Rev. Proc. 98-25) Companies tend to discover these requirements during an audit, when reconstructing the trail is expensive. Building it in from the start costs far less.
EDI Payments Versus API-Based Payments
APIs are increasingly common for B2B data exchange, so the comparison comes up quickly. The tradeoff is straightforward. EDI excels at high-volume, batch-oriented transactions between established trading partners. APIs offer real-time processing that works well for inventory visibility, instant order confirmations, and situations where both sides need immediate feedback.
EDI typically requires more upfront investment in software, mapping, and testing but delivers lower per-transaction costs once running at scale. APIs cost less to set up but carry ongoing maintenance as interfaces change, and per-call fees add up. In practice, many businesses use both: EDI for core payment and invoicing workflows where formats are stable and volumes are high, APIs for real-time integrations where speed matters more than batch efficiency. Replacing working EDI infrastructure with APIs purely to modernize rarely pencils out. Adding APIs alongside EDI for specific use cases often does.