TPCx reaches end of life December 2026 | Don't wait until partners go dark | Plan Your Migration →
Comparatio logo
Epicor Prophet 21 · Native EDI

Epicor Prophet 21® EDI that reads P21 directly

Comparatio was built around P21 first. It reads P21 directly, imports through P21’s own import files or the P21 Transaction API, and brings 70+ combined years of Prophet 21 experience — not a generic connector with a P21 adapter bolted on.

  • Reads P21 directly
  • UD-field support
  • Multi-company P21
70+
combined years of Prophet 21 experience
4–8 wks
typical new trading-partner go-live
Same day
map updates for existing partners (median 103 minutes, 90 days to 28 Oct 2026)
100M+
EDI transactions processed to date

Why depth matters

Prophet 21 EDI integration is only as good as its P21 knowledge

Most EDI providers treat P21 as one ERP among fifty. The difference shows up in the details your team lives with every day.

Warehouse aisle lined with yellow parts bins

With a generic EDI connector

  • User-defined fields, custom workflows, and multi-company setups need workarounds you build yourself.
  • Map changes for existing partners wait in a project or work-order queue.
  • Failed transactions get re-sent as-is: same broken file, same failure.
  • Your 3PLs, marketplaces, and vending systems each need another middleware hop.

With Comparatio's native P21 integration

  • Reads P21 directly; imports through P21’s own import files or the P21 Transaction API — including UD fields and multi-company support.
  • Same-day map updates for existing partners: map changes took a median of 103 minutes in the 90 days to 28 October 2026.
  • Smart resend rebuilds failed transactions from current ERP data instead of re-sending the broken file.
  • One platform carries EDI, ecommerce, 3PL, and procurement-network traffic into P21.

P21 ERP integration solutions

What ships in the box

Everything below is standard in Comparatio's Epicor P21 integration solutions — not an add-on tier.

Reads P21 directly; imports through P21’s own import files or the P21 Transaction API

Reads your P21 database directly and hands documents to P21 through its own import files, with EDI fields kept in P21 user-defined (UD) tables. The P21 Transaction API is an optional import path, switched on one document type at a time after a shadow run.

Native UD-field handling

Trading-partner data imports into P21 user-defined fields natively — no side tables, no manual re-keying.

Multi-company & intercompany EDI

Run multiple P21 companies on one deployment — including EDI between two of your own P21 instances.

Tested in P21 Play first

Mapping changes and new partners are proven in your P21 Play environment before production; on Epicor-hosted P21, ask Epicor for the Play login.

EDI Candidate Analysis

Finds the customers and vendors with 40+ orders a month and 1,000+ in total who aren’t on EDI yet.

P21-aware reporting

PO lifecycle, order status (including orders received via EDI but missing from P21), invoice tracking, and discrepancy reports — delivered as scheduled Excel.

Proactive monitoring built in

Missing 997s, unconfirmed orders and absent ASNs open tickets automatically. In the 90 days to 28 October 2026, 61% of our support tickets were opened by our own monitoring, not by a customer.

Every connection type

AS2, SFTP, VANs, Ariba, Coupa, cXML with Oracle Business Network, EDIFACT, and REST — modern and classic protocols on one platform.

Named engineers on every ticket

Your team works with the same engineers on every request, with a median first response of 79 minutes (Oct 2025–Oct 2026) — the support model that keeps distributors on Comparatio for a decade.

Supplier side: Procure-to-pay EDI for distributors: purchase orders out, and supplier acknowledgments, ship notices and invoices into P21.

How it works

From kickoff to trading in weeks, not quarters

  1. 1

    Install

    A Windows service or program on your server or one we host for you: about 100MB, with a route to P21 wherever it runs. No middleware layer.

  2. 2

    Configure & test

    We map your trading partners and prove each flow in your P21 Play environment before production — with your data, not samples.

  3. 3

    Go live

    Typical new trading-partner go-live in 4–8 weeks including enrollment, testing, and certification, paced by the trading partner. Existing-partner map changes ship same day.

Deployment

Runs wherever your P21 runs

On your own servers, Comparatio reads the Prophet 21 database directly and hands documents to P21 through its import folder. P21 in Epicor’s cloud connects differently, so it has its own section below.

On-premises P21

The most common deployment: the EDI server runs in your own network, close to an on-premises P21 database.

Co-located P21

P21 on servers you manage, in a data center or your own cloud account, connects like on-premises P21: the EDI server needs network access to the database and the import folder.

P21 in Epicor’s cloud

We read Epicor-hosted P21 through read-only database logins over the encrypted connection Epicor requires; in the moves we have handled, Epicor provided them on request. Imports go through an SFTP import folder or the P21 Transaction API, after a one-time reconfiguration.

EDI server hosted by us

Don’t want to run another server? Comparatio can host your EDI server on AWS, with server and uptime monitoring.

Prophet 21 in Epicor’s cloud

Moving P21 to Epicor’s cloud: what changes for your EDI

