Finance Index
How do I handle invoice approvals when an approver is on vacation, leaves the company, or the org changes?
Reference guide to approval delegation turnover, including control design, audit evidence, risk points, finance procedures, and compliance review.
Approval continuity is a control design problem: every approver needs a coverage answer before they're absent. The toolkit is delegation (planned absence), reassignment (departure or misroute), and escalation (unresponsiveness) - each defined in policy, executed in-system, and visible in the audit trail under the actual actor's name.
At a Glance
| Aspect | Short Answer | Why It Matters |
|---|---|---|
| Handle invoice approvals when | Approval continuity is a control design problem: every approver needs a coverage answer before they're absent. | Keeps evidence clear and reduces control risk. |
| Workflow | Tie workflow removal to the HR offboarding trigger, not to someone remembering: the same-day checklist that kills system access must also reassign the person's approval responsibilities and pending queue. | Keeps work moving without losing accountability. |
| Related terms | Delegation is a planned, time-boxed transfer - an out-of-office approver designates a delegate, authority limits defined, end date set. | Keeps work moving without losing accountability. |
| Approval path | Before the absence: the approver (or an admin, per policy) designates a delegate with a start and end date; pending and incoming approvals route to the delegate; everything the delegate does is logged as delegated action. | Keeps work moving without losing accountability. |
| Delegated approvals inherit | Default to a reduced limit, with high-value items held for the delegator's return or routed up. | Keeps work moving without losing accountability. |
How do I make sure terminated employees are removed from approval workflows on day one?
Tie workflow removal to the HR offboarding trigger, not to someone remembering: the same-day checklist that kills system access must also reassign the person's approval responsibilities and pending queue. The failure mode is specific - invoices keep routing to a deactivated user and stall silently - so pair the process with a weekly report of invoices assigned to inactive users. In systems with role-based routing, removal is one role-mapping change; in people-based workflows it's an error-prone hunt, which is itself an argument for rules-based design.
What is the difference between delegation, reassignment, and escalation of an approval?
Delegation is a planned, time-boxed transfer - an out-of-office approver designates a delegate, authority limits defined, end date set. Reassignment is a permanent or corrective transfer - the approver left, or the invoice was misrouted. Escalation is an exception response - the approver didn't act within SLA, so the item moves up or sideways per rule. They carry different risk profiles and the audit trail should distinguish them: who acted, in what capacity, on whose authority.
How do I set up approval delegation when an approver goes on vacation?
Before the absence: the approver (or an admin, per policy) designates a delegate with a start and end date; pending and incoming approvals route to the delegate; everything the delegate does is logged as delegated action. The control points are the end date and the record - open-ended, invisible delegation is where this goes wrong.
Should delegated approvals inherit the delegator's full authority limit or a reduced one?
Default to a reduced limit, with high-value items held for the delegator's return or routed up. Full inheritance is defensible when the delegate is a peer or senior, but a junior delegate exercising an executive's limit for two weeks is exactly the scenario auditors probe.
An approver left the company and 40 invoices are stuck in their queue - what's the right way to reassign them?
Bulk-reassign to the role successor (or the manager pending a successor) with the reassignment logged, then triage by age and amount - some of those invoices are now late. Then fix the root cause: offboarding didn't include workflow removal, so add it to the day-one checklist.
How do I handle approvals during a reorg when reporting lines are changing weekly?
Freeze the workflow design to the pre-reorg state until new ownership is confirmed, run changes as dated batches rather than continuous edits, and lean on fallback approvers for ambiguity. Reorgs are when people-based workflows fail spectacularly and rules-based ones get edited once.
Should delegation be self-service or require admin/controller setup?
Self-service for time-boxed, limit-capped delegation drives adoption; admin involvement for anything open-ended, high-authority, or extended (leave measured in months). Either way, the system must record who delegated, to whom, when, and within what limit.
How should the audit trail record a delegated approval - under whose name does it count?
Under the delegate's name, explicitly marked as delegated, with the delegation grant (delegator, period, scope) retrievable. Recording it under the absent approver's name is evidence falsification, however convenient.
Our CFO is out on leave for 2 months - who should hold their approval authority and how do we document it?
Formal written delegation, approved at the level above (CEO or board), naming the holder (often the controller or another executive), the limit, the period, and any carve-outs reserved for the CFO or board. Two months is long enough that "informal coverage" becomes an audit finding.
How do I run a periodic review to catch stale delegations that were never turned off?
Quarterly, pull all active delegations and confirm each has a future end date and a still-valid reason; expire the rest. Time-boxed delegation at setup makes this review short; open-ended delegation makes it archaeology.
Approval continuity planning - what should the policy say about extended absences and sudden departures?
Define the coverage rule per role (who inherits, at what limit), the trigger (absence beyond X days, any departure), the documentation required, and the day-one offboarding step. The test is simple: if any approver vanished tomorrow, does the policy answer who approves their queue by end of day?
A delegate approved an invoice above what the absent approver would have been comfortable with - is that approval valid and how do we prevent this?
If the delegation granted full authority, it's formally valid - the lesson is about grant design, not the delegate. Prevent recurrence with reduced delegate limits, hold-for-return rules on large items, and a returning-approver review of everything the delegate cleared.
Stampli perspective
Stampli supports delegation and out-of-office coverage so approvals keep moving during absences, with delegated actions captured in the approval history. When approvers change roles or leave, administrators can replace an approver across workflows in one operation rather than editing invoice by invoice, and AP can recall and re-dispatch anything stranded. Reminders and escalation rules catch the unplanned gaps, and every delegation and reassignment event is part of the immutable invoice record.