Payroll · Human Resources
Collect the month once, from the records it already lives in.
From the records to the ledger, in five steps.
The month's inputs are on the records
The contract, the regime and the salary on the employee file. Approved absences from Time Off. Approved hours from Timesheets. Approved claims from Expenses. The bonus on the file, the car from Fleet. Nothing is typed a second time.
From the records to the ledger, in five steps.
The contract, the regime and the salary on the employee file. Approved absences from Time Off. Approved hours from Timesheets. Approved claims from Expenses. The bonus on the file, the car from Fleet. Nothing is typed a second time.
The file, the changes, the cut-off, the payslip, the cost.
What counts as a working day, who checks the month and where the cost lands are yours to set.
A file that is current
Regime, salary, car, vouchers: each field on the employee record carries the date it changed, so the month knows which value applies to which week.
What changed, as a list
The month's differences against last month, by person, so the check takes minutes and misses nothing.
Reminders before the cut-off
The Thursday before, the people with an absence still unapproved or a claim still open get one message, once.
The cost, by department
What the month cost against what was budgeted, per department, the day it is posted.
The same month, for a business that pays hours and one that pays salaries.
What adapts: what makes a working day (a shift on a site, a day at a desk), which inputs the month has (hours and supplements, or salary and bonus), which provider receives it and in what format, who checks it, and how the cost is split. Two businesses can run Payroll and disagree on every one of those.
A cleaning contractor with part-timers
Twenty people on regimes from 12 to 38 hours, hours read from the site timesheets, Saturday supplements by the rule you set, the sick certificate on the record. The month is hours, and it goes to the social secretariat as hours.
An accounting firm with fixed salaries
Twelve people on a monthly salary, days off from Time Off, a bonus after the closing season, a car and vouchers on most files. The month is a salary and its variables, and it goes to the payroll software as variables.
The provider computes the pay. You keep the record.
What counts as a working day, who checks the month and where the cost lands are yours to set.
One employee's September.
Nineteen days worked, read from the timesheets. Two days off, approved in Time Off on 3 September. One day sick, the certificate on the record. Three expense claims, approved, €200.60. The car, with the details the provider asks for ⟨to confirm⟩. The €500.00 bonus for the Maison Berger close, added by Mathilde on the 18th. That is Karim's month, on Karim's file, before anyone opens a spreadsheet.
This is the room.
The team's month: days worked, absences, hours, claims and bonuses per person, what changed since August, who has been checked, and whether the month has left.
A month read twice.
The same September, once collected from three spreadsheets and keyed into a portal on the 25th, once read from the records and sent.
- Three spreadsheets and a portal (Unresolved): The employee list. A spreadsheet of contracts and salaries, updated when someone remembers.. The month on the record: The employee file. Contract, regime, salary and car on one record, each change dated..
- Three spreadsheets and a portal (Unresolved): The absences. Leave read off a calendar, sick notes in an email folder.. The month on the record: Absences from Time Off. Approved days on the month, the certificate on the record..
- Three spreadsheets and a portal (Unresolved): The hours. A second spreadsheet, filled in from memory on the last day.. The month on the record: Hours from Timesheets. What was clocked on the job, already approved..
- Three spreadsheets and a portal (Unresolved): The expense claims. Receipts in a drawer, the total typed into the portal.. The month on the record: Claims from Expenses. Approved claims on the month, the refused ones nowhere near it..
- Three spreadsheets and a portal (Unresolved): The company cars. A third spreadsheet, out of date since the last lease.. The month on the record: The car on the file. From Fleet, with the details the provider asks for..
- Three spreadsheets and a portal (Unresolved): The hand-off. Keyed into the portal line by line on the cut-off day.. The month on the record: One export in their format. Sent once, received once, the month locked..
- Three spreadsheets and a portal (Unresolved): The payslips. Downloaded from the portal, emailed, asked for again in March.. The month on the record: On each employee's record. Filed the day they arrive, visible to that person..
- Three spreadsheets and a portal (Unresolved): The cost. One line in accounting, typed from the provider's summary.. The month on the record: Posted per department. Gross, contributions and provisions, on the ledger the accountant closes..
A payroll portal computes the pay correctly. It only sees the month you key into it.
The employee file with contract, regime and car
- A spreadsheet
- A tab
- A payroll portal
- Their file
- A suite module
- Yes
- Enobase
- Yes, the record the rest of the business uses
Absences and leave on the month
- A spreadsheet
- By hand
- A payroll portal
- Keyed in
- A suite module
- Yes
- Enobase
- Yes, from Time Off, approved
Hours and supplements from the job
- A spreadsheet
- Copied
- A payroll portal
- Keyed in or imported
- A suite module
- From their timesheets
- Enobase
- Yes, from Timesheets, approved
Approved expense claims on the month
- A spreadsheet
- Typed
- A payroll portal
- Keyed in
- A suite module
- Yes
- Enobase
- Yes, from Expenses
The pay computed, the declarations filed
- A spreadsheet
- No
- A payroll portal
- Yes
- A suite module
- Yes
- Enobase
- By your provider, from the month you hand over
The payslip on the employee's record
- A spreadsheet
- No
- A payroll portal
- In their vault
- A suite module
- In their HR
- Enobase
- Yes, on the file, visible to that person
The cost posted per department
- A spreadsheet
- Typed
- A payroll portal
- Exported
- A suite module
- In their accounting
- Enobase
- Yes, in Accounting, the day it arrives
Time to live
- A spreadsheet
- A day
- A payroll portal
- Weeks
- A suite module
- Months
- Enobase
- One week
| What you need | A spreadsheet | A payroll portal | A suite module | Enobase |
|---|---|---|---|---|
| The employee file with contract, regime and car | A tab | Their file | Yes | Yes, the record the rest of the business uses |
| Absences and leave on the month | By hand | Keyed in | Yes | Yes, from Time Off, approved |
| Hours and supplements from the job | Copied | Keyed in or imported | From their timesheets | Yes, from Timesheets, approved |
| Approved expense claims on the month | Typed | Keyed in | Yes | Yes, from Expenses |
| The pay computed, the declarations filed | No | Yes | Yes | By your provider, from the month you hand over |
| The payslip on the employee's record | No | In their vault | In their HR | Yes, on the file, visible to that person |
| The cost posted per department | Typed | Exported | In their accounting | Yes, in Accounting, the day it arrives |
| Time to live | A day | Weeks | Months | One week |
Questions about Payroll
Payroll reads the employee file, so Employees is the one it needs. Without Time Off the absences are typed on the month; without Timesheets the hours are. Turn each one on and that input stops being typed.