Dynamics 365
Power Platform
Dynamics
Cloud & ProductivityBusiness Central EDI buyer’s guide: Costs, document types, trading partners, and 3PL integration
Electronic data interchange, or EDI, reduces manual order entry and allows a business to meet the requirements of major customers, retailers, suppliers, and logistics providers. The value of EDI depends on how well the solution connects those partners to Microsoft Dynamics 365 Business Central and supports the company’s order, warehouse, inventory, and financial processes.
A Business Central EDI integration is not a file transfer project. It changes how sales, purchasing, fulfillment, warehousing, inventory, and finance work together, which is why the evaluation should extend well past the initial subscription price. Compare supported document types, trading partner onboarding, mapping, transaction volume, 3PL integration, error management, implementation services, and ongoing support.
Business Central EDI at a glance
Microsoft Dynamics 365 Business Central does not include full EDI functionality out of the box. Most businesses require an integrated EDI app, managed service, external platform, or custom integration to exchange standardized documents with customers, retailers, suppliers, and third-party logistics providers.
Before selecting a solution, compare total implementation and ongoing costs, supported documents and trading partners, depth of Business Central integration, 3PL capabilities, error handling, onboarding effort, and support. The right solution should link EDI transactions to related orders, shipments, receipts, inventory, and invoices in Business Central while providing clear exception management.
Table of contents
- What is EDI in Microsoft Dynamics 365 Business Central?
- Does Business Central include EDI?
- Why businesses invest in Business Central EDI integration
- What types of EDI solutions are available?
- How much does EDI for Business Central cost?
- Which EDI documents does your business need?
- How trading partner requirements affect EDI
- How does Business Central EDI work with a 3PL?
- What are the benefits of integrated EDI?
- What should you look for in an EDI provider?
- Common Business Central EDI implementation mistakes
- Meet EDI 365 from Rand Group
- How AGT Products automated order entry with EDI 365
- Business Central EDI requirements checklist
- Key takeaways
- Frequently asked questions
What is EDI in Microsoft Dynamics 365 Business Central?
Electronic data interchange is the computer-to-computer exchange of standardized business documents between organizations. Instead of emailing a purchase order, entering it manually, and sending a separate shipping confirmation, EDI allows systems to exchange that information in an agreed format.
The organizations exchanging documents are called trading partners. They include:
- Customers
- Retailers
- Distributors
- Suppliers
- Manufacturers
- Third-party logistics providers
When EDI is integrated with Business Central, an inbound document creates or updates a record in the ERP. An EDI 850 purchase order from a retailer creates a sales order in Business Central. Once the company ships the order, Business Central data is used to send an EDI 856 advance shipment notice and an EDI 810 invoice.
A typical process follows this pattern:
Trading partner → EDI platform → document validation and mapping → Business Central
For outbound documents, the process works in reverse.
The EDI platform translates the partner’s document into data Business Central can process. It also validates required fields, returns acknowledgments, monitors document status, and alerts users when a transaction fails.
Does Business Central include EDI?
No. Microsoft Dynamics 365 Business Central does not include complete EDI functionality out of the box. A business that needs to exchange EDI documents with retailers, suppliers, distributors, or 3PL providers will need an EDI app, external EDI platform, managed EDI service, or custom integration.
Business Central provides REST APIs and other integration tools that an EDI solution uses to exchange data with the ERP. These APIs allow an outside EDI service to create, update, or read Business Central records. They do not deliver the EDI process itself.
Business Central does not natively provide the capabilities commonly required for trading partner EDI, including:
- EDI document translation
- Partner-specific maps
- Trading partner networks
- AS2, SFTP, VAN, and other communication services
- Partner testing and certification
- Transaction monitoring and error reprocessing
Business Central does include an E-Documents framework for electronic invoicing and regulatory document scenarios such as PEPPOL. Electronic invoicing is not the same as retail, supply chain, or 3PL EDI. The E-Documents framework handles compliance-driven invoice exchange. It does not manage retailer purchase orders, advance shipment notices, or warehouse instructions.
The practical distinction is straightforward: Business Central manages the financial and operational records, while an integrated EDI solution manages the standardized document exchange and trading partner requirements.
To learn more about connecting outside systems to the ERP, read the Microsoft Dynamics 365 Business Central integration guide.
Why businesses invest in Business Central EDI integration
Most businesses first consider EDI because a large customer or retailer requires it. Others adopt it because manual document processing can no longer support their transaction volume.
Without integration, employees need to:
- Download an order from an EDI portal.
- Enter the order into Business Central.
- Update the portal when the order is accepted.
- Copy shipment and tracking information back into the EDI system.
- Enter invoice information in another portal.
- Investigate differences between the ERP and the trading partner’s records.
This work becomes harder as the number of partners, orders, warehouses, and document types grows. Integrated EDI moves purchase orders, acknowledgments, shipping notices, invoices, inventory messages, and warehouse instructions between Business Central and outside systems without manual re-entry.
Businesses use EDI to:
- Meet customer and retailer requirements.
- Reduce manual order entry.
- Process higher document volumes.
- Shorten order-to-cash cycles.
- Improve order and shipment accuracy.
- Exchange data with suppliers and 3PLs.
What types of EDI solutions are available?
EDI can be handled in several ways, including portal-based EDI, integrated EDI software, managed EDI services, value-added networks, middleware, or custom integrations. The right option depends on your trading partners, transaction volume, Business Central processes, internal support capacity, and how much automation you need.
Web-based or portal EDI
With portal EDI, employees log in to a website to receive orders, enter acknowledgments, create shipping notices, and submit invoices.
Portal EDI suits a company with:
- One or two trading partners
- Low document volume
- Simple document requirements
- No immediate need for ERP integration
The tradeoff is that portal EDI still requires employees to re-enter information between the portal and Business Central. It satisfies the partner’s communication requirement without automating the internal process.
Integrated EDI software
An integrated EDI solution connects directly with Business Central. It translates partner documents and creates, updates, or reads ERP records. This model reduces manual work, but the reduction depends on details buyers need to confirm:
- How deep the Business Central integration goes
- Whether the provider supplies prebuilt maps
- Who manages testing
- Where employees resolve errors
- Whether custom fields and workflows are supported
- Who maintains the integration after updates
Managed EDI service
A managed service combines EDI software with ongoing operational support. Scope varies by provider and contract, and generally covers partner onboarding, mapping, testing, monitoring, and specification updates.
This approach suits businesses that do not want to build an internal EDI team. Document the service scope, response times, support responsibilities, and change fees before signing a contract.
Value-added network
A value-added network, or VAN, acts as an intermediary that receives, routes, and delivers EDI documents between trading partners.
A VAN simplifies communications when partners use different protocols. Fees are based on document volume, data volume, connections, or other usage measures.
Integration platform or middleware
Some businesses use an integration platform to connect Business Central with EDI, ecommerce, CRM, warehouse systems, shipping applications, and other services.
Middleware provides flexibility across a larger integration environment. The company still needs a way to translate EDI standards, maintain partner maps, manage communication protocols, and monitor transactions.
Custom EDI integration
A custom integration works for a small, stable document flow with limited partners. It becomes riskier when requirements change frequently or several systems participate in the process.
Before choosing custom development, resolve:
- Who will maintain the code
- How partner changes will be handled
- How errors will be monitored
- Whether supported Business Central APIs are used
- How Business Central updates will be tested
- How quickly another partner can be added
How much does EDI for Business Central cost?
There is no reliable universal price for Business Central EDI. Costs vary according to the number of partners, document types, transactions, maps, systems, legal entities, and services included. Compare total cost rather than the lowest advertised subscription.
One-time EDI implementation costs
Initial costs cover:
- EDI app or connector activation
- Business Central configuration
- Security and connection setup
- Document and partner-specific mapping
- Testing and certification
- 3PL or warehouse integration
Additional costs apply when the project requires custom Business Central fields, extensions, API development, training, or go-live support.
An advertised connection to a retailer does not mean that retailer can be activated without additional work. The provider still needs to configure partner identifiers, products, locations, fulfillment models, and Business Central field mappings.
Recurring EDI costs
Ongoing charges cover:
- Software subscriptions
- Trading partner fees
- Document or transaction fees
- Data-volume or VAN charges
- Managed service and support fees
- Map changes and new document setup
Ask whether a transaction means one business process or each individual EDI message. A single customer order produces several messages, including an order, acknowledgment, shipment notice, invoice, and functional acknowledgments.
Costs that buyers often miss
The lowest initial quote rarely represents the lowest total cost. Frequently overlooked expenses include:
- Adding a new partner or division
- Supporting multiple ship-to locations
- Updating maps after specification changes
- Correcting failed documents
- Connecting another Business Central company or 3PL
- Supporting labels, returns, allowances, or chargebacks
Business Central EDI cost comparison checklist
A complete proposal states what is included, what is optional, and what will trigger additional charges.
Which EDI documents does your business need?
The right documents depend on whether your company sells to customers, purchases from suppliers, works with a 3PL, or supports several of these flows. Document direction also depends on the company’s role. For example, an EDI 850 is inbound when a retailer places an order with your business, and outbound when your company sends a purchase order to a supplier.
Common sales and retail EDI documents
The 850, 855, 856, and 810 are the core retail order-to-cash document set. A full requirement often adds inventory, order changes, remittance, receiving advice, returns, warehouse instructions, and technical acknowledgments.
Common 3PL and warehouse EDI documents
Document numbers alone do not define the project. The trading partner’s implementation guide determines the required fields, codes, timing, and validation rules.
How trading partner requirements affect EDI
Two partners can use the same EDI transaction number and still require entirely different information. Two retailers may both send an EDI 850. One requires store-level ship-to codes, while another requires distribution center routing, special packaging, or customer-specific item numbers.
Partner requirements define:
- EDI standard and version
- Required data segments
- Product and partner identifiers
- Units of measure and location codes
- Carrier, packaging, and labeling rules
- Testing and acknowledgment requirements
A provider’s claim that it supports the 850 does not prove that it supports every retailer’s version of the 850.
How does Business Central EDI work with a 3PL?
A 3PL integration connects Business Central with an outside warehouse responsible for storing, picking, packing, or shipping inventory.
Consider an order-to-cash process involving a retailer and a 3PL:
- The retailer sends an EDI 850 purchase order.
- The EDI solution creates a sales order in Business Central.
- Business Central sends a 940 warehouse shipping order to the 3PL.
- The 3PL ships the order and returns a 945 warehouse shipping advice.
- Business Central updates or posts the shipment.
- The retailer receives an 856 advance shipment notice and an 810 invoice.
This flow connects customer demand, ERP order management, warehouse execution, inventory, shipping communication, and billing.
Decisions to make before integrating a 3PL
A successful 3PL integration requires more than exchanging a 940 and 945. Make the following decisions before configuration begins:
- Choose the inventory system of record: Define whether Business Central or the 3PL system controls inventory balances and how often the systems reconcile.
- Set shipment posting rules: Decide whether a 945 posts the shipment automatically or requires review, especially for shortages, substitutions, or split shipments.
- Define ASN ownership: Determine whether Business Central, the EDI platform, or the 3PL creates the 856 using package, carrier, and tracking details.
- Plan item-tracking exchanges: Specify how the 3PL sends lot, serial, expiration date, and other item-tracking details to Business Central.
- Document returns and adjustments: Include damaged goods, returns, cycle count differences, lost inventory, and warehouse adjustments.
- Create mismatch controls: Define what happens when the item, quantity, location, unit of measure, or tracking data does not match Business Central.
What are the benefits of integrated EDI?
Portal-based EDI satisfies a trading partner mandate, but it leaves employees moving information between the portal and Business Central. Integrated EDI connects document exchange to the related ERP process and delivers the following benefits:
- Reduce manual data entry: Orders, shipping information, invoices, and other documents are not repeatedly entered into separate systems.
- Improve transaction accuracy: Less re-keying reduces avoidable errors, and validation rules identify incorrect data earlier.
- Process orders faster: Inbound orders reach Business Central without waiting for an employee to download and enter them.
- Accelerate shipping and invoicing: Advance shipment notices and invoices are generated from completed Business Central processes.
- Improve transaction visibility: Users connect partner documents with related orders, shipments, receipts, and invoices.
- Support higher transaction volumes: Businesses process more routine documents without increasing administrative work at the same rate.
The value of integration still depends on accurate master data, reliable mappings, well-designed controls, and a clear process for exceptions. For an industry-specific example, read how EDI in food and beverage can improve order processing, accuracy, and supply chain coordination.
Connect Business Central with your trading partners
Your EDI requirements may include retailers, suppliers, 3PLs, cross-docks, warehouse documents, custom fields, and partner-specific rules. Rand Group can assess the complete process and help you build an EDI integration that fits your Business Central environment.
What should you look for in an EDI provider?
The right provider understands both EDI standards and the Business Central processes connected to each document. Compare providers on how well they support your trading partners, ERP workflows, 3PL requirements, exception handling, and long-term operating needs rather than on price or transaction volume alone.
- Business Central experience: Confirm the provider understands sales orders, purchase orders, shipments, receipts, invoices, inventory, item references, warehouse records, and custom extensions.
- Trading partner onboarding: Ask who manages requirements, mapping, testing, certification, production cutover, and future partner changes.
- Document and 3PL coverage: Verify that the provider supports the complete process, including acknowledgments, invoices, shipping notices, warehouse transactions, returns, and adjustments.
- Error management and visibility: Business users should be able to identify failures, correct appropriate data, reprocess transactions, and review a complete audit trail.
- Security and support: Review communication protocols, encryption, access controls, monitoring, response expectations, and whether the support team understands Business Central.
- Transparent total cost: Request a breakdown of implementation, partner, document, transaction, testing, support, change, renewal, and exit costs.
Common Business Central EDI implementation mistakes
Across the Business Central EDI projects Rand Group has implemented, the same avoidable mistakes tend to surface, and they rarely show up as technical failures. The document transmits correctly, but the order posts to the wrong location, the retailer charges back a late ASN, or a failed invoice sits unnoticed for a week. In our experience, the projects that struggle are the ones that treated EDI as a file transfer rather than a business process. The most common mistakes include:
- Starting without a complete requirements list: Document each partner, transaction, direction, volume, connected system, and deadline.
- Treating EDI as an IT-only project: Sales, purchasing, warehouse, logistics, finance, and IT should help define the process.
- Ignoring master data: Validate partner numbers, item references, units of measure, locations, product codes, and shipping methods before testing.
- Testing individual documents instead of complete scenarios: Test partial shipments, order changes, duplicates, invalid items, rejected documents, returns, and 3PL differences.
- Automating an inefficient or uncontrolled process: Define which validations, approvals, and posting controls belong in Business Central.
- Going live without monitoring ownership: Identify who reviews failures, responds to alerts, contacts partners, corrects data, and reprocesses documents.
Meet EDI 365 from Rand Group
EDI 365 is Rand Group’s full-service EDI and integration solution for Business Central. The solution is fully embedded within Business Central, allowing users to review and action EDI data without moving to an external portal. It supports trading partner communication directly within Business Central and includes onboarding assistance, mapping, testing, monitoring, training, support, and upgrades. EDI 365 supports hundreds of trading partners, so most retailers, suppliers, distributors, and 3PLs your business needs to reach are already within its network.
EDI 365 pricing is published publicly, with costs structured around an initial setup fee, monthly pricing by trading partner type, onboarding, communication method, and non-standard document or customization needs. Pricing starts at $69.99 per customer trading partner per month, with separate pricing for vendor and 3PL trading partners.
Rand Group is a Microsoft solutions partner that implements and supports Business Central alongside the connected applications that surround it. That combination matters for EDI: the same team that understands your sales orders, warehouse documents, inventory, and financial processes also manages the document exchange, so the integration reflects how your business actually runs rather than treating EDI as an isolated file transfer.
EDI 365 was also included in ERP Software Blog’s 2026 roundup of Microsoft Dynamics ERP supply chain management tools. Read more about EDI 365’s recognition as a Microsoft Dynamics ERP supply chain tool.
How AGT Products automated order entry with EDI 365
AGT Products Inc. manufactures building materials and previously relied on a legacy ERP that created siloed data, manual order entry, paper-based processes, and complex integrations.
Rand Group implemented Microsoft Dynamics 365 Business Central as a centralized ERP across finance, warehouse, production, and sales. EDI 365 was integrated to automate order entry, while other connected applications supported inventory, sales, payroll, production, and ecommerce workflows.
Following the implementation:
- 90% of daily order entry was automated.
- Same-store sales increased by 20%.
- AGT gained integrated inventory and sales workflows.
The result shows why EDI should be evaluated as part of the broader ERP process. Automating EDI documents alone would not have solved AGT’s disconnected finance, warehouse, production, and sales workflows. Read the full AGT Products Business Central and EDI automation case study.
Automate EDI transactions inside Business Central
EDI 365 connects Microsoft Dynamics 365 Business Central with retailers, suppliers, 3PLs, and other trading partners. Rand Group provides trading partner onboarding, mapping, testing, monitoring, and ongoing support through one integrated EDI solution.
Business Central EDI requirements checklist
Use this checklist before requesting proposals from EDI providers.
Key takeaways
- Business Central does not include complete EDI functionality, so businesses need an EDI app, platform, managed service, or custom integration.
- Total EDI cost depends on partners, documents, volume, mapping, testing, support, and connected systems.
- The same EDI document carries different requirements for each trading partner.
- A 3PL integration must address inventory, shipment posting, tracking, exceptions, and reconciliation.
- Buyers should compare Business Central expertise, onboarding, error handling, support, and long-term cost.
- Strong master data and end-to-end testing are essential for reliable EDI automation.
Frequently asked questions
What is EDI in Microsoft Dynamics 365 Business Central?
EDI in Business Central is the automated exchange of standardized business documents between Business Central and external customers, suppliers, retailers, warehouses, and logistics providers. An integrated EDI solution uses incoming documents to create or update ERP records and uses Business Central data to generate outbound documents.
Does Microsoft Dynamics 365 Business Central have built-in EDI?
No. Business Central does not provide complete EDI functionality out of the box. Businesses need an EDI app, external platform, managed service, or custom integration to translate documents, connect with trading partners, manage partner maps, monitor transactions, and handle testing. Business Central does include an E-Documents framework for electronic invoicing and regulatory scenarios, which is separate from retail and supply chain EDI.
How much does Business Central EDI cost?
Business Central EDI costs depend on the number of trading partners, documents, transactions, companies, maps, systems, and services required. Compare activation, partner onboarding, mapping, testing, transaction, support, change, and 3PL integration costs rather than relying only on the advertised subscription.
What are the most common EDI documents for Business Central?
Common retail documents include the 850 purchase order, 855 order acknowledgment, 856 advance shipment notice, and 810 invoice. Depending on the process, companies also require inventory advice, order changes, remittance information, receiving advice, functional acknowledgments, and warehouse documents.
What is the difference between EDI 850, 855, 856, and 810?
An EDI 850 communicates a purchase order. The 855 responds to the order. The 856 describes the shipment and generally includes packaging and tracking details. The 810 communicates invoice information. Together, these documents support a common order-to-cash process.
Can Business Central connect to a 3PL through EDI?
Yes. Business Central exchanges warehouse instructions and confirmations with a 3PL through an integrated EDI solution. A common process sends a 940 warehouse shipping order to the 3PL and receives a 945 warehouse shipping advice after fulfillment.
What are EDI 940 and 945 documents?
An EDI 940 tells a warehouse or 3PL what to ship. An EDI 945 confirms what the warehouse actually shipped. The 945 returns quantities, dates, carrier information, tracking data, and other shipment details needed to update Business Central and notify the customer.
What is the difference between EDI 943 and 944?
An EDI 943 notifies a warehouse that a stock transfer shipment is on the way. An EDI 944 confirms that the warehouse received the transferred inventory. Both apply to inventory moving between your own locations, which distinguishes them from the 940 and 945 used for customer shipments.
How long does it take to onboard an EDI trading partner?
The timeline depends on whether a current map already exists, the number of documents, partner testing availability, Business Central configuration, master-data quality, custom fields, and process complexity. A provider should give a timeline after reviewing the partner’s implementation guide and required Business Central workflow.
What should I look for in a Business Central EDI provider?
Look for experience with Business Central, partner-specific mapping, onboarding, testing, 3PL workflows, error management, transaction monitoring, security, and ongoing support. The provider should clearly explain pricing, responsibilities, change management, and how the solution handles exceptions.
Choose an EDI solution based on the full process
A Business Central EDI integration should do more than move files. It should connect trading partner requirements with sales orders, purchasing, warehouse execution, inventory, shipping, invoicing, and financial controls.
Before selecting a provider, document your partners, transaction sets, Business Central records, 3PL requirements, exception scenarios, and expected growth. When you are ready to evaluate your options, contact Rand Group to discuss your trading partner requirements and the best way to integrate EDI with Microsoft Dynamics 365 Business Central.
