Order-to-cash
Some example steps listed- 850 Purchase Order
- 855 Purchase Order Acknowledgment
- 856 Ship Notice / Manifest (ASN) not listed on Kehe via SPS
- 810 Invoice
Channel
Plan a reliable EDI exchange for KeHE Distributors / Kehe via SPS. Explore 3 document references, map them to your business records and test the complete workflow before launch.
Implementation guide
Build a reliable EDI workflow for KeHE Distributors / Kehe via SPS. Use 3 document types to plan record mapping, prevent duplicate processing and reconcile results in your business systems.
The document list is based on the linked partner reference. Confirm the required messages, versions and directions for your account.
| Document or decision | Record and matching IDs | What to test |
|---|---|---|
| X12 855 Purchase Order AcknowledgmentListed for Kehe via SPS | purchase-order response original purchase order, response revision and order line |
|
| X12 810 InvoiceListed for Kehe via SPS | accounts-receivable or accounts-payable invoice invoice number, purchase order and invoice line |
|
| X12 850 Purchase OrderListed for Kehe via SPS | purchase order or sales order buyer purchase order, order line and trading-party identifiers |
|
Confirm the supplier or customer account, sender and receiver IDs, test environment and current guide for Kehe via SPS. Compare other KeHE Distributors channels before reusing a mapping.
Start with purchase-order response, accounts-receivable or accounts-payable invoice, purchase order or sales order. For each document, assign the source system, destination record, stable identifiers and person responsible for exceptions. Agree whether a change updates an existing record or creates a new event.
Run a successful exchange and the failure cases in the mapping table. Track delivery, document validation and processing in your business system separately. Agree on the KeHE Distributors production handoff and save the results of each approved test.
Match records between systems using original purchase order, response revision and order line. Assign an owner to missing responses, duplicates and rejected records. Test recovery before enabling automatic retries.
Document catalog
3 EDI transactions listed in this catalog.
Document flow on this channel
This channel lists 3 of the 9KeHE Distributors document types; other entries appear on KeHE Distributors channels (listed below). Example relationships are shown below; confirm the required sequence in the channel guide.
Network onboarding
The directory associates SPS Commerce with 74 partner entries across 94 channels. Confirm transport, network enrollment, commercial terms and testing with the channel owner before implementation.
X12 855 Purchase Order Acknowledgment; X12 810 Invoice; X12 850 Purchase Order. Confirm which documents, directions and versions apply to your account.
Kehe via SPS lists 3 distinct document types. Match the channel to your business unit, account and delivery arrangement; compare the other channel links before choosing a connection. Confirm access and enrollment with the channel owner.
For X12 855 Purchase Order Acknowledgment, plan around original purchase order, response revision and order line. For X12 810 Invoice, use invoice number, purchase order and invoice line. Use the partner guide to locate these values and check their allowed formats.
Track delivery, document validation and business processing separately. An AS2 message disposition notification (MDN) confirms transport receipt; an X12 997 or 999 reports technical validation. Use the agreed business response or reconciliation report to confirm that the order, shipment or invoice was processed.
Test a partially accepted order with a backordered line and retain both outcomes. Do not treat a syntax acknowledgment as acceptance of price, quantity or delivery dates. Also test missing responses and recovery after a destination failure. Assign an owner to each failure and obtain partner approval before launch.
Related references
Compare the document lists for other KeHE Distributors channels.
Showing 4 of 4 references
Browse the full directorySee how Stacksync can fit your enterprise EDI workflow. Bring one partner guide and a sample exchange to plan the system mapping, exception handling and production rollout.