Schedule, attendance and payroll inputs in one place
Instead of one file with the supervisor, another with HR and a third with the managing director. A system in production use today at a company that runs its monthly payroll on it.
What it usually looks like before
The schedule is made in a spreadsheet, attendance is noted on a printout at the entrance, leave requests travel on paper, and at the end of the month someone retypes all of it into a third file to produce the payroll figures. Every retyping is a chance for a mistake, and every mistake in this area affects a specific person and their pay.
On top of that comes a question nobody can answer quickly: who is actually at work today, and is tomorrow's staffing covered?
What the system does
A schedule that sees the staffing
Shift planning with a view of whether every position is covered and whether someone has been booked twice at the same time. A change to the schedule is visible straight away to everyone who uses it, without sending round a new version of the file.
Attendance and working time
Clock-ins and clock-outs, overtime, late arrivals and absences recorded as they happen. Working time records build themselves from what happened during the month, rather than being reconstructed from memory on the last day.
Leave requests without paper
The employee submits the request, the supervisor approves it and the leave balance updates itself. The history stays in the system, so the question "how many days do I have left" no longer needs a visit to HR.
Pay inputs and allowances
Bonuses and allowances calculated according to the company's own rules, including the less obvious ones, such as an allowance that depends on shift length. This is usually where off-the-shelf software gives up, because every company has its own pay rules, and those rarely fit into a drop-down list.
Employees and agency staff as two flows
Employees and agency staff are settled differently and with different parties, so they are kept separately. A shared table for both only looks simpler until the first settlement with the agency.
Reports for management
Staffing cost, overtime, absence and turnover calculated from data that is created anyway during normal work. A statement takes a click, not a working day of the HR team.
Many companies in one installation
The system is built so that several companies can use one installation, each with its own completely isolated data area. Today it is in production use at one company, with a trial rollout under way at a second. For a group of companies or a firm serving several businesses, this means one system to maintain instead of several, with no data mixed between companies.
Frequently asked questions
Can the system handle employees and agency staff at the same time?
Yes, but as two separate flows, because they follow different rules. Employees have contracts, leave and working time records, while agency staff are settled through a statement with the agency.
Can it be connected to an HR and payroll program?
Yes. The system collects what the payroll program cannot see, meaning how shifts actually went, overtime, absences and allowances, and then hands over a ready statement for payroll.
Can several companies use one installation?
Yes. Each company has its own isolated data area, and only the application itself and its updates are shared.
Where is employee data stored?
Where the company decides, because the company is the controller of that data. The server is on Fabria's side, which then acts as the processor, so a data processing agreement is needed that sets out the scope of access, the retention period and how the data is deleted. This is not a box to tick, it is a requirement for HR data.
How many files does your schedule live in today?
Tell me how the flow from schedule to payslip looks today. It can usually be cut by a few steps in the very first stage.
Send a messageProduction systems · Excise stamp records · Integrations and automation