The Core Four documents (850, 855, 856, 810) cover the vast majority of B2B commerce. Automotive is an exception.
If you’re running Acumatica in an automotive supply chain, the 830, 862, and 824 transactions covered here aren’t a side note. These are the documents your OEM relationship runs on, and having them work inside the Acumatica screens your team already lives in every day is what lets automotive suppliers get the full value out of running Acumatica in the first place.
Tier-1 suppliers build finished parts, tier-2 suppliers make the components that go into those parts, and tier-3 suppliers provide the raw materials underneath it all. A single OEM order can trigger a chain of EDI transactions running several layers deep, each one on its own clock. Add just-in-time manufacturing, where a missed shipment window can stop a production line, and the room for error drops close to zero.
That’s why automotive EDI relies on documents outside of the core 4.
830: The Planning Schedule with Release
Where most industries run on a purchase order, automotive runs on a rolling forecast. The 830 gives suppliers a look ahead at OEM demand, then layers firm, near-term releases on top of that forecast so production can be scheduled with confidence. A supplier reading the 830 correctly knows not just what’s coming, but how firm that number actually is.
Get the forecast-versus-firm distinction wrong in your mapping, and a supplier either overbuilds against a number that was never guaranteed or underbuilds against a release that was.
862: The Shipping Schedule
The 862 is the automotive industry’s answer to just-in-time delivery. Instead of a single ship date, it can specify exact delivery windows tied to the OEM’s production sequence, sometimes down to the hour. A shipment that’s early can be as much of a problem as one that’s late if the receiving dock has no room for it yet.
824: The Application Advice
Automotive OEMs process documents automatically and at volume, which means rejections happen automatically too. The 824 is how a trading partner tells you, via EDI, that something didn’t pass their validation, whether that’s a pricing mismatch, an invalid part number, or a quantity discrepancy. Teams that treat the 824 as a crucial document instead of an afterthought catch problems before they become a chargeback.
Two Standards, One Supply Chain
Domestic OEMs typically transact in X12. Global OEMs, and many tier-1 and tier-2 suppliers with international operations, often require EDIFACT for at least part of their document flow. A mapping team that’s only ever built X12 connections will hit a wall the first time a global automotive account asks for EDIFACT support.
Where UniLink Fits In
UniLink has supported the automotive supply chain for over 20 years, with production connections today to Ford, GM, Chrysler, Toyota, and many others.
As Jess Fournier, our Director of Engineering, puts it, our automotive clients have mission-critical relationships with the businesses that make the OEM relationship possible in the first place, from Kennametal and 3M to Michelin, Honda, and John Deere.
Our Smart Map technology is built specifically to handle that complexity: tier-1 finished parts, tier-2 intermediary components, and tier-3 raw materials, each with its own rules of engagement, without requiring the customer to rework their ERP systems to accommodate it.
For Acumatica users in the automotive space, that means the 830s, 862s, and 824s running natively inside the ERP screens your team already works in, with a dedicated Acumatica team handling the mapping and a developer who stays on as your long-term support contact once you’re live.
How is your team currently handling planning schedule changes from your OEM without adding headcount?
Learn more about UniLink’s EDI integration for Acumatica.