Epicor has announced that Prophet 21 2028.1, tentatively scheduled for May 2028, is the last on-premises feature release; later versions run in Epicor’s cloud, and Active Support for 2028.1 runs to June 30, 2029. 27 of our Prophet 21 installations run against Epicor-hosted P21 (November 2026). Your maps and trading-partner setups stay; how EDI reaches P21 changes.

Read-only logins to Live and Play

We read Epicor-hosted P21 through read-only database logins over the encrypted connection Epicor requires; in the moves we have handled, Epicor provided them on request. Ask Epicor for the Play login too: it isn’t always included, and without it your first real EDI test happens in Live. Epicor may charge extra for read-only access to the Play database.

Imports over SFTP or the P21 Transaction API

Import files go to the SFTP import folder Epicor provides for hosted P21. Or the P21 Transaction API takes over, one document type at a time, after a shadow run in which both paths are compared.

A one-time reconfiguration

We change how EDI reaches P21 — logins, connection, import path and schedules — test it in your hosted Play environment, and quote the work before the move. Updates EDI made directly in P21 on-premises, such as UD status fields, are handled another way.

A home for the EDI server

Moving P21 doesn’t move the EDI server. Run it on a virtual machine you control, or let Comparatio host it on AWS with monitoring.

Read the P21 Cloud EDI Guide

Looking at other ERPs while you plan? Comparatio also connects NetSuite and Infor CloudSuite Distribution. Changing ERPs? Your EDI moves with you.

FAQ

Prophet 21 EDI, asked and answered

Can Comparatio run intercompany EDI between two Prophet 21 instances?

Yes. Two P21 companies can trade with each other over standard EDI documents — orders, confirmations, ASNs, invoices — with each side seeing a normal trading-partner relationship. We run this in production today.

Can EDI data reach P21 user-defined (UD) fields?

Yes. Comparatio has a native workaround for importing into UD fields, so trading-partner data lands where your team actually uses it — not in a side table.

Does Comparatio support multi-company P21?

Yes. Multiple P21 companies can share one Comparatio deployment, with per-company routing, monitoring, and reporting.

How safe is testing against our P21 system?

Mapping changes and new trading partners are proven in your P21 Play environment before production; on Epicor-hosted P21, ask Epicor for the Play login.

What if we are on an older X12 version?

Version flexibility is built in — 3010, 3020, 4010, and 4030 documents are all in production across our trading-partner network. Your partners choose their version; we handle the differences.

We’re moving P21 to Epicor’s cloud. What do you need, and does it cost anything?

We read Epicor-hosted P21 through read-only database logins over the encrypted connection Epicor requires; in the moves we have handled, Epicor provided them on request. We need those logins for Live and Play (ask Epicor for the Play login; it isn’t always included), and the SFTP import folder Epicor provides. Your maps and trading-partner setups stay. We reconfigure how EDI reaches P21 once, test it in your hosted Play environment, and quote that work before the move. The EDI server still needs a home: a virtual machine you control, or a server we host for you.

Read the P21 cloud guide

What do you need from us before a P21 cloud switch?

Three things, before switch day: the server names for Live and Play, the read-only logins for both, and the SFTP folders Epicor provides. Ask Epicor about the Play login early: Epicor may charge extra for read-only access to the Play database.

Do we need the P21 API in Epicor’s cloud?

No. Imports go through the SFTP import folder Epicor provides. The P21 Transaction API is an option for very busy systems, switched on one document type at a time after a shadow run.

What changes day to day in Epicor’s cloud?

Three things. The 855-resend checkbox stops working, because it needs a database write the read-only login refuses, so 855 resends move to the EDI Portal. P21’s Scheduled Import Manager runs as a scheduled task you set up. And test imports run in your hosted Play environment.

Does Comparatio use the P21 Transaction API?

It can. Since release 14.18, every P21 import can go through the P21 Transaction API instead of an import file. Each document type moves on its own: it first runs in shadow mode, with the import file doing the real work and the API result compared against it, and switches only after those comparisons are reviewed. Import files remain the standard path.

What happens to EDI when we refresh Play, upgrade P21, or move the SQL server?

Tell us the date before you do it. For a Play refresh, we set the test setups’ cut-off to that day, so nothing older goes out. Test documents are marked as tests and go to the partner’s test system where it has one; where it doesn’t, we agree the test plan with the partner first. For a P21 upgrade or a server or cloud move, we reconfigure, test, and cut over EDI with you, and we quote larger moves up front.

What happens if the P21 Import Manager stops?

Our monitoring notices. When EDI import files stop being picked up, it raises an alert that lists the waiting files by document type and trading partner, so orders and invoices don’t sit unnoticed outside P21.

What are Suspended Records? Do we key the order again?

No. When P21’s own import refuses a document, P21 keeps it as a suspended record. Fix the field in P21’s Edit Import Suspended Records and reimport it from there. Keying the order again makes a duplicate.

Why didn’t a purchase order go out by EDI?

Check the EDI box on the purchase order. It must be set before the PO is approved; setting it afterwards does nothing. Set it when you enter the PO.

Put 70+ years of P21 expertise behind your EDI

See how Comparatio runs Prophet 21 EDI against your own trading partners.