Pay cycles and periods

Everything in InstructorHUB is organized around pay periods: hours are generated for a period, reviewed for a period, and paid for a period. Your pay cycle is how long each of those periods is, and setting it to match how you actually pay your team means the right hours always fall into the right run without you having to line them up by hand.

You can pay on one of three cycles. Weekly periods run Monday to Sunday. Monthly periods run from the first of the month to its end. Fortnightly periods are fourteen days long, and because a fortnight does not line up with the calendar on its own, you set an anchor date that tells InstructorHUB where one fortnight ends and the next begins. Once that is set, every fortnightly period falls into place from it. Whichever cycle you choose, the periods are contiguous and never overlap, so every day belongs to exactly one period and nothing is paid twice or missed.

The date on an entry is what decides which period it belongs to, which is why the date you or your staff enter when logging hours matters. A class taught on the last day of a period is paid in that period; the same class a day later falls into the next one. This is also why the importer and the schedule are careful about dates: they are what sort your hours into the correct run.

If you change your pay cycle, the change is made safely rather than immediately. A new cycle takes effect at the next period boundary under your current one, so the period you are part-way through finishes cleanly on the old cycle before the new one begins. That keeps your history intact and avoids a half-length or overlapping period at the switch. Once your periods are set, running pay for one is covered in Run a pay period.