A per-tenant AL extension that aggregates bank transactions via Plaid/Yodlee/open-banking APIs and auto-matches them to BC ledger entries for continuous reconciliation. Built, installed, and supported by ECOSIRE. Built to order by ECOSIRE for Dynamics 365 BC (build-to-order) — indicative price from $499.00 USD; request a quote for a scoped proposal.
示意预览A per-tenant AL extension that aggregates bank transactions via Plaid/Yodlee/open-banking APIs and auto-matches them to BC ledger entries for continuous reconciliation. Built, installed, and supported by ECOSIRE.
无需自行搭建——由 ECOSIRE 构建、安装并提供支持的可用应用。
以一次性构建价格开始。我们在启动时与您共同确定范围。
ECOSIRE 在您的 Dynamics 365 Business Central 上构建、配置并安装。
约 2–4 周内上线,并提供上线后的支持期。
Business Central ships with a basic bank feed (the Envestnet Yodlee linkage and AMC Banking 365), but coverage is regional, the import is largely manual, and matching logic is shallow. This build-to-order extension closes those gaps with a connector tailored to your banks, your posting groups, and your matching rules.
ECOSIRE builds, installs, and supports a per-tenant AL extension on your Business Central environment (Online or on-prem). It registers an OAuth/token-based integration with Plaid, Yodlee, or a direct open-banking (PSD2/Open Banking UK) API, then runs a Job Queue Entry that pulls cleared and pending transactions on a daily (or hourly) cadence into the standard Bank Acc. Reconciliation and Bank Account Ledger flow.
Incoming lines are normalized and passed through a configurable matching engine — built with event subscribers on the reconciliation tables and table/page extensions that surface match confidence, counterparty, and the raw payload. Auto-match runs against open Bank Account Ledger Entries, customer/vendor payments, and amount+date+reference heuristics; unmatched lines are queued for one-click review.
Credentials never sit in plain text: access and refresh tokens are held in an Isolated Storage / Azure Key Vault token vault, scoped per company. The extension respects multi-company, multi-bank, and multi-currency setups, applying the correct exchange-rate and currency code per Bank Account Card.
Because it is delivered as a per-tenant extension (not a public AppSource listing), ECOSIRE can hard-wire your aggregator choice, bank-specific field mappings, permission sets, and Power Platform / Dataverse hooks. You get the source-aligned extension installed on your tenant, a permission set, the Job Queue configured, and a documented runbook. No instant download — an honest, scoped delivery.
Wants reconciliation closed daily instead of at month-end, with a clear audit trail of how each bank line was matched to a ledger entry.
Spends hours importing CSV statements and matching by hand; needs transactions to arrive automatically and pre-matched, leaving only exceptions to review.
Needs a secure, supportable integration — proper permission sets, vaulted tokens, Job Queue monitoring, and telemetry — rather than ad-hoc scripts or a generic AppSource app that doesn't fit their banks.
| 标准 | 伊科西尔 | 定制建造 | 竞争对手 | 奥杜本机 |
|---|---|---|---|---|
| Automatic daily bank-feed pull (no manual import) | 包含 | 部分支持 | 部分支持 | |
| Plaid / Yodlee / direct open-banking aggregator of your choice | 包含 | 部分支持 | 不包括在内 | |
| Auto-match tuned to your posting groups and matching rules | 包含 | 部分支持 | 不包括在内 | |
| Multi-bank, multi-company, multi-currency handling | 包含 | 部分支持 | 部分支持 | |
| Vaulted OAuth tokens (Isolated Storage / Key Vault) + dedicated permission set | 包含 | 部分支持 | 部分支持 | |
| Built, installed, and supported on your tenant by the vendor | 包含 | 不包括在内 | 不包括在内 | |
| No per-user or recurring SaaS subscription fee | 包含 | 包含 | 不包括在内 |
Typical delivery is 2 to 4 weeks from kickoff, depending on the number of banks, your aggregator choice, and how custom your matching rules are. We need your Business Central version and access (a sandbox to build against), the list of bank accounts to connect, and an aggregator account (Plaid/Yodlee) or open-banking credentials. We build in a sandbox, demo it, then install the per-tenant extension on production.
No. This is a build-to-order, per-tenant AL extension. ECOSIRE builds it for your specific banks and posting setup, then installs it directly on your Business Central tenant. That is deliberate — it lets us hard-wire your aggregator, field mappings, permission sets, and matching logic instead of shipping a one-size-fits-all listing.
The one-time build price includes the install and a handover. We offer an optional support and maintenance retainer covering BC version-upgrade compatibility (AL recompiles against new runtimes), aggregator API changes, PSD2 re-consent handling, and adding new bank accounts or matching rules over time. You own the deployed extension; we keep it running.
Your banking login is never stored by the extension — it lives with the aggregator (Plaid/Yodlee) under their security model. The OAuth access and refresh tokens the extension uses are held in Business Central Isolated Storage or Azure Key Vault, scoped per company, never in plain text fields, and reachable only through the dedicated permission set.
Yes. The connector is multi-bank, multi-company, and multi-currency aware. Each Bank Account Card maps to its own feed and currency code, transactions are converted using the correct exchange rate, and duplicate detection keeps re-runs idempotent so nothing double-posts across companies.
A per-tenant AL extension that aggregates bank transactions via Plaid/Yodlee/open-banking APIs and auto-matches them to BC ledger entries for continuous reconciliation. Built, installed, and supported by ECOSIRE.