Bank Statement Import & E-Reconciliation

核心功能

Statement import engine for CSV, XML, MT940 and ISO 20022 CAMT.053 files into Bank Account Reconciliation lines

Configurable auto-matching rules engine matching statement lines against bank account ledger entries by amount, date window, document number and text patterns

Confidence-scored suggested matches for near-misses, applied with a single confirm action

Exception queue surfacing unmatched lines with drill-down to candidate ledger entries

Multi-bank format library so each bank's export layout maps to a reusable named template

Payment-to-invoice reconciliation that applies statement lines to open customer and vendor ledger entries and posts the application

Setup page for rules, tolerances and field mappings — onboard a new bank without a code change

Job Queue entry for scheduled unattended imports from a watched folder or SFTP drop

Dedicated permission set scoping who can import, match and post reconciliations

Built as table and page extensions plus event subscribers — base app objects stay untouched and upgrade-safe

Audit trail linking each matched statement line to the resulting bank ledger entry and applied invoice

Optional OData/REST API exposure of reconciliation status for Power BI dashboards and Power Automate flows

Tolerance handling for rounding, bank fees and FX differences with auto-posting of fee lines to a configured G/L account

Per-tenant extension deployment validated against your real statement files before go-live

按需定制，全程代劳

无需自行搭建——由 ECOSIRE 构建、安装并提供支持的可用应用。

您下单

以一次性构建价格开始。我们在启动时与您共同确定范围。

我们构建与安装

ECOSIRE 在您的 Dynamics 365 Business Central 上构建、配置并安装。

上线 + 支持

约 2–4 周内上线，并提供上线后的支持期。

关于此产品

Stop hand-keying your bank reconciliation in Business Central

Business Central ships with a Bank Account Reconciliation page and the AMC Banking 365 connector, but most teams still fight statement formats their bank actually exports, brittle matching, and a payment-application step that lives in a separate window. Bank Statement Import & E-Reconciliation is a build-to-order AL extension that ECOSIRE designs, builds, installs, and supports directly on your Business Central environment to close that gap.

It is delivered as a per-tenant extension (not a one-click AppSource download): we scope your banks and statement formats, develop the extension in AL using table and page extensions plus event subscribers, deploy it to your tenant, validate it against your real statements, and support it afterwards. You own a clean, upgrade-safe extension — no customized base-app objects.

What it does

The extension adds an import engine that parses CSV, XML, MT940 and ISO 20022 CAMT.053 files into Bank Account Reconciliation lines, then runs a configurable matching-rules engine against your bank account ledger entries. Confident matches are applied automatically; near-matches surface as suggested matches; everything else lands in an exception queue an accountant can clear in a few clicks. For incoming and outgoing payments it reconciles statement lines to open customer and vendor invoices, posting the application so your aged balances stay correct.

Rules, bank-format mappings, and tolerances are configurable on a setup page — no code change to onboard a new bank. Imports can run on demand or be scheduled through the BC Job Queue, and a dedicated permission set keeps access scoped. Where useful, the same reconciliation data is exposed via the BC OData/REST API for Power BI or Power Automate.

Honest expectation: this is bespoke software with a delivery lead time, built to your formats and signed off with you before go-live.

你得到什么

Custom AL per-tenant extension package (.app) built to your bank formats and installed on your Business Central environment

Bank format templates configured and tested for each bank/account in scope (CSV/XML/MT940/CAMT.053)

Configured matching-rules set, tolerances and G/L mappings tuned to your chart of accounts

Dedicated permission set and Job Queue entry for scheduled imports

Source code handover and AppSource-ready / per-tenant deployment artifacts as agreed

Admin and accountant user guide plus a recorded walkthrough of the import-and-reconcile flow

Post-delivery support and update window covering BC version compatibility and bank-format changes

这是给谁的

Accountant / AP-AR Specialist

Reconciles bank accounts daily or weekly and wants statement lines to auto-match against ledger entries and open invoices, with only true exceptions needing manual attention.

Finance Manager / Controller

Owns month-end close and cares that bank reconciliation is fast, auditable, and ties statement lines to posted entries without spreadsheet workarounds.

Business Central Administrator / Partner

Manages the BC tenant and needs a clean, upgrade-safe per-tenant extension with a scoped permission set and Job Queue automation rather than modified base-app objects.

Bank Statement Import & E-Reconciliation 如何比较

标准	伊科西尔	定制建造	竞争对手
Imports CSV, XML, MT940 and CAMT.053 without manual reformatting	包含	部分支持	部分支持
Configurable matching-rules engine (amount, date window, document no., text patterns)	包含	部分支持	部分支持
Suggested-match plus exception queue workflow	包含	部分支持	包含
Payment-to-invoice reconciliation that posts the application	包含	部分支持	部分支持
Tailored to your exact banks and chart of accounts	包含	包含	不包括在内
Built as upgrade-safe extensions and event subscribers (no base-app changes)	包含	部分支持	包含
Scheduled unattended import via Job Queue	包含	部分支持	部分支持
Installed and supported by the builder on your tenant	包含	不包括在内	不包括在内
OData/REST exposure for Power BI and Power Automate	包含	部分支持	部分支持

关于Bank Statement Import & E-Reconciliation的常见问题

Is this an instant download from Microsoft AppSource?

No. This is build-to-order. ECOSIRE designs and develops the AL extension to your specific banks and statement formats, then installs it on your Business Central environment as a per-tenant extension. You are buying a custom build with installation and support, not a self-service AppSource listing.

What is the delivery lead time?

Most builds are delivered within roughly 2 to 4 weeks of confirming scope and receiving sample statement files for each bank in scope. Timeline depends on how many bank formats you need, whether payment-to-invoice posting and Job Queue automation are included, and your environment's availability for validation and sign-off. We confirm a firm date during scoping.

Which statement formats and banks are supported?

The engine handles CSV, XML, MT940 and ISO 20022 CAMT.053 out of the box. Each bank's specific layout is mapped to a reusable named template during the build, so onboarding an additional bank later is a configuration task, not new development, as long as it exports one of those formats.

How does it differ from Business Central's native bank reconciliation?

BC core gives you the Bank Account Reconciliation page and the AMC Banking connector, but format coverage, matching flexibility, the exception queue, and one-screen payment-to-invoice application are limited. This extension adds a configurable rules engine, a multi-format import library, a confidence-scored suggested-match and exception workflow, and posts invoice applications — built as extensions and event subscribers so the base app stays upgrade-safe.

What ongoing support and updates are included?

Every build includes a post-delivery support window. We keep the extension compatible across Business Central monthly and major updates, adjust bank-format templates when a bank changes its export, and fix any defects. Extended support, new bank onboarding, and feature additions are available as follow-on work under a support agreement.

Will it modify my base application or affect upgrades?

No base-app objects are modified. The solution is delivered as table extensions, page extensions and event subscribers in a dedicated per-tenant extension, with its own permission set. That keeps your tenant clean and means Microsoft's BC upgrades apply normally; we validate the extension against new BC versions as part of the support window.