First, the conclusion: order entry mapping is not about getting one 850 purchase order right. The 850, the 856 advance ship notice, and the 810 invoice have to grow out of a single mapping table. The 850 says what was ordered, the 856 says what shipped, the 810 says what is owed — and all three have to describe the same thing. Any one document can look perfect on its own while the chain is broken somewhere, and when the chain breaks, payment gets held. This article is about aligning that document chain: how to build it, how to check it, and what failure looks like.

I have seen this exact failure three times. The first was a home-goods client whose retailer held back a payment of more than $20,000 in their second month after go-live. (Dollar figures below are illustrative scenarios.) The 850 mapped cleanly. The problem was in the 856: the ship-to address on the advance ship notice was the client's headquarters, while the 850 carried the distribution center address. The retailer's system compared the two, flagged a mismatch, and treated the shipment as delivered to the wrong place. Nothing was wrong with either document on its own. The chain was broken. The second time, an 810 invoice showed two cartons more than the 856 — the warehouse had shipped two extra cartons, invoiced honestly, and the retailer paid against the 856, so payment for those two cartons sat for over forty days. The third time was the most unfair: a date format issue. The 850 used month-day-year, the 856 mapped it as day-month-year, and the system read it as an early shipment and applied a penalty. Three failures, three different causes, one root problem: the mapping covered the 850 and stopped there.

Why Order Entry Mapping Has to Cover All Three Documents: The 850, 856, and 810 Are One Chain

Most teams treat order entry mapping as translating the customer's 850 into an order our system can read, and call it done. Wrong. The 850 is only the start of the chain. After the retailer receives the 856, they compare it field by field against the 850 — item code, quantity, ship-to address, required delivery date — and anything that does not match goes into an exception queue. Then finance compares the 810 invoice against the 856: what shipped versus what is being charged. Any inconsistency in field definitions anywhere in the chain, and the time saved up front gets paid back double later.

Here is the counterintuitive part: the mapping table is not a technical document. It is a financial document. The technical team cares whether a field can be transmitted. Finance cares whether the money can be collected. A mapping table that only lists field-to-field correspondences, without stating what happens when a field is wrong and who owns it, is a half-finished product on day one. My practice now is to add a business consequence to every row of the mapping table — for example, "ship-to mismatch → retailer treats as mis-shipment, payment held." Once that line is there, the business side actually reviews the table.

The Step-by-Step Build: Four Steps to One Shared Mapping Table

Step one: draw the chain before writing a single field. On a whiteboard, map the full flow — 850 → picking and shipping → 856 → 810 — and mark where each document is generated, whose hands it passes through, and who performs the final check. Skip this step and every field you write afterward is disconnected.

Step two: work backward from the 810. Settle the invoice fields and definitions first — which item code set, whether quantities are in cases or eaches, whether the price includes freight — then work backward to what the 856 must carry to support that invoice, and finally to which 850 fields must pass through untouched. Working backward from the money avoids half the pitfalls of working forward from the order.

Step three: one mapping table for all three documents, not three tables. Any given field has exactly one definition across the chain: one item code, one ship-to address, one date format. Each field is defined once in the mapping table and referenced by all three documents. If anyone wants to change a field's definition in the 856, they change it in the mapping table first, and all three documents get regression-tested together.

Step four: run the go-live night checklist item by item. Take three real historical orders and run the full chain from the 850, comparing the 856 and 810 output field by field. Then deliberately create two bad orders — one with a wrong address digit, one short a carton — and confirm the system catches them. Finally, confirm the 810 billing definitions match finance's accounts-receivable definitions. Only when that whole pass is green do you go live. If it is not green, delay the launch. Do not test with real money.

One related note: the 850 on its own has plenty of traps too. The field-level approach for that single document is covered in this complete guide to EDI 850 purchase order mapping. Get the single document solid first, then come back and align the whole chain.

The Most Common Order Entry Mapping Failure Points: The Go-Live Night Checklist

First, units of measure. The 850 says 10 cases, the system holds 120 eaches, the 856 goes back to 10 cases — every conversion between cases and eaches doubles the chance of an error. My rule: the chain uses exactly one unit everywhere, conversion happens once in the mapping table, and the conversion is written in the notes.

Second, item code aliases. The code on the customer's 850 is not the code in your warehouse; a cross-reference table translates between them. One missing row in that table and the whole order stalls at the 856 step. Every time the customer adds a new item, the first job is adding its code to the cross-reference table — before accepting any orders for it.

Third, date formats and time zones. Month-day-year or day-month-year must be written into the mapping table, never left to "everybody knows." And time zones: is the required delivery date in the customer's local time or the warehouse's? One day off reads as a late delivery.

Fourth, the 856 went out but the 810 never followed. The ship notice and the invoice are owned by different people. The 856 goes out on time, the 810 is raised three days late, and since payment terms run from the invoice date, that is three days of cash collected late for nothing. My rule: the 810 must be raised within 24 hours of the 856 going out. If it cannot be written into the process, write it into a system reminder.

One last piece of advice: once the mapping table is built, do not lock it in a drawer. The day the customer changes a rule, the mapping table changes with it — and all three documents get regression-tested together. That is the part of order entry mapping nobody puts on a project plan, and it is the part that decides whether the chain holds. The chain is alive. The mapping table has to be alive too.

By Lin Xiao, WMS Implementation Consultant