Bank Reconciliation & Open Banking Feeds for Business Central

This is build-to-order, not an instant AppSource install. After a short scoping call we typically deliver in about 3 to 6 weeks depending on how many banks, currencies and matching rules are in scope and your aggregator's onboarding timeline. ECOSIRE builds the AL extension, tests it in your sandbox, then installs it as a per-tenant extension on your production Business Central environment. The price covers the standard build; complex multi-entity or unusual bank-API requirements are quoted after scoping.

ECOSIRE does. The extension is built on event subscribers with no base-application modification, so it is resilient to Microsoft's monthly releases — but we still validate it against each major update and against the twice-yearly wave releases as part of the post-go-live support window. Support covers feed connectivity, matching-rule tuning, exception troubleshooting and compatibility fixes. We agree the support term and any extension at scoping; we do not silently auto-renew.

Any bank reachable through your chosen open-banking aggregator (an account-information service provider) or that exposes a direct statement API. Where a live feed isn't available we can still automate scheduled import of CAMT.053, MT940 or CSV files into the same reconciliation flow. We confirm your specific banks during scoping before committing to the feed approach.

The engine scores each statement line against open Bank Account Ledger Entries and customer/vendor entries using amount, date tolerance, payment reference and counterparty patterns, plus your rule-based categories for recurring items. High-confidence matches can auto-post to the reconciliation and generate payment journal lines; anything below your confidence threshold is queued on the worksheet for a human to approve. You set the threshold — nothing posts automatically unless you allow it.

Yes, optionally. We can sync reconciliation status and exception data to Dataverse so it surfaces in Power BI dashboards, or trigger a Power Automate approval flow when an exception needs sign-off. This is scoped as an add-on because it depends on your Power Platform licensing and environment, and it's built on the supported BC REST/OData and Dataverse integration rather than any unsupported hack.

Feed tokens and credentials are stored in Business Central isolated storage, never hard-coded into the extension or exposed in pages. Access is governed by dedicated permission sets so treasury, AP/AR and auditors each get least-privilege rights, and every auto-posted match is fully traceable to its source feed and match decision for audit. We never store statement data outside your Business Central / Dataverse environment.