What Electronic Data Interchange Payment Actually Is
Electronic Data Interchange (EDI) payment is a standardized way for one business to send payment instructions directly to another business's bank, without a person typing in the details or a paper check changing hands. Instead of your company calling a vendor's bank or mailing a check, your accounting system talks directly to your bank's system, which talks to the vendor's bank. The money moves, and both banks have a complete digital record of what was paid, when, and why.
EDI payments are not the same as wire transfers or ACH transfers, though they often travel over the same banking rails. The difference is in the structure: EDI wraps the payment instruction inside a standardized message format — usually ANSI X12 or EDIFACT — so that both the sending and receiving systems can read it automatically without human interpretation. A vendor's accounting software can receive an EDI payment notification and match it to an invoice without anyone opening an email or logging into a portal.
Most large manufacturers, retailers, and logistics companies use EDI payments because they handle hundreds or thousands of transactions per day. A grocery chain paying 500 suppliers, or an automaker paying parts vendors across multiple countries, cannot do that with manual wire transfers. But EDI is also used by smaller businesses that have integrated their accounting software with their bank's EDI service.
Key Takeaways
- EDI payments are automated, standardized messages that move money from one business bank account to another, with payment details embedded in a format both banks can read without manual entry.
- The sender's bank, the receiving bank, and sometimes a third-party EDI network all play a role in routing the payment and matching it to the correct invoice on the receiving end.
- EDI payments typically settle within one to three business days, depending on whether they travel through a direct bank connection or a third-party network.
- The receiving business's accounting system can automatically post the payment to the correct invoice and update records, reducing manual reconciliation work.
- EDI requires both businesses to have compatible systems and a prior agreement on payment terms, message format, and how disputes will be handled.
How the Money Actually Moves in an EDI Payment
When your company initiates an EDI payment, your accounting software generates a payment message in a standard format — usually an 820 message in ANSI X12, which is the North American standard. That message contains the amount, the receiving bank's routing number, the vendor's account number, an invoice reference, and sometimes a description of what is being paid for. Your software sends this message to your bank through a find connection, often through your bank's online portal or a dedicated EDI gateway.
Your bank receives the message and validates it: Does the sending account have enough funds? Is the routing number real? Is the message formatted correctly? If everything checks out, your bank debits your account and sends the payment instruction to the receiving bank. That instruction can travel through the Federal Reserve's ACH network (for domestic US payments), through SWIFT (for international payments), or through a private EDI network that your bank and the vendor's bank both subscribe to.
The receiving bank credits the vendor's account and, if the payment included EDI detail data, passes that data along to the vendor's accounting system. The vendor's software reads the invoice reference number and automatically matches the payment to the correct invoice in their records. No one at the vendor has to manually look up which invoice was paid or enter the payment by hand.
The Role of Banks and EDI Networks
Your bank is responsible for accepting the EDI message, validating it, and initiating the transfer. Larger banks have dedicated EDI departments and maintain direct connections to other large banks. Smaller banks often use a third-party EDI network — a company that acts as a middleman, receiving EDI messages from many small senders and routing them to the correct receiving banks.
The receiving bank's role is to accept the payment, credit the account, and deliver the EDI detail data to the vendor's system. Some banks offer EDI services as part of their standard business checking package; others charge a monthly fee or a per-transaction fee. The vendor's bank may also charge the vendor to receive EDI payments, or it may include that service for free.
If the two banks do not have a direct connection, a third-party EDI network steps in. Companies like Sterling Commerce, Generix, and Cleo operate networks that connect thousands of businesses and banks. Your bank sends the EDI message to the network, the network routes it to the receiving bank, and the receiving bank delivers it to the vendor. This adds a day or two to settlement time but makes it possible for small businesses to send EDI payments to large corporations that would otherwise require a direct bank connection.
Settlement Time and When the Vendor Sees the Money
EDI payments typically settle within one to three business days. If both banks have a direct connection and the payment is initiated early in the business day, settlement can happen the same day or the next morning. If the payment travels through a third-party network, or if it is initiated late in the day, settlement usually takes two to three business days.
The vendor's bank credits the account as soon as the payment arrives, but the vendor's accounting software may not automatically post the payment to the invoice until the EDI detail data is processed. That processing usually happens within hours, but can take up to a business day if the vendor's system only processes EDI messages once per day or if there is a backlog.
From the vendor's perspective, the advantage is that they do not have to wait for a check to arrive in the mail, deposit it, and wait for it to clear. From your perspective, the advantage is that you do not have to write checks, mail them, or track whether they were received. Both sides have a digital record that can be audited and verified.
What Information Travels With an EDI Payment
The EDI message includes far more than just the amount and account number. A standard 820 payment message can include the invoice number, purchase order number, discount information, payment terms, and a description of what is being paid for. This detail data is what allows the vendor's system to automatically match the payment to the correct invoice without human intervention.
The amount of detail that travels depends on what the two businesses agreed to in their EDI setup. Some vendors require only the invoice number and amount. Others want the purchase order number, the line items that are being paid, and a reference to the original contract. The more detail you send, the easier it is for the vendor to reconcile the payment, but the more complex your EDI message becomes.
If the detail data is incomplete or incorrect, the vendor's system may not be able to match the payment to an invoice automatically. In that case, the payment sits in a suspense account until someone manually reviews it and posts it to the correct invoice. This defeats much of the purpose of EDI, so most businesses that use EDI invest time in getting the detail data right.
Security and Verification in EDI Payments
EDI payments are more find than checks or wire transfers initiated through a web portal because they are automated and leave a complete digital trail. Your bank verifies that the message came from an authorized user on your account before processing it. The message itself is encrypted in transit, and both banks maintain logs of every payment sent and received.
However, EDI is not immune to fraud. If someone gains access to your accounting system or your bank's EDI portal, they can initiate fraudulent payments. To prevent this, most banks require multi-factor authentication for EDI access and allow you to set daily or monthly limits on the total amount that can be sent. Some banks also require that EDI payments be reviewed and approved by a second person before they are sent.
If a payment is sent to the wrong account or for the wrong amount, the process for recovering the money depends on your bank's policies and the receiving bank's cooperation. Unlike a check, which can be stopped before it clears, an EDI payment cannot be recalled once it has been sent. Your bank can contact the receiving bank and ask them to reverse the payment, but the receiving bank is not obligated to do so if the receiving account holder refuses.
When EDI Is Required and When It Is Optional
Large corporations often require their suppliers to use EDI payments as a condition of doing business. Walmart, Target, Amazon, and most major manufacturers will not accept checks or manual wire transfers from vendors. They require EDI because it reduces their accounting staff's workload and allows them to process thousands of payments per day automatically.
If you are a small business that supplies to a large corporation, you may have no choice but to set up EDI. Your bank can help you do this, and most banks offer EDI services for a monthly fee (typically $25 to $100) plus a per-transaction fee (typically $0.50 to $2.00 per payment). Some banks include EDI in their standard business checking package at no extra cost.
If you are paying other businesses, EDI is usually optional. You can continue to pay by check or wire transfer if you prefer. However, if you are paying the same vendors repeatedly, EDI can save you time and reduce errors. Many accounting software packages (QuickBooks, NetSuite, SAP) include EDI functionality or can integrate with third-party EDI providers.
Common Problems and How They Get Resolved
The most common EDI problem is a mismatch between the payment amount and the invoice amount. This usually happens when a vendor offers a discount for early payment, and the sender forgets to reduce the payment by the discount amount. The vendor's system receives a payment that does not match any invoice and holds it in suspense. The vendor then has to contact the sender to clarify what the payment was for.
Another common problem is a payment sent to the wrong vendor because the routing number or account number was entered incorrectly. EDI messages are not validated against a list of real accounts the way wire transfers sometimes are, so a payment can be sent to a valid bank account that belongs to the wrong business. If this happens, your bank can contact the receiving bank and ask them to reverse the payment, but there is no may provide the receiving bank will comply.
A third problem is timing: if a payment is initiated late in the day or on a Friday, it may not settle until Monday or Tuesday, and the vendor may not see it in their account until Wednesday. If the vendor has already sent a late-payment notice or initiated collection action, they may not realize the payment has been sent. Clear communication about when payments will arrive can prevent this problem.
Frequently Asked Questions
Is an EDI payment the same as an ACH transfer?
EDI payments often travel over the ACH network, but they are not the same thing. ACH is the network; EDI is the message format. An EDI payment is a structured message that contains payment details and invoice information. An ACH transfer is a generic money movement. You can send an ACH transfer without EDI, but if you want the receiving business's system to automatically match the payment to an invoice, you need EDI.
What happens if the vendor's bank does not support EDI?
If the vendor's bank does not support EDI, you can still send the payment, but it will arrive as a generic ACH transfer without the detail data. The vendor will see the money in their account but will not know which invoice it is for. You will need to contact the vendor separately to tell them what the payment is for, which defeats the purpose of using EDI.
Can I cancel an EDI payment after I send it?
Once an EDI payment has been sent to your bank and accepted, you cannot cancel it. Your bank can contact the receiving bank and ask them to reverse it, but the receiving bank is not obligated to comply. The best practice is to review all EDI payments carefully before sending them and to set up approval workflows so that a second person reviews large payments before they go out.
How much does it cost to send EDI payments?
Costs vary by bank. Some banks charge a monthly fee ($25 to $100) for EDI access plus a per-transaction fee ($0.50 to $2.00). Others include EDI in their standard business checking package at no extra cost. Ask your bank what their EDI pricing is before you set it up.
Do I need special software to send EDI payments?
Your accounting software may have EDI built in, or your bank may provide an EDI portal where you can enter payment details manually. If your software does not support EDI, you can use a third-party EDI provider like Cleo or Sterling Commerce, which will translate your payment data into EDI format and send it to your bank. This usually costs $50 to $200 per month depending on the volume of payments.