An EDI file is a standardized electronic document that businesses send to each other to exchange orders, invoices, and shipping information

EDI stands for Electronic Data Interchange. Instead of printing a purchase order, mailing it, and waiting for someone to type it into a computer, two businesses exchange the same information in a structured digital format that both their computer systems can read automatically. The file contains the same data a paper document would — item numbers, quantities, prices, delivery addresses — but organized in a way that removes the need for human data entry on the receiving end.

EDI files are not emails or PDFs. They are plain-text documents with a specific layout that follows an agreed-upon standard. When a large retailer orders products from a supplier, the retailer's system generates an EDI file, sends it to the supplier's system, and the supplier's computer reads it directly into their order management software. No person has to open the file and type anything in.

Most people never see an EDI file directly because they work behind the scenes in business-to-business transactions. If you work in supply chain, purchasing, accounting, or warehouse operations, you may encounter them or need to understand how they move through your company's systems.

Key Takeaways

  • EDI files are structured text documents that let computer systems exchange business information like orders and invoices without human data entry.
  • The most common EDI standard in North America is called X12, while Europe often uses EDIFACT, but both serve the same purpose.
  • EDI files are sent over secure networks or through third-party services called VAN providers, not through regular email.
  • A business typically needs EDI capability only if a large customer or supplier requires it, since setting it up involves cost and technical work.

How EDI files are structured and what they contain

An EDI file is organized into segments, each representing a piece of information. A segment for the shipping address looks different from a segment for line items, but both follow the same rule: data appears in the same position every time, separated by delimiters — usually asterisks or tildes — so the receiving computer knows where one piece of information ends and the next begins.

The file itself is plain text, not binary. If you opened one in Notepad, you would see characters and numbers, but the layout would look strange because the delimiters and segment markers are not designed for human reading. A purchase order EDI file might contain the buyer's name, the supplier's name, the items being ordered, quantities, unit prices, delivery date, and payment terms — everything that would appear on a paper purchase order, just encoded differently.

Common EDI documents include purchase orders (the buyer tells the seller what to send), invoices (the seller tells the buyer what they owe), advance ship notices (the seller tells the buyer a shipment is coming), and payment information. Larger companies may exchange dozens of different EDI document types, but most small businesses that use EDI work with just two or three.

The difference between EDI standards

Two major EDI standards exist. X12 is the standard used in North America, developed and maintained by a standards organization called ASC X12. EDIFACT is used primarily in Europe and other parts of the world. Both do the same job — they let computers exchange business documents — but they use different segment codes and different rules for how data is arranged.

A company in the United States typically uses X12 because that is what their customers and suppliers expect. A company doing business in Europe would use EDIFACT. Some large multinational companies support both, but a small business usually works with only one standard, determined by who they are trading with.

Within X12, there are different versions — X12 version 4010, version 5010, and others. These versions add new features or change how certain information is recorded, but they are all X12. A business and its trading partner must agree on which version they will use, because a file created in one version may not be readable by a system set up for a different version.

How EDI files are sent and received

EDI files are not sent through regular email. They move over secure networks or through third-party services called VAN providers — Value Added Network providers. A VAN is a company that specializes in receiving EDI files from one business, storing them temporarily, and delivering them to another business. The VAN acts as a secure mailbox that both parties trust.

Some large companies set up direct connections with their biggest trading partners, sending EDI files over a secure protocol called AS2 or SFTP without using a VAN. But most small and mid-sized businesses use a VAN because it is simpler than managing multiple direct connections and because the VAN handles the technical details of encryption and delivery confirmation.

When an EDI file arrives at a company, their software reads it, checks it for errors, and either imports the data into their business system automatically or flags it for a person to review if something looks wrong. The whole process can happen in minutes, whereas a paper document or email attachment might take days to process.

When a business needs EDI capability

A business typically needs to set up EDI because a large customer or supplier requires it. Walmart, Amazon, Target, and other major retailers often require their suppliers to send orders and invoices via EDI. If you are a small manufacturer or distributor and your biggest customer demands EDI, you have to implement it or lose the business.

