Case 43
Where the Process Leaks
Scenario
You manage the accounts payable team at Linton Retail. Paying a supplier invoice takes much longer than it should, and the team spends its days chasing approvals.
Why this framework
Uses PIN: what it's for, the context and source of truth, and a narrow ask. Enough for most everyday work.
Example context
Process description (Linton Retail accounts payable): 1. Invoice arrives by email to the AP inbox. 2. AP keys the invoice within 2 working days. 3. System matches to purchase order (PO). 4. If matched, routed to budget holder for approval within 3 working days. 5. Approved invoices paid in the next weekly payment run (Thursdays). Target: paid within 30 days of invoice date. Sample of last month's invoices (20 invoices; days elapsed at each step): - Received to keyed: median 4 days; 6 invoices over 7 days. - Keyed to PO match: 14 matched same day; 6 had no PO and were emailed to the requester to raise one, median 9 days to get a PO. - Match to approval: median 8 days; 5 invoices over 15 days; 3 of these were with store managers who were on leave with no delegate set. - Approval to payment: median 3 days. - Overall: median 21 days invoice to payment; 7 of 20 paid after 30 days; 2 late payment charges totalling £310. - AP team notes: 'Roughly a third of our day is chasing approvals by email'; invoices arrive as PDFs and 4 were sent to individuals instead of the AP inbox.
Prompt
Purpose: Find where time and money are lost in our invoice payment process, so I can pick two fixes for next month.
Context: Use the attached process description and the sample of last month's invoices with dates for each step. Treat the dates as the facts; the description is how it is supposed to work.
Narrow the ask: Give me
- The steps where invoices wait longest, with the evidence
- Where the actual process differs from the description
- Three fixes ranked by effort and likely impact
Bullets only, no more than 300 words.
Materials (pasted here in place of the attachments):
Process description (Linton Retail accounts payable): 1. Invoice arrives by email to the AP inbox. 2. AP keys the invoice within 2 working days. 3. System matches to purchase order (PO). 4. If matched, routed to budget holder for approval within 3 working days. 5. Approved invoices paid in the next weekly payment run (Thursdays). Target: paid within 30 days of invoice date.
Sample of last month's invoices (20 invoices; days elapsed at each step):
- Received to keyed: median 4 days; 6 invoices over 7 days.
- Keyed to PO match: 14 matched same day; 6 had no PO and were emailed to the requester to raise one, median 9 days to get a PO.
- Match to approval: median 8 days; 5 invoices over 15 days; 3 of these were with store managers who were on leave with no delegate set.
- Approval to payment: median 3 days.
- Overall: median 21 days invoice to payment; 7 of 20 paid after 30 days; 2 late payment charges totalling £310.
- AP team notes: 'Roughly a third of our day is chasing approvals by email'; invoices arrive as PDFs and 4 were sent to individuals instead of the AP inbox.Example output from ChatGPT
Invoice Payment Process Review to Linton Retail
- Sample: 20 invoices from last month. Target: payment within 30 days.
1. Where invoices wait longest
- PO matching exceptions to 9 days median: 6/20 invoices (30%) had no PO and required requester intervention.
- Budget holder approval to 8 days median: Against a 3-working-day requirement. Five invoices took over 15 days; three involved managers on leave without delegates.
- Invoice entry to 4 days median: Six invoices took over 7 days. Four arrived outside the AP inbox.
- Payment processing to 3 days median: Relatively efficient compared with upstream stages.
2. Where the actual process differs
| Process requirement | Actual evidence |
|---|---|
| Key within 2 working days | Median 4 elapsed days |
| System matches invoice to PO | 30% required manual PO creation |
| Approval within 3 working days | Median 8 elapsed days |
| Pay within 30 days | 7/20 (35%) paid late |
- Financial impact: £310 in late-payment charges across two invoices.
- Productivity impact: AP estimates one-third of its day goes to chasing approvals.
- Caution: Working-day targets and elapsed-day observations are not directly comparable.
3. Recommended fixes, ranked
| Rank | Fix | Effort | Likely impact |
|---|---|---|---|
| 1 | Set approval delegates and automatic reminders/escalations | Low–Medium | High |
| 2 | Require valid POs before suppliers submit invoices; track missing-PO exceptions | Medium | High |
| 3 | Centralise invoice intake and introduce automated PDF data capture | Medium–High | Medium |
4. Two fixes for next month
- First: Introduce approval delegation and escalation. Target the five approvals exceeding 15 days and reduce manual chasing.
- Second: Enforce PO readiness before invoicing. Target the six missing-PO cases and their 9-day median delay.
- Measure: Approval turnaround, missing-PO frequency, percentage paid within 30 days, AP chasing time and late-payment charges.
Conclusion: Prioritise approval delays and missing POs. These are the clearest documented bottlenecks, although the sample does not establish how much each contributes to late payments.
