Common EDI Documents in Pharma: Purchase Orders, Invoices, ASNs, and More

Estimated read time: 9 minutes

---

Introduction

If you've spent any time researching pharma supply chain connectivity, you've probably seen the same three transaction numbers mentioned together: 850, 810, and 856. Those three cover a lot of ground — but they aren't the whole picture.

Pharma trading partners often exchange a handful of additional EDI documents as part of their everyday workflows: order acknowledgments, functional acknowledgments, payment remittances, and others that appear depending on the partner type and workflow in question.

This article is a practical tour of the pharma EDI documents you're most likely to encounter — what each one does, where it fits in the order-to-cash cycle, and why knowing the full list matters before you scope a new trading-partner connection.

If you're just getting started with the topic, What is pharma EDI? is a good place to build foundational context before reading this.

---

What We Mean by "EDI Documents"

EDI documents are formally called transaction sets in the X12 standard — the format used across most pharma supply chain relationships in North America. Each transaction set has a three-digit number that maps to a specific business event: a purchase order, an invoice, a shipment notice, and so on.

Trading partners don't exchange every transaction set in the X12 catalog. In practice, each trading relationship uses a defined subset: documents that are required, sometimes a few that are optional, and usually one or two that handle acknowledgment and error reporting.

Understanding which transaction sets a given partner requires — and which are optional — is one of the first things to confirm when planning a new connection.

---

Why It Matters in Pharma Supply Chains

Pharma supply chains involve a wide range of trading partner types: wholesalers, distributors, specialty pharmacies, 503B compounders, health systems, GPOs, and buying groups. Each of these relationships can have a different document set.

A specialty pharmacy connecting to a large wholesaler may only need three or four transaction types. A 503B compounder selling to health systems may encounter additional documents — like order acknowledgments or application advice — that aren't common in every wholesale relationship.

Knowing which pharma EDI documents you actually need helps you scope a project accurately, avoid surprise onboarding delays, and set realistic go-live expectations with your trading partners.

---

The Core Pharma EDI Documents

EDI 850 — Purchase Order

The 850 is typically the starting point of any order-to-cash workflow. A buyer — a pharmacy, health system, or distributor — sends an 850 to a supplier to initiate a purchase. It carries all the essential order data: item numbers, quantities, pricing, ship-to address, and delivery expectations.

For most pharma operators, the 850 is the highest-volume document they send or receive on a regular basis.

EDI 810 — Invoice

The 810 is the electronic invoice. After an order ships, the supplier sends an 810 to the buyer requesting payment. It references the original purchase order and itemizes what was shipped, at what price.

Discrepancies between an 850 and an 810 — mismatched item numbers, pricing differences, or quantity variances — are a common source of workflow friction and often require manual reconciliation if they aren't caught during processing.

EDI 856 — Advance Ship Notice (ASN)

The 856 is sent by the supplier when an order ships, before the goods arrive. It tells the buyer what's coming, how it's packaged, and when to expect it. In pharma, the 856 often carries lot numbers and expiration dates, which are important for inventory management and regulatory traceability.

For a deeper look at how these three work together, see EDI 850, 810, and 856 explained.

EDI 855 — Purchase Order Acknowledgment

The 855 is the supplier's response to an 850. It confirms whether the order was accepted, modified, or rejected — and if modified, what changed. Not every trading partner requires an 855, but health systems and some specialty distributors often do.

If your partner expects an 855 and you don't send one, they may assume the order wasn't received, which can lead to duplicate orders or fulfillment delays.

EDI 997 / 999 — Functional Acknowledgment

The 997 — and its newer counterpart, the 999 — is the handshake of EDI. It confirms that a transaction set was received and that it was syntactically valid, meaning the file was parseable, not that the business logic was correct.

Every serious EDI relationship generates functional acknowledgments in both directions. If you send an 850 and don't receive a 997 back within a reasonable window, that's typically an early signal of a transmission or mapping problem.

It's worth noting: a 997 confirms the document arrived intact, not that the order will be fulfilled.

EDI 820 — Payment Order / Remittance Advice

The 820 is used for electronic payment instructions and remittance information. In pharma, it's common in relationships where a buyer or payer wants to communicate payment details back to a supplier — for example, indicating which invoices a payment covers and any adjustments applied.

Not all pharma trading relationships use an 820. It appears more often in larger health system or GPO relationships where remittance data needs to reconcile against multiple open invoices.

EDI 824 — Application Advice

The 824 is less commonly discussed but worth knowing. It's used to report errors or acceptance at the application level — going beyond the syntax check of a 997 to indicate whether the business data in a transaction was actually processable by the receiving system.

503B compounders and specialty distributors working with health systems may encounter 824s when a health system's internal system rejects an order or invoice for business-rule reasons, even after a 997 confirmed clean receipt.

