Finance Index
How should approval reminders and escalations work in AP?
Reference guide to approval reminders escalation, including control design, audit evidence, risk points, finance procedures, and compliance review.
Reminders and escalation are the enforcement layer of an approval SLA: reminders nudge the assigned approver on a defined cadence; escalation transfers or elevates the item when the SLA breaches. Both should be automatic, rule-driven, and logged - chasing approvals manually is exactly the work a workflow exists to eliminate.
At a Glance
| Aspect | Short Answer | Why It Matters |
|---|---|---|
| Approval reminders | Reminders and escalation are the enforcement layer of an approval SLA: reminders nudge the assigned approver on a defined cadence; escalation transfers or elevates the item when the SLA breaches. | Reduces payment errors, timing issues, and reconciliation cleanup. |
| Approval path | Add, don't skip, as the default: the original approver keeps the ability to act (they have the context), while their manager gains visibility and can either prompt action or approve with authority. | Keeps work moving without losing accountability. |
| What reminder cadence works without | A useful pattern: first reminder at 48 hours, second at 96, escalation at five business days - tighter for urgent queues. | Helps finance decide what to do next. |
| Set up automatic reminders | Define the trigger (days pending), cadence, and channel in your AP system's workflow settings, and scope reminders to actionable items only. | Keeps vendor records and payment decisions reliable. |
| How often should approval | Two reminders before escalation is a sensible default - enough to cover vacation-adjacent inattention, not so many that escalation never arrives. | Keeps vendor records and payment decisions reliable. |
How should escalation be designed - skip the original approver or add their manager?
Add, don't skip, as the default: the original approver keeps the ability to act (they have the context), while their manager gains visibility and can either prompt action or approve with authority. Skipping entirely makes sense only on the second escalation tier or for true urgency - because the manager often has less knowledge of the specific spend, and an escalation that ends in an uninformed approval has traded a delay problem for a control problem. Whatever the design, escalation paths should mirror authority: an item should never escalate to someone below the required DOA level.
What reminder cadence works without training people to ignore notifications?
A useful pattern: first reminder at 48 hours, second at 96, escalation at five business days - tighter for urgent queues. The cadence matters less than the hygiene around it: reminders must only fire for genuinely actionable items, must stop immediately once the approver acts, and should consolidate into a digest when someone has multiple pending. Notification fatigue comes from noise, not frequency.
How do I set up automatic reminders for pending invoice approvals?
Define the trigger (days pending), cadence, and channel in your AP system's workflow settings, and scope reminders to actionable items only. If your current process requires AP to send reminders manually, that's a tooling gap, not a discipline gap.
How often should approval reminders fire before escalating?
Two reminders before escalation is a sensible default - enough to cover vacation-adjacent inattention, not so many that escalation never arrives. Compress the whole sequence for payment-critical or discount-bearing invoices.
Should escalation be logged in the audit trail as a control event?
Yes. Escalations are evidence that the monitoring control operated - and escalation frequency by approver is a management signal worth reviewing. An escalation that leaves no trace can't prove either.
Reminders are being ignored because approvers get too many notifications - how do I fix notification fatigue?
Cut noise before adding volume: eliminate FYI-only notifications, digest multiple pending items into one message, route everything actionable to one channel (ideally mobile-actionable), and reserve real-time pings for genuine urgency. Then the reminders that remain mean something.
How do I escalate urgent invoices (utilities about to be cut off, legal deadlines) outside the normal queue?
Maintain a defined urgent path - flagged priority, immediate notification, short SLA, direct escalation - rather than ad-hoc "walk it over" handling. Urgency is a workflow state, not a workflow bypass: the invoice still gets approved by someone with authority, just faster, and the urgent flag is logged.
How do I get visibility into everything currently escalated across the company?
A standing escalation dashboard or report: every item past SLA, current holder, days overdue, amount. Review it weekly at the AP leadership level; recurring names and categories tell you where the process - not the people - needs redesign.
Escalation sent an invoice to a vp who has no context and rubber-stamped it - does escalation actually weaken control?
Badly designed escalation can. The fix is in the design: escalate with full context attached, prefer add-the-manager over skip-the-approver so knowledge stays in the loop, and treat escalated approvals as a category worth sampling in management review - they're decisions made under less information by construction.
Stampli perspective
Stampli automates the chase: configurable reminders keep pending approvals in front of approvers, escalation rules move unactioned items per policy, and mobile approval removes the most common excuse for delay. Because reminders, escalations, and the eventual decision all land in the invoice's activity record, the SLA's operation is itself documented - useful when demonstrating to auditors that monitoring controls actually ran.