Platform · Approvals & Budget

Approval, to the right person, with a reason

Sequential approval steps by amount, company and budget usage; overruns become visible, owned and traceable.

ONY-01

Approval inbox: pending requests, document and amount

What it does

From request to decision, with a trail

The tools of approvers and budget owners, on one screen.

ONY-02

Approval policy list: document type, amount range, company and budget band

Approval policies

Policies by document type, amount range and company; sequential steps in each policy.

Manager chain

The approver can be a role or the requester’s manager and their manager; the chain is fixed when the request is made.

Segregation of duties

The requester can’t decide their own document.

Decisions with reasons

Approve, reject and return with reason codes; a return goes back to the previous approver or to invoice coding.

Approve from your phone

Approvers also decide from the Hadron Me approval inbox; history and reasons are visible.

ONY-03

Supplier invoice budget position: plan, actual, commitment, this invoice and remaining

Budget usage bands

The same amount is routine in an ample budget and a senior call in a full one: policies can also be chosen by budget usage %, with a mandatory reason on overruns.

How it works

Five steps from request to decision

Every decision stays with who, when and why.

1

Request

The document goes for approval the moment it is saved.

  • Purchase orders, sales orders, supplier invoices and leave
  • No goods receipt against an unapproved order
  • An unapproved invoice isn’t posted
ONY-04

A purchase order awaiting approval

2

Routing

The policy determines the approver.

  • Amount range, company and budget usage band
  • A role or the requester’s manager chain
  • The next step opens when the previous one is approved
ONY-05

Policy form: steps, approver and conditions

3

Decision

Approve, reject or return, with a reason.

  • The requester can’t approve their own document
  • The reason code is picked from a list
  • From the web or from Hadron Me
ONY-06

Decision window: decision and reason

4

Overrun

A budget overrun doesn’t block the invoice; it escalates.

  • The overrunning request goes to a higher approver
  • A reason is mandatory to approve an overrun
  • Usage % is fixed at request time
ONY-07

A request escalated because of an overrun

5

Trail

The decision history is never deleted.

  • Approver, time and reason of every step
  • History of returns to invoice coding
  • Budget revisions logged with old and new amounts and a reason
ONY-08

Budget revision history: old and new amount, reason and linked request

FAQ

About approval workflows

The most common questions before going live.

Purchase orders, sales orders, non-PO supplier invoices and leave requests. Policies are defined by document type, amount range and company and contain sequential steps.

At each step the approver can be a role or the requester’s manager and their manager. The manager chain is resolved from the employee record and fixed at request time; later org changes don’t move an open request.

No. The requester can’t decide their own document; this rule applies to every approval regardless of policy.

The invoice isn’t blocked; an incoming invoice is a liability that already exists. The overrunning request escalates to a higher approver who must give a reason. Budget usage % is fixed at request time, so the overrun record isn’t lost even if the budget is raised later.

The approver returns the invoice to coding with a reason; the chain resets and the corrected invoice goes for approval again. The return history is never deleted.

Yes. From the Hadron Me approval inbox they see requests, review history and reasons, and decide.

See Hadron with
your own data

In a 30-minute demo, we set up your processes on Hadron together.