The Hour bank lets a collaborator's categorized hours (overtime, night, holiday, etc.) accumulate into a balance instead of always being paid out in payroll. That balance is later compensated as time off or as payment, and it works together with Time Off to manage time-off requests against that balance.
The hour bank is turned on at the community level. While it's off, no time policy can use it and the feature doesn't exist for collaborators.
- Go to admin.humand.co → Attendance Control → General configuration.
- Click Hour bank settings.
- Turn on the Hour bank usage toggle.
When you turn it on, you define two rules that apply equally company-wide:
• Reset frequency: how often the counter returns to zero and accumulated hours become expired (weekly, monthly, quarterly or yearly). You can turn off the reset with No bank reset so collaborators and managers handle accumulated time manually.
• Accumulable hours limit: the maximum number of hours that can accumulate. Once exceeded, the expired and over-the-limit hours rule applies.
For expired or over-the-limit hours, you choose whether the system automatically settles them (included in the hours-to-pay report) or discards them (not included in reports).
Changing the limit or the cycle doesn't trigger retroactive closings or recalculate hours already credited: the new criteria applies starting the next period.
The bank is configured hour by hour within each time policy, under Hour management. There, you turn on the relevant hour category and choose its compensation method: Payroll payment or Hour bank.
The same category can combine both methods depending on how many hours were worked: you define ranges by number of hours, and each range has its own destination. The platform shows the ranges as a proportional bar so you can see at a glance how the category is split.
If the bank is turned off at the community level, the ranges that pointed to the bank are removed from the policies and only the payment ones remain. If a category only had the bank as its method, it's turned off.
Hours enter the bank when the collaborator's categorized hours are calculated, meaning once the hour is approved (manually or automatically). Each time hours are credited, the corresponding range is evaluated and, if the destination is the bank, the accumulable limit is checked before adding them.
The balance is also deducted when the collaborator didn't work the scheduled time: when time off is requested from Time Off against an assigned shift, the scheduled time for that shift is deducted.
Every movement is logged with date, hour type, and reason, so any specific case can be audited.
The balance can go negative if the collaborator's policy allows requesting time with a negative balance.
When you turn on the Hour bank, Humand automatically creates a policy type and a policy in Time Off. With that policy, you define the request rules and whether the collaborator can request the time off themselves or only their manager can.
Hours are reserved when the time off is requested, not when it's approved: they're locked so they can't be spent twice while the request is pending. The balance the collaborator sees doesn't drop because of a pending request; what drops is what's available for new operations.
With the bank on and the categories configured, each collaborator sees their balance and movement history, and their manager can compensate it as payment or as time off from the team's timesheet.