EDI 850, 810, and 856 Explained for Pharma Trading Partners

Estimated read time: 7 minutes

---

Introduction

If you've recently started evaluating EDI options — or you're inheriting a trading-partner setup you didn't build — the document numbers can feel like alphabet soup. 850. 810. 856. Everyone mentions them, but the explanations often assume you already know what they mean.

This article is a practical orientation for operations and IT teams who work in pharma but aren't EDI specialists. The 850, 810, and 856 are the three transaction types most teams encounter first. Together they cover the core of a typical pharma supply-chain exchange: a purchase order goes out, a shipping notice comes back, and an invoice follows. Understanding what each one does — and where things tend to break down — is a useful foundation before you start connecting to trading partners.

If you're looking for broader context first, What is pharma EDI? covers the fundamentals of how EDI works in this industry.

---

What These Document Numbers Actually Mean

The numbers 850, 810, and 856 come from the ANSI X12 standard — a set of formats that define how electronic business documents are structured across most US industries, pharma included. Each number identifies a specific document type.

• 850 = Purchase Order
• 810 = Invoice
• 856 = Advance Ship Notice (ASN)

The X12 standard defines the underlying structure: segments, data elements, and required fields. But every trading partner relationship also involves a partner-specific implementation guide — a document that spells out exactly which segments are required, what code lists are accepted, and how acknowledgments should flow. The standard sets the grammar; trading partners negotiate the vocabulary.

This distinction matters in practice. Two wholesalers both using the 850 standard may have very different specifications. What's required for one might be optional or absent for another.

---

Why These Three Transactions Matter in Pharma

Pharma supply chains are built around ordering, billing, and shipping — and those three steps map directly to the 850, 810, and 856. A simplified version of the common flow looks like this:

1. A pharmacy or health system places an order → sends an EDI 850 to the wholesaler or manufacturer
2. The supplier ships the goods and sends an EDI 856 so the receiver can prepare for the delivery
3. The supplier sends the bill as an EDI 810 invoice, typically referencing the original purchase order

This pattern appears across nearly every pharma trading-partner relationship: pharmacy-to-wholesaler, health system-to-distributor, 503B compounder-to-hospital, manufacturer-to-GPO. The specifics vary, but the underlying document flow is recognizable.

For a broader view of which EDI documents appear in pharma workflows beyond these three, see Common EDI documents in pharma.

---

A Closer Look at Each Transaction

EDI 850 — Purchase Order

The 850 is how a buyer tells a supplier what they want. A pharma 850 typically includes:

• Item identifiers (NDC, GTIN, or partner-specific product codes)
• Ordered quantities and units of measure
• Requested ship date or delivery window
• Ship-to location and contact details
• Agreed pricing, where applicable

One common friction point: product identification. Wholesalers and manufacturers often use different item identifiers, and an 850 that references the wrong code may reject at the partner's system before anyone processes it.

EDI 810 — Invoice

The 810 is the electronic invoice — the supplier's bill to the buyer. In a well-functioning workflow, the 810 references the original 850 purchase order number, making it easier to match and reconcile.

Key fields in a pharma 810 typically include:

• Invoice number and date
• PO reference from the original 850
• Line-item detail with quantities shipped and prices charged
• Payment terms
• Any applicable chargebacks, allowances, or contract pricing adjustments

Invoice discrepancies — mismatched quantities, pricing differences, missing PO references — are a common source of manual work when EDI isn't configured carefully.

EDI 856 — Advance Ship Notice (ASN)

The 856 is sent by the supplier when goods leave the facility, before the shipment arrives. A well-structured 856 gives the receiving side time to prepare: dock scheduling, receiving staff allocation, inventory system updates.

A pharma 856 often includes:

• Shipment and carrier details
• Expected delivery date and time window
• Package and pallet hierarchy (how items are packed)
• Item-level detail including lot numbers and expiration dates (requirements vary by partner and product type)
• Reference to the original 850

The 856 tends to be the most complex of the three transactions structurally, partly because it describes a physical shipment hierarchy that can vary significantly by product and packaging configuration.

---

Common Challenges in Practice

Even though 850, 810, and 856 are standardized formats, connecting to a new trading partner is rarely plug-and-play.

