Stage 5 · Operational map
Finance / AP Invoicing — Operational Map
Curated v1.0 — human-confirmed after merge-review resolution. Published to Function Lead and Leadership.
Workflows mapped
11
Action nodes
6
Handoff nodes
3
Control nodes
5 (2 not functioning as designed)
Shadow systems identified
3
High-friction handoffs
5
Automation-potential: Very High
4 workflows
Automation-potential: High
3 workflows
Automation-potential: Medium
3 workflows
Team hours lost to avoidable manual work / week
55-75h
Workflow nodes
W01
Invoice Receipt and Logging
Hours/week: ~25-35h (4 clerks x 6-10h manual entry each)
W02
PO Matching (3-Way Match)
Hours/week: <1h (system) — but failure rate ~30-40% triggers W04
W03
Approval Routing
Hours/week: ~15-25h (clerks sending/chasing) + ~12-20h (Nadia tier approving)
W04
Exception Handling
Hours/week: ~15-20h (Omar) + re-routing time for clerks when resolved
W05
GRN Confirmation
Hours/week: ~5-8h (posting + Friday sweep)
W06
FX Revaluation
Hours/week: ~3-6h
W07
Dispute Tracking and Vendor Query Management
Hours/week: ~5-8h
W08
Month-End Accruals
Hours/week: ~6-10h at close
W09
AP Aging Reporting
Hours/week: ~4-5h (building)
W10
Payment Processing
Hours/week: ~3-5h
W11
Duplicate Invoice Detection
Hours/week: ~0h (not systematically performed)
Shadow systems
| Shadow system | Official system | Purpose | Status |
|---|---|---|---|
| "The Sheet" (Excel) | SAP S/4HANA (invoice record) | Parallel invoice tracker — all clerks update, always out of sync | High confidence |
| FX revaluation template (Excel) | SAP + Central Bank website (FX journals) | Personal tool — manual rate lookup, error-prone | High confidence |
| Dispute log (SharePoint Word doc) | SAP + Outlook (vendor comms) | Personally owned dispute management — no SLA, no backup owner | Confirmed in curation (92%) |
High-friction handoffs
| Handoff | From → To | Delay | Information lost | Confidence |
|---|---|---|---|---|
| Invoice → GRN confirmation | Vendor delivery → Procurement Liaison | 0-7 days | Delivery confirmation, GRN trigger | High |
| Exception → PO fix | AP Specialist → Procurement / requestor | 2 days - 3 weeks | Root cause context | Medium |
| Invoice → Approval | Clerk → Budget holder | 1-7 days | Due date, penalty clause, urgency | High |
| AP status → Management | Team Lead → Finance Manager / Controller | 5-7 day lag | Real-time position | High |
| Delivery → Accrual | Procurement / PM → Controller | Unpredictable | Services delivered vs invoiced status | Medium |
Top friction points
F1
Invoice data entry (W01): the biggest time sink
Clerks manually re-key PDF invoice data into SAP
- Volume: ~1,200 invoices/month, ~25-35 team hours/week
- Rework rate: ~30% park immediately due to data issues the OCR-less entry doesn't catch
- Root cause: no intelligent document processing on the AP inbox
- If fixed: eliminates ~25-30h/week of manual entry; reduces W01-triggered parking
F2
GRN bottleneck (W05): the invisible blocker
Invoice sits parked waiting for a GRN the liaison may not know is needed
- Elapsed time lost: 0 to 7 days per invoice (Friday sweep cadence)
- Scale: ~40% of all exceptions trace back to a missing or incorrect GRN or PO
- Root cause: no automated delivery notification; a person is the human trigger
- If fixed: removes the largest single cause of exception queue growth
F3
Approval routing (W03): slowest handoff in the chain
Budget holders approve by email, with no context, no due date, no urgency signal
- Elapsed time: median ~2-3 days; tail cases 1 week+
- Penalty risk: interest/penalty clauses missed because due date not surfaced
- WhatsApp workaround: ~50% of approvals happen outside the system — no audit trail
- If fixed: reduces approval wait time; creates audit trail; surfaces penalty risk
F4
FX revaluation (W06): highest error-rate step per transaction
Manual exchange rate lookup, AED calculation, journal posting
- Time: 20-30 min per multi-currency invoice
- Error rate: 2 confirmed posting errors in past year on a volume that likely has more
- If fixed: eliminates error risk entirely; saves ~3-6h/week
F5
Accrual building (W08): structural incompleteness problem
Controller cannot reliably know what has been delivered but not yet invoiced
- Impact: 2-3 restatements per quarter; CFO sign-off required each time
- Root cause: GRN data exists in SAP but is not surfaced to the Controller in a usable form
- If fixed: GRN data feeds accrual engine automatically; restatements drop to near-zero