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 $399.00 USD; request a quote for a scoped proposal.
示意预览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.
无需自行搭建——由 ECOSIRE 构建、安装并提供支持的可用应用。
以一次性构建价格开始。我们在启动时与您共同确定范围。
ECOSIRE 在您的 Dynamics 365 Business Central 上构建、配置并安装。
约 2–4 周内上线,并提供上线后的支持期。
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.
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.
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.
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.
| 标准 | 伊科西尔 | 定制建造 | 竞争对手 | 奥杜本机 |
|---|---|---|---|---|
| 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 | 包含 | 部分支持 | 部分支持 |
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.
Typical lead time is about 2 to 4 weeks 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.
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.
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.
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.
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.