Decide HR Requests In My Approvals

Across Veona HR, every request that needs a sign-off — a leave request, a shift swap, an overtime claim, an expense, a job requisition — flows through one shared approvals engine. When a request reaches a stage that you own, it lands in your personal inbox. My Approvals is where you read those requests and decide them. Each decision is sealed with your eSign PIN (eSign PIN = your personal 6-digit electronic-signature code), so an approval is a real, permanent, signed act — not a casual click.

You decide what routes to you, and only what routes to you. The same screen also shows requests that have been delegated to you while a colleague is away, clearly flagged so you know whose authority you are exercising.

Who / when: a line manager, an HR manager, or any approver or delegate, whenever a request is waiting on their decision. We’ll follow Mrs. Bello, a department head, clearing her inbox at the start of the day.

The main path

1. Approver — open Human Resources → My HR → My Approvals. Every request currently waiting on you is listed, including any that are delegated to you. Each card names the request type, who raised it, a short summary and when it was submitted.
2. Approver — read a request. The card lays out the full approval path under “Stages” — each stage’s approver and its current decision (Pending, Approved, Rejected) — and marks which stage is “current”. If a card carries a “Delegated to you by …” note, you are deciding on that person’s behalf.
3. Approver — to approve, select “Approve” on the request. A signing dialog opens. You may add an optional note in “Reason” (for example, “Approved, cover arranged”), then enter your 6-digit code in “eSign PIN” and select “Sign & Approve”.
4. Approver — the request leaves your inbox. For a sequential chain, it advances to the next approver; once every stage has approved, the request is fully approved and the underlying record updates itself (the leave balance is debited, the shifts are swapped, the expense moves to reimbursement).

Note

The signing dialog reminds you that the decision is electronically signed with your 6-digit eSign PIN and permanently recorded. That signature is bound to this exact decision and written to the tamper-evident audit trail — who decided, what, when, and why.

Tip

Use the “Reason” box even on approvals when context helps the next person — “Approved, cover arranged” or “Within budget” tells the requester and the next approver why you said yes, and it lives on the record forever.

Other ways this goes

If you reject the request

1. Approver — select “Reject” on the request, then enter a reason in “Reason” — this is required. A rejection without a reason is refused, so the person who raised it always learns why.
2. Approver — enter your eSign PIN and select “Sign & Reject”. The whole request is rejected at once: in any chain, a single rejection at any stage stops it dead, and the underlying record (leave, swap, expense) is returned to its requester unfulfilled.

When the request needs several approvers in order

1. First approver — you approve your stage as above. The request does not complete; it moves to the next named approver in the sequence, who now sees it in their own My Approvals.
2. Next approver — they approve in turn. Only when the last stage approves does the request finalise and the record update. Any approver along the way can reject, which ends it immediately.

When the request needs several approvers at once

1. Each approver — a parallel request appears in every required approver’s inbox at the same time. You each decide independently.
2. The engine — the request finalises as approved only when all required approvers have approved. The first rejection from anyone finalises it as rejected. Your decision is recorded the moment you sign; the request simply waits on the others.

If you are not actually the approver

If you open a request by some other route and try to decide it when you are neither its stage approver nor an active delegate, the engine refuses with a “not the approver for the current stage” message and records nothing. Seeing a request is never the same as being able to decide it — authority is checked again at the moment you sign, every time.

When your inbox is empty

If nothing is waiting on you, My Approvals simply says you have no approvals pending and that new requests will appear here. There is nothing to do; check back, or use “Refresh” after a colleague tells you they have submitted something.

What happens next

Every decision you sign is final and audited, and it flows straight back to the request it belongs to — a balance is debited, shifts are exchanged, an expense advances to payment, or a requisition opens for posting. The requester is notified of the outcome, and the signed decision (with your reason) stays on the record permanently. Your inbox shrinks to exactly what still needs you.

Follow the trail

• Previous: Configure Approval Chains And Delegations · Request Leave And Track My Balance · View My Timesheets And Clock State · Submit And Track My Expense Claims
• Related: Configure Approval Chains And Delegations · Request Leave And Track My Balance · View My Timesheets And Clock State · Submit And Track My Expense Claims