Managed EDI for distributors, connected to the ERP you run
Comparatio EDI turns your trading partners’ documents into ERP transactions and builds the acknowledgments, ASNs and invoices that go back. Our engineers build the maps, test with each partner, run the connections and act on monitoring alerts.
- On your server or one we host
- Customer and supplier side
- Maps run by our engineers
Your customers
- Received: 850 orders
- Sent: 855 · 856 · 810 · 846
Your suppliers
- Sent: 850 purchase orders
- Received: 855 · 856 · 810
Comparatio
Translates, checks and monitors your documents
Your ERP
- Prophet 21
- NetSuite
- CloudSuite Distribution
- Agility
- 170+
- customers
- ~8,000
- live trading-partner connections
- 1,000+
- pre-built trading-partner maps
- 100M+
- EDI transactions processed to date
What Comparatio EDI is
EDI software, and the engineers who run it
You don’t buy a translator and staff it yourself. Comparatio EDI is the software that moves your documents and the team that keeps it running: named engineers on every ticket. 1,000+ pre-built maps and nearly 8,000 live partner connections mean your partner’s map often exists already.
The formats your partners send
X12, EDIFACT, cXML, SAP IDOC, GS1/UCC-128 labels, CSV, Excel, flat files and JSON, translated to and from your ERP.
A connection to each partner
AS2, SFTP, FTP, HTTPS and VAN connections and the ECGrid API, plus procurement networks and marketplaces. We set up and maintain each one, certificates included.
Connected to your ERP
Customer orders land as ERP orders, and outbound documents are built from your ERP’s own records. On Prophet 21, NetSuite and CloudSuite Distribution, the supplier side is covered too.
Outbound documents checked
Every outbound X12 document is checked and reported, and can be held per partner. A field-level audit trail shows what each document carried.
Watches for what’s missing
Monitoratio flags missing acknowledgments, missing ASNs and orders that never reached your ERP, and opens the ticket. In the 90 days to 28 Oct 2026, 61% of our support tickets were opened this way.
Every document in view
The EDI Portal shows your team its documents, the raw X12 next to a readable version, with full-text search.
Where it runs
On your server, or on one we host for you
Comparatio runs on your server or on one we host for you. Documents travel over the connection each trading partner uses. AI features send the document, or the question and the log lines and configuration rows needed to answer it, to Anthropic’s Claude; PDF Import does this under your own API key. Access, certificates and hosting are covered on Security & Compliance.

ERP integration
Connected to the ERP you run
Each connection uses the interface that ERP is built to take data through. Each ERP has its own page with the documents, the ERP records they land on, and their status.
Epicor Prophet 21
Reads P21 directly and hands documents to P21 through its own import files, with EDI fields kept in user-defined (UD) tables. Multi-company P21 included.
Oracle NetSuite
A RESTlet in your NetSuite account. Customer orders become Sales Orders; supplier acknowledgments, ASNs and invoices land on the Purchase Order, as Inbound Shipments and as Vendor Bills.
Infor CloudSuite Distribution
Through Infor’s ION API gateway: customer orders in; acknowledgments, ASNs and invoices out; supplier documents too. On-premises SX.e on request.
DMSi Agility
Through the Agility API: customer orders become Agility sales orders, and acknowledgments, ASNs, invoices and inventory advice go back out. In production at a large distributor.
SAP Business One
An SAP Business One integration, documented on its own page.
Infor SyteLine (CloudSuite Industrial)
Live through SyteLine’s own EDI import since 2019: customer orders in, invoices out.
INxSQL
On request: built, then switched on and tested for you during setup.
Changing ERPs?
Your trading-partner connections stay with Comparatio and most maps carry over. Documents from the new ERP are compared with the old ones before the switch.
Running something else?
Other ERPs and warehouse systems connect through files or APIs, set up for your system. Tell us what you run.
Documents
29 X12 transaction sets and 10 EDIFACT message types in production
Orders, acknowledgments, ship notices, invoices, inventory, catalogs, remittances, planning and warehouse documents, plus cXML, SAP IDOC, GS1/UCC-128 labels, CSV, Excel, flat files and JSON. Each set, by name, is on Transaction types.
- 840
- 850
- 855
- 810
- 856
- 997
- 820
- 830
- 832
- 846
- 852
- 860
- 861
- 867
- 844
- 824
- 753
- 754
- 180
- 210
- 214
- 865
- 870
- 875
- 940
- 943
- 944
- 945
- 947
AI document intake
PDFs from partners who will never send EDI
Some suppliers and customers send PDFs instead of EDI. PDF Import reads them, checks them and posts them to your ERP alongside your EDI traffic.
No per-vendor templates
Anthropic’s Claude reads each PDF under your own API key: vendor invoices, customer purchase orders, order confirmations and ship notices.
Checked before it posts
Duplicate, arithmetic, PO and vendor checks run on each document. 100% detection rate in production: every PDF that failed a check was held for review.
Into your ERP
What passes posts to your ERP. In production on Prophet 21; available for CloudSuite Distribution and NetSuite. Freight and service bills without a PO post as non-PO vouchers in Prophet 21; in CloudSuite Distribution and NetSuite they are flagged for your team to enter.
Leaving TPCx?
TPCx reaches end of life in December 2026
Comparatio moves Prophet 21 distributors off TPCx partner by partner. 80+ trading partners are in our migration program. Our first TPCx migration finished in October: every partner is off TPCx. Partners who reach you through a VAN keep your EDI ID; partners connected directly, such as over AS2, set up and test again. After cutover we watch the old TPCx mailbox. How a TPCx migration works

