EDI Integration

核心功能

Inbound EDI processing: parses partner 850 / ORDERS into draft Business Central sales orders with line, price, and ship-to validation before posting

Outbound EDI generation: emits 855 PO acknowledgments, 856 / DESADV ASNs, and 810 / INVOIC invoices on BC posting events via AL event subscribers

Trading-partner profile management: dedicated setup pages holding standard, document versions, ISA/GS/UNB envelope IDs, qualifiers, and per-partner mapping overrides

Multi-standard mapping engine: X12, EDIFACT, and partner-specific XML translated to/from BC fields with segment-level transformation rules

ASN (856) automation: builds hierarchical Shipment/Order/Tare/Item loops from Warehouse Shipment and Item Tracking (SSCC/lot/serial) data

Invoice automation: posted sales invoices auto-translate to 810/INVOIC and transmit to the partner endpoint without manual export

Functional acknowledgment (997 / CONTRL) handling: outbound acks for received documents and inbound ack matching with status logging

Job Queue-driven transport: scheduled polling and sending over your VAN, AS2 gateway, or SFTP endpoint with retry on transient failure

EDI transmission log table: full audit trail of every inbound/outbound document, raw payload, control numbers, and processing status

Control-number management: automatic ISA/GS/ST (and UNB/UNG/UNH) interchange, group, and transaction sequencing per partner

Error handling and quarantine: malformed or unmapped documents are isolated with actionable error detail instead of silently failing

Permission sets: EDI Setup, EDI Operator, and EDI Admin sets separating configuration from day-to-day posting rights

Optional Dataverse / Power Platform surfacing: EDI status exposed for Power BI dashboards and Power Automate flow triggers

Cross-reference tables: partner item numbers, UOM, and GLN/DUNS location codes mapped to your BC items and ship-to addresses

按需定制，全程代劳

无需自行搭建——由 ECOSIRE 构建、安装并提供支持的可用应用。

您下单

以一次性构建价格开始。我们在启动时与您共同确定范围。

我们构建与安装

ECOSIRE 在您的 Dynamics 365 Business Central 上构建、配置并安装。

上线 + 支持

约 2–4 周内上线，并提供上线后的支持期。

关于此产品

EDI Integration is a per-tenant AL extension that ECOSIRE builds, installs, and supports on your own Dynamics 365 Business Central environment. It turns inbound and outbound EDI traffic into native BC documents — partner purchase orders become sales orders, sales shipments emit ASNs, and posted sales invoices flow back to your customers — without spreadsheets, re-keying, or a disconnected middleware portal your accounts team can't see.

The extension ships as table and page extensions over Sales Order, Warehouse Shipment, and Sales Invoice, plus dedicated setup pages for trading-partner profiles. Each partner profile holds the standard (X12, EDIFACT, or partner-specific XML), the document versions they require, ISA/GS or UNB/UNH envelope identifiers, qualifiers, and per-segment mapping rules. A mapping engine translates between EDI segments and BC fields, with validation that rejects malformed documents before they touch your ledger.

Document movement runs on the BC Job Queue: scheduled entries poll your VAN, AS2 gateway, or SFTP endpoint, parse inbound files, and push outbound transmissions on posting events via AL event subscribers (OnAfterPostSalesDoc and shipment-release triggers). Inbound 850s create draft sales orders for review; 855/856/810 generation is automated. Functional 997 acknowledgments are matched, logged, and surfaced so you always know what a partner received.

Because it is built to order, we map to YOUR partners' exact specs and your BC localization. Delivery is honest: we scope, build, test in a sandbox, and deploy to production as a per-tenant extension. Permission sets isolate EDI configuration from posting rights, and an EDI log table gives auditors a complete transmission history. Optional Power Platform / Dataverse surfacing exposes EDI status to Power BI and Power Automate.

你得到什么

A per-tenant AL extension (.app) built to your trading partners' specs, installed on your Business Central production environment by ECOSIRE