Each partner has its own specification. A pharmacy connecting to five wholesalers may need to manage five different versions of the same 850 — each with slightly different required fields, code lists, and acknowledgment rules.

Acknowledgments add another layer. Most EDI workflows use a 997 or 999 functional acknowledgment to confirm that a document was received and structurally valid. If an acknowledgment doesn't come back — or comes back with errors — the sending side needs to know why and what to do next.

Testing takes longer than expected. Partners typically require a test cycle before going live. The timeline depends on how responsive the partner's EDI team is, how complex the document requirements are, and whether any mapping revisions are needed after the first test round.

Errors in production aren't always visible. Without active monitoring, a failed transaction can sit unnoticed until someone notices a missing shipment or a disputed invoice.

---

What to Look for When Evaluating EDI Options

Whether you're building out your first EDI connections or migrating from an existing provider, the following areas typically determine how smoothly onboarding goes:

• Partner spec review process — Who reads the implementation guide and translates it into your map configuration?
• Testing support — Does your EDI provider coordinate test transactions with the trading partner, or does that fall on your team?
• Acknowledgment handling — How are 997/999 acknowledgments tracked and surfaced when something fails?
• Error visibility — Can you see transaction failures quickly, or do you find out downstream?
• Pricing model — Per-transaction fees can make costs unpredictable as volume grows; flat monthly pricing is easier to plan around.

For teams weighing whether EDI or API connections make more sense for a given partner, EDI vs. API in pharma walks through the practical tradeoffs.

---

How Managed EDI Can Help

Managing 850, 810, and 856 transactions across multiple trading partners is less about understanding the standard and more about operational execution: reading partner specs correctly, configuring maps accurately, running test cycles, catching errors before they affect orders or invoices.

A managed EDI service takes on that execution work. Rather than your IT team building and maintaining maps for each partner, a managed provider maintains templates for common 850/810/856 patterns, coordinates testing with trading partners on your behalf, and monitors production transactions for failures.

For already-mapped trading partners, this can mean going live in days rather than weeks. For new partner maps, timelines typically depend on partner responsiveness and the complexity of the document requirements — but the operational burden stays with the provider rather than your internal team.

---

Where APXConnect Fits

APXConnect is a managed EDI and API service designed for pharma trading-partner workflows. Teams send APXConnect their trading partner list and document requirements; APXConnect helps manage mapping, testing, monitoring, and ongoing support across the 850, 810, 856, and related transactions.

Pricing is flat monthly — no per-transaction fees — with tiers based on the number of active trading partners. If you're working through initial EDI setup or looking to reduce the overhead of managing multiple partner connections, the onboarding checklist is a practical starting point for understanding what's involved.

---

Frequently Asked Questions

What is an EDI 850?

EDI 850 is the electronic purchase order. It communicates what a buyer wants to order from a supplier — including item identifiers, quantities, ship-to details, and pricing. In pharma, it's typically sent from a pharmacy, health system, or distributor to a wholesaler or manufacturer.

What is an EDI 810?

EDI 810 is the electronic invoice. The supplier sends it to the buyer after shipping, usually referencing the original 850 purchase order. A well-matched 810 and 850 make invoice reconciliation significantly faster than manual processes.

What is an EDI 856?

EDI 856 is the advance ship notice (ASN). The supplier sends it when goods leave the facility — before the shipment arrives — so the receiver can plan for the delivery. In pharma, the 856 often includes lot number and expiration date detail, depending on trading partner requirements.

Do you need all three?

Most pharma trading-partner relationships require the 850 and 810 at minimum. The 856 ASN is common with wholesalers and distributors but may not be required for every partner or workflow. Functional acknowledgments (997/999) are typically expected alongside all three to confirm document receipt and validity.

How long does it take to go live with a new trading partner?

It varies. For trading partners with existing maps, go-live can sometimes happen within days. New partner maps typically take one to three weeks, depending on how quickly the partner's EDI team responds during testing and how complex the document specifications are. Partner responsiveness is often the biggest variable.

---

Next Steps

If you're mapping out your trading-partner connections — or trying to get a clearer picture of what your EDI setup actually needs — a short conversation is often the fastest way to sort out the specifics.

Talk through my EDI setup — share your trading partner list and we'll help map the fastest path to go-live.