EDI Integration for Business Central

Key Features

Inbound 850 purchase order import that validates, maps and creates Business Central Sales Orders through an idempotent, restartable pipeline

Outbound 810 invoice generation triggered by event subscribers on standard BC posting routines, dispatched to the partner automatically

856 Advance Ship Notice (ASN) built from posted warehouse shipments, including pack/SSCC structure where the partner requires it

855 functional acknowledgment and 997 technical acknowledgment matched back to the originating document for closed-loop confirmation

Trading-partner map library — reusable, configurable maps per partner so qualifier/segment differences are data, not code

Document validation layer with partner-specific business rules enforced before any document posts

Error queue page with inspect, correct and reprocess actions so failed transactions never disappear silently

AS2, SFTP and VAN connectivity options configured to your partners' transport and security requirements

Job Queue entries that schedule polling, dispatch and acknowledgment reconciliation on your chosen cadence

Dedicated permission set scoping EDI setup, operation and error-handling roles without over-granting access

Per-tenant AL extension installed via the BC Extension Management page — zero changes to base application objects, upgrade-safe

Built on the BC REST/OData API and table/page extensions so EDI data is queryable and reportable alongside native documents

Optional Power Platform / Dataverse surfacing of EDI status for dashboards and partner-onboarding workflows

Sandbox-first deployment with documented cutover to production and a rollback path

Built to order, done for you

No DIY setup — a working app, built, installed and supported by ECOSIRE.

You order

Start with a one-time build price. We scope it with you at kickoff.

We build & install

ECOSIRE builds, configures and installs it on your Dynamics 365 Business Central.

Go live + support

You go live in about 2–4 weeks, with a post-launch support window.

About this Product

EDI Integration for Business Central turns your trading-partner document flow into a first-class part of your ERP instead of a bolt-on spreadsheet-and-email process. ECOSIRE builds this as a per-tenant AL extension installed directly on your Dynamics 365 Business Central environment (cloud SaaS or on-prem), so EDI orders, shipments and invoices live next to the sales documents they create.

Inbound 850 purchase orders are validated, mapped and posted as Business Central Sales Orders through an idempotent import pipeline; outbound 810 invoices and 856 ASNs are generated from posted shipments and invoices via event subscribers on the standard posting routines, then dispatched to your partner. Functional and technical acknowledgments (855 and 997) are matched back to the originating document so nothing falls through silently. Every transaction passes through a document validation layer and lands in an error queue page where your team can inspect, correct and reprocess failures — no black box.

This is honest build-to-order work, not an instant AppSource download. After purchase, ECOSIRE scopes your partner specifications, builds the trading-partner map library, connects your transport (AS2, SFTP or VAN), installs the extension on a sandbox first, and migrates it to production with a documented permission set and Job Queue schedule. We use BC's REST/OData APIs and event-driven AL — no modifications to base application objects, so your environment stays upgrade-safe.

The result is EDI you can actually see and operate: partner maps you own, errors you can fix, and ASNs/invoices that flow automatically from the documents your team already posts. ECOSIRE remains on hand for partner onboarding, map changes and BC update compatibility.

What you get

A per-tenant Business Central AL extension (.app) built to your trading-partner specifications, installed on your sandbox and production tenants

Configured trading-partner map library covering each partner's 850/810/856/855/997 segment and qualifier requirements

Transport configured and tested end-to-end (AS2 certificates, SFTP credentials, or VAN mailbox) per partner

Dedicated EDI permission set plus Job Queue entries scheduled for polling, dispatch and acknowledgment reconciliation

Source code and the signed .app package, with a documented deployment and rollback procedure

Setup and operator documentation covering the error queue, reprocessing, and adding a new partner

A handover walkthrough plus a defined post-go-live support window for fixes and partner onboarding

Who this is for

Supply-Chain / IT Lead at a Distributor

Owns the trading-partner relationships and the ERP. Needs retail-partner orders to land as Sales Orders and ASNs/invoices to flow back automatically, with full visibility when a document fails — not a brittle middleware that nobody on the team can debug.

Manufacturer Operations Manager with Retail Partners

Ships to big-box and grocery partners that mandate 856 ASNs with SSCC labels and 810 invoices on strict timelines. Wants EDI generated from the shipments and invoices already posted in Business Central, so compliance does not depend on manual re-keying.

Business Central Administrator

Responsible for keeping the tenant upgrade-safe and access controlled. Values a per-tenant extension that touches no base objects, ships with a scoped permission set, and runs on the Job Queue with an observable error queue rather than hidden background jobs.

How EDI Integration for Business Central Compares

Criterion	ECOSIRE	Custom Build	Competitor
Embedded in Business Central (orders, ASNs, invoices live with native documents)	Included	Partial support	Partial support
Trading-partner maps you own and can extend without re-engineering	Included	Partial support	Partial support
Inbound 850 / outbound 810 / 856 ASN / 855 / 997 out of the box for your partners	Included	Partial support	Included
Visible error queue with inspect and reprocess (no black box)	Included	Partial support	Partial support
Per-tenant AL extension, no base-object changes, upgrade-safe	Included	Partial support	Included
AS2 / SFTP / VAN transport configured and tested per partner	Included	Partial support	Included
Built, installed and supported on your tenant by the vendor	Included	Not included	Partial support
No recurring per-document or per-partner SaaS metering imposed by the app	Included	Included	Not included

Frequently Asked Questions about EDI Integration for Business Central

How long until the EDI integration is live, and how does delivery work?

This is build-to-order, not an instant AppSource install. After purchase we run a short scoping call to collect your trading-partner specifications and transport details. A typical build for one to three partners with the standard 850/810/856/855/997 document set runs about two to four weeks, depending on how clean the partner specs are and how quickly partner connectivity can be tested. We build and install on your sandbox first, validate documents end-to-end with each partner, then cut over to production on a scheduled date. You get a realistic timeline in writing before work starts.

What happens with ongoing support and Business Central updates after go-live?

Every engagement includes a defined post-go-live support window for fixes and clarifications. Because it is installed as a per-tenant AL extension that touches no base application objects, it stays compatible across BC's monthly and major updates; if a specific update changes a posting routine our event subscribers hook into, we adjust the extension under a support agreement. Adding new trading partners or changing an existing partner's map is straightforward configuration or a scoped map update that ECOSIRE can deliver as needed — you are not locked out of growing your partner list.

Is this a Microsoft AppSource app I can just download?

No. We do not sell an instant AppSource download. ECOSIRE builds the extension specifically for your trading partners and installs it on your tenant via the Extension Management page as a per-tenant extension. This is deliberate — EDI maps are partner-specific, and a configurable build mapped to your real partners beats a generic app you would still have to heavily customize.

Will this modify my Business Central base application or risk my upgrades?

No base application objects are modified. The solution is pure AL using table and page extensions plus event subscribers on standard posting routines, packaged as a signed per-tenant extension. That is the Microsoft-recommended pattern and is what keeps your environment upgrade-safe. It also ships with a dedicated permission set so EDI access is scoped rather than granted through broad admin rights.

Can EDI status feed into Power BI or the Power Platform?

Yes. EDI documents and their statuses live in extension tables that are exposed through the BC REST/OData API, so they are queryable for Power BI dashboards. Where you want partner-onboarding workflows or status surfaced in Dataverse, we can wire EDI status into the Power Platform as a scoped add-on to the build. The error queue and acknowledgments are all real BC data, not a separate silo.