Planned, worked, and the norm
Three figures describe a person’s period before any overtime rule applies.
Norm hours is the yardstick. It comes from the person’s contract and their country’s working-time rules, not from anything they did. Overtime and undertime are measured against it.
Overtime and undertime
Overtime and undertime are two positive columns. Overtime/undertime is the same information as a single number: positive above the norm, negative below it. Use the pair for payroll, where hours owed and hours short are separate conversations, and the combined column when you only want the net position.
The period balances
Some overtime policies accrue over a multi-month window — a quarter, for example — rather than resetting every month. Three columns describe that window.
If nobody on the report accrues overtime over a period, the columns say so instead of repeating the monthly pair:
Period overtime and undertime are unavailable because nobody on this report accrues overtime over a period. Their period figures would repeat the monthly ones.
When a figure is unavailable
An empty hour cell is not always a zero. Begin distinguishes “we measured nothing” from “we refused to compute this”, and explains the refusal. You will meet these:- Not grouped by person — the calculator works one person at a time, so a position, location or label group has nothing to sum.
- A filter is applied — a norm covers the whole contract, so a filtered subset cannot divide it.
- The country of work is not supported — norm and overtime are unavailable. Scheduled and worked hours are unaffected.
- You cannot see draft shifts — norm, overtime and premium hours are unavailable, because each would count hours you cannot open.
- The person has left the workspace — calculated figures stop. Their shift count and recorded hours are unaffected.
Why a total may not equal the rows above it
This is the question that generates support tickets, so it is worth a minute. Hour totals are calculated. Break, count and time-off columns are summed. A calculated total is not the arithmetic sum of the rows above it, because policies and rounding apply to the calculation rather than to each visible row. Under a report whose totals differ from its records, Begin puts a Why totals differ button. Open it and you get one plain sentence per column that moved:Reported time shows 0:00. The records add up to 34:13. The rows list entries in every status. The hours count approved entries only.Under those sentences, Show the numbers opens the arithmetic: each column, what the records held, the adjustment, and the calculated result. The reasons you will meet:
None of these is an error. Each is a policy your workspace configured, applied where it belongs.
When nothing was adjusted, the panel says so plainly:
These hours match the records.
Rounding is applied once, to the total. Begin does not round each row and add the rounded numbers
up — that would drift. So a column of rounded-looking rows can legitimately add to a different
total than the one shown.
Charts read a different path
A chart block reads the source records directly rather than the hours calculator, and says so:These figures come from the source records, not the hours calculator, so they may differ from a table block over the same period.For payroll figures, read the table.
Next
Downloading a report
Decimal hours, and what happens when a report is too large.
Building a report
Sources, columns, and the record-versus-summary choice.
Still need help?
Contact support
Email the Begin team and we’ll get back to you.
Ask Begin AI
Open the AI assistant and get instant answers based on these docs.