Payroll for a team where most people never sign in to anything
Attendance in a notebook, salary on a calculator and an advance somebody remembers differently is not a small problem. It is the one that ends up in an argument.
In short
This is an employment record for every person who works in the restaurant, whether or not they have a login: shifts and weekly offs per person, attendance marked once a day, leave balances that work themselves out, and versioned salary structures. A month's pay is calculated from that attendance under rules you set, with a payslip for each person. Statutory contributions and income tax are not calculated. It is priced as an add-on, per branch.
- No login needed for a person to be on the payroll
- One attendance screen a day, per branch
- Salary structures versioned, never overwritten
- Advances that recover themselves month by month
The record is of the person, not of a user account
Every payroll product assumes the employee logs in. In a restaurant that assumption is wrong for most of the building — the kitchen, the cleaners, the delivery riders. So the employment record here exists independently of whether anybody ever gave that person a password.
Each person gets their own shift and their own weekly off, because a kitchen cannot all rest on Monday, and a branch keeps its own holiday list.
- An employment record for everybody, login or no login
- Shifts and weekly offs set per person
- Branch holidays, kept per branch
- A leaving date in the future keeps somebody on the roll until the day passes
Attendance in one pass, once a day
The roster is one screen: everybody on the roll for that branch, each marked present, absent, half day, on leave, on their weekly off or on a holiday. That is deliberately the entire interaction, because a system that takes twenty minutes a day does not get used past the second week.
Leave types carry balances that derive themselves from what has been taken, so nobody is maintaining a parallel count of how many days somebody has left.
Pay worked out from exactly that
At the end of the month the pay comes from the attendance that was recorded — under rules you set as named options for your own restaurant, so the arithmetic matches how you have always done it rather than how a product assumed you should. A payslip is produced for each person, and payslips can be printed in bulk.
Salary structures are versioned rather than edited. A change from this month does not reach back and alter what last month's payslip said, which is the only way a payslip is worth anything as a record.
- Basic, allowances and deductions, versioned per person
- A monthly run with a preview before anything is committed
- Payment recorded per person, with partly-paid derived rather than typed
- One-off bonuses, deductions and dated review notes
- Advances recorded once and recovered automatically
Who can see and who can approve
Payroll is split into recording attendance, managing payroll and approving it, so the person who marks the roster every morning is not necessarily the person who releases the money. A staff member with a login can see their own pay and nobody else's, and every money-affecting change is written to the audit log with a name against it.
Statutory compliance — PF, ESI, professional tax, TDS — is out of scope. This calculates and records what you pay; it does not file anything.
Priced as an add-on, and named as one
Everything to do with selling, serving and settling up is in the base subscription. Staff and payroll is not: it is priced per branch, on top, and it is the only capability on this site in that position other than additional branches. Both prices are on the pricing page rather than saved for a call.
Questions about this
More general questions — price, commission, data, multiple outlets — are answered here.
Do my kitchen staff need a login for this to work?
No, and that is the whole design. Most of a kitchen never signs in to anything, so the employment record belongs to the person rather than to a user account. Somebody with no login still has a shift, a weekly off, a leave balance, a salary structure and a payslip.
Does it calculate PF, ESI or income tax?
No. It works out the month's pay from attendance under rules you set, including allowances, deductions, advances and one-off bonuses or fines. Statutory contributions and anybody's income tax are not calculated, and that stays with your accountant.
How does attendance actually get recorded?
One screen a day. Everybody on the roll for that branch is listed, and each person is marked present, absent, half day, on leave, on their weekly off or on a branch holiday. Shifts and weekly offs are set per person, because a kitchen cannot all rest on Monday.
What happens to an advance somebody asks for before a festival?
It is recorded once and then recovers itself out of the following months' pay, without anybody having to remember. Salary structures work the same way: a change is a new version rather than an edit, so last month's payslip still says what it said when it was issued.
Can a staff member see their own payslip?
Yes, if they have a login — there is a screen that shows a person their own pay and nobody else's. It is available on the basis of who they are, not on a permission somebody has to remember to grant.
Is this included in the subscription?
No — staff and payroll is priced separately, per branch. It is the one capability on this site that is an add-on rather than part of the plan, and the price is stated on the pricing page.
Read next
Bring last month's muster to the demo.
Show us how you record attendance and how you work out pay today, and we will tell you honestly whether this is worth the add-on for you.
Thank you — we've got it.
Our team will call you back shortly to set up your demo.