Configured trading-partner profiles for the partners scoped at kickoff (standards, document versions, envelope IDs, qualifiers)

Document maps for the transaction sets in scope (typically 850, 855, 856, 810 / their EDIFACT equivalents)

Job Queue setup for inbound polling and outbound transmission against your VAN, AS2, or SFTP endpoint

Permission sets and role assignments separating EDI configuration from posting

Sandbox validation pass with sample partner documents before production go-live, plus a short admin handover session and written runbook

这是给谁的

Distribution Operations Manager

Runs order fulfillment for a distributor with retail or wholesale EDI partners. Needs inbound 850s to land as sales orders automatically and ASNs to go out on time to avoid chargebacks — without staff re-keying documents from a separate EDI portal.

Manufacturing IT / ERP Lead

Owns the Business Central environment and is accountable for keeping EDI inside the ERP rather than in disconnected middleware. Wants a maintainable AL extension, clear permission sets, and an audit log instead of a black-box translator nobody on the team understands.

AR / Billing Supervisor

Responsible for getting 810 invoices to customers in the format each one mandates. Wants posted BC invoices to translate and transmit automatically, with 997 acknowledgments confirming the partner actually received them.

EDI Integration 如何比较

标准	伊科西尔	定制建造	竞争对手
Maps to your trading partners' exact published specs	包含	包含	部分支持
Installed as a maintainable per-tenant AL extension	包含	包含	部分支持
Inbound 850 and outbound 855/856/810 automation out of the engagement	包含	部分支持	包含
Built, installed, and supported for you (no in-house AL team needed)	包含	不包括在内	部分支持
997 acknowledgment matching and logging	包含	部分支持	包含
Job Queue transport over your VAN / AS2 / SFTP	包含	包含	部分支持
Full EDI audit log and permission-set separation inside BC	包含	部分支持	部分支持
No per-document or per-partner SaaS metering fees	包含	包含	不包括在内

关于EDI Integration的常见问题

How long until the EDI Integration extension is live in our environment?

It is build-to-order, so timing depends on how many trading partners and transaction sets are in scope. A typical engagement covering one to three partners with the core 850/855/856/810 set runs about 3 to 5 weeks: a scoping and mapping-spec phase, AL development, sandbox testing with your partners' sample documents, then production deployment. More partners, exotic EDIFACT subsets, or AS2 onboarding can extend that. We confirm a concrete timeline in writing after the scoping call before any build starts.

Who handles support, partner spec changes, and Business Central updates after go-live?

ECOSIRE supports the extension we build. Because it is installed as a per-tenant extension on your tenant, we maintain it directly — adding new trading partners, adjusting maps when a partner changes their spec, and recompiling and revalidating against new Business Central major releases (BC keeps per-tenant extensions in scope during its update cycle, and we test on your sandbox before the production wave). Support is provided under an agreed plan; there is no AppSource auto-update channel because this is a custom extension, not a published marketplace app.

Is this a Microsoft AppSource app I can just download and install?

No. EDI mapping is partner-specific, so this is delivered as a custom per-tenant extension that ECOSIRE builds, installs, and configures on your environment. You will not find an instant download link — you get a solution mapped to your actual partners and your BC localization, deployed by us.

What transport and EDI standards do you support?

On standards: X12, EDIFACT, and partner-specific XML, with the document maps built to each partner's published spec. On transport: we integrate with your existing VAN, an AS2 gateway, or SFTP — the BC Job Queue polls and sends on schedule. If you do not yet have a VAN or AS2 provider, we can advise on options during scoping, but ECOSIRE does not resell connectivity.

Will it interfere with our existing posting routines and customizations?

It is additive. Outbound generation hooks into standard posting events via AL event subscribers rather than replacing your sales and shipment flows, and inbound documents create drafts for review rather than auto-posting. We test against your existing customizations in a sandbox before production, and permission sets keep EDI configuration separate from posting rights.