How setup works
A new trading partner, typically live in 4–8 weeks
Paced by the trading partner, including enrollment, testing and certification. With 1,000+ pre-built maps, many partners need no new build. The six steps are on Setup process.
- 1
Install and connect
We install Comparatio EDI on your server or ours and connect it to your ERP, with the access listed on our checklist.
- 2
Map and test
We reuse or build each trading partner’s map and run real test documents with the partner until both sides sign off.
- 3
Go live
The partner switches to production once testing passes. Monitoring starts on day one, and later map changes go to the same engineers, with no project queue.
Who does what
Managed EDI: what we run, and what your team does
Map changes for existing trading partners took a median of 103 minutes in the 90 days to 28 October 2026, and support tickets got a median first response of 79 minutes (Oct 2025–Oct 2026).

| Task | Comparatio | Your team |
|---|---|---|
| Trading-partner maps | Builds every map and changes it when a partner’s requirements change | Forwards partner notices if they reach you first |
| Partner testing | Runs the test cycle with each trading partner | Checks that test documents look right in your ERP |
| Connections | Sets up and maintains AS2, SFTP, FTP, HTTPS and VAN connections and certificates | Nothing |
| Monitoring | Watches for missing orders, acknowledgments and ASNs, and opens the ticket | Makes the business call when one is needed |
| ERP connection | Sets up and maintains the connection to your ERP | Grants the access on our checklist |
| Items and partners | Maps partner item numbers, UPCs and customer part numbers | Keeps ERP item, customer and vendor records current |
| Business rules | Configures them in the integration | Decides them |
FAQ
Comparatio EDI questions, answered
What is Comparatio EDI?
Managed EDI for distributors. Comparatio EDI turns your trading partners’ documents into ERP transactions and builds the acknowledgments, ASNs and invoices that go back. Our engineers build and change the maps, test with each trading partner, maintain the connections and act on monitoring alerts.
Where does Comparatio EDI run?
Comparatio runs on your server or on one we host for you. Documents travel over the connection each trading partner uses. AI features send the document, or the question and the log lines and configuration rows needed to answer it, to Anthropic’s Claude; PDF Import does this under your own API key.
Which ERPs does Comparatio EDI work with?
Prophet 21, NetSuite, Infor CloudSuite Distribution, DMSi Agility, SAP Business One and Infor SyteLine, each through the interface that ERP is built to take data through. INxSQL and on-premises SX.e connections are available on request. Running something else? Tell us what you have.
See the ERP integrationsWhich EDI documents does Comparatio EDI support?
29 X12 transaction sets and 10 EDIFACT message types in production, plus cXML, SAP IDOC, GS1/UCC-128 labels, CSV, Excel, flat files and JSON. If a new partner sends something else, we add it as part of that partner’s setup.
See every transaction typeDo we need EDI staff to run it?
No. Our engineers build and change the maps, test with each trading partner, maintain the connections and certificates, and act on monitoring alerts. Your team keeps ERP records current and makes the business calls.
How long does it take to add a trading partner?
A new trading partner typically goes live in 4–8 weeks, including enrollment, testing and certification, paced by the trading partner. With 1,000+ pre-built maps, many partners need no new build.
See the setup processHow do you know when something goes wrong?
Monitoratio watches for what is missing, not only for what failed: acknowledgments, ASNs and orders that never reached your ERP, with checks set up per trading partner during onboarding. In the 90 days to 28 October 2026, 61% of our support tickets were opened by our own monitoring.
Can Comparatio EDI handle PDFs from partners who don’t send EDI?
Yes, with PDF Import. It reads vendor invoices, customer purchase orders, order confirmations and ship notices, checks them, and posts them to your ERP, with no per-vendor templates. In production on Prophet 21; available for CloudSuite Distribution and NetSuite. It has a 100% detection rate in production: every PDF that failed a check was held for review.
More about PDF ImportWe’re on TPCx. Can you move us before it shuts down?
Yes. TPCx reaches end of life in December 2026. 80+ trading partners are in our migration program. Our first TPCx migration finished in October: every partner is off TPCx. A typical partner moves in 4–8 weeks, paced by the trading partner.
See the TPCx migrationCan we change ERPs without starting our EDI over?
Yes. Your trading-partner connections stay with Comparatio and most maps carry over; the few that need ERP-specific data are rebuilt. Before the switch, documents from the new ERP are compared with the old ERP’s, partner by partner. Plan on a few months, with a planned cutover.
Changing ERPs? Your EDI moves with youWhat does Comparatio EDI cost?
It depends on how many trading partners and documents you run. We quote a subscription and a one-time setup after a short discussion, so you know the total before you start.
Where can we see what changed in each release?
In the Changelog, which lists every Comparatio EDI release and the mapping templates added in it.
Open the ChangelogSee Comparatio EDI with your own partners and ERP
Bring your trading-partner list and tell us which ERP you run. We’ll show you which maps already exist and how your documents would flow.