The walkthrough
78.7 seconds. Captions are burned in; an
.srt and .vtt sit beside the file.
The friction, as reported
“Because some companies have more than 1 directors/managers, so this feature will improve users’ workflow in approving the bills within Xero.”
Verbatim from the Xero Product Ideas board. Reproduced as a contiguous extract and checked against the harvested record.
What the walkthrough shows
- A second level puts six bills in a state that had no name.
- Level one approved on 14 July. Level two needs a director.
- Awaiting payment has no status column to hold the new state.
- It borrows the planned date cell instead.
- Awaiting payment is the number people run the business by.
- It no longer covers 35,405.00 that is neither pending nor payable.
- 48 bills were approved yesterday under the old single rule.
- Require re-approval stops the payment run dead.
- Leave as approved puts a hole in the control.
- Neither button is styled as the answer.
- Unapprove is already accepted and it ships before this.
- With two levels it has two destinations and no default.
- The chain records who approved what, and when.
- There is no audit trail report for it to appear in.
- 48 bills still grandfathered. Neither button pressed.
The assessment
The constraint.
48 bills already approved under the old rule, and no clean way to treat them.
The audit report this control depends on has not been built either.
The reasoning
Implementable, and genuinely valuable to the organisations that need it. It disturbs four things, in order of severity.
Already-approved bills. No migration path is clean. The organisation must choose between stopping the payment run dead and carrying a hole in the control from day one. Neither button is the answer, and the mockup styles neither as one.
Unapprove is already Accepted and ships first. The moment a second level exists it has two destinations and no default.
The audit story the feature depends on is Not in pipeline. Shipping the chain without the report ships the appearance of a control rather than a control.
The role model and the status enum are read by every filter, report and API consumer. A new state that has no column to live in borrows the planned-date cell, and the Awaiting Payment total silently stops covering 35,405.00 that is neither pending nor payable.
This idea has the smaller vote count of the two bills ideas in this selection and by far the largest change. That inversion is itself the finding, and the film does not smooth it over.