Approvals exist so money does not leave without a named person. They fail when the path is unclear, the backup is missing, or the reminder lives in chat.

A stalled invoice is usually a stalled person. The workflow should name that person and the next one.

Speed is not the goal. Movement is. An invoice that waits in a known queue is better than one that waits in an inbox.

Write the route on the invoice

Amount, vendor, and department should pick the approver. If people have to remember the route, they will improvise, and improvisation stalls.

Show the current owner on the record. If that person is out, the backup should already be on the same record.

Reminders that belong on the record

Chat reminders vanish. Email reminders bury. A reminder on the invoice, with a due time, is the one AP can audit.

If nothing happens after two reminders, escalate to the named backup. Do not add a third ping to the same person.

• Encode the route from vendor, amount, and department.
• Show the current owner and backup on the invoice.
• Escalate after two missed reminders, not after a week of silence.

Thresholds that people can see

A second approver should appear because the amount crossed a line, not because someone felt nervous. Put the line on the invoice.

If every invoice needs the same two people, you do not have a threshold. You have a bottleneck. Split routine amounts from exceptions.

Rejects that come back clean

A reject should say what is wrong: wrong vendor, wrong amount, missing receipt. Then the invoice returns to intake with that note attached.

Silent rejects stall as badly as silent approvals. The queue has to show the reason.

• Show the amount line that adds a second approver.
• Keep routine invoices on a short path.
• Require a reason when an invoice is sent back.

Do not approve in the chat tool

A thumbs-up in chat is not an audit trail. If you need a fast ping, send people to the invoice. Capture the decision there.

Month-end will ask who approved. The answer should be on the record, with a time.

• Keep the decision on the invoice, even if the nudge started in chat.
• Store who approved and when.
• Do not treat a chat reaction as the system of record.

Approvals in Control

Control holds the route, the owner, and the history. It does not move money. It keeps invoices from waiting in a private inbox.

If your team still approves by memory, start with the named owner and backup. The rest of the workflow gets easier after that.

• Name the owner and backup on every invoice.
• Escalate after two reminders, with a reason on rejects.
• Keep the approval decision on the record Control already holds.