The month's salaries, and the cover nobody was paying for

Employments carry the salary, the run creates the payslips, and the whole month posts to the books in one step.

Substitutes are the part every school does out of a drawer: a teacher is ill, someone covers four hours, and the payment happens outside the payroll and outside the accounts. Cover is recorded with a start, an end and an hourly rate; the hours and the amount are worked out for you, and the month's salary run picks them up — a payslip of their own for a substitute with no employment, and an addition for a member of staff who also covered.

For the office

What a secretary, a bursar or a head of year can do with it.

  • Monthly salary runs per organization, with payslips
  • Substitutes paid by the hour: who covered, for whom, from when to when, at what rate
  • Cover is never paid twice, and never forgotten
  • Everything posts to the books as it is run

For whoever has to approve it

Where the data sits, who can read it, and what it connects to.

  • Payroll is behind its own module permission — a registrar with full student access sees none of it
  • Salary figures are a restricted field, not merely a hidden screen

Questions we are asked

Does this file our payroll taxes?
No. It produces the run, the payslips and the postings; statutory filing stays with your payroll bureau or accountant, who can take the export.
Can staff be paid from different entities?
Yes — an employment names the organization that pays it, and each run is per organization.

See it with your own school's data

Sixty days free, no card up front — or open a ready-made demo school and click around it first.

Read next