Prophet 21 EDI: Integration and Exceptions

What P21's EDI module covers

The core documents are the 850 inbound purchase order, the 855 purchase order acknowledgement, the 856 advance ship notice, and the 810 invoice. Integrations in the field also handle the 860 PO change, 820 payment remittance, and 846 inventory inquiry, and Infocon lists the outbound 940 and 945 warehouse documents for shops that ship through a 3PL. Most distributors start with orders and invoices and add ship notices as volume grows.

Configuration is per trading partner: you create a partner record, then attach rules to it that control how documents are read and written. One documented example reads a two-digit code from the N302 element in the ship-to loop of an inbound 850 and uses it to pick the warehouse the sales order is created against. The rules engine is flexible. It is also old enough that much of the reference material dates to the Activant era, so expect setup to lean on your EDI provider or a consultant rather than current vendor documentation.

How EDI orders actually land in P21

EDI-created orders flow through the same import review as P21's other file-based order intake, the Scheduled Import Service Manager. Orders that fail validation land in an Import Suspended state, and someone corrects them there before they commit. That review queue is where the staffing actually goes, because the clean orders take care of themselves. Public documentation on P21 EDI exception handling is thin, and epiusers.help, the main P21 user forum, has essentially no threads on 850 failures. Our read is that shops either lean entirely on their provider or work the queue quietly by hand.

Consultants in the P21 world sell tooling for exactly this gap, and their pitch lists are a fair summary of what shops complain about: poor visibility into what's happening, constant errors and rework, and heavy reliance on technical support.

Who P21 shops run EDI through

Four providers show up attached to P21 by name: Comparatio, which sells a P21-specific EDI product with mapping services; Infocon Systems; TrueCommerce, typically integrated to P21 through BPA Platform; and Atlas Precision's own EDI tool. If a provider you're evaluating only advertises Epicor Kinetic support, ask them to show you a live P21 integration before you sign. Kinetic and P21 are separate products with separate integration surfaces, and even people who know Epicor well mix up what applies to which.

The orders EDI will never cover

EDI covers the accounts big enough to set it up. The long tail of your customers sends purchase orders as PDF attachments and emails, and at most distributors we talk to, that is the majority of order count. Pushing those customers onto EDI mostly does not work; they keep emailing.

This is where AI order entry fits alongside EDI rather than replacing it. The same system that reads an emailed PDF PO can also work your EDI exception queue, because a kicked-out 850 is just another document whose lines need matching and correcting before a person approves the order. In both cases it resolves lines against your item master and customer part number cross references, applies the account's contract pricing, and flags anything it is not confident about for the rep who reviews the draft.

On the vendor side, Epicor announced an EDI status agent in its 2026 AI lineup, but for Kinetic only. Its P21 answer for unstructured orders is a partnership with Conexiom, announced in July 2026, rather than anything native.

This is the system we build for Prophet 21 shops. Talk to us

Frequently asked questions