What is EDI?
EDI is the computer-to-computer exchange of business documents in a standard format. A purchase order that once arrived as a PDF now arrives as a structured file that the receiving system reads without anyone retyping it. The most common standard in North America is ANSI X12; EDIFACT is common internationally. Retailers, healthcare payers, distributors and logistics companies use EDI because every document looks the same to every partner, so their systems can process it automatically.
- •Replaces emailed PDFs, faxes and manual re-entry
- •Uses agreed document types, called transaction sets (850 purchase order, 856 ship notice, 810 invoice, 997 acknowledgement)
- •Usually starts because a customer or payer requires it
Why do trading partners require EDI?
Large buyers handle thousands of orders and invoices. A fixed format lets their systems accept, match and pay documents without staff touching each one, and the acknowledgement loop shows both sides what arrived. That is why a vendor guide often says "EDI only". Meeting it is a condition of selling to them, and the partner, not you, decides how and when it approves your setup.
- •Fewer manual emails and keying errors
- •Consistent data fields on every document
- •A built-in confirmation that each file was received
How does EDI work?
EDI works in five steps, and the same loop repeats for every document.
- •Step 1: A system creates a business document, for example a retailer's purchase order.
- •Step 2: EDI software translates the internal data into the standard format (X12) and wraps it in an envelope that says who it is from and to.
- •Step 3: The file travels over the connection both sides agreed, such as AS2, SFTP, an API or a VAN.
- •Step 4: The receiving EDI software checks the envelope, validates the document against the standard and the partner's rules, and translates it into data the receiver's system understands.
- •Step 5: The receiver sends back a functional acknowledgement (a 997 or 999) saying whether it accepted the file, and the business conversation continues with the next document.
What is EDI translation software?
EDI translation software converts between your own data (a spreadsheet, QuickBooks, an ERP or JSON from your application) and EDI standards such as X12. A good one does more than convert: it validates documents before they are sent, maps your fields to each partner's rules, delivers over the partner's connection and tracks acknowledgements so you can see status. SignalEDI validates X12 before send, supports AS2, SFTP and API delivery, and shows document status and acknowledgements in one place.
- •Translates both directions (your data to X12, and X12 to your data)
- •Validates against the standard and the partner's rules
- •Delivers and tracks acknowledgements
What does a worked EDI example look like?
The table below follows one order between a retailer and a supplier. The order numbers and quantities are illustrative. The same four document types cover most retail programs, and each step ends with an acknowledgement.
Which EDI documents do small businesses use first?
Do not learn the whole catalogue. Learn the documents in your partner's vendor guide. Retail programs usually start with the 850, 856 and 810 (and often an 855 acknowledgement of the order). Healthcare starts with the 837 claim, 835 remittance and 270/271 eligibility. Every program also uses 997 or 999 acknowledgements.
- •Retail first: 850 purchase order, 856 advance ship notice, 810 invoice
- •Healthcare first: 837 claim, 835 remittance, 270/271 eligibility
- •Always: 997 or 999 acknowledgements
How should a small business evaluate EDI?
For a small business the goal is not to become an EDI expert; it is to meet a trading partner's requirement with validated documents, visible status and a predictable cost. Look beyond file translation. Start from the partner's requirement, list the document types, confirm which connection the partner uses, then compare total cost and support. SignalEDI publishes its plan prices on the pricing page so you can check cost before you commit. Partner testing and approval stay on the partner's calendar, so plan for that, not for a fixed go-live date.
- •Start with the document types in the partner's guide
- •Confirm the transport (AS2, SFTP, API)
- •Compare total cost and support, including testing time
