Pay periods
A calendar week can be handy, but it is not always the period your pay follows. When work runs from the middle of one month into the next, or a client pays on a different schedule, adding dates by hand invites mistakes.
HoursKit groups shifts around the pay period you choose so the window on screen matches the one that matters.
Pay periods
Organize hours around the weekly, biweekly, semimonthly, or monthly pay cadence that matters to each job.
Set a weekly, biweekly, semimonthly, or monthly pay schedule and anchor it to the right date. Each job can keep its own schedule when an employer pays every two weeks while freelance work follows a monthly cycle.
The current pay period then has a defined beginning and end, even when it crosses calendar months.
A pay-period view gathers the completed work, hours, and estimated earnings that fall inside the selected range. Open individual entries to check a break, change a time, or confirm the job they belong to.
That makes the period a working space for catching a missed shift before it becomes a question on payday. It also prevents the first few days of a new period from being mixed into the last few days of the previous one.
Rates, currency, overtime settings, special-day rules, and paid status stay attached to the relevant work, so you can see why the period total looks the way it does.
A regular paycheque and a separate contract remain distinct without requiring separate apps or duplicated tracking.
As the period closes, the shifts, paid status, and estimate are already gathered in one place. You can check the days at the boundary before the next window starts.
If you later need a timesheet for an invoice or personal archive, its scope is already defined by the pay period you have been following. That keeps the close of a busy cycle from becoming a separate sorting task.
Related pages
Organize hours around the weekly, biweekly, semimonthly, or monthly pay cadence that matters to each job.
For iPhone and iPad