示意预览A per-tenant Business Central extension that receives structured e-invoices (Peppol/UBL/Factur-X/ZUGFeRD),
auto-creates purchase invoices and orders, maps vendors and items with learning, matches against POs, and routes exceptions — built, installed and supported by ECOSIRE.
什么是 E-Document Inbound Automation for Business Central？
A per-tenant Business Central extension that receives structured e-invoices (Peppol/UBL/Factur-X/ZUGFeRD), auto-creates purchase invoices and orders, maps vendors and items with learning, matches against POs, and routes exceptions — built, installed and supported by ECOSIRE. 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
上线 + 支持
约一个工作周内上线，并包含两周上线支持。我们交付的代码中的缺陷免费修复。
关于此产品
E-Document Inbound Automation for Business Central is a custom AL extension we build, install and support on your own Business Central tenant. It is not an instant AppSource download — it is engineered to your vendor mix, document formats and approval rules, then deployed as a per-tenant extension.
The extension builds on Business Central's native E-Document framework. We register an inbound E-Document Service and AL event subscribers that pick up structured invoices arriving by Peppol Access Point, OData/REST upload, SMTP-captured attachment, or an incoming-document import. Payloads in UBL 2.1, Peppol BIS Billing 3.0, Factur-X and ZUGFeRD are parsed and validated, then drafted into Purchase Invoice or Purchase Order documents via the standard purchasing tables and pages.
A learning vendor and item mapping layer resolves the supplier's GLN/VAT and line identifiers to your Vendor and Item (or G/L account) records, remembering manual corrections so accuracy improves over time. Three-way PO matching compares received quantities and prices against open purchase orders and receipts; clean documents flow straight through, while mismatches, missing mappings and tolerance breaches are routed to an exception queue for AP review. Duplicate detection keys on vendor, document number, amount and hash to stop double entry.
Background processing runs through the BC Job Queue; dedicated permission sets scope access; and an optional Dataverse / Power Platform hook lets you trigger Power Automate approvals. We deliver the source as a signed extension, hand over documentation, and provide post-launch support and BC update compatibility under a maintenance agreement.
你得到什么
- Signed per-tenant Business Central AL extension (.app) installed on your sandbox and production environments
- Configured inbound E-Document Service plus channel setup (Peppol Access Point / REST / SMTP / incoming document) for your formats
- Vendor and item mapping tables pre-seeded from your existing master data with the learning layer enabled
- PO matching rules and tolerance configuration tuned to your purchasing policy
- Permission sets and Job Queue entries for scheduled background processing
- Administrator and AP-user documentation plus a recorded handover walkthrough and post-launch support window
这是给谁的
AP Manager scaling e-invoice volume
Owns accounts payable and is seeing structured Peppol/UBL invoices grow past what manual keying can handle. Wants straight-through processing for clean documents and a clear exception queue for the rest.
Business Central Administrator
Responsible for the BC tenant, extensions and integrations. Needs a clean per-tenant AL extension that uses event subscribers and permission sets rather than modifying core objects, and that survives BC version updates.
Finance Controller / Compliance Lead
Accountable for e-invoicing mandates, audit trails and duplicate-payment prevention. Wants validated UBL/Factur-X/ZUGFeRD ingestion, traceable matching, and Power Platform approval visibility.
E-Document Inbound Automation for Business Central 如何比较
| 标准 | 伊科西尔 | 定制建造 | 竞争对手 | Dynamics 365 Business Central 原生 |
|---|---|---|---|---|
| Inbound UBL/Peppol/Factur-X/ZUGFeRD parsing | 包含 | 部分支持 | 包含 | 部分支持 |
| Auto-creation of purchase invoices/orders from e-documents | 包含 | 部分支持 | 部分支持 | 不包括在内 |
| Learning vendor and item mapping | 包含 | 部分支持 | 部分支持 | 不包括在内 |
| Three-way PO matching with exception routing | 包含 | 部分支持 | 部分支持 | 不包括在内 |
| Duplicate detection (hash + vendor/doc/amount) | 包含 | 部分支持 | 部分支持 | 不包括在内 |
| Built, installed and supported on your tenant by the vendor | 包含 | 不包括在内 | 不包括在内 | 不包括在内 |
| Tailored to your exact vendor mix and approval rules | 包含 | 包含 | 不包括在内 | 不包括在内 |
| Optional Dataverse / Power Platform approval integration | 包含 | 部分支持 | 部分支持 | 部分支持 |
关于E-Document Inbound Automation for Business Central的常见问题
Is this a download from Microsoft AppSource?
No. This is a build-to-order extension. We engineer it to your vendor mix, e-invoice formats and approval rules, then install it as a signed per-tenant extension on your own Business Central environment. There is no instant AppSource listing or self-serve download.
How long does delivery take after I order?
Typical lead time is about one working week from kickoff, depending on the number of inbound channels, formats and the complexity of your PO matching rules. We begin with a short scoping call, deploy first to your sandbox for validation, then promote to production once you sign off.
What inbound formats and channels are supported?
UBL 2.1, Peppol BIS Billing 3.0, Factur-X and ZUGFeRD out of the gate, arriving via a Peppol Access Point, an OData/REST upload endpoint, SMTP attachment capture, or manual incoming-document import. Additional national UBL variants can be added during scoping.
How does PO matching and exception handling work?
For each inbound document the extension performs three-way matching of quantity, unit price and amount against open purchase orders and posted receipts within configurable tolerances. Clean documents are created straight through; anything that fails matching, validation or mapping is routed to an exception queue for an AP user to resolve.
What about ongoing support and Business Central updates?
Under a maintenance agreement we provide post-launch support, bug fixes, and compatibility testing against Business Central major and minor updates. Because it is built on event subscribers and the native E-Document framework rather than core modifications, version upgrades are low-risk and we validate each one before you apply it.
相关模块
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.
ECOSIRE Retail POS for Business Central
A fast, touch-friendly in-browser POS embedded directly in Business Central so retailers ring up sales, manage tills and sync inventory in real time — built and installed by ECOSIRE as a per-tenant AL extension, no separate till system.
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.
Egypt ETA e-Invoice & Payment Bridge for Business Central
A per-tenant Business Central AL extension that captures online payments and submits compliant ETA e-invoices and e-receipts in one workflow — built, installed and supported by ECOSIRE for Egyptian merchants under the e-invoicing mandate.
E-Document Inbound Automation for Business Central
A per-tenant Business Central extension that receives structured e-invoices (Peppol/UBL/Factur-X/ZUGFeRD), auto-creates purchase invoices and orders, maps vendors and items with learning, matches against POs, and routes exceptions — built, installed and supported by ECOSIRE.
- Inbound parsing of UBL 2.1, Peppol BIS Billing 3.0, Factur-X and ZUGFeRD structured e-invoices via a registered BC E-Document Service
- Auto-creation of Purchase Invoice and Purchase Order documents on the standard BC purchasing tables and pages
- Learning vendor mapping that resolves supplier GLN/VAT to your Vendor records and remembers manual corrections
- Learning item/line mapping to Item No. or G/L account, with unit-of-measure and supplier-item cross references