No. This is a build-to-order extension. ECOSIRE engineers it in AL against your real Business Central configuration — your chart of accounts, customer ledger structure, payment tolerances, and remittance formats — then installs it as a per-tenant extension in your environment. There is no public AppSource listing to click and install; you get a solution fitted to your data and our hands-on deployment.

A typical build runs about 3 to 6 weeks from kickoff to production go-live, depending on the number of distinct remittance and lockbox formats, your bank-feed setup, and whether you want the optional Dataverse/Power Platform exceptions app. We start in a Business Central sandbox, validate against your real open-invoice population in a pilot, then promote to production. We confirm a firm timeline after a short scoping call.

Every build includes a post-launch support window for bug fixes and match-rate tuning. Because it's a per-tenant extension built on event subscribers (not base-app modifications), it stays upgrade-safe across BC release waves — and we offer an optional retainer to retest and recompile against each major BC update, add new remittance formats, and keep the learning loop tuned.

You own it. We hand over the AL source for the per-tenant extension. The matching and learning logic runs inside your Business Central environment (with optional Azure middleware you control), so there is no opaque SaaS you can't audit. If you ever part ways with ECOSIRE, the extension and its source remain yours.

Every correction an analyst makes to a proposed match is captured as labeled training data, so the engine learns your customers' payment behaviors and remittance quirks and lifts auto-match rates over time. Data stays within your tenant and infrastructure; the parsing and matching are scoped to least-privilege service accounts and permission sets, with a full audit trail from each posted application back to its source remittance.