A per-tenant AL extension that adds segregation-of-duties rules, field-level change logging, maker-checker approvals on master data, and tamper-evident audit reporting to your Business Central environment — 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 adds segregation-of-duties rules, field-level change logging, maker-checker approvals on master data, and tamper-evident audit reporting to your Business Central environment — built, installed, and supported by ECOSIRE.
自分での設定は不要 — ECOSIRE が構築・インストール・サポートする実働アプリです。
一回限りの構築料金から始めます。キックオフで一緒に範囲を決めます。
ECOSIRE がお客様の Dynamics 365 Business Central 上で構築・設定・インストールします。
約2〜4週間で稼働し、リリース後のサポート期間が付きます。
Microsoft Dynamics 365 Business Central ships with a built-in Change Log and a generic approval workflow engine, but neither gives auditors what SOX, ISO 27001, or internal-controls reviews actually demand: enforced segregation of duties, a true two-person maker-checker gate on master-data edits, and audit evidence that can be proven untampered.
This is a build-to-order AL extension that closes that gap. ECOSIRE scopes your control matrix, builds the extension, and installs it as a per-tenant extension directly on your Business Central environment (cloud SaaS or on-prem) — there is no AppSource download. You receive the working app on your tenant plus the source.
Under the hood we use table and page extensions plus event subscribers (OnBeforeModify, OnBeforeDelete, OnAfterValidate) to intercept changes to the records you designate — Customer, Vendor, Item, Bank Account, Payment Journal lines, G/L Account, and your own custom tables. A flagged change is parked in a pending-changes table and routed to an authorized checker; only on approval is the record committed. Every field-level before/after value is written to an append-only log with the actor, timestamp, and a chained hash so any later edit to the log itself is detectable.
Segregation-of-duties conflict rules are evaluated against Business Central permission sets and user groups, surfacing toxic combinations (e.g., a user who can both create a vendor and release a payment). Periodic user access reviews are generated on a Job Queue schedule and exported via the BC REST/OData API to Power BI or Dataverse for your GRC tooling. Reports export to PDF/Excel for auditors.
Owns the SOX or ISO 27001 control matrix and needs enforced segregation of duties plus defensible audit evidence, not just a passive change log they have to reconcile by hand.
Wants a real two-person gate on bank-account, vendor, and payment-master changes to prevent fraud and error, with a clean approval trail for external auditors.
Maintains permission sets and user groups and needs visibility into toxic permission combinations plus scheduled, exportable access reviews without building it all in raw AL.
| 基準 | エコシエール | カスタムビルド | 競合他社 | オドゥー ネイティブ |
|---|---|---|---|---|
| Enforced two-person maker-checker gate on master-data edits | 付属 | 部分的なサポート | 部分的なサポート | |
| Field-level before/after change log with actor and timestamp | 付属 | 部分的なサポート | 付属 | |
| Tamper-evident audit log (chained hash, edit-detectable) | 付属 | 部分的なサポート | 含まれていない | |
| Segregation-of-duties conflict engine over permission sets | 付属 | 部分的なサポート | 部分的なサポート | |
| Scheduled user access reviews with sign-off via Job Queue | 付属 | 部分的なサポート | 部分的なサポート | |
| Scoped to your exact control matrix and custom tables | 付属 | 付属 | 含まれていない | |
| Installed and upgrade-maintained for you per BC release | 付属 | 含まれていない | 部分的なサポート | |
| REST/OData export to Power BI / Dataverse / GRC tooling | 付属 | 部分的なサポート | 部分的なサポート |
No. This is a build-to-order engagement. ECOSIRE scopes your control matrix and monitored tables, builds the AL extension, then installs it as a per-tenant extension directly on your Business Central environment. You also receive the source. There is no AppSource listing or self-service download involved.
A standard scope — change log, maker-checker on the common master tables, an SoD matrix, and access reviews — is usually delivered in about 2 to 4 weeks from sign-off and access. Wider scope (many custom tables, deep Dataverse/GRC integration) extends that, and we confirm the timeline in writing before starting.
Because it is a per-tenant extension we maintain for you, ECOSIRE handles compatibility with Business Central monthly and major releases, fixes, and reasonable rule changes under a support arrangement agreed at purchase. You are never left to re-test the extension against a BC upgrade alone.
It complements them. The native Change Log is passive and the native approval workflow is generic; this extension adds an enforced two-person maker-checker gate, a tamper-evident chained-hash log, and an SoD conflict engine — controls the core product does not provide. We can run alongside or supersede the native Change Log depending on your audit preference.
Yes. It is written in AL as a standard extension and installs on Business Central online (SaaS) as a per-tenant extension, or on a supported on-premises deployment. Some integration paths (Dataverse, certain APIs) differ slightly between cloud and on-prem, and we account for your deployment during scoping.
Yes. The event-subscriber and pending-changes design extends to any table, including custom tables added by other extensions, as long as we can subscribe to their modify events. Your custom-table scope is defined during the build.
A build-to-order AL extension that brings Adyen's 150+ global payment methods and unified settlement reconciliation into Business Central accounts receivable, complementing the first-party D365 Commerce Adyen connector.
A per-tenant AL extension that adds segregation-of-duties rules, field-level change logging, maker-checker approvals on master data, and tamper-evident audit reporting to your Business Central environment — built, installed, and supported by ECOSIRE.