Native Business Central approvals are limited: a fixed approver hierarchy, email notifications that bounce you back into the web client, and little room for conditional logic without code. This ECOSIRE extension replaces that with a real workflow engine — and lets people approve where they already work.

What it does. We build a per-tenant AL extension that adds conditional, multi-level approval matrices on top of the standard Approval Entry and Workflow tables. Routing is driven by document type, amount thresholds, dimensions, vendor/customer, or any field you choose — implemented with table extensions, page extensions, and event subscribers on the standard approval codeunits (so we extend BC, never fork it). When a document enters approval, the engine calls out through an Azure-hosted relay to post an adaptive card into the approver's Microsoft Teams chat and Outlook inbox. They approve or reject inline; the response flows back via the BC REST/OData v4 API and updates the approval entry — no need to open the web client.

Beyond native. Substitute / out-of-office routing reassigns pending approvals automatically. Mobile push lands through the Teams app. Every action — request, approve, reject, delegate, escalate — is written to a tamper-evident audit log with user, timestamp, and comment. A Job Queue entry handles escalations and reminders on a schedule you set.

How we deliver. This is build-to-order. After purchase, ECOSIRE scopes your approval rules, builds the extension, installs it as a per-tenant extension (or via your Power Platform / Dataverse environment where Teams integration warrants it), assigns the required permission sets, and validates end-to-end on your tenant — sandbox first, then production. You get the source, the documentation, and ongoing support. No AppSource listing, no instant download — a working extension on your environment.