示意预览A custom AL extension that embeds EDI document exchange inside Business Central
— inbound POs, outbound invoices, ASNs and acknowledgments mapped to your trading partners, with validation, an error queue and AS2/SFTP/VAN connectivity. Built, installed and supported by
ECOSIRE on your tenant.
什么是 EDI Integration for Business Central？
A custom AL extension that embeds EDI document exchange inside Business Central — inbound POs, outbound invoices, ASNs and acknowledgments mapped to your trading partners, with validation, an error queue and AS2/SFTP/VAN connectivity. Built, installed and supported by ECOSIRE on your tenant. Built to order by ECOSIRE for Dynamics 365 BC (build-to-order) — indicative price from $999.00 USD; request a quote for a scoped proposal.
核心功能
按需定制，全程代劳
无需自行搭建——由 ECOSIRE 构建、安装并提供支持的可用应用。
- 1
您下单
以一次性构建价格开始。我们在启动时与您共同确定范围。
- 2
我们构建与安装
ECOSIRE 在您的 Dynamics 365 Business Central 上构建、配置并安装。
- 3
上线 + 支持
约一个工作周内上线，并包含两周上线支持。我们交付的代码中的缺陷免费修复。
关于此产品
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.
你得到什么
- 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
这是给谁的
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.
EDI Integration for Business Central 如何比较
| 标准 | 伊科西尔 | 定制建造 | 竞争对手 | Dynamics 365 Business Central 原生 |
|---|---|---|---|---|
| Embedded in Business Central (orders, ASNs, invoices live with native documents) | 包含 | 部分支持 | 部分支持 | 不包括在内 |
| Trading-partner maps you own and can extend without re-engineering | 包含 | 部分支持 | 部分支持 | 不包括在内 |
| Inbound 850 / outbound 810 / 856 ASN / 855 / 997 out of the box for your partners | 包含 | 部分支持 | 包含 | 不包括在内 |
| Visible error queue with inspect and reprocess (no black box) | 包含 | 部分支持 | 部分支持 | 不包括在内 |
| Per-tenant AL extension, no base-object changes, upgrade-safe | 包含 | 部分支持 | 包含 | 不包括在内 |
| AS2 / SFTP / VAN transport configured and tested per partner | 包含 | 部分支持 | 包含 | 不包括在内 |
| Built, installed and supported on your tenant by the vendor | 包含 | 不包括在内 | 部分支持 | 不包括在内 |
| No recurring per-document or per-partner SaaS metering imposed by the app | 包含 | 包含 | 不包括在内 | 包含 |
关于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 one working week, 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.
相关模块
Dental Clinic Management for Business Central
A build-to-order AL extension that gives dental practices chair-level appointment scheduling, versioned treatment plan estimates, procedure-coded invoicing and lab case tracking inside Dynamics 365 Business Central. ECOSIRE scopes, builds, installs and supports it for your tenant.
Document Attachment & Quality Records (DMS)
A build-to-order Business Central (AL) extension that attaches controlled documents — drawings, certificates of analysis, quality records and SOPs — to any page or record, with revision control, role-based access and SharePoint backing. Built, installed as a per-tenant extension and supported by ECOSIRE.
Egypt ETA E-Invoicing & E-Receipt for Business Central
A per-tenant AL extension that clears your sales invoices, credit/debit notes and POS receipts through Egypt's Tax Authority (ETA) portal directly from Business Central — with UUID generation, digital signing, EGS/GS1 code mapping and live status polling. Built, deployed and supported by ECOSIRE.
Energy & Utility Operations
A build-to-order Business Central extension that turns meter readings into billed, collectable revenue — connection registry, cycle billing runs, slab tariffs, service complaints and disconnection workflows. ECOSIRE scopes, builds, installs and supports it for your tenant.
EDI Integration for Business Central
A custom AL extension that embeds EDI document exchange inside Business Central — inbound POs, outbound invoices, ASNs and acknowledgments mapped to your trading partners, with validation, an error queue and AS2/SFTP/VAN connectivity. Built, installed and supported by ECOSIRE on your tenant.
- 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