---

Common Challenges

Even with a clear list of required documents, trading-partner connections in pharma can run into friction:

• Partner variability. Two wholesalers may both require an 850, but their specific field requirements, code sets, and acknowledgment expectations can differ significantly.
• Optional documents becoming operationally required. A partner may list a document as optional during setup but consistently expect it to be sent in practice.
• Acknowledgment gaps. Missing or delayed 997s that go unmonitored can let transmission failures go undetected until an order doesn't arrive.
• Scope creep during onboarding. Starting with three document types and adding a fourth mid-onboarding typically requires another round of testing, which extends timelines.
• Manual reconciliation. When document data doesn't match across the 850, 856, and 810, someone usually has to resolve discrepancies by hand.

---

What to Confirm Before Starting a New Partner Connection

Before kicking off any new trading-partner onboarding, it's worth getting clear answers to a few practical questions:

• Which documents does this partner require? Get the full list in writing, including whether items like the 855 or 820 are required or optional.
• What acknowledgment behavior do they expect? Some partners expect 997s within minutes; others are less strict.
• What is their testing protocol? Most partners require a formal test cycle before going live in production. Understanding who coordinates testing helps set realistic timelines.
• Are there partner-specific field requirements? Many pharma partners have implementation guides that layer requirements on top of the X12 standard. These need to be reviewed before mapping begins.
• What happens when something fails? Knowing the partner's error-handling and re-transmission expectations ahead of time avoids surprises.

You can use the onboarding checklist as a starting framework for what to gather before a new connection begins.

---

How Managed EDI Can Help

Mapping and testing every document type for every trading partner is time-consuming work, especially when partner implementation guides vary. Managed EDI services maintain reusable templates across common pharma document types and handle the partner-specific customization, test cycles, and acknowledgment monitoring that each connection requires.

When a new partner's document requirements are similar to one already mapped, that reuse can meaningfully compress onboarding timelines. When a partner's requirements are unusual — such as a non-standard 824 implementation — having experienced support helps avoid delays that would otherwise fall on internal teams.

Proactive monitoring matters too. Tracking acknowledgments in both directions means transmission problems get caught quickly rather than surfacing days later when a shipment doesn't arrive.

If you're weighing whether a managed EDI approach or a direct API integration makes more sense for a particular workflow, EDI vs. API in pharma walks through the practical differences.

---

Where APXConnect Fits

APXConnect is a managed EDI and API service designed for pharma operators who want trading-partner connectivity without taking on every map, test cycle, and support issue in-house.

Customers send APXConnect their trading partner list; APXConnect helps manage mapping, testing, monitoring, and ongoing support. The common pharma workflows — 850 purchase orders, 810 invoices, 856 ASNs, and related acknowledgment documents — are central to what the service is built around.

Pricing is flat monthly with no per-transaction fees. For partners APXConnect has already mapped, go-live can often happen in days. New partner maps typically take one to three weeks, depending on partner responsiveness and workflow complexity.

Tiers start at $749/month for up to five trading partners, with options scaling to larger partner sets for teams managing broader networks.

---

Frequently Asked Questions

Do all pharma trading partners use the same EDI documents?

No. Each trading partner defines which documents are required in their relationship. Most pharma connections include some version of the 850, 810, and 856, but requirements for documents like the 855, 820, or 824 vary by partner type and workflow. Confirming the full document set before onboarding begins is one of the most useful steps you can take.

Is the 997 the same as the 999?

They serve the same purpose — confirming receipt and syntactic validity of a transaction set — but the 999 is the newer version introduced in later X12 releases. Some partners still use 997; others have moved to 999. It's worth confirming which version your partner expects before testing begins.

What's the difference between a 997 and an 855?

A 997 is a technical acknowledgment: it confirms a document was received and was syntactically valid. An 855 is a business-level response: the supplier explicitly accepts, modifies, or rejects the purchase order. They serve different purposes and can both be present in the same workflow.

If a partner lists a document as optional, should I still send it?

It depends on the partner's operational behavior. Some optional documents — like the 856 ASN — may be listed as optional in a partner's technical specification but are expected in practice for inventory planning. It's worth asking your trading partner contact how they use optional documents before deciding to omit them.

How do I find out which documents a new partner requires?

Most established trading partners have an implementation guide or EDI specifications document that lists required and optional transaction sets, field requirements, and testing protocols. Requesting this document early in the onboarding conversation — before any mapping work begins — typically saves significant time downstream.

---

Next Steps

Understanding which pharma EDI documents your trading partners require is the right starting point — but the practical work is in the mapping, testing, and ongoing monitoring for each connection.

If you're ready to get a clearer picture of what your specific partner list requires, send us your trading partner list and we'll help map the fastest path to go-live.