Approval workflow

An approval workflow is a structured routing of a transactional document — purchase order, sales quote, vendor invoice, journal, expense report — through one or more approvers before it can post or progress. Dynamics 365 implements approval workflows three ways: Business Central's built-in workflow engine (template-driven, with approval limits and hierarchical routing), Finance & Operations' workflow engine (a graphical designer with parallel branches, escalations, and automated tasks), and Power Automate approvals (cross-system orchestration, the modern choice for workflows that reach outside one system). Common patterns: purchase orders over a threshold require manager approval; customer credit overrides need sales-leader sign-off; vendor invoices over a limit need controller approval.

In practice, the choice between the three isn't about which is "better" so much as where the workflow needs to reach. Both BC's and F&O's built-in engines are the right tool when the entire approval stays inside that one system — they're aware of posting groups, approval limits, and document status in a way a generic tool isn't, so a rejected purchase order simply reverts to Open without any extra plumbing. Power Automate earns its place the moment the approval needs to leave the ERP — routing to someone without a Dynamics 365 licence via Teams or email, pulling in a signature from an external e-signature tool, or chaining a decision into a separate system entirely. Mixing the two inside one process (say, BC's built-in workflow calling out to Power Automate for the email notification) is also common and usually the pragmatic answer.

Where confusion shows up: an approval workflow is often assumed to be a hard control the moment it's turned on, but every engine still depends on someone actually configuring the threshold, the hierarchy, and the escalation correctly — a workflow with the wrong approval limit or a hierarchy that's gone stale after a reorg approves things it shouldn't just as readily as it blocks things it should. Reviewing approval workflows against the current org chart and current dollar thresholds is a recurring audit task, not a one-time setup step.