The first-party connector handles payment acceptance at the storefront and POS — authorizing and capturing the transaction. It does not reconcile Adyen's batched settlement payouts back to the open invoices in your Business Central general ledger. This extension lives entirely in BC AR: it imports Adyen settlement reports, auto-matches each line to Customer Ledger Entries, and posts fees, FX, refunds, and chargebacks. It complements the Commerce connector rather than replacing it.

No. This is a build-to-order per-tenant extension. ECOSIRE scopes your Adyen configuration, currencies, and chart-of-accounts mapping, then builds the AL extension and installs it directly on your Business Central tenant. There is no instant AppSource download — the work is custom-fit to your environment and delivered with a defined lead time.

After a scoping call to confirm your Adyen merchant accounts, currencies, acquirers, and AR posting setup, a standard build is typically delivered and installed within about 2 to 4 weeks. Multi-entity, multi-currency, or heavy Dataverse/Power BI integration scope can extend that, and we confirm the timeline in writing before work begins.

The build comes with a defined support agreement. Because the extension uses event subscribers on the standard reconciliation engine and never modifies the base app, it is built to survive Business Central upgrades — but we test it against each major BC release wave and ship a compatibility update if Microsoft changes a relevant interface. Bug fixes, Adyen API changes, and configuration adjustments are handled under the support terms agreed at purchase.

Yes. The extension exposes settlement and reconciliation records through the Business Central OData/REST API. Where you run Power Platform, we can surface that data into Dataverse so your existing Power BI dashboards report on payment-method mix, settlement timing, fees, and FX without manual exports.