Finance asked for two things: a receipt the ledger has already paid must be refused, whoever is approving that week, and a report nobody on the team may approve must go to the CFO rather than come back unhandled. The pull request does both inside the chain. It is approved by one reviewer and waiting for yours.
In staging, a duplicate hotel receipt was approved and paid twice, and a 12,000 equipment order came back “approved by CFO” although the CFO has never seen it. Approvals carry the approver’s name into the audit log.
Reproduce
A duplicate 300 travel report comes back EX-31: approved by travel desk; checked travel desk. A 12,000 equipment report comes back approved by CFO.
Acceptance criteria
- A duplicate is refused before anyone on the roster sees it, whatever the roster and whoever is away: EX-31: refused as a duplicate; checked -.
- A report nobody on the roster may approve is escalated, not approved: EX-32: escalated to the CFO; checked travel desk > Sam > Dana > finance, and checked - when everyone is away.
- Nobody is recorded as approving or refusing a report they did not decide.
- CHAIN-101’s and CHAIN-102’s rules still hold: roster order, limits, absences, the travel desk first and its cap.
Notes
- Each case gives one roster, then submits each report in turn; the lines print joined by “ | ”.
- Keep the names and signatures of submit, routeExpense and report. The checked list names the roster members a report visited.