Match partner data to your records
Map buyer SKUs, ship-to codes, and units to the right records before processing orders.
Business Central EDI Integration Services
Connect Business Central orders to retail-ready shipments.
An EDI order needs to move through Business Central's sales and warehouse processes before a trading partner receives the correct shipment notice and invoice. Tirnav connects those stages with attention to posting, item references, packing detail, and warehouse responsibilities. Our existing SymSafe project includes Business Central connectivity, shipment workflows, and SSCC label automation.
An EDI order needs to move through Business Central's sales and warehouse processes before a trading partner receives the correct shipment notice and invoice. Tirnav connects those stages with attention to posting, item references, packing detail, and warehouse responsibilities. Our existing SymSafe project includes Business Central connectivity, shipment workflows, and SSCC label automation.
Expertise:
- Business Central integration planning
- Retail EDI mapping
- Warehouse & finance workflows
- Failure recovery & support
OR
Trusted by ambitious teams at startups and global enterprises across 5 continents
The problem
Your customer sees one order.
Your systems see separate pieces.
Business Central + EDI gets complicated at the handoffs: where a buyer's SKU becomes a product, where an order becomes a shipment, and where a failed update becomes someone's responsibility.
Give every handoff a clear owner
Define who owns orders, fulfillment, and invoicing so updates stay consistent across systems.
Track processing beyond delivery
A delivered file can still fail processing. Track exceptions and recover without duplicate records.
How it works
One connected transaction.
Clear responsibility at every step.
For distributors, suppliers, and 3PL-connected businesses using Dynamics 365 Business Central. This page covers Business Central specifically; Dynamics 365 Finance and Supply Chain Management have a separate integration scope and page.
- 01
850 Purchase Order
Trading partner
- 02
EDI Network
Document exchange
- 03
Tirnav EDI Platform
Validation & mapping
- 04
Business Central Order Workflow
Business Central
- 05
Fulfillment
Warehouse / WMS / 3PL
- 06
856 ASN
Shipment notice to the buyer
- 07
810 Invoice
Approved finance source → trading partner
Every document is validated, tracked and tied back to the business transaction.
Illustrative workflow; record ownership depends on your configuration.
Business Central exposes sales-order resources through its standard API. We evaluate standard APIs against your company setup, extensions, warehouse configuration, and posted document requirements. Custom API pages or other supported interfaces may be needed when a partner requires fields that the standard resources do not expose. SaaS and on-premises access arrangements are reviewed separately.
Microsoft: Business Central sales-order APIEDI transactions
Connect the complete order-to-cash conversation
Scope the X12 documents your trading partners require and the Business Central or operational records each document needs. These supplier-side examples are confirmed against the partner's version and implementation guide.
01 / Buyer → supplier
Order
EDI 850Purchase Order
What does the buyer need?
Mapping details
Sales order and lines
Map buyer references, item numbers, units, delivery dates, locations, and customer details into the agreed company and sales-order workflow.
02 / Supplier → buyer
Confirmation
EDI 855Purchase Order Acknowledgment
What can you supply, and when?
Mapping details
Reviewed order response
Translate accepted quantities, date changes, and rejected lines into the partner's acknowledgment after the agreed business review.
03 / Supplier → buyer
Fulfillment
EDI 856Advance Ship Notice
What shipped, and how is it packed?
Mapping details
Shipment + packing hierarchy
Use the agreed warehouse or posted-shipment event, enriched with carton, pallet, and SSCC information captured during packing.
04 / Supplier → buyer
Billing
EDI 810Invoice
What is the buyer being charged?
Mapping details
Posted sales invoice
Use the approved posting event and preserve order, shipment, item, and charge references required by the trading partner.
05 / Buyer → supplier
Payment
EDI 820Payment / Remittance
Which invoices does the remittance cover?
Mapping details
Finance reconciliation + application visibility
Match retailer remittance references, invoice amounts, and deductions to approved finance records. Define how Business Central receives reconciliation status; a remittance message alone does not establish payment settlement.
The business journey is shown in sequence; actual timing follows the partner agreement. An EDI 820 carries payment instructions or remittance information. Payment execution and settlement are confirmed through the agreed finance and banking process.
Supporting the transaction throughout its lifecycle
Available stock by agreed location
Define availability independently of a raw item balance, including reservations and excluded locations where applicable.
Technical acknowledgment tracking
Link functional acknowledgment status to the original EDI interchange. Keep technical acceptance separate from order acceptance and application processing.
Additional scope can include 860 order changes, 940 warehouse shipping orders, 945 shipping advice, or EDIFACT equivalents. A technical acknowledgment is separate from a commercial acceptance. Documents and directions are agreed for each partner.
Business Central workflows
Give sales, service, and operations the same order context
Example journey
EDI → Business Central → WMS / 3PL / commerce
- 01
Capture the partner order
Match customer and item references, then create or synchronize the agreed order records.
- 02
Confirm fulfillment with the warehouse
Use confirmed quantities, packing, and tracking data to prepare the shipment notice.
- 03
Reconcile the approved invoice
Send the approved invoice with its original PO and shipment references intact.
Illustrative workflow; records depend on your edition and configuration.
Warehouse activity versus shipment completion
Send shipment notices from the agreed completion event, using confirmed packing data.
Extensions and additional fields
Check API access to extension fields required by each trading partner.
Company, location, and item references
Route documents to the correct company, location, customer, and item.
SSCC and packing operations
Keep SSCC labels, carton contents, and outbound ASNs aligned after repacking.
EDI failure & recovery
When an order fails,
your team needs a way forward.
Recovery is part of the integration design. We define how to locate the failure, correct the cause, resume processing, and verify the result across EDI, Business Central, and the systems downstream.
Detect the actual failure
Track document receipt, validation, application processing, and partner acknowledgment separately. Surface the failed stage, affected order line, and source error instead of showing one ambiguous success flag.
Give someone enough context to act
Route mapping issues, application validation errors, and warehouse exceptions to the right owner. Keep partner control references, record IDs, timestamps, and the required correction together.
Replay with duplicate protection
Check whether the destination already committed a record before retrying. Preserve the original correlation reference, retry only the appropriate stage, and require review when the outcome is uncertain.
Reconcile before closing the issue
Confirm that source and destination records agree and that the required downstream messages completed. Record the correction and recovery result so operations can explain what happened later.
Example: a Business Central order update times out
Ambiguous outcomeA timeout does not prove the write failed. Check the original external reference and the supported Business Central record state before retrying. If the agreed order record exists, resume from the next incomplete stage. If it does not, a controlled retry can proceed. Uncertain matches go to review. Edition-specific permissions and posting rules govern any correction.
Try the sample recovery workflowImplementation process
From the first partner guide to production support
Six clear steps from discovery to ongoing support.
- 01
Discover
Agree on partners, systems, scope, and ownership.
- 02
Map
Match partner documents to your business records.
- 03
Build
Connect systems with validation and recovery controls.
- 04
Test
Verify complete transactions, exceptions, and partner requirements.
- 05
Go-live
Launch with a controlled cutover and verified live orders.
- 06
Support
Monitor transactions, resolve issues, and maintain mappings.
Customer examples
See the integration work behind the service
These documented projects show our EDI, warehouse, and accounting integration experience. Each card identifies the actual systems and scope delivered. Use these examples to review the relevant partner mapping, warehouse handoffs, and accounting connections for your project.
Retail EDI + custom ERP
World Depot
Explore multi-retailer EDI integration with a custom ERP, connecting partner documents to the business's logistics workflows.
Relevant to partner mapping and cross-system order processing.
Read the World Depot case studyBusiness Central + shipment operations
SymSafe
See a logistics portal connected to Microsoft Business Central, including shipment synchronization and SSCC label automation.
Relevant to warehouse handoffs and shipment data ownership.
Read the SymSafe case study
Commerce + QuickBooks
HookedOnTronics
Review connected ecommerce and accounting work with QuickBooks as part of a wider system modernization project.
Relevant to financial record connectivity and application integration.
Read the HookedOnTronics case studyPlatform integrations
Connect the systems behind every customer promise
ERP & finance
Orders, allocations, invoice posting, and financial reconciliation.
Shopify & commerce
Catalog references, wholesale order context, and channel inventory rules.
WMS & warehouses
Confirmed quantities, carton hierarchy, tracking, and SSCC data.
3PL & logistics
Fulfillment handoffs, dispatch events, shipment corrections, and partner references.
Connections are scoped to the available APIs or supported file interfaces. Review the platform guides below for mapping and implementation considerations.
EDI integrations by platform
Need EDI beyond Business Central?
Tirnav also connects EDI workflows with Salesforce, Shopify, SAP, Microsoft Dynamics, WMS, 3PL and other business systems.
- CRM & Customer Operations
Salesforce EDI integration
Bring trading-partner orders and EDI visibility into Salesforce.
- Cloud ERP
NetSuite EDI integration
Bring retail EDI into your NetSuite workflow.
- Ecommerce
Shopify EDI integration
Connect wholesale EDI orders to Shopify operations.
- Accounting
QuickBooks EDI integration
Connect retail EDI with your QuickBooks accounting.
- Modular ERP
Odoo EDI integration
Connect Odoo sales, inventory, and accounting through EDI.
- ERP for growing businesses
SAP Business One EDI integration
Connect SAP Business One to your retail trading partners.
- Enterprise ERP
SAP S/4HANA EDI integration
Connect enterprise EDI to SAP S/4HANA processes.
- Enterprise ERP
Microsoft Dynamics 365 EDI integration
Connect Dynamics 365 operations to enterprise EDI.
- Cloud ERP
Acumatica EDI integration
Connect Acumatica distribution workflows to retail EDI.
- ERP and accounting
Sage EDI integration
Build an EDI connection around your Sage product.
- Open-source ERP
ERPNext EDI integration
Connect ERPNext documents to retail EDI workflows.
Frequently asked questions
Business Central EDI integration FAQs
Our SymSafe case study documents a portal integrated with Microsoft Business Central, shipment synchronization, and SSCC label automation. The project's scope is available in the linked case study; your integration is scoped against your own setup and partner requirements.
That depends on your extensions and trading-partner requirements. We assess standard resources first and identify custom API or extension work where required fields are not exposed.
No. Business Central and Finance/Supply Chain Management have different integration models and operational configurations. We maintain separate scopes and pages for them.
The agreed scope covers discovery, source-to-target mapping, connectivity, validation, exception handling, end-to-end testing, and go-live support. Deliverables identify the trading partners, document types, application records, and any ERP or warehouse changes required. Ongoing support responsibilities are agreed separately.
Timing depends on partner testing windows, document complexity, master-data readiness, interface access, and application changes. After discovery, we provide a dated plan with dependencies and acceptance criteria rather than promise one timeline for every project.
We assess the existing provider's interfaces, mapping ownership, transport agreements, and support responsibilities. The project can focus on the application connection where suitable. If migration is needed, we plan partner testing, reconciliation, and cutover explicitly.
Scope is driven by the number of partners and document maps, application interfaces, custom fields, warehouse dependencies, environments, and support requirements. We separate implementation work from any recurring service, transport, or third-party licensing costs in the proposal.
Connect your Business Central EDI workflow
Bring your trading partners, Business Central setup, and the workflow that needs attention. We will help define the integration scope, demonstrate the relevant EDI platform workflow, and plan the next step.
Email Strategy[email protected]