This page concerns Ardoise School in the OHADA scope, subject to enabled modules and permissions. School, school accounting and payroll are not offered in Austria. Check local requirements; CountryConfig does not certify compliance.
This module is part of Ardoise Enterprise - see Subscription and pricing. The
staff list itself (adding people, roles) stays free; it is the payroll cycle that is Enterprise.
Permanent and hourly-paid staff
Every member of staff has a contract that is either permanent (fixed monthly salary) or hourly-paid (paid by the hour). For hourly-paid staff, only confirmed/approved hours count towards the payroll calculation - an hour that has been entered but not yet validated never enters a payroll cycle.No staff member without a contract
A contract is created automatically for every member of staff, whatever route they arrive by: the founder’s “create staff access” screen, a provisioned account, or a candidate accepted through recruitment. The creation form asks for the employment terms (contract type, salary) while the person doing the hiring still knows them. The salary can be left empty until it has been decided - but payroll then refuses to generate a payslip for that contract, rather than producing a zero payslip. An unset salary is a pending decision, not a salary of zero. The same rule applies to an hourly-paid contract with no hourly rate.Payroll cycle
Payroll separates three responsibilities: the accountant prepares, the founder decides, the accountant executes. The person who prepares a payroll run cannot authorise it alone.1
Hours entry
An hourly-paid member of staff (or whoever enters on their behalf) records the hours worked.
2
Confirmation
Hours are confirmed/approved before they can enter a payroll cycle.
3
Preparation
The accountant generates the payroll run for the period.
4
Decision
The founder validates the run: they decide who is paid and who is not.
5
Execution
Once the run is validated, the accountant pays each payslip and its accounting entry is posted.
The founder can delegate the decision right to a named person (a director, for example). It is a
permission granted to a person, not to a role: granting it to one director gives nothing to any other.
Everyone sees only the buttons that match their authority: the validate button appears only for a
decider, the pay button only for a payer.
Paying a salary
A salary is paid in one of three ways, chosen per person rather than per cycle - a school can transfer to its teachers, pay one member of staff by mobile money and another in cash, all in the same cycle:Cash
Handed over at the school.
Mobile Money
MTN MoMo or Moov Flooz, to the number held on the staff record.
Bank transfer
To the account held on the staff record.
Salary advances
A member of staff can request a salary advance. The founder (or a delegated decider) approves or rejects it. Once approved, it is paid out - in cash, by mobile money or by bank transfer - and the payout is recorded. It is then deducted automatically from the next payslip.Only an advance that has actually been paid out is recovered from a payslip: nobody has salary
withheld for money they have not received.
Leave
Leave requests follow a simple circuit: request, approval (or rejection), balance tracking.The social contribution (CNSS) and tax withholding (IRPP) rates applied to payroll are configurable per school, but the values shipped are only starting values. Check them with your accountant before relying on them for an official filing.