Setting up EDI involves cost and technical work. A company needs to either build EDI capability into their existing accounting or order management software, or buy a separate EDI software tool. They need to work with their trading partner to agree on which documents will be exchanged, which EDI standard and version to use, and how to handle errors or exceptions. They may also need to hire someone or contract with a consultant to manage the setup and ongoing maintenance.

For this reason, EDI is most common among larger companies or companies that do high-volume business with major retailers. A small business with only a few customers may never need EDI. But if you work in supply chain or purchasing for a mid-sized or larger company, EDI is likely part of your daily work.

Common problems with EDI files and how they are fixed

The most common EDI problem is a mismatch between what one system sends and what the other system expects. If the supplier sends an invoice EDI file but the buyer's system is configured to receive only purchase order files, the file will be rejected. This usually happens when two companies agree on EDI but do not fully document which documents they will exchange or which version of the standard they will use.

Another frequent issue is data that does not fit the format. If a product description is too long for the field that holds it, or if a date is formatted differently than expected, the receiving system may reject the entire file rather than just that one piece of data. These problems are usually caught during testing before the companies go live with EDI, but they can still happen if someone changes their system without telling their trading partner.

When an EDI file is rejected, the receiving company's system usually generates an error report. The person managing EDI on that side contacts their trading partner, explains what went wrong, and they work together to fix it. This is why most companies assign one or two people to be responsible for EDI — they become the experts who troubleshoot problems and coordinate with trading partners when something breaks.

EDI versus other ways businesses exchange data

Before EDI, businesses exchanged information on paper or over the phone. Today, they might also use email with attached spreadsheets or CSV files, or they might use a web portal where one company logs in and enters data directly into another company's system. Each method has trade-offs.

Email and spreadsheets are easier to set up but require someone to manually enter or copy data, which is slow and error-prone. A web portal is more automated but requires both companies to use the same portal software. EDI is more complex to set up but once it is running, it is fast, reliable, and requires almost no manual work. For high-volume transactions between large companies, EDI is usually the best choice.

Some companies use EDI for certain trading partners and email or portals for others, depending on the partner's size and the volume of transactions. There is no single right answer — it depends on the specific business relationship and how much automation is worth the effort to set up.

Frequently Asked Questions

Can I open an EDI file in Excel or Word?

You can open an EDI file in a text editor like Notepad and see the raw data, but it will not be readable because of the delimiters and segment codes. You cannot meaningfully edit it in Excel or Word. EDI files are meant to be read by computer systems, not by people. If you need to view the data in a human-readable format, you need EDI software or a converter tool that translates the file into a spreadsheet or document.

What does the file extension look like for an EDI file?

EDI files often have extensions like .edi, .txt, or .dat. The extension does not matter much because the file format is determined by its internal structure, not its name. Some companies use .edi to make it clear the file is EDI, while others use .txt or no extension at all. When you receive an EDI file, the person sending it should tell you what to expect.

Do I need special software to send or receive EDI files?

Yes. Your company needs either EDI software built into your accounting or order management system, or a separate EDI tool. You cannot send or receive EDI files through regular email or file transfer. Your IT department or a consultant can help you choose the right software based on your company's size and the number of trading partners you work with.

What happens if my trading partner and I disagree on which EDI standard to use?

One of you will need to change. Usually, the larger company or the one with more trading partners sets the standard, and the smaller company adapts. If you are a supplier to a large retailer, you use their standard. If you are the large retailer, your suppliers use your standard. This is one reason why X12 is so common in North America — many large companies use it, so their suppliers have to support it.

Is EDI secure?

EDI is more secure than email because files are sent over encrypted networks or through trusted VAN providers, not through public email systems. However, security depends on how well the VAN or direct connection is set up and maintained. Most VANs and large companies take security seriously because they handle sensitive business information. You should ask your trading partner or VAN provider about their security practices before you start exchanging EDI files.