The missing invoice: an FDE finance operations simulation
Reduce invoice matching work. The pilot may create draft matches; payments and bank-detail changes stay outside its authority.
Cedar Supply is a fictional customer. Your contact is Elena Ruiz, accounts-payable lead.
Reduce invoice matching work. The pilot may create draft matches; payments and bank-detail changes stay outside its authority.
Your first conversation
Each weekly batch takes us 6.5 hours. The sponsor says automate everything. Most of my time goes on missing receipt evidence, not typing fields.
Evidence to inspect
Weekly batch: Exact matches, partial receipts, credit notes, and disputed quantities.
Authority: Elena accepts draft matching. No permission has been granted for payments.
Bottleneck: Missing receipt evidence creates most of the exception work.
Five decisions in the engagement
- Discover: Scope an outcome and its authority before making a delivery commitment.
- Connect: Use business identity and durable state to reason about repeated operations.
- Evaluate: A correct extraction does not prove a correct business result.
- Recover: Establish destination state before replaying a business operation.
- Hand off: Transfer operating capability and define what requires another engagement.
Delivery gates
- Finish five decisions within 14 simulated days. There is no real-time timer.
- End with customer trust of at least 60 and reliability of at least 70.
- Recover the incident and demonstrate handoff to an owner and backup.
- A smaller supported service or controlled pause can count as a successful delivery.
- Only the best result for each mission contributes to campaign XP.