Automate supplier invoice approval: routing, deputies, audit trail
How to automate supplier invoice approval after capture
To automate supplier invoice approval after capture, you need five pieces: a routing rule by supplier, cost centre or amount; approval in Outlook or Teams without logging into accounting; a holiday deputy; a record of each decision; and a clean handover to accounting and the payment run. If your accounting program already covers approvals and every approver works there, start there. Build around it when approvers stay in Outlook and Teams, or when routing needs data that lives outside the program.
This is for the finance lead or office manager in an SME where invoices are approved by initials on a printout, by a reply to a forwarded mail, or by a thumbs-up in a chat. How invoices get captured in the first place is a separate step, covered in invoice capture: what accounting software misses. This article starts where that one stops.
- Captured
The invoice sits in the accounting tool or a review queue, fields read.
- Routed
A rule picks the approver.
- Approved
One click in Outlook or Teams, or a rejection with a reason.
- Booked
Accounting sees the status and books.
- Paid
Only approved invoices reach the payment run.
When the approval in your accounting program is enough
Many accounting programs ship with approval, and for plenty of SMEs that is enough. Abacus lists in its accounts payable flyer one-click approval in MyAbacus and customisable routing. If every approver has a login and your rules are clear (“project manager for their project, managing director above a threshold”), configure it in the program and stop. Two approval systems mean two places to check.
Build around it when the approvers are not users of the accounting program, for example site managers or department heads without a licence. Or when approval has to happen where people already work, in Outlook or Teams. Or when the routing needs data that lives elsewhere, such as the project list with its managers in a SharePoint list or an ERP. What your program offers in approvals and interfaces, we clarify in the Check.
Step 1: write the routing rules down
Routing is a table, not a feeling. Before anything is automated, write down who approves what. Three keys cover most SMEs: supplier, cost centre or project, and amount. The values below are examples, not recommendations.
| Rule | Approver | Deputy |
|---|---|---|
| Framework supplier, under CHF 500 | Office lead | Finance lead |
| Invoice with a project number | Manager of that project | Their department head |
| Cost centre without a project | Cost centre owner | Managing director |
| Above CHF 5’000 | Additionally the managing director | Second authorised signatory |
| Unknown supplier | Finance lead checks first | Managing director |
Two rules make the table work. Every invoice has exactly one first approver, because “the team” is not an approver. And an invoice that matches no rule does not wait silently: it goes to the finance lead.
Step 2: approval in Outlook or Teams
Approval happens where the approver already works. In Microsoft 365, Power Automate has a Start and wait for an approval action. The approver can respond directly from an Outlook email, from a Teams adaptive card, or in the Power Automate action centre. Microsoft lists several types: first to respond, everyone must approve, custom responses, and sequential approval, where each approver responds in a set order. Sequential fits the rule “project manager first, then the managing director above CHF 5’000”.
In Teams, requests appear in the Approvals app. Microsoft describes it as bringing auditing, compliance, accountability and workflows to approvals in Teams. It needs a Power Automate, Microsoft 365 or Dynamics 365 licence, and it stores approval data in Microsoft Dataverse.
What the approver sees: supplier, amount, due date, cost centre or project, the PDF, and two buttons. A rejection needs a reason, which goes back to the office. Nothing more. If people have to open three systems to decide, they will keep approving by reply mail.
Step 3: deputies during holidays
Deputies belong in the rule table, not in an afterthought. Three mechanisms cover it, in this order.
- Before sending, the flow checks whether the approver has automatic replies switched on. The Outlook connector has an action to get mail tips for a mailbox, which includes automatic replies. If they are on, the request goes straight to the deputy from the table.
- While it is open, an approver can reassign a request to someone else in Power Automate. The requester cannot; they can only cancel it and start again.
- Before the due date, for example three working days ahead, a request that is still open goes to the deputy, and the office gets a note.
Step 4: audit trail and handover to accounting and payment
Every decision needs a record: which invoice, which amount, who approved, when, with which comment, and whether a deputy stepped in. The Teams Approvals app logs events such as created, approved, rejected and reassigned in the Microsoft Purview portal. For day-to-day use, the flow also writes one line per decision into a list next to the invoice, so that accounting and the auditor can see it without admin rights.
Keep that record with the invoice. Accounting records must be kept for ten years, and according to kmu.admin.ch electronic records have to be stored so that they cannot be changed or deleted without the change being detectable; protocols and log files must be kept as well. Ask your fiduciary or auditor how they want to see the approval before you build it, not after.
The handover is a status, not a payment. Once approved, the invoice gets the status “approved” in the accounting program or in the review list, and accounting books it. The payment run is still created in the accounting program or in e-banking. In Switzerland, the payment order to the bank uses the ISO 20022 message pain.001, specified in the Swiss Payment Standards that SIX publishes on behalf of the Payments Committee Switzerland. Abacus lists pain.001 among its payment formats. The approval flow does not need to produce that file, and it should not. Its job is to make sure only approved invoices reach the run.
An example: about 200 invoices a month
A hypothetical picture, not a client case. A building-services company with about 45 people, about 200 supplier invoices a month and a dozen active projects. Invoices are captured in the accounting program. Approval happens on paper: the office prints each invoice, puts it in the project manager’s tray and waits. Site managers are rarely in the office, so invoices wait a week, sometimes until the reminder arrives.
The rule table has five lines. An invoice with a project number goes to the project manager. Material from the framework supplier under CHF 1’000 goes to the office lead. Above CHF 10’000 the managing director approves as well. Anything without a project number or from an unknown supplier goes to the finance lead. The project list with its managers sits in a SharePoint list, and the approval runs in Power Automate. Site managers approve on their phone in Outlook or Teams. Before sending, the flow checks for automatic replies, and after three days an open request goes to the deputy. Every decision lands in a list with the invoice number, which accounting filters by “approved” before the payment run.
What stays manual: invoices without a project number, which the finance lead assigns; rejections, which the office clarifies with the supplier; and the payment run itself. With several steps and two systems, this shape sits closer to the Medium package than to Small. The Check sets the size.
When to leave it
Leave it when a handful of invoices a month are approved by the one person who also pays them. Leave it when your accounting program’s own approval already reaches everyone who approves. And leave it when the rules are not clear. If nobody can say who approves an invoice without a project number, write that down first. Automating an unclear rule only makes the waiting faster.
If the bigger problem is upstream, in a mailbox where invoices and documents arrive unsorted, the same logic is described in sorting the client inbox and chasing missing receipts.
Bring your approval path to the Process Check
If invoices in your company wait on paper, in forwarded mails or in a chat, and you can name who should approve what, that is one recurring task, and the Process Check is built for exactly that. In 30 minutes we look at how invoices arrive, who approves, and where the project list lives. Describing it is enough. You leave with where to start, whether it pays off, a price range and a rough duration for implementation, and a short written summary. You can book the free half hour online.
Written by
Aurum Avis Labs
Builds and ships at Aurum Avis Labs. Writes here about what we learn working with founders and SMEs in the DACH region.
Related Articles
You might also be interested in these articles
Invoice capture: what accounting software misses
Invoice capture beside bexio, Abacus or DeepCloud: mail, portals and approval. OCR inside the tool stays. The trustee stays for the close.
Fiduciary firms: sort the client inbox, chase missing receipts
How a Swiss fiduciary firm sorts client mail by client and period, files attachments, and chases missing receipts until each file is complete.
What the Process Check is and what it is not
A free Process Check: a 30-minute call on one workflow, a concrete case and a package size. Not a workshop.