TRANXACT.AI Ajuda

Approving on behalf and reassigning approvals

Since release 20261106f Requisition Approvals and PO Approvals have Approve, Reject and Reassign. An administrator, or a role given Approve on Behalf and Reassign Approvals, can decide a level that is not theirs, recorded as on behalf of the approver, or move it to someone else. Nobody approves what they raised, and an approver who has left counts as away.

Use this when a requisition or purchase order stays at one level because its approver has left, or is away for a long time and handed nothing over. Approvers still decide their own approvals from My approvals, as before.

Who can do it

  • An administrator.
  • Anyone whose role is given Supply Chain › Approve on Behalf and Reassign Approvals (Change) on Administration › Roles.

You have to give the right to a role by name. A role that can change everything in Supply Chain does not get it automatically. If you want a procurement head to unblock approvals without making them an administrator, give their role this right.

Approving or rejecting on behalf of an approver

  1. Open Supply Chain › Procurement Control › Requisition Approvals, or Supply Chain › Requisitions & Orders › PO Approvals.
  2. Find the signature with status pending. Levels are decided in order, so the lowest pending level of a document must be decided first.
  3. Press Approve (add a comment if you want) or Reject (a reason is required).
  4. If the level was not yours, it is recorded as decided on behalf of the person it was waiting on.
  • The record keeps who the approval was waiting on.
  • The approval trail on the document shows "approved on behalf of ... by ... on ...".
  • The Audit Log marks it.

You cannot approve a document you raised: one you requested, are the buyer of, or created. This applies to administrators too. Someone else has to approve it.

Reassigning a waiting approval

  1. On Requisition Approvals or PO Approvals, press Reassign on the pending signature.
  2. In Decided instead by, choose any active sign-in.
  3. In Why, give the reason. It is required and is kept in the approval history.
  4. Save. The approval moves to that person: it appears in their My approvals and disappears from the previous approver’s, and they are notified.

The approval trail shows "reassigned by ... from ... to ...: reason".

You cannot reassign to someone who raised the document, someone who has already signed it, someone whose sign-in is switched off, or someone who has left.

When an approver leaves: automatic escalation

An approver who has left (terminated in HRMS) counts as unavailable, just like someone on approved leave. If their sign-in is switched off and they have no employee record, they count as unavailable too. For each approval waiting on them:

  • If the Approval Level (or the PO rule) has Escalate at once when the approver is away, the approval escalates. If the level may be skipped, it goes to the next level. Otherwise it goes to the leaver’s manager in HRMS, or to the person or role the level names under Escalate to.
  • If the level has When the approver is unavailable, try set, it tries the backup approver, then someone with the same designation, then escalation, in the order listed.
  • This happens straight away when the employee is terminated, or their status is changed, on HRMS. It does not wait for the next escalation check. It covers purchase orders, requisitions and hiring requests.
  • If a level has no escalation set up, nothing moves on its own. Use Reassign.

Hiring requests: a Hiring rule on Approval Levels

Hiring requests are approved by the Approval Levels of their Hiring Approval Rule.

  1. Open Supply Chain › Procurement Control › Approval Levels and press New.
  2. Under Hiring rule, choose the rule (from HRMS › Hiring Approval Rules). Leave Requisition rule and Purchase order rule empty, because a level belongs to one rule only.
  3. Set the level number, who signs, and the amounts if you need them. Only at or above and Only up to are the annual cost of the vacancy.
  4. Save. HRMS › Hiring Approval Rules now shows Levels and Who signs (Approval Levels) for each rule. A rule with no levels says so.
  • If a hiring rule covers a request but none of its levels applies at that cost, Send for approval refuses the request and names the rule. Before this release the request was approved without anyone signing it.
  • Approve on a hiring request is only for a vacancy no rule covers. If a rule covers it, send it for approval and it is signed level by level.
  • While the company has active hiring rules, a request with no annual cost cannot be approved in one press.

To stop it happening again

On Approval Levels, turn on Escalate at once when the approver is away, or set When the approver is unavailable, try with a backup. See When an approver is unavailable: backup, same designation, escalation and the emergency route, and Handing over your approvals while you are away.