An approval request records that a decision is needed. Approval records the authorized decision. Rejection records a different outcome; neither can be inferred from a user opening the record or changing its quantity. Keep the request state separate from operational progress.
In this model, a matching threshold rule is required. The acting role must have approval permission, match the configured approver role, remain within its amount limit and include the transaction’s subsidiary. Administrator isn't an automatic substitute for a rule assigned to Controller. A pending or rejected order can't be received, fulfilled or billed through this route. Approval makes the supported next action available but doesn't create the physical movement itself. Production workflow histories and user assignments have more detail than this local role-based state model.