TPCx reaches end of life December 2026 | Don't wait until partners go dark | Plan Your Migration →
Comparatio logo
Manufacturing · Automotive · Heavy truck

Manufacturing EDI for suppliers to vehicle and equipment makers

Truck makers, equipment builders and their Tier-1 plants send schedules, not just purchase orders. Comparatio reads 830s, 862s and EDIFACT DELFOR releases into your ERP and sends ship notices and invoices back in each OEM’s format. Our engineers build and run every map.

  • X12 and EDIFACT
  • Plant-level IDs
  • Maps run by our engineers

Your customers

  • Received: 830 · 862 · DELFOR · 850
  • Sent: 856 · DESADV · 810 · INVOIC

Your suppliers

  • Sent: 850 · 830 releases
  • Received: 855 · 856 · 810

Comparatio

Translates, checks and monitors your documents

Your ERP

  • Sales orders
  • Scheduled releases
  • Shipments
  • Invoices
Your customers here are the OEM plants you ship to.
76
Vehicle and equipment OEM maps
14
Customer maps that send EDIFACT
1,000+
Pre-built trading-partner maps
4–8 weeks
Typical partner go-live

Documents

The automotive document set, and what each one does in your ERP

OEMs plan in schedules. The 830 forecasts, the 862 or DELFOR fixes the next shipments, and the ship notice has to match what the plant expects to receive. Comparatio handles the whole set in X12 and EDIFACT.

Manufacturing EDI documents handled by Comparatio, with direction, result and status
DocumentDirectionWhat happensStatus
830 Planning scheduleFrom OEMForecast and firm quantities become scheduled releases in your ERPIn production
862 Shipping scheduleFrom OEMNear-term ship dates and quantities become scheduled releasesIn customer testing
DELFOR Delivery schedule (EDIFACT)From OEMScheduled releases, as with an 830; a CONTRL goes back where the OEM requires oneIn production
DELJIT Just-in-time call-off (EDIFACT)From OEMScheduled releases for just-in-time deliveriesIn production
850 / ORDERS Purchase orderFrom OEMSales order createdIn production
ORDRSP Order response (EDIFACT)To OEMOrder acknowledgment for partners on EDIFACTIn production
856 / DESADV Ship noticeTo OEMBuilt from your shipment, with the receiving plant’s IDsIn production
810 / INVOIC InvoiceTo OEMBuilt from your invoice; cross-border plants get local tax charges and currencyIn production
824 Application adviceFrom OEMAn invoice rejection is recorded, so your team sees what the OEM refusedIn production
997 / CONTRL AcknowledgmentBoth waysMatched to the document it answersIn production

In production: on our production lists of X12 sets and EDIFACT messages (see Transaction types). In customer testing: built, and running through a customer’s test cycle before go-live.

How it works

Built for the way OEM plants order and receive

Releases, not just orders

830s, 862s, DELFOR and DELJIT become scheduled releases in your ERP. Release notices can also go by e-mail to a contact you name for each OEM.

Plant-level identity

Each plant can have its own map or IDs, so a ship notice carries the receiving plant’s codes. PACCAR plants get their own DUNS number in the envelope.

Cross-border plants

Invoices to PACCAR’s Mexican and Canadian plants carry the tax charges as SAC segments and state the currency.

EDIFACT for European OEMs

14 customer maps send EDIFACT, for partners such as Bosch, Cummins, MAHLE, Volvo and Webasto. Files with several messages are split before processing.

Spreadsheet schedules

Partners without EDI can send release schedules in Excel. They become scheduled releases the same way an 830 does.

Rejections explained

Acknowledgments are matched to the documents you sent. When an OEM rejects an invoice with an 824, the rejection is recorded and explained in plain English.

Who we connect

OEMs and manufacturers already in our map library

Most new partners start from a map we have already built for another customer. These counts cover both directions: the manufacturers you sell to and the ones you buy from.

Manufacturing trading-partner maps in the Comparatio library, by group
Partner groupMapsExamples
Vehicle and equipment OEMs76Truck makers, ag and construction equipment builders, Tier-1 component plants: PACCAR, Daimler Truck, Volvo, General Motors, Chrysler, Tesla, John Deere, Caterpillar, Komatsu, Cummins
Manufacturers buying from distributors52MRO, components and production supplies: Parker Hannifin, Eaton, Schneider Electric, Siemens, Lincoln Electric, Kohler
Manufacturers you buy from355Supplier maps for fluid power, plumbing and HVAC, electrical, safety, cutting tools and more: Parker Hannifin, Bosch Rexroth, Festo, Siemens, Eaton

Map counts from the Comparatio map library, 16 October 2026. A map means the partner’s format is built; it does not by itself mean the partner is live at every customer.

Your suppliers

The same schedules, sent to the manufacturers you buy from

Distributors and component makers that ship to OEMs also buy from manufacturers. The supplier side runs on the same platform.

Releases and changes out

830 release schedules, 860 PO changes and 820 payment advices go to suppliers, each switched on per supplier.

Acknowledgments checked

Each supplier 855 is compared line by line with your PO. Price, quantity or unit differences beyond the supplier’s tolerance are e-mailed to the buyer.

Ship notices and invoices posted

In Prophet 21, supplier 856s can become receipts and 810 invoices become AP vouchers, matched to the purchase order.

FAQ

Manufacturing EDI questions, answered

What is an EDI 830 planning schedule?

An 830 is a customer’s forecast of what it will need from you, period by period, usually with the nearest periods marked firm. OEMs send it so suppliers can plan production and stock. Comparatio turns each 830 into scheduled releases in your ERP, so your team works from the OEM’s latest numbers instead of re-keying them.

The 830, explained

What is the difference between an 830 and an 862?

The 830 is the longer-range plan. The 862 is the short-term shipping schedule: exact quantities and ship dates for the next days or weeks, which take precedence over the 830 for that period. Many OEMs send both. Comparatio reads both into scheduled releases; our 862 handling is in customer testing today.

The 862, explained

Do you support EDIFACT DELFOR and DESADV?

Yes. DELFOR and DELJIT delivery schedules come in as scheduled releases, and a CONTRL goes back where the OEM requires one. DESADV ship notices, INVOIC invoices and ORDRSP order responses go out. 14 of our customer maps send EDIFACT, for partners such as Bosch, Cummins, MAHLE, Volvo and Webasto.

Our OEM has plants in Mexico and Canada. Can our invoices carry local tax and currency?

Yes. For PACCAR’s Mexican and Canadian plants, tax charges travel as SAC segments and the currency is stated on the invoice. Each plant can also have its own map or IDs, including a per-plant DUNS number in the envelope.

What if a customer sends release schedules in a spreadsheet?

We accept spreadsheet release schedules from partners without EDI. They become scheduled releases the same way an 830 does, and release notices can go by e-mail to a contact you name for each partner.

How long does it take to connect a new OEM?

A new trading partner typically goes live in 4–8 weeks, paced mostly by how quickly the OEM tests. If the OEM is one of our 76 vehicle and equipment maps, setup starts from that map instead of a blank page.

We trade with our OEM customers through Epicor TPCx. What happens when it shuts down?

TPCx reaches end of life in December 2026. We move your OEM connections to Comparatio: schedules, ship notices and invoices included, with each partner tested before it switches.

TPCx migration

Talk through your OEM schedules before you commit

Bring an 830 or DELFOR from one of your OEM customers, and we’ll talk through where each release lands in your ERP.