Why hours are approved before they are paid

The essentials

Overview

Orbit will not let a pay run leave while a timesheet in that period is still open or waiting on a manager. It is refused at the moment of export, not hidden on the screen, so there is no way around it and no way to forget it.

Anything that does not match the roster is marked for you — a late start, a long break, a shift that ran over. It is marked so you look at it, not so anybody is told off; approve what is right and correct what is not.

Before you start

You need approval access for the store. Read the request details rather than relying on a summary count.

Step by step

1. Hours become pay only after approval

   Orbit will not let a pay run leave while a timesheet in the period is still open or waiting on somebody. That is a floor, not a preference — it cannot be switched off.

2. Approve today’s hours

   Anything that does not match the roster is flagged so you look at it rather than hunt for it. Approve what is right; fix what is not.

3. Where approved hours land

   The pay period view fills up as you approve. When nothing is left open, the period is ready to pay.

4. Approving is quiet

   Approving somebody’s hours does not ping them — there is nothing for them to do about it. What Orbit does tell people about is set by your business.

   Review the choices available for your organisation in Orbit.

What to check

If you need more help

If an action is unavailable, check your permissions and whether someone else has already reviewed the item. Do not approve incorrect hours just to clear a list.