ERP Approval Workflow: How to Design One That Keeps Moving
An ERP approval workflow is a set of rules inside your ERP that decides who must sign off on a document or change, in what order, and what happens after they decide. Done well, it protects money and master data without slowing down the people who need answers. Done badly, it becomes a pile of requests waiting in an absent manager’s inbox. This guide covers the stages, the routing models, the controls auditors look for, and the step most articles skip: how requests that start in an email get into the workflow in the first place.
TL;DR
- An ERP workflow is a sequence of tasks triggered by an action, condition or rule. Approvals are the most common use: purchase documents, sales documents, vendor-bank changes, credit limits, item prices and finance journals.
- Every approval follows the same arc: submit, validate, route, review, decide, record, act. The quality of the first two steps decides how smooth the rest is.
- Most stalls come from absent approvers with no delegate, outdated routing, incomplete master data and missed notifications. All of them are preventable with maintenance and escalation rules.
- Many approvals begin as an email with a PDF or a free-text request. Capturing and validating that data before it reaches the approver removes the manual re-keying that creates errors.
Table of Contents
- What an ERP approval workflow controls
- The stages of an approval, from request to recorded decision
- Routing models: sequential, parallel, conditional and fallback
- Roles, thresholds and routing rules
- Audit trail: what to record at every step
- The gap before the workflow: requests that arrive by email
- How to set up an approval workflow in your ERP
- Why approvals stall, and how to prevent it
- How to tell whether your workflow is working
- Our perspective
- Bring your inbox into the approval workflow
- FAQ
- Sources
What an ERP approval workflow controls
Microsoft’s documentation for Dynamics 365 Business Central defines a workflow as a sequence of tasks triggered by an action, condition or rule. The same page lists what approvals commonly cover: master data, sensitive changes such as vendor bank details and customer credit limits, item sales prices, purchase and sales documents, incoming documents, and finance journals before they are posted.
The important idea is that approval is a business control, not a notification. In Microsoft’s model, a workflow can enforce separation of duties, keep the old value of a field until the change is approved, and combine human approvals with automatic system steps such as posting a document once everyone has signed off.
In practice, the documents that most often need an approval gate are:
- Purchase orders and purchase requisitions: to cap spending and confirm budget.
- Supplier invoices: to confirm that what was billed matches what was ordered and received.
- Sales orders: especially large orders, special pricing, or customers near their credit limit.
- Master data changes: a new vendor, a changed bank account, a new customer credit limit.
- Journals: manual finance entries before posting.
The stages of an approval, from request to recorded decision
The vocabulary varies by system, but the arc is consistent. A widely used breakdown describes submission, validation, routing, review, decision, recording and downstream action, with rework, escalation, parallel review and conditional routing added when the process needs them. Here is what each stage means inside an ERP:
- Submit. Someone creates the request: a purchase requisition, a sales order, a vendor change. In many companies this is where an email gets turned into an ERP document.
- Validate. The system checks that required fields exist and make sense: a valid vendor, a cost center, a price, a quantity. Catching errors here is far cheaper than catching them after an approver has already signed.
- Route. Rules pick the approver or approvers based on amount, department, document type or business unit.
- Review. The approver sees the document and its context. Good workflows show the source attachment next to the data.
- Decide. Approve, reject or send back with a reason.
- Record. The decision, the person and the time are stored.
- Act. The ERP releases the purchase order, posts the invoice, activates the vendor or applies the new price.
SAP documents a clear example in SAP Business One’s approval procedures. When a document meets an approval condition, it is held as a draft pending approval. After each stage approves, the next stage is notified. If someone rejects it, the document goes back to the originator for changes.
Routing models: sequential, parallel, conditional and fallback
Oracle’s guidance for Fusion Cloud Project Management documents four routing structures and recommends choosing the one that matches the business process: sequential, parallel, conditional and fallback. Here is how they differ in everyday terms.
| Model | How it works | Best for | Watch out for |
|---|---|---|---|
| Sequential | Approvers act one after another | Escalating spend levels, such as supervisor then manager then finance | Slowest option; one absence blocks everyone behind |
| Parallel | Several approvers review at the same time | Cross-functional sign-off, such as technical and commercial | Decide whether all or only one must approve |
| Conditional | Rules choose the path based on amount, type or department | Mixed document volumes with different risk levels | Rules must be kept up to date |
| Fallback | A backup approver or group takes over when the first is unavailable | Any step that has a single named approver | Backup must also have the right authority |
A practical rule: start with the simplest model that satisfies your control policy. Add parallel and conditional paths only when a real business reason demands them, because every branch is something you must test and maintain.
Roles, thresholds and routing rules
Oracle’s approach starts with people. Begin by identifying participants, whether individual users, roles or approval groups, and keep that data current so segregation of duties stays effective. Then define the rules: they specify when a workflow starts, for example by amount, business unit or project type, and the actions determine the next step.
Microsoft shows the same idea from the configuration side: separate workflow instances can use different filters so requests from different departments route to different approvers.
A simple threshold table might look like this. The amounts are placeholders to show the pattern, not a recommendation; set yours from your own financial policy.
| Purchase order value | Approver | Extra rule |
|---|---|---|
| Up to your first limit | Department supervisor | None |
| Between first and second limit | Department manager | Budget check |
| Above second limit | Finance director | Parallel review by purchasing |
| Any value, new vendor | Purchasing manager | Vendor master data approved first |
Two habits keep a table like this healthy. First, assign approval authority to roles rather than to named individuals wherever your ERP allows it. Second, tie role changes to your HR process, so a promotion, transfer or departure updates approvers automatically.
Audit trail: what to record at every step
An approval that cannot be reconstructed later is only half a control. At a minimum, your trail should show who requested, who approved or rejected, when, which rule selected that approver, the comments and attachments reviewed, and what the ERP did afterward, such as releasing a purchase order or posting an invoice.
One point deserves emphasis: if a material field changes after approval, such as amount, vendor or bank account, the earlier approval should no longer count. Good designs invalidate the approval and send the document back through review. Microsoft’s concept of preserving the old value until a change is approved serves the same purpose.
For regulated industries, a system log alone is rarely enough. Our guide to the ERP audit trail and what auditors need beyond system logs goes deeper on what to capture.
The gap before the workflow: requests that arrive by email
Most ERP approval guides assume the request already exists as a clean ERP document. In wholesale and manufacturing, that is often not true. Orders arrive as PDFs, Excel sheets, scanned documents or a few lines of free text in Outlook or Gmail. Someone has to read them, find the right customer and item numbers, and key everything in. Only then does the approval workflow start.
That manual step is where errors enter, and the approver downstream then signs off on data that may already be wrong. Three changes help:
- Extract the data automatically from the email body and attachments, without forcing customers or suppliers to use a template.
- Validate before routing. Check customers, items, prices and quantities against your ERP master data, so the approver sees verified data rather than raw input.
- Keep the source next to the decision. The approver should see the original email or document beside the extracted fields.
This is the problem Ampwise is built for. We explain the full flow in how email to ERP automation works, and the approval step in particular in our piece on a one-click approval workflow for managers. For purchase orders specifically, see the three checks to run before ERP release. On the invoice side, invoice automation for AP teams covers a pilot approach for email and scanned documents.
How to set up an approval workflow in your ERP
Implementation checklists differ, but they converge on the same sequence. Use this one:
- Map the current process. Write down who approves what today, including the informal approvals that happen by email or in the hallway.
- Define the policy. Decide thresholds, document types, separation of duties and what counts as an exception.
- Choose the routing model for each document type: sequential, parallel, conditional, with a fallback approver.
- Configure the workflow in the ERP, using roles or approval groups instead of single names.
- Connect external channels. Microsoft’s Dynamics 365 reference architecture shows the pattern: a workflow business event triggers an external approval process, Power Automate retrieves approvers, notifications go out through Teams or Outlook, and the decision returns to the ERP. The ERP remains responsible for the transaction, while outside tools handle messages and responses.
- Test in a non-production environment with routine and exceptional cases.
- Train approvers and requesters, then go live with a small document type first.
- Review after go-live. Look at cycle times, rejections and stalled items, and adjust the rules.
Test cases should include more than the happy path. Cover an absent approver, a high-value document, a foreign-currency amount, a period close and a system failure. After testing, compare workflow states with the ERP documents and ledger totals, so you know the two agree.
Why approvals stall, and how to prevent it
Approvals rarely fail because the software is broken. They stall for human and data reasons:
- The approver is absent and no delegate exists. Set delegation rules and a time limit, then escalate automatically to the next level.
- Notifications are missed. Send reminders through the channel people actually watch, and give each step a defined owner and deadline.
- The assigned person no longer has authority. Link approver lists to HR changes and review them on a schedule.
- Master data is incomplete. A missing cost center or vendor field blocks routing. Validate at submission, not at review.
- Purchase-order lines do not match. Compare quantities and prices before the approver sees the document.
- Routing no longer matches the organization. After a reorganization, re-check every rule.
Integration adds its own failure modes. When a workflow posts back to the ERP, a timeout should not create a duplicate. Sound designs use an idempotency key when posting, check the destination state before retrying, and send unrecoverable errors to a repair queue with a named owner.
If your team is working on the broader process around these controls, our article on ERP workflow automation for operations teams is a good companion.
How to tell whether your workflow is working
Choose a few measures before you start, so you can compare afterward:
- Cycle time: days from submission to decision, and from decision to ERP posting.
- Error and rework rate: how many documents are sent back or corrected after approval.
- Touches per document: how many people handle a request before it is final.
- Aging items: requests waiting beyond your service target, by approver.
- Exceptions: how often approvals are bypassed or done outside the system.
Research points in the same direction. A 2025 study of 100 employees in India reported that digital forms, e-signatures and automated routing reduced errors and turnaround time in HR and accounts-payable workflows, with larger gains among high adopters. It is a small, single-country sample, so treat it as a sign of direction, and set your own baseline.
Our perspective
We see the same pattern in nearly every wholesale and manufacturing company we talk to. The approval workflow in the ERP is usually fine. The trouble starts a step earlier, when a customer order, a purchase order confirmation or a supplier invoice lands in a shared inbox and someone retypes it.
That is why we think of approval as the end of a chain, not the start. If the data was extracted correctly, matched against your ERP records and flagged where something looks off, the approver’s job becomes a quick, confident decision instead of a detective exercise.
Ampwise is designed to work in Outlook and Gmail, to handle PDFs, Excel files, scanned documents and free-text emails without templates, and to let a person approve verified data into the ERP with one click. We built it so your staff do not have to change how they work or be retrained on a new tool. Our aim is simple: fewer keystrokes, fewer errors, and approvals that move at the speed of the business.
Evert
Bring your inbox into the approval workflow
If orders, inquiries, invoices or PO confirmations reach you by email, Ampwise reads them in Outlook or Gmail, extracts and validates the data, and prepares it for one-click approval into your ERP. Ampwise says it can reduce manual data entry by up to 90%, and it works without templates or changes to your current workflow.
See how it fits your process on the Ampwise AI page, or start from the Ampwise homepage. If you want to begin small, our 2 to 4 week pilot approach from inbox to ERP shows how teams typically get started.
FAQ
What is the difference between an ERP workflow and an approval workflow?
A workflow is any sequence of tasks triggered by an action, condition or rule. An approval workflow is the kind that asks named people or roles to sign off before the process continues. Many ERP workflows mix both, for example an approval followed by an automatic posting step.
How many approval levels should a purchase order have?
Use as few as your control policy allows. Most companies tie levels to value and risk, such as supervisor, manager and finance, and add extra checks only for new vendors or unusual items. Each added level slows the process and adds another place for a request to wait.
Can approvals be handled outside the ERP, for example in Outlook?
Yes, as long as the decision returns to the ERP and is recorded there. Microsoft’s reference architecture for Dynamics 365 shows approvers being notified through Teams or Outlook while the ERP remains the system of record for the transaction.
What should happen when an approver is out of office?
The step should pass to a delegate or fallback approver with the same authority, and escalate automatically if nobody acts within a set time. Define this per step, and test it before go-live.
Sources
- Using approval workflows, Business Central (Microsoft Learn)
- Implementing the Approval Processes in SAP Business One (SAP Learning)
- Approval workflows in Oracle Fusion Cloud Project Management (Oracle)
- Automate purchase requisition and supplier invoice approval (Microsoft Learn)
- Workflow Approval Process: Guide, Steps, and Examples
- A study of effects of digital forms and automated workflows (Management Paper, 2025)
