イメージプレビューA build-to-order Business Central extension that exchanges EDI documents (850/856/810,
ORDERS/DESADV/INVOIC) with your trading partners, with full X12/EDIFACT/XML mapping, ASN and invoice automation, and 997 acknowledgment handling.
EDI Integrationとは？
A build-to-order Business Central extension that exchanges EDI documents (850/856/810, ORDERS/DESADV/INVOIC) with your trading partners, with full X12/EDIFACT/XML mapping, ASN and invoice automation, and 997 acknowledgment handling. 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
本番稼働 + サポート
約1週間（営業日ベース）で稼働し、本番稼働後2週間のサポートが付きます。納品したコードの不具合は無償で修正します。
この製品について
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 の比較方法
| 基準 | エコシエール | カスタムビルド | 競合他社 | Dynamics 365 Business Central 標準機能 |
|---|---|---|---|---|
| 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 one working week: 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.
関連モジュール
Easypaisa Payments Connector (Pakistan)
A custom AL extension that lets your Pakistani business collect Easypaisa mobile-wallet payments directly against Business Central sales invoices — with pay links, QR codes, automatic settlement, and webhook reconciliation. Built, installed, and supported by ECOSIRE on your tenant.
EBizCharge-style Card & ACH Processing for Business Central
A gateway-agnostic card and ACH processing layer built directly into Business Central — pay-links, bulk payment requests, EMV terminals, tokenized stored cards and Level 2/3 interchange optimization, delivered as a supported per-tenant AL extension.
E-Documents Connector (Peppol & UBL)
Send and receive compliant electronic documents over Peppol/UBL directly from Business Central, with outbound dispatch, inbound PO matching, and full per-document status tracking. Built, installed and supported by ECOSIRE as a per-tenant extension.
Egypt E-Invoice & E-Receipt (ETA) for Business Central
A per-tenant Business Central AL extension that generates, signs, and submits ETA-compliant e-invoices and e-receipts directly from your posted documents — built, installed, and supported by ECOSIRE on your environment.
EDI Integration
A build-to-order Business Central extension that exchanges EDI documents (850/856/810, ORDERS/DESADV/INVOIC) with your trading partners, with full X12/EDIFACT/XML mapping, ASN and invoice automation, and 997 acknowledgment handling.
- 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