In this article
EDI 943 and 944 mapping keeps warehouse transfers balanced by linking the shipment advice to the warehouse's actual receipt. The X12 943, Warehouse Stock Transfer Shipment Advice, tells a receiving warehouse what is on its way. The X12 944, Warehouse Stock Transfer Receipt Advice, tells the inventory owner what the warehouse received. Your integration should match both records to the same transfer while preserving any difference in item or quantity.
That distinction matters when goods arrive short, damaged or in a different unit of measure than the sending system expects. An accepted EDI document alone does not settle the inventory balance. BOLD VAN's approach is to map the shipment and receipt as separate business events, then make differences visible for the people who can resolve them.
What the 943 and 944 each represent
A 943 is an instruction and advance record for the destination warehouse, not proof that its staff counted the goods. The warehouse uses it to identify an expected inbound transfer. After receiving, its WMS can produce a 944 describing the recorded receipt. Your ERP can then compare the expected transfer with what arrived and apply its own inventory posting rules.
| Document | Business meaning | Useful control |
|---|---|---|
| EDI 943 | Warehouse Stock Transfer Shipment Advice: stock sent toward the warehouse | Create or identify an expected receipt without assuming physical acceptance |
| EDI 944 | Warehouse Stock Transfer Receipt Advice: stock recorded at receipt | Compare actual receipts with expected lines and route differences |
| EDI 997 | Functional acknowledgment: result of the receiver's syntax check | Investigate an accepted or rejected document separately from inventory posting |
The exact X12 version, required information and permitted exception handling depend on the trading partner. Check that partner's published EDI implementation guide before finalizing the map. A 997 can report syntax acceptance or rejection, but it does not mean a shipment or its contents passed the receiving system's business checks.
Keep actual receipts independent of expected shipments. If you build a 944 by copying quantities from the 943, a short or damaged transfer may appear balanced even though the warehouse counted something different.
How to map a transfer from shipment to receipt
We recommend defining the reconciliation rule before translating a file. Start with the business record in the sending ERP: which transfer is leaving, where it is going and which item quantities are expected? Next, identify how the destination WMS represents that expected receipt. Finally, define which recorded receiving event should produce the 944. That sequence keeps the mapping tied to operational decisions rather than similar-looking document labels.
Preserve a reliable match
Determine which transfer or shipment reference the two organizations will use to connect the 943 and 944. Include the receiving location and item identity in the matching design. If either system uses different product codes, maintain a cross-reference and decide who owns corrections when an item has no match. Check your ERP and WMS documentation for implementation-specific behavior.
Separate expected and received quantities
Define how units of measure and packaging translate between systems, then compare like with like. A warehouse may record a partial arrival before the rest is received. Your design should say whether that event remains open or is handled through another approved process. Do not silently change the original shipment quantity to make the numbers agree. Map the recorded receipt and send the difference to an identified owner.
Decide when inventory changes
Map creation and inventory posting are separate decisions. A 943 may establish an expected receipt, while a 944 can inform posting after the warehouse records what arrived. Your ERP's configuration determines whether inventory moves into an in-transit state, becomes available or remains under review. Confirm those rules against system documentation and the trading partner's published EDI implementation guide.
Where transfer balances go wrong
- Weak references: A receipt matched only by an ambiguous number may attach to the wrong transfer when references are reused.
- Item mismatches: An internal SKU and a warehouse item code may describe the same product but fail to match without a maintained cross-reference.
- Unit conversion errors: Comparing cases to individual units without an agreed conversion creates a false shortage or overage.
- Duplicate processing: A resent 944 may cause a second posting unless the receiving workflow recognizes it as the same business event.
- Unowned exceptions: A discrepancy left in an error report can persist after the warehouse has finished receiving.
These issues can affect inventory decisions, fulfillment plans and accounting review. The remedy is a matching rule, a clear posting rule and an exception owner. If the partner changes its message requirements, revisit all three rather than editing the EDI translation alone.
Best practices for testing and operations
Test the business outcome, not only whether the documents exchange successfully. A complete receipt should close the expected transfer according to your ERP policy. A short receipt should retain the discrepancy for review. An unknown item, invalid location, duplicate 944 and syntax rejection should each have a defined path. Record who resolves warehouse counts, who corrects item references and who handles transmission errors.
Keep the original 943, the 944 and the resulting ERP and WMS statuses available for comparison. If a receipt remains open, start with the common reference and item mapping, then check whether the 944 reached the ERP and whether its posting was accepted. This is more useful than treating every unmatched transfer as a transport failure.
Connecting warehouse and ERP workflows
BOLD Integration maps EDI between trading partners and your ERP, WMS or other system. BOLD VAN works with SAP, Oracle ERP, Infor CloudSuite and other ERPs as well as ShipHero and other warehouse systems. Where a platform uses an API instead of EDI, we can connect to that platform's API and map data in either direction. The specific exchange depends on that system's documentation and the partner guide.
Every document is tracked in the portal, where you can search, requeue and report, with notifications when something needs your attention. New maps are typically ready to test in about two days. When a trading partner changes its requirements, we update the map, and minor changes are typically handled at no cost.
To keep a transfer balanced, treat the 943 as the expected shipment, the 944 as the recorded receipt and the difference as a decision someone owns. If you are reviewing that handoff across an ERP and warehouse, BOLD Integration can help you map and test it.
Frequently asked questions
What is the difference between EDI 943 and EDI 944?
EDI 943 is a Warehouse Stock Transfer Shipment Advice that tells a warehouse what stock is being sent. EDI 944 is a Warehouse Stock Transfer Receipt Advice that reports what the warehouse recorded as received.
Should an EDI 943 update available inventory?
A 943 represents a shipment notice to the warehouse, not a physical count at receipt. Confirm your ERP posting rules before making stock available. The recorded receipt and any exceptions should be considered in that decision.
How do you handle a short receipt in an EDI 944?
Map the quantity actually recorded at the warehouse and retain the difference from the expected 943 quantity for review. Follow the trading partner's published EDI implementation guide and your ERP's rules for partial receipts and inventory adjustments.
Does an EDI 997 mean the warehouse accepted the transfer?
No. A 997 functional acknowledgment tells the sender whether a document passed the receiver's syntax check. It can report acceptance or rejection, but it does not confirm that shipment quantities or receipt content were accepted.
