# Business Central EDI Integration: 850 to Orders

> How Business Central EDI integration works. Map inbound 850 to sales orders, generate 856 and 810 from posted documents, and connect any order format.

<QuickAnswer>
Dynamics 365 Business Central has no native EDI engine. EDI is added through AppSource ISV apps, AL extensions, or middleware that calls the Business Central REST and OData APIs. An inbound EDI 850 becomes a sales order, and the 856 ship notice and 810 invoice generate from the posted shipment and posted sales invoice.
</QuickAnswer>

Business Central is Microsoft's ERP for small and mid-size companies, the successor to Dynamics NAV. It handles sales quotes, sales orders, blanket orders, and the posted shipment and invoice documents that follow. What it does not do is read a raw EDI file. When a retailer sends you a vendor compliance guide asking for 850, 856, and 810 support, that gap is what you need to fill.

This guide covers how EDI maps into Business Central, the integration methods available, and how orders that never arrive as EDI still land in the system without manual keying. If you run the larger Finance & Operations product, see our separate [Dynamics 365 EDI integration](/blog/edi-dynamics-365-integration) guide.

## Does Business Central Have Native EDI?

**Business Central does not include an EDI translator. EDI is added through AppSource apps, AL extensions, or middleware that uses the Business Central REST and OData APIs.** Microsoft exposes a documented API surface and lets partners handle the [X12](https://x12.org/) and EDIFACT specifics, rather than building translation into the ERP itself.

The Business Central API endpoints cover sales orders, sales invoices, shipments, customers, and items. Microsoft documents them in the [Business Central API reference](https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/api-reference/v2.0/). An EDI provider maps an inbound 850 to the salesOrder resource, then reads the shipment and posted invoice resources to build the outbound 856 and 810.

Raw X12 does not touch Business Central directly. A translator receives the 850 over AS2, SFTP, or a VAN, converts it to the JSON the API expects, and creates the order. To inspect what the source EDI segments actually contain before mapping them, the [free EDI Inspector](/edi-inspector) parses any X12 file with no signup.

## How EDI Documents Map to Business Central

**An inbound 850 creates a sales order, and outbound 856 and 810 documents generate from the posted shipment and posted sales invoice.** The mapping follows the standard Business Central document flow, so each EDI transaction lines up with a step your team already runs.

| Direction | X12 Transaction | Business Central Document | Source |
|---|---|---|---|
| Inbound | 850 Purchase Order | Sales order | salesOrder API resource |
| Inbound | 860 PO Change | Sales order update | salesOrder resource |
| Outbound | 855 PO Acknowledgment | Order confirmation | Confirmed sales order |
| Outbound | 856 Ship Notice (ASN) | Posted sales shipment | Posted shipment document |
| Outbound | 810 Invoice | Posted sales invoice | salesInvoice resource |

Business Central also supports sales quotes and blanket sales orders. A blanket order holds a total quantity commitment, and individual sales orders draw against it. For an EDI program where a retailer sends repeating 850s against a standing commitment, the integration can create each order as a draw from the blanket order rather than a standalone document. Our [EDI 850 purchase order guide](/guides/edi/850-purchase-order) breaks down every segment the retailer can include.

## Integration Methods for Business Central

**Business Central offers three practical EDI paths: an AppSource EDI app, a custom AL extension, or middleware over the REST and OData APIs.** Each trades setup effort against control and ongoing cost.

- **AppSource EDI apps**: partners like SPS Commerce, TrueCommerce, and Lanham EDI publish Business Central apps with pre-built trading partner maps. Fastest to a known retailer, but priced with monthly plus per-document fees, and spec changes usually route through a support queue.
- **Custom AL extensions**: your partner or developer builds the mapping in AL against Business Central pages and APIs. Full control, but it needs someone who understands both X12 structure and the Business Central data model.
- **Middleware over APIs**: an external service reads and writes through the REST and OData endpoints. This keeps EDI logic outside the ERP, which fits well when you also process PDF and email orders.

The API-first design is the key point for smaller companies. Because Business Central publishes a stable REST surface, a modern integration can create orders and read posted documents without installing heavy per-partner infrastructure inside the ERP. For the broader connection patterns, see our guide to [ERP integration](/erp-integration), and for the choice between direct EDI and API approaches, our [EDI vs API comparison](/blog/edi-vs-api).

## The Full Order-to-Cash Flow

**A complete Business Central EDI cycle moves an inbound purchase order to a sales order, then generates outbound EDI as each document posts.** Here is the sequence for a distributor selling to a retailer.

1. **Inbound 850**: the translator maps the retailer's purchase order to the salesOrder resource and creates the order. A 997 functional acknowledgment confirms receipt back to the retailer.
2. **Outbound 855**: on order confirmation, the integration sends the acknowledgment, flagging any line quantity or substitution changes.
3. **Outbound 856**: when you post the sales shipment, the integration reads the posted shipment and builds the EDI 856 ship notice with carton and SSCC-18 detail. Retailers usually require the ASN before delivery, and a late one triggers chargebacks. Our [EDI 856 ship notice guide](/guides/edi/856-ship-notice) covers the structure.
4. **Outbound 810**: after posting the sales invoice, the integration produces the EDI 810, reconciling allowances and freight against the original 850 to avoid payment disputes.

For the wider view of how this chain runs across systems, read our overview of [order-to-cash automation](/blog/order-to-cash-automation).

## How OrderSync Connects Orders to Business Central

**OrderSync creates Business Central sales orders from inbound orders in any format, then syncs shipments and invoices back out as EDI.** The clean EDI partners are the easy accounts. The hard ones are the retail customers who email a PDF purchase order or send a spreadsheet, which still get keyed into Business Central by hand. To connect orders to Business Central with OrderSync, see the [Dynamics 365 integration page](/integrations/microsoft-dynamics-365).

OrderSync ingests EDI 850s, PDF purchase orders, emailed orders, and CSV files through one pipeline. It maps buyer part numbers to your Business Central item numbers, validates quantities and pricing, and creates the sales order through the API. When you post the shipment and invoice, OrderSync generates the outbound 856 and 810 for the trading partner. PDF and email orders flow through the same automation instead of landing in a manual queue.

Smaller distributors on Business Central almost always have a long tail of accounts that will never adopt EDI, which is exactly where a single multi-format pipeline pays off. See how the [multi-format order pipeline](/multi-format-orders) handles them. For teams comparing platforms, we also document [NetSuite EDI integration](/blog/edi-netsuite-integration) and [QuickBooks EDI integration](/blog/edi-quickbooks-integration) in dedicated guides.

## Frequently Asked Questions

### Does Business Central have built-in EDI support?

No. Business Central does not include an EDI translation engine. EDI is added through an AppSource ISV app, a custom AL extension, or middleware that reads and writes through the Business Central REST and OData APIs. Microsoft exposes a documented API surface and leaves X12 translation to integration partners.

### How does an EDI 850 become a sales order in Business Central?

A translation layer receives the X12 850, maps the retailer's part numbers to your Business Central item numbers, and creates the order through the salesOrder API resource. Business Central then treats it as a standard sales order, and a 997 acknowledgment confirms receipt back to the retailer.

### Can I use blanket sales orders with EDI in Business Central?

Yes. A blanket sales order holds a total quantity commitment, and individual sales orders draw against it. When a retailer sends recurring 850s against a standing commitment, the integration can create each order as a draw from the blanket order, keeping the remaining quantity accurate without re-keying the terms each time.

### What is the difference between Business Central EDI and Finance & Operations EDI?

Both lack a native EDI engine and rely on connectors or API-based integration, but the surface differs. Business Central uses AL extensions and its REST and OData APIs and suits smaller companies. Finance & Operations uses X++ extensions, data entities, and the Data Management Framework and targets larger enterprises with more complex requirements.

### How does OrderSync handle non-EDI orders in Business Central?

OrderSync processes PDF purchase orders, emailed orders, and CSV files through the same pipeline as EDI 850s and creates Business Central sales orders from all of them. Retail accounts that do not send EDI never require a separate translator or manual keying, which removes the long tail of orders that Business Central EDI setups usually leave for staff to enter by hand.