Bank Reconciliation & Statement Intelligence for Business Central

Fonctionnalités clés

Bank statement import for CAMT.053 (ISO 20022), MT940, OFX, and fully configurable CSV column mappings, with per-bank profiles

Configurable, table-driven reconciliation rules engine matching on amount, date tolerance, reference, counterparty IBAN, and description tokens

AI-assisted fuzzy matching that resolves truncated or inconsistent bank narratives to the correct open ledger entry

Auto-matching of open Bank Account, Customer, and Vendor ledger entries within the Payment Reconciliation Journal

Auto-creation of journal lines for recurring bank fees, charges, and interest, posted to nominated G/L accounts

Built natively as AL table and page extensions on BC's Bank Account Reconciliation pages — no replacement of standard posting routines

Event subscribers on the reconciliation codeunits so matching logic stays upgrade-safe across BC monthly releases

Job Queue entry for scheduled, unattended statement import and pre-matching overnight

Match confidence scoring with a clear review queue so accountants approve low-confidence suggestions before posting

Dedicated permission set scoped to reconciliation roles, respecting BC user groups and entitlements

Optional REST/OData v4 endpoints to push statements in or pull reconciliation status into Power BI or Dataverse

Per-tenant deployment to your cloud SaaS or on-prem environment, with sandbox UAT before production promotion

Audit trail linking each matched statement line to its source ledger entry and the rule that matched it

Multi-bank-account and multi-currency aware, honoring BC currency exchange and realized-gain/loss accounts

Fait sur commande, clé en main

Aucune configuration à faire vous-même — une app fonctionnelle conçue, installée et prise en charge par ECOSIRE.

Vous commandez

Commencez par un prix de développement unique. Nous cadrons le projet avec vous au lancement.

Nous développons et installons

ECOSIRE la développe, la configure et l'installe sur votre Dynamics 365 Business Central.

Mise en ligne + assistance

Vous êtes en ligne en 2–4 semaines environ, avec une période d’assistance après le lancement.

À propos de ce produit

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.

Ce que vous obtenez

A custom AL per-tenant extension (.app) built to your bank formats, chart of accounts, and matching rules

Deployment to your Business Central sandbox for UAT, then promotion to your production environment

Per-bank import profiles configured for each CAMT.053 / MT940 / OFX / CSV format you supply

A configured reconciliation rules engine seeded with your common counterparties, fees, and tolerances

A scoped permission set and Job Queue entry set up for your reconciliation users and schedule

Source code and the AL project handed over, plus a deployment/runbook document

Admin and accountant walkthrough session covering import, review queue, and rule maintenance

Post-launch support window and a compatibility check against BC monthly platform updates

Pour qui c'est

Accountant / Controller

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.

Finance Manager / CFO

Needs faster, auditable month-end close with a clear trail from each statement line to its ledger entry, without abandoning native BC posting controls.

BC Implementation Partner / IT Lead

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.

Comment Bank Reconciliation & Statement Intelligence for Business Central se compare

Critère	ÉCOSIRE	Construction personnalisée	Concurrent
Multi-format statement import (CAMT.053, MT940, OFX, CSV)	Inclus	Prise en charge partielle	Prise en charge partielle
Configurable rules engine for auto-matching	Inclus	Prise en charge partielle	Prise en charge partielle
AI / fuzzy matching for poor bank descriptions	Inclus	Non inclus	Prise en charge partielle
Auto-creation of journal lines for fees and charges	Inclus	Prise en charge partielle	Prise en charge partielle
Built to your chart of accounts and bank profiles	Inclus	Inclus	Non inclus
Installed and supported on your tenant by the vendor	Inclus	Prise en charge partielle	Non inclus
Upgrade-safe via event subscribers / table extensions	Inclus	Prise en charge partielle	Inclus
No per-user recurring subscription fee	Inclus	Inclus	Non inclus

Foire aux questions sur Bank Reconciliation & Statement Intelligence for Business Central

Is this a Microsoft AppSource app I can install instantly?

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.

How long does delivery take?

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.

What ongoing support and updates do I get after go-live?

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.

Which bank statement formats are supported?

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.

Will it interfere with our existing Business Central posting and permissions?

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.