How panels use scenarios (read this first)
A scenario question is never about the final answer. The interviewer is scoring your diagnostic order (what you check first), your vocabulary precision (hold names, process names, real screens), and whether your experience sounds lived or read. One concrete detail — an actual hold name, an actual process parameter — outweighs a paragraph of generic method. With that lens, the ten:
Invoice processing & holds
1. "Month-end. Dozens of supplier invoices are stuck unvalidated and users are escalating. Walk me through your first fifteen minutes."
The panel listens for: diagnosis before action — which holds, system or manual? Validation process scheduled or run ad-hoc? Period status? Any recent change to invoice options or tolerances? Candidates who open with "I'd re-run Validate Payables Invoice" have told the panel they debug by retrying.
2. "A three-way-matched invoice shows a quantity-received hold, but the receipt exists. What now?"
The panel listens for: whether you know where matching actually happens — PO shipment level, receipt routing, tolerance setup — and whether you check the receipt's processing status versus its mere existence. Bonus signal: mentioning how you'd confirm which match approval level the PO uses.
3. "The client demands that no one can release a specific hold type manually. Can you make that happen?"
The panel listens for: awareness that hold-and-release authority is controllable, and the instinct to ask why — because a policy answer (segregation of duties, audit) matters as much as the setup path. Saying "yes" instantly without the governance angle reads junior.
Payments
4. "Your Payment Process Request selected 400 invoices but paid 380. Twenty vanished. Where did they go?"
The panel listens for: the systematic sweep — validation failures, missing bank details on supplier sites, currency/payment-method mismatches with the PPR criteria, invoices needing approval, pay-through dates. Naming even three of those calmly signals real PPR scar tissue.
5. "The client wants one PPR to pay from three business units with different banks. How do you set that up — and what do you warn them about?"
The panel listens for: cross-BU payment awareness (service provider relationships, bank-account access) and — the senior tell — a warning: reconciliation complexity, approval routing, who owns failures. Solutions plus consequences is the pattern panels reward.
Accounting & close
6. "AP period won't close. Tell me your checklist."
The panel listens for: the real blockers in order — unaccounted invoices/payments, incomplete payment files, unvalidated invoices, then the sweep decision (what moves to next period and what must not). Knowing that a sweep is a business decision, not a button, is the difference between operator and consultant.
7. "A prepayment was applied to the wrong invoice and the period is now closed. The controller is watching you. Go."
The panel listens for: composure and sequence — unapply/reverse in the open period, the accounting impact of each step, and communicating the audit trail to the controller. The scenario is 50% technical, 50% "how do you behave near an angry controller."
The 2026 layer: automation & AI agents
Panels increasingly bolt an automation angle onto AP scenarios — because clients are asking about Oracle Fusion AI agents and intelligent document processing. Two shapes we're seeing:
8. "The client wants AI to resolve invoice holds automatically. Which holds would you let it touch — and which never?"
The panel listens for: segmentation instinct — high-volume, rule-bounded holds (variance within tolerance, missing minor data) are automation candidates; judgment holds and anything with fraud surface stay human. Mentioning a human-approval threshold and a baseline-month measurement marks you senior. Full breakdown in our
AI agents field guide.
9. "Supplier invoices arrive as PDFs by email. Describe the future-state process you'd propose."
The panel listens for: whether you know Fusion's document-recognition capabilities exist and where the humans stay in the loop (exceptions, first-time suppliers, low-confidence extractions). Proposing 100% automation is a red flag to the panel, not a flex.
The one that isn't about Payables at all
10. "Tell me about a time an AP go-live went wrong because of something you missed."
The panel listens for: a real story — which means one concrete, unflattering detail (the actual missed config, the actual date it blew up) and what changed in your checklist afterwards. A story where nothing was your fault fails. A story with no specifics fails worse. This is the question
The Skeptic exists for.
How to practice these (reading is not practicing)
Knowing these ten shapes gets you to the door. What decides the interview is whether you can survive the follow-up chain — the second and third question that probes your first answer. That can't be read; it has to be rehearsed against something that pushes back.
Run this exact drill against The Panel.
Our AI interviewers run scenario chains like these — then score your answers the way a real panel hears them. First drill free, no signup.
Face the Panel — free →
Updated July 2026 · Scenario commentary reflects real hiring-panel experience from a working Oracle ERP consultant. Also read: the full Fusion Financials interview guide and the AI agents field guide.