Who approves what: configurable approval workflows inside AnooreHR

A leave request goes to the line manager, who is on leave. It sits in an inbox for nine days. The employee books a flight anyway, then cancels it.

An expense claim for 400,000 naira gets approved by whoever happened to be at their desk that afternoon. Nobody checked if that person had the authority to approve it.

A payroll run goes out before finance has confirmed the new hires were added correctly. The error is only caught when three people call HR asking why their pay is short.

None of these are dishonesty problems. They're workflow problems — no defined chain of who signs off on what, in what order, with what happens next if someone is unavailable. Spreadsheets and email don't enforce sequence. Approval workflows do.

What an approval workflow actually is

An approval workflow is a rule: "this type of action needs sign-off from these people, in this order, before it takes effect."

That's it. But the details matter:

• Which actions require approval — leave requests, expense claims, new hire onboarding, salary changes, payroll run execution, budget revisions, vendor payments, whatever your company decides needs a second pair of eyes.
• Who approves — a named person, a role (e.g. "Head of Finance"), or a level in the org chart (e.g. "employee's manager, then that manager's manager").
• In what order — single approver, or a chain where step two only opens after step one clears.
• What happens on rejection — sent back with a reason, or terminated outright.
• What happens on delay — depends on your configuration; the point of building the chain explicitly is that you can see where something is stuck instead of it disappearing into someone's inbox.

Once that rule exists, the system enforces it every time, for every employee, without anyone having to remember to check.

How it's built in AnooreHR

Approval workflows in AnooreHR are configurable per company, per action type. You are not stuck with one fixed chain for everything.

A small company might route all expense claims through a single owner-approver. A larger one might set:

Expense claims under 50,000 naira: manager approval only. Expense claims 50,000 naira and above: manager, then finance. Expense claims involving a new vendor: manager, then finance, then compliance.

Different thresholds, different chains, same underlying engine. You set the rule once in configuration; every employee who submits a claim that matches the rule goes through the same chain, automatically.

The same mechanism applies across modules:

HR actions. Leave requests, new hire onboarding steps, document changes, performance review sign-off — each can carry its own chain. A leave request might need only a manager. A termination might need manager, then HR, then a final sign-off before it's processed.

Finance actions. Budget revisions, vendor payments, journal entries above a threshold, payroll run execution — these carry more weight, and the chains tend to be longer. Payroll running is usually gated behind at least one confirmation step precisely because it moves real money to real bank accounts on a fixed date.

Because HR and finance sit on the same platform and the same ledger in AnooreHR, an approval chain that spans both — say, a new hire's salary needs HR confirmation and finance sign-off before the first payroll run includes them — doesn't require stitching together two separate systems. It's one workflow engine underneath both modules.

Where it shows up for employees

On the self-service portal, an employee submitting a leave request or expense claim sees where it sits in the chain — submitted, pending with [name/role], approved, or rejected with a reason. No more "did anyone see this?" messages to HR.

For approvers, pending items show up as a queue: what's waiting on you, how long it's been waiting, and one click to approve, reject, or comment. If you're not available, the chain doesn't have to freeze silently — you (or an admin) can reassign it before it stalls.

Where it connects to the AI assistant

AnooreHR's AI assistant can draft routine entries — a leave balance adjustment, a standard journal entry, a first pass at a budget line. It does not skip the approval chain to do it. The assistant prepares the draft; a human still approves it before it takes effect. That's a fixed rule, not a configuration option, for anything that moves money or touches a statutory filing. The workflow engine doesn't get bypassed because a draft came from AI instead of a person — it goes through the same chain either way.

What this replaces

If you're currently running approvals through email threads, WhatsApp messages, or a shared spreadsheet with a "status" column someone updates manually, the honest comparison is: those systems don't enforce order, don't show a clear audit trail of who approved what and when, and depend entirely on someone remembering to follow up. An approval workflow engine removes the "did they see it" uncertainty and gives you a record — useful when an auditor, a regulator, or your own finance team asks "who signed off on this."

Does AnooreHR handle this?

Yes, today, live for Nigerian companies on the platform. Configurable approval chains are available now across HR actions (leave, onboarding, performance review sign-off) and finance actions (expense claims, budget revisions, payroll run execution, journal entries), with per-action thresholds and multi-step chains you define in configuration — no code, no support ticket to change a rule.

On the roadmap: payroll and statutory compliance for countries beyond Nigeria ship as country profile packs on the same engine — approval workflows themselves aren't tax logic, so the workflow engine already runs company-wide regardless of jurisdiction, but full payroll processing outside Nigeria is not live yet. If you're outside Nigeria and want to know current status for your country, ask us directly.

Set up your approval chains and see the queue in action: start free at app.anoorehr.com/signup, or book a quick demo and we'll walk through your specific approval structure.

Related reading: Leave and time-off management in AnooreHR · Payslips and the self-service portal · One system for HR, payroll and finance — one ledger