Multi-step approvals slow down when they depend on paper and email. This guide explains how German businesses can digitise them, covering e-invoicing deadlines, archiving rules, works council rights and a comparison of leading workflow tools.
A purchase request is raised on Monday. The department head signs it on Wednesday, finance queries the cost centre on Thursday, and by the following week nobody can say whether the managing director has seen it.
This is the usual state of multi-step approvals in firms that still rely on paper forms, shared inboxes and spreadsheets. In Germany the cost of leaving it that way is rising, because new e-invoicing rules, strict archiving expectations and works council rights all affect how approvals have to be built.
This guide covers how to digitise approval chains such as invoices, purchase orders, contracts, leave and expenses. It sets out the German requirements that shape the design, compares the main tools and gives a method for choosing between them.
Why multi-step approvals break down
A single sign-off is easy to manage. Trouble starts when a request needs several people in a set order, with conditions attached. An invoice over a certain value might need a budget holder, then finance, then a director. A supplier contract might need legal review in parallel with the commercial sign-off.
Manual processes fail in predictable places:
- Visibility. Nobody can see where a request is sitting, so people chase by email or phone.
- Rules held in people’s heads. The approval limits exist, but only a few long-serving employees know them, and exceptions go unrecorded.
- Holidays and absences. Without a delegation rule, a request waits for someone’s return.
- Weak evidence. When an auditor or tax inspector asks who approved what and when, the answer is reconstructed from email threads.
Digitising the process addresses all four, but only if the underlying rules are clear first. Software applied to a muddled process produces a faster muddle.
Map the process before choosing software
Start with one approval flow and write down what happens now, including the awkward parts. For each step, record who approves, what information they need to decide, what the thresholds are, and what happens on rejection or delay.
A short map usually exposes problems that nobody had named. Two approvers might be checking the same thing. A step may exist only because of a rule that was abandoned years ago. Remove those before automating, because every step you keep becomes something the system has to enforce.
The basic design choices are worth settling at this stage:
- Sequential or parallel. Sequential suits approvals where each person needs the previous decision. Parallel suits independent checks, such as legal and finance reviewing a contract at the same time.
- Value thresholds. Most firms vary the number of approvers by amount. Keep the matrix simple enough to explain in two sentences.
- Delegation and escalation. Decide who covers for an absent approver and how long a request can sit before it moves up a level.
- Rejection routes. Decide whether a rejected request returns to the requester or ends, and whether a reason is mandatory.
German requirements that shape the design
Some of this is specific to Germany, and it is easier to design for it at the start than to retrofit it.
E-invoicing
Invoice approval is where most firms feel the pressure first. Every German business has had to be able to receive structured e-invoices since 1 January 2025, and an ordinary email inbox is enough to receive them. The issuing side is phased.
From 1 January 2027, companies with prior-year turnover above €800,000 must issue e-invoices, and from 1 January 2028 the obligation covers all domestic B2B companies.
Formats such as XRechnung (pure XML) and ZUGFeRD (a hybrid of PDF and XML) are accepted, as the hybrid format combines a PDF with XML data.
For approval design, this matters because a structured invoice carries its data in machine-readable form. A workflow can read the supplier, amount and cost centre directly rather than relying on someone to key them in, and it can route the invoice automatically. A PDF-only approval process built today will need rework within a year or two.
Retention and audit trail
German bookkeeping rules (the GoBD principles) expect records to be traceable, complete and unaltered. An approval log that can be edited afterwards, or that lives in someone’s personal mailbox, does not meet that expectation. Look for a system that records each decision with a user, a timestamp and the version of the document that was approved.
Retention periods have also changed. The archiving period for accounting vouchers was reduced from 10 years to 8 years from 2025. Other records, such as books and annual accounts, may still carry longer periods, so confirm the periods that apply to each document type with your tax adviser before setting archive rules.
Data protection and the works council
Approval systems process employee data, including who approved, how quickly and how often. Under GDPR (DSGVO in German), you need a lawful basis for that processing, and approver names and decision histories should be visible only to those who need them.
The works council (Betriebsrat) is the other consideration. Under Section 87 of the Works Constitution Act (Betriebsverfassungsgesetz), the council generally has a co-determination right over technical systems capable of monitoring employee behaviour or performance.
An approval tool that reports approval times by person can fall into that category. Involving the council early, with a clear explanation of what is and is not reported, tends to be much smoother than raising it after purchase. Take legal advice on the specifics for your organisation.
Electronic signatures
Not every approval needs a signature, and many internal sign-offs are adequately covered by an authenticated, logged click. Where a signature is needed, the EU eIDAS framework recognises three levels: simple, advanced and qualified.
A qualified electronic signature carries the same legal effect as a handwritten one. Some documents still require written form by law, so check the requirement for each document type rather than assuming the highest level is needed everywhere.
Comparing the main tools
The right tool depends mostly on what you already run. The table describes fit rather than price, because licensing for these products changes often and varies by contract.
| Tool | Best suited to | Approval strengths | Watch for |
|---|---|---|---|
| Microsoft Power Automate | Firms already on Microsoft 365 | Built-in approval actions, sequential and parallel flows, links to Teams and Outlook | Licence tier requirements and the need for governance as flows multiply |
| SAP Build Process Automation | Organisations running SAP ERP | Workflows that use SAP master data and documents directly | Cost and implementation effort for smaller firms |
| Camunda | Complex, cross-system processes with in-house developers | BPMN-based modelling and orchestration across many systems | It is an engine, so it needs engineering effort to build the user-facing screens |
| ELO or d.velop | Firms where document archiving and retention are the main concern | Document management with workflow and archiving, from German vendors | Confirm any compliance claims against your own retention rules |
| DocuSign or Yousign | Contract and agreement sign-off, including external parties | Strong signature handling and a clear signing audit trail | Primarily signature tools, so they may not cover a full internal approval chain |
Many firms end up combining two of these, for example a workflow tool for internal routing and a signature tool for the final contract.
How to choose
Work through these questions in order. The answers usually narrow the field quickly.
- What is your core system? If your finance and procurement already run in SAP, start with SAP’s own tooling. If your staff work mostly in Microsoft 365, Power Automate is the natural first candidate.
- How many systems does one approval touch? A flow that stays inside one platform is simple. A flow that reads from an ERP, checks a CRM and writes to an archive is a better fit for an orchestration tool such as Camunda, and that usually means developer involvement.
- Who are the approvers? If they include external parties such as customers or suppliers, a signature platform becomes more important.
- How heavy is your archiving burden? If auditors regularly ask for historic records, prioritise a system with strong retention and export features.
- Who will maintain it? A flow built by one enthusiastic employee and understood by nobody else becomes a risk. Choose something your team can realistically own.
Designing the workflow
A worked example makes the design choices concrete. The figures below are illustrative, not a benchmark.
Imagine a manufacturer with around 120 staff processing supplier invoices. A reasonable matrix might look like this:
- Under €1,000: the budget holder approves alone.
- €1,000 to €10,000: the budget holder and a finance team member approve in sequence.
- Over €10,000: the budget holder, finance and a director approve, with finance able to flag a query that pauses the flow.
If an approver does not respond within a set number of working days, the request escalates to their named deputy and then to their manager. Each decision is logged automatically, and the approved invoice is archived with its approval record attached.
The aim is for the system to enforce rules the business has already agreed. Avoid building exceptions into the workflow itself. If a one-off case needs special handling, let an administrator reassign it manually and record the reason.
Rolling out without disruption
Begin with one process that is high in volume and low in controversy, such as expense claims or purchase orders under a modest value. A pilot in one department produces real feedback without putting the whole business at risk. If you are planning a wider programme, this Digital Transformation Roadmap for German SMEs sets out how to sequence work from a first process through to full implementation.
Run the old and new processes side by side for a short period so that nothing is lost if the new flow behaves unexpectedly. Then measure the results against the baseline you recorded earlier.
Useful measures include average time from request to final approval, the number of requests that stall at each step, and how many are rejected and why. If a particular step is the bottleneck, that is a process question to solve with the people involved, not a software problem.
Training deserves more attention than it usually gets. Approvers who receive a notification they do not understand will ignore it, and the whole system then slows down.
Mistakes to avoid
Copying the paper process exactly into software is the most common one. Digitising is a good moment to remove steps that add delay without adding control.
The second is building too many approval levels. Every extra approver adds waiting time, and people begin approving without reading. Fewer, better-informed approvers produce a stronger control than a long chain.
The third is leaving out the works council and the data protection officer until the end. Both can delay a launch by weeks if they are consulted late.
A practical next step
Choose one approval flow and spend an hour mapping it: who approves, in what order, at what thresholds and with what evidence. Note any step that exists only out of habit. That single page will tell you whether you need a lightweight tool inside software you already use or something heavier, and it gives your tax adviser, works council and IT team something specific to review. If you handle invoices and turn over more than €800,000 a year, start there, as the 2027 issuing deadline is already close.
Published by TheStarBizNEWS.
