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 brings Adyen's 150+ global payment methods and unified settlement reconciliation into Business Central accounts receivable, complementing the first-party D365 Commerce Adyen connector.
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.