Money
Edit approval for documents
When a cashier needs to change an issued document, Fixmo raises a request rather than applying the edit. An admin or manager approves it from their own account, or by typing their security PIN on the cashier's screen. Both the before and after state are stored.
What it does
Issued documents are the shop's record of what was agreed, so letting anyone edit them quietly is how disputes become unwinnable.
An admin or manager edits directly. A cashier raises a request, which holds the proposed change until someone senior looks at it.
Approval can happen two ways. The approver signs in themselves, or they stand at the cashier's screen and type their security PIN. The PIN holder is treated as the authority, not the cashier who is signed in.
Whichever route was used is stored on the request, alongside the state before the edit and the state after it.
A request also remembers which version of the document it was written against. If the document moves on before approval, that is detectable rather than silently overwritten.
How a request travels
- 01
Raised
A cashier proposes the change. Nothing is applied.
- 02
Reviewed
An admin or manager sees the request and the reason.
- 03
Approved
From their own account, or with their PIN on the cashier's screen.
- 04
Applied
The edit lands, with the before and after state stored.
Every capability
| Direct edit | Admins and managers edit without a request |
|---|---|
| Request | Raised by a cashier, holding the proposed change |
| Reason | Recorded on the request |
| Approval by account | The approver signs in and approves |
| Approval by PIN | The approver types their PIN on the cashier's screen |
| Authority | The PIN holder is the approver, not the signed-in cashier |
| Stored | Method used, before state and after state |
| Rejection | With a reason, and nothing is applied |
| Version check | The request remembers the document version it was written against |
Questions
Can a cashier approve their own request?
No. Approving requires the approve permission, and the PIN route checks the PIN holder's permissions rather than the signed-in user's.
What if the document changes while a request is waiting?
The request records the version it was based on, so a stale edit does not overwrite a newer one unnoticed.
Is the original state kept?
Yes. Both the state before the edit and the state after it are stored on the request.