Four kinds of financial decision wait in one queue: expenses, payroll, commissions and advances.
They are together because the person deciding is usually the same person, and four separate lists is how things sit for a week.
What is in it
Expenses. Company spending and personal claims.
Payroll. A run waiting to be approved before it goes out.
Commissions. Earned amounts awaiting sign-off.
Advances. Money requested ahead of payroll.
The queue filters to any one of them, or shows everything.
Working it often beats working it carefully
The failure mode of an approval queue is not carelessness, it is latency.
An organisation where approvals take a fortnight has people who stop claiming, managers who approve in batches without reading, and a payables figure permanently understated because half of it has not been submitted yet.
Twice a week, quickly, beats once a fortnight, thoroughly. The thoroughness that matters is on the few items that are material, and those are visible from the amount.
Approving well
Read the description, not just the amount. The amount tells you whether it is material. The description tells you whether it is right, and a well-described small expense is more likely to be correct than a vague large one.
Check the receipt is there on anything above whatever threshold your organisation cares about. It is the only moment anybody will.
Reject with a reason. A rejection with no explanation produces a resubmission of the same thing, usually within the hour.
Decide, do not defer. Everything here is somebody waiting, frequently for their own money. A queue worked twice a week is a queue that works; one worked when it gets uncomfortable is a queue people route around.
Filtering
The queue shows everything by default and filters to any one kind.
The habit that works is filtering rather than scrolling. Expenses and payroll want different attention and different amounts of time, and working them as one undifferentiated list means the payroll run gets the same three seconds as a taxi receipt.
Multiple levels
Where your organisation requires more than one approval, an item moves to the next approver rather than being finished by the first.
Worth knowing in both directions. As an approver, your approval may not be the last one, so approving is not the same as releasing. As a claimant, an item can sit approved-by-one and still be waiting.
The policy for who approves what is set elsewhere, in the approval policies configuration, and this surface applies it rather than defining it.
Payroll is different
A payroll run approves as a whole, not line by line, and it is the one item in this queue where the consequence of approving carelessly is largest.
The Finance view of payroll is exactly that: an approval view of a run prepared in People HQ. It is not a second payroll engine and nothing is calculated here.
Advances
Money paid ahead of the normal cycle.
These deserve more attention than their size suggests, because they are a genuine loan and the recovery is the part that gets forgotten. Approve knowing how it comes back.
Working it in five minutes
Filter to expenses first. The largest count, the smallest individual consequence, and the group most affected by delay.
Go oldest first. Somebody has been waiting.
Anything you cannot decide in fifteen seconds, ask about rather than leaving. A one-line question moves it; leaving it does not.
Do payroll deliberately and separately. It is not a queue item to clear, it is a decision, and mixing it into a fast pass is how a mistake gets approved.
Commissions and advances
Two smaller categories that behave differently from expenses and are easy to wave through.
A commission is earned money and the check is whether the calculation is right, which usually means checking the deal it came from rather than the number in the queue.
An advance is a loan against future pay. The approval question is not whether the person needs it, it is whether the recovery is agreed and recorded. An advance approved without a recovery arrangement becomes an awkward conversation months later.
For the person waiting
You can see where it is. The state on your own expense says whether it is with somebody and who.
Chase after two days. Approvers are not ignoring you; the queue is not on their screen unless they open it.
A rejection is not a judgement. Most are a missing receipt or an unclear description, and both take a minute to fix.
Where the policy lives
Who approves what, and how many levels are required, is configured in approval policies rather than on this screen.
That separation is worth knowing when something routes oddly. An expense reaching the wrong person, or reaching nobody, is a policy question, and changing it here is not possible by design: an approval route that individuals could adjust would not be a control.
What an approval means
An approval is a statement that the spending is legitimate and appropriate, not that the money is available.
That distinction matters when a queue is being worked quickly. The person approving is confirming the thing happened and should be paid; whether the organisation can afford everything approved this month is a separate question answered in cash flow.
The count is the point
The queue carries a number, and the number is doing real work.
An outstanding count that is visible is uncomfortable in a way that an old email is not, and that discomfort is what keeps a queue moving. An organisation where the count is routinely in the dozens has a routing problem rather than a diligence problem: too much is reaching one person, and the approval policy is where that gets fixed.
Why one queue matters
The alternative, which most organisations live with, is approvals arriving as email. They get skimmed, buried, and answered inconsistently, and nobody can tell you what is currently outstanding.
A single queue with a count on it is a small thing that changes behaviour, because an unread number is uncomfortable in a way an old email is not.
Did this answer your question?
No, ask a person