Dooap Blog

How Do You Set Up Invoice Approval Workflows in Dynamics 365 Finance?

Written by Sam Bush | November 2026

Best-in-class accounts payable teams move an invoice to payment-ready status in 3.1 days and hold their exception rate to 9%, against 22% for everyone else, according to Ardent Partners’ AP Metrics that Matter in 2025. Approval routing accounts for a large share of that gap. Capture and matching can finish in minutes, but an invoice that sits for a week in a department head’s queue still pays late, and better OCR does nothing about it.

In Dynamics 365 Finance, you set up invoice approval workflows under Accounts payable > Setup > Accounts payable workflows, where you build a vendor invoice workflow from approval steps, conditions, time limits and escalation paths. The configuration itself is manageable. The harder work sits on either side of it: deciding who should approve what before you open the editor, and making sure approvers can act quickly once invoices start arriving.

What the vendor invoice workflow can do

The workflow editor in D365 Finance does more than its reputation suggests. Each approval step has an assignment type, and Microsoft offers four: a participant role or group, a position in an organizational hierarchy, a user already involved in the workflow, or named individuals, as the Microsoft Learn guide to approval steps lays out. Hierarchy assignment is the one finance teams underuse most, because it starts from the person tied to the spend and climbs until it reaches someone with enough signing authority, without anyone maintaining a list of names.

Conditions decide whether a step runs at all. You can require a step every time or only when a condition holds, such as an invoice total above a set threshold, and the editor’s Test button checks your conditions against a real record before you activate anything. When a step goes to several people, the completion policy settles the outcome: the first response, a majority, a percentage, or every approver. Most AP teams need the first option for routine spend and reserve the last for a handful of high-value or sensitive categories. We cover the rest of the standard toolset in What Does D365 Finance Actually Give You for Accounts Payable?

Decide the approval matrix before you build it

Teams that start in the editor end up encoding whatever the old email chain did. A better starting point is a one-page approval matrix that says which invoices need approval, who approves them, and at what amount approval moves up a level. Write it in business terms first: cost center owners approve spend against their budgets, plant managers approve operating costs for their sites, and anything above a defined limit goes to a controller or the CFO. That document becomes your workflow.

The matrix should also name the invoices that need no human approval at all. A purchase order invoice that matches its receipt within tolerance has already been approved twice, once when the PO was released and again when the goods arrived. D365 Finance can submit imported invoices to workflow automatically once product receipts are matched, hold them back until the received quantity equals the invoiced quantity, and post them through an automated task at the end of the workflow. Sending those invoices to a manager adds days. It rarely adds control.

Non-PO invoices are where approval design earns its keep. A utility bill, a consultant’s monthly fee or a one-off repair has no prior authorization behind it, so the approver is the only control between the invoice and the payment run. Route these by financial dimension, usually cost center or department, so the person who owns the budget sees the spend before it posts.

Plan for the approver who doesn’t respond

Here is the expectation gap. Teams assume the workflow will chase late approvers, and it won’t unless you tell it to. Every approval step has a time limit where you set how long the approver has to act, in hours, days or weeks against your working calendar, and once that time passes the invoice is marked overdue. An escalation path can then reassign it to the next person in the hierarchy or a named backup, each with a time limit of their own, and an end action decides what happens if nobody responds at all.

Delegation covers planned absences. From the Workflow tab in their user options, approvers can hand all their work items, everything for one workflow type, or a single workflow to a colleague for a set date range. Honestly, this is where most approval designs break down in practice: not in the routing logic, but in the assumption that a regional manager will remember to set up a delegation rule on the afternoon before two weeks of vacation. Setting up rules for escalations help catch the gaps in delegation, so building both is the best path for success.

The approver experience Microsoft stepped back from

Everything above works well for people who spend their day in D365 Finance. Most approvers don’t. A site manager who approves fifteen invoices a month has little reason to learn the web client’s navigation, and the tool Microsoft once offered that person is going away. The finance and operations mobile app is no longer supported and has been removed from app stores, and Microsoft marks the Invoice approval mobile workspace to retire rather than replace.

Microsoft’s guidance for new mobile experiences is to build them in Power Apps using virtual tables over finance and operations data. That path works for teams with Power Platform skills and the time to maintain an app. Everyone else is left choosing between email alerts that send approvers into the web client and an AP layer that gives them a simpler place to act. The right answer depends less on technology than on a plain question: how many of your approvers logged in to D365 Finance last month?

Where a dedicated AP tool fits

Dooap is built specifically for D365 Finance and uses the same building blocks for approvals, with approval workflows driven by signing limits, dimensions or position hierarchy, and invoices that pass validation routing straight to approval without an AP check. Master data, controls and the audit trail stay in Dynamics. The difference shows up on the approver’s side: approvers sign in with their D365 credentials, get a daily email only when something is waiting, and can review, comment, code and approve from the Dooap mobile app.

Scale is where that matters most. One Dooap customer, writing on Microsoft’s Tech Community blog, described processing more than 30,000 invoices a month with two coders and a group of approvers spread across 30 districts and seven regions. Few of those approvers would ever open the D365 Finance web client on their own.

Where to start

Before you change any configuration, find out where invoices actually wait. Pull a month of posted invoices and compare the time each one spent in approval with the time it spent in capture and matching. If approval is the long pole, the matrix, escalation and delegation work above will move your cycle time; if it isn’t, matching tolerances and receipt timing are the better place to start.

And if approval wait time turns out to be the bigger problem, with approvers who rarely open D365 Finance, it’s worth seeing how Dooap handles approvals for D365 Finance teams next to the workflow you already run.