850 · Purchase Order
A buyer’s order to a supplier: the items, quantities, prices, dates, and ship-to locations.
See The 850EDI Software Without The Translator, The Gateway, Or The VAN
Exchange purchase orders, invoices, ship notices, and remittances with every trading partner from one platform. EDI is how businesses send structured documents to each other machine to machine, and running it has meant a translator product, an AS2 gateway or a VAN, and something watching for the file that never arrived. Files.com is the standards-compliant AS2 endpoint, the X12 and EDIFACT parser, the validation, the routing, and the audit trail, as configuration, so your partners see a compliant endpoint and your ERP sees clean records.
No credit card required · 7-day free trial · Live in minutes
#1 MFT vendor in Gartner Peer Insights
Trusted by 4,000+ companies
Every protocol included
4,000+ organizations rely on Files.com every day
Real companies. Real file flows. Real results.
Where The Work Of EDI Actually Goes
The document standards are stable. An X12 850 is a purchase order today the way it was thirty years ago, and every partner’s implementation guide is a variation on a format your systems already understand. The work is everywhere else: translating each partner’s variant into the shape your ERP ingests, carrying documents over the transport each partner mandates, proving each one arrived and was acknowledged, and onboarding the next partner without hiring for it.
The legacy answer was three products and a server: a translator, an AS2 gateway, and a monitoring tool, plus a VAN subscription billed per document. Files.com collapses that stack into one platform that already moves your files. The AS2 endpoint, the parser, the validation, the routing, and the audit log are settings on the same partner folders, so a new document type is a map and a new partner is a configuration, not a project.
Everything An EDI Exchange Needs, On One Platform
Transport, translation, validation, routing, receipts, and onboarding, each a setting rather than a system.
The Transport Your Partners Mandate
Files.com is a standards-compliant RFC 4130 AS2 endpoint with S/MIME encryption and signing, a signed MDN receipt on every message, and certificates managed in the app. Partners who exchange EDI over SFTP or FTPS instead connect the same way to the same platform. Nobody runs an AS2 gateway in a rack to answer a retailer’s mandate.
Translation As Configuration
TransformScript parses X12, EDIFACT, and HL7 natively and writes the JSON, CSV, or XML your ERP, WMS, or accounting system ingests. The map is an expression in the platform, in a DataWeave-style language most integration teams already read, not a translator product you license, host, and patch.
Validation Before Ingestion
File extraction pulls fields out of the parsed document into searchable metadata, and content validation reads inside it, so the invoice that references an unknown PO or the ship notice whose quantities do not add up is flagged at intake, before it reaches the system that would choke on it.
A Folder For Every Partner, And Automation On Every Folder
Each trading partner gets an inbox, an outbox, and a sent folder. A document landing in an inbox triggers a workflow: parse, validate, rename, route to the ERP’s pickup location, notify the team. A file dropped in an outbox goes out over AS2 and retries until delivery is confirmed.
Receipts And The Missing File
Every transmission and its MDN status land in the audit log, and delivery monitoring declares when a partner’s document is due and alerts when it does not arrive. The failure that costs EDI teams the most is the file that never came, and it stops being silent.
Onboarding That Does Not Scale With Headcount
A new partner is a partner onboarding flow: their space, their certificates, their protocol, their maps, all configuration. The hundredth partner costs what the tenth did, which is the difference between an EDI team and an EDI setting.
Customers Running Files.com With EDI
David J. Joseph Runs Nucor Mill EDI on Files.com After Retiring Its FTP Server
Files.com preserved the scheduled, bidirectional workflows connecting DJJ’s applications and Nucor’s mills while taking the underlying infrastructure off DJJ’s engineering team.
Read The Story
HI-LEX Moved a Live OEM AS2 Connection Off a Dedicated Gateway Without Missing a Sequencing File
The live migration required synchronous receipts and an unusual non-X12 header, then established a repeatable pattern for future AS2 partners.
Read The Story
Kasanova Moved Supplier and Customer EDI Off an In-House Windows FTP Server Without Rewriting a Partner Map
Kasanova kept its internal systems reading and writing in the same locations while Files.com took over the exposed endpoint and absorbed 30% growth.
Read The Story
Guardian Fall Protection Lands Supplier EDI Straight Into Epicor and Closed Its Acknowledgement Gaps
A Files.com mount made each supplier upload immediately available to Guardian’s Epicor-connected EDI system, without an intermediary mailbox, polling job, or self-hosted SFTP server.
Read The Story
The Transaction-Set Library
The X12 documents an EDI exchange runs on: what each one is for, who sends it, the segments inside it, and how it moves on Files.com.
810 · Invoice
The supplier’s bill for goods or services delivered against a purchase order.
See The 810820 · Payment Order / Remittance Advice
A payer’s notice of payment: which invoices are being paid, for how much, and how.
See The 820940 · Warehouse Shipping Order
A shipper’s instruction to a warehouse or 3PL to ship goods to a customer.
See The 940855 · Purchase Order Acknowledgment
The supplier’s answer to a purchase order: accepted, rejected, changed, or backordered, line by line.
See The 855846 · Inventory Inquiry / Advice
A supplier’s report of stock levels: on hand, available, committed, and on order.
See The 846852 · Product Activity Data
A retailer’s report of sales and inventory movement by product and location, sent back to the supplier.
See The 852945 · Warehouse Shipping Advice
A warehouse’s confirmation that an order shipped: what, when, by which carrier, with tracking.
See The 945997 · Functional Acknowledgment
The receipt that says an EDI transmission arrived and was parsed, with any syntax errors found.
See The 997214 · Transportation Carrier Shipment Status Message
A carrier’s status update on a shipment in transit: picked up, in transit, out for delivery, delivered.
See The 214856 · Ship Notice / Manifest (ASN)
The advance ship notice: what is in the shipment, how it is packed, and how it is labeled, sent before it arrives.
See The 856860 · Purchase Order Change Request (Buyer Initiated)
A buyer’s change to an order already sent: add, delete, or modify lines, quantities, prices, or dates.
See The 860824 · Application Advice
A business-level accept or reject of a received document, with the reasons, beyond what a 997 can say.
See The 824210 · Motor Carrier Freight Details and Invoice
A trucking carrier’s invoice for a shipment, with the freight details the charges are based on.
See The 210830 · Planning Schedule with Release Capability
A customer’s forecast of what it will need, by item and period, which suppliers plan against and may ship against.
See The 830832 · Price / Sales Catalog
A supplier’s catalog of items with descriptions, identifiers, packaging, and prices.
See The 832943 · Warehouse Stock Transfer Shipment Advice
A shipper’s notice to a warehouse that inbound inventory is on its way to be received.
See The 943867 · Product Transfer and Resale Report
A distributor’s report to a manufacturer of what it sold, to whom, and what it transferred between locations.
See The 867812 · Credit / Debit Adjustment
A notice that an amount owed is being adjusted up or down, with the invoice it applies to and the reason.
See The 812944 · Warehouse Stock Transfer Receipt Advice
A warehouse’s confirmation of inventory received: what arrived, in what quantity and condition.
See The 944864 · Text Message
A free-form text message inside the EDI channel, for notices that have no structured document.
See The 864990 · Response to a Load Tender
A carrier’s acceptance or decline of a shipper’s request to move a load.
See The 990861 · Receiving Advice / Acceptance Certificate
A buyer’s report of what was received against a shipment: quantities accepted, rejected, and why.
See The 861870 · Order Status Report
A supplier’s report on the status of an order or its lines: in process, shipped, backordered, cancelled.
See The 870865 · Purchase Order Change Acknowledgment / Request (Seller Initiated)
The seller’s answer to a buyer’s change request, or a change the seller proposes on its own.
See The 865The Platform Your Partners Already Connect To
Files.com customers exchange EDI with effectively every major trading partner. Automotive suppliers meet an OEM’s custom AS2 specification, distributors land supplier documents straight into their ERP, and companies retiring a dedicated AS2 gateway move live partner connections one at a time without a cutover weekend. Each partner connects the way it connects to everyone else, and the mandate is answered.
AS2 is available on the Power tier and above, and Enterprise includes as many connections as you require. Files.com publishes what each plan includes, and a partner onboarding portal under your own brand is part of the platform, not an add-on.
EDI Questions
What teams evaluating EDI software ask about translation, transport, acknowledgments, healthcare documents, and onboarding partners on Files.com.
EDI software is whatever translates standardized business documents (X12 or EDIFACT purchase orders, invoices, ship notices, remittances) between a trading partner’s format and your own systems, carries them over the transport the partner requires, and tracks that each one arrived and was acknowledged. Historically that meant three products: a translator, an AS2 gateway or a VAN subscription, and monitoring. Files.com does all three as configuration on one platform. The plain-language explanation is in What is EDI.
Yes. TransformScript, the transformation language built into Files.com, parses X12, EDIFACT, and HL7 natively and outputs JSON, CSV, or XML, so an inbound 850 becomes the order record your ERP ingests and an outbound invoice is generated from your system’s export. Maps are expressions written in the platform, in a DataWeave-style syntax, and run inside the same workflow that receives the file.
No. Files.com connects directly to trading partners over AS2, SFTP, and FTPS with no per-document fee. When a partner exchanges through a VAN, Files.com connects to the VAN’s SFTP or FTPS endpoint as a remote server mount, so the VAN traffic lands in the same partner folders and workflows as direct connections.
Any X12 or EDIFACT document. The transport carries the payload byte for byte, and TransformScript parses the standard, not a fixed list of document types. The transaction-set library on this page covers the 25 most common X12 documents, from the 850 purchase order to the 997 functional acknowledgment, with the segments, the flow, and how each moves on Files.com.
Only if your partner requires it. Retailers, clearinghouses, and supply-chain networks usually mandate AS2; many other partners exchange EDI over SFTP or FTPS. Files.com is a standards-compliant AS2 endpoint and a managed SFTP and FTPS server on the same platform, so the partner’s protocol is a per-partner setting, not a product decision.
Every AS2 transmission is paired with a signed MDN receipt that cryptographically confirms the recipient received the exact bytes sent, and outbound messages retry automatically until delivery is confirmed. The EDI-level acknowledgments, the 997 functional acknowledgment and the business replies such as the 855 and 824, are documents that travel through the same partner folders and workflows as everything else, and every transmission and receipt is recorded in the audit log.
Yes. TransformScript parses HL7 v2 alongside X12 and EDIFACT, healthcare clearinghouses connect over AS2 the same way retailers do, and Files.com signs HIPAA business associate agreements. The compliance posture is published on the compliance pages.
Through partner onboarding: create the partner, exchange AS2 certificates or issue SFTP credentials, and the partner’s inbox, outbox, and sent folders exist. Maps for that partner’s documents are TransformScript steps on the workflows attached to those folders. Files.com customers exchange EDI with effectively every major trading partner, including Walmart, Amazon, Target, Costco, and the healthcare clearinghouses.
AS2 is available on the Power tier and above, and Enterprise includes as many AS2 connections as you require. TransformScript usage is metered in transformation credits included with every plan. Current tiers, connection counts, and credit allotments are published.
The AS2 endpoint is live when the trial starts. A partner connection is live once certificates are exchanged, which is usually the same day the partner’s EDI team returns them. Files.com customers have moved live AS2 connections off dedicated gateways one partner at a time without interrupting production traffic.
Run EDI Without The Legacy Stack
Start the 7-day trial, turn AS2 on, and exchange certificates with your first partner. Documents land in their folder, parse into the records your systems read, and every transmission carries a signed receipt.
No credit card required • Free for 7 days • Live in minutes