Before attendance can be marked or salary calculated, the people have to exist in the app. This is that list.
Small businesses keep staff details in a phone: a number, a salary figure, a vague sense of when someone joined. It works until a salary is disputed, someone leaves owing an advance, or a sale needs attributing to whoever made it.
An employee record gathers it in one place, and everything else in this area reads from it — the attendance register, the payroll that follows, the advances taken against it, and the salesperson selected on a bill.
| Limit | Starter | Growth | Scale | Enterprise |
|---|---|---|---|---|
| Employee records | − | 10 employees | 100 employees | 500 employees |
With their details and their pay.
Against them, daily.
Which reads both.
What was paid, and when.
Staff records, the daily attendance register, and the salary that comes out of it. Pay is worked out from the attendance already marked, with advances and weekly offs accounted for, rather than from a separate calculation.
Attendance is a daily habit and payroll is a monthly one, so the value shows up at month end when the two meet without a spreadsheet in between.
All plans
Everything downstream of having the people on record.
Employee report · Employee attendance · Employee transaction
Every feature, by plan →No. An employee record is for attendance and payroll; a staff login is for access to the app. A person may have one or both.
Attendance, payroll, advances, and attributing a sale to the person who made it.
Yes, through the salary statement and the employee transaction report.
Attendance, payroll and attribution all start from the same list.
