A build-to-order AL extension that imports bank statements (CAMT.053, MT940, CSV, OFX) into Business Central and auto-matches open ledger entries with a configurable rules engine and AI-assisted fuzzy matching — built, installed per-tenant, 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 build-to-order AL extension that imports bank statements (CAMT.053, MT940, CSV, OFX) into Business Central and auto-matches open ledger entries with a configurable rules engine and AI-assisted fuzzy matching — built, installed per-tenant, and supported by ECOSIRE.
无需自行搭建——由 ECOSIRE 构建、安装并提供支持的可用应用。
以一次性构建价格开始。我们在启动时与您共同确定范围。
ECOSIRE 在您的 Dynamics 365 Business Central 上构建、配置并安装。
约 2–4 周内上线,并提供上线后的支持期。
Bank Reconciliation & Statement Intelligence is a custom Microsoft Dynamics 365 Business Central extension that takes the manual grind out of monthly bank reconciliation. It is not an instant AppSource download — ECOSIRE builds it in AL to fit your chart of accounts, bank formats, and matching conventions, then installs it as a per-tenant extension directly on your Business Central environment (cloud SaaS or on-prem) and supports it afterward.
The extension layers on top of BC's native Bank Account Reconciliation and Payment Reconciliation Journal rather than replacing them. It adds a statement import pipeline supporting CAMT.053 (ISO 20022), MT940, OFX, and configurable CSV mappings, so your accountant stops re-keying lines from PDFs and online-banking exports.
At its core is a configurable reconciliation rules engine — table-driven match rules on amount, date tolerance, reference, counterparty IBAN, and description tokens — combined with AI-assisted fuzzy matching for the real-world case where bank narratives are truncated or inconsistent. Matched statement lines are applied against open Bank Account Ledger and Customer/Vendor entries; unmatched fees, charges, and interest can auto-generate journal lines posted to the G/L accounts you nominate.
Delivery uses BC-native plumbing: AL table and page extensions, event subscribers on the reconciliation codeunits, a job queue entry for scheduled imports, and a dedicated permission set. Optional hooks to the BC REST/OData v4 API and Power Platform / Dataverse let you pull statements from a connector or surface match status in Power BI.
Pricing is a one-time build fee. ECOSIRE scopes your formats and rules, develops, deploys to a sandbox for UAT, promotes to production, and provides post-launch support and BC monthly-update compatibility checks.
Currently spends hours each month re-keying bank lines and hunting for matches; wants imported statements and AI-assisted matching to cut reconciliation to a review-and-approve task.
Needs faster, auditable month-end close with a clear trail from each statement line to its ledger entry, without abandoning native BC posting controls.
Wants a clean, upgrade-safe per-tenant extension built on event subscribers and table/page extensions that won't break on BC's monthly releases and respects existing permission sets.
| 标准 | 伊科西尔 | 定制建造 | 竞争对手 | 奥杜本机 |
|---|---|---|---|---|
| Multi-format statement import (CAMT.053, MT940, OFX, CSV) | 包含 | 部分支持 | 部分支持 | |
| Configurable rules engine for auto-matching | 包含 | 部分支持 | 部分支持 | |
| AI / fuzzy matching for poor bank descriptions | 包含 | 不包括在内 | 部分支持 | |
| Auto-creation of journal lines for fees and charges | 包含 | 部分支持 | 部分支持 | |
| Built to your chart of accounts and bank profiles | 包含 | 包含 | 不包括在内 | |
| Installed and supported on your tenant by the vendor | 包含 | 部分支持 | 不包括在内 | |
| Upgrade-safe via event subscribers / table extensions | 包含 | 部分支持 | 包含 | |
| No per-user recurring subscription fee | 包含 | 包含 | 不包括在内 |
No. This is a build-to-order extension. ECOSIRE develops it in AL to fit your bank formats, chart of accounts, and matching rules, then installs it as a per-tenant extension on your Business Central environment. There is no instant AppSource download — every deployment is scoped, built, and validated for your tenant.
Typical lead time is about 3 to 5 weeks from a confirmed scope, depending on how many bank formats and how complex your matching rules are. The flow is: discovery and format collection, AL development, sandbox deployment for your UAT, then promotion to production. We confirm a firm timeline after the scoping call.
The build includes a post-launch support window for fixes and questions, plus a compatibility check against Business Central's monthly platform updates so the extension keeps working across releases. Because it is built on event subscribers and table/page extensions rather than overriding standard objects, upgrades are low-risk. Longer-term support and enhancement retainers are available.
Out of the box the import pipeline handles CAMT.053 (ISO 20022 XML), MT940, OFX, and configurable CSV. For CSV and bank-specific dialects we build a per-bank profile mapping your columns and date/amount conventions. If your bank exports a format not listed, share a sample during scoping and we will assess adding it.
No. It builds on BC's native Bank Account Reconciliation and Payment Reconciliation Journal and uses event subscribers, so standard posting routines are untouched. Access is governed by a dedicated permission set that fits within your existing user groups and entitlements, and every matched line keeps an audit trail to its source ledger entry.
A build-to-order AL extension that imports bank statements (CAMT.053, MT940, CSV, OFX) into Business Central and auto-matches open ledger entries with a configurable rules engine and AI-assisted fuzzy matching — built, installed per-tenant, and supported by ECOSIRE.