Clean pay runs, and the peace of mind that follows

The worst part of running payroll is not the maths. It is the doubt. The nagging sense that a number was typed wrong, that someone's sick leave never made it into the run, that a driver's licence quietly expired two weeks ago and nobody noticed. Office is built to take that doubt away. Not by promising magic, but by making every number in a pay run trace back to something real, and by refusing to let the run close until a human has looked at it.

Let us be honest about scope up front. Office does payroll prep, not the final statutory calculation. The legally binding net, the social contributions, the tax tables: those come from your payroll provider or your accountant's software, fed by a clean export from Office. What Office owns is everything that leads up to that moment, and everything that has to be true for the export to be trustworthy.

A pay run that builds itself from what actually happened

Most payroll pain comes from re-entering data that already exists somewhere else. Hours live in a timesheet. Leave lives in an approvals inbox. Salaries live in an employment record. By the time all of that is copied into a payroll sheet by hand, three things have gone wrong and nobody can say which.

Office starts a pay run from the source of truth instead. It pulls approved hours from time entries, reads approved absence from the leave module, and reconciles both against each employee's current employment. A run is not a blank spreadsheet you fill in. It is a draft that already knows what happened, waiting for you to confirm it.

• Real hours, already approved. Time entries that managers have signed off flow straight into the run. If Fleet by Elevera is in the picture, driver hours arrive as time entries automatically, so the people who were on the road are paid for the road.
• Absence that is already settled. Approved leave reduces or adjusts pay where it should, drawn from the same balances employees see in self-service. No parallel tally, no end-of-month surprise.
• Employment as the anchor. Salary, contract type and start or end dates come from the employment record, so a mid-month change is reflected once and everywhere.

Review, then lock. In that order.

A draft pay run is editable. That is the point of a draft. But a draft that can be edited forever is a draft nobody trusts. So Office gives a run exactly one moment that matters: the lock.

Before the lock, you review. You see each employee's hours, absence and gross, you catch the obvious anomalies, you fix the thing that looks off. When the run is right, you lock it. After the lock, the figures are frozen and the run becomes a record, not a worksheet. Anyone who needs to change something after that has to do it in the open, as a new action, on the record, where the audit trail will see it.

A pay run should be boring by the time it closes. The drama belongs in the review, not in the export, and never in the month after.

That ordering, review then lock, is what turns prep into peace of mind. You are not hoping the numbers are right. You looked at them, you locked them, and the lock is what you hand downstream.

Export clean: DATEV, a Croatian format, or generic CSV

A locked run is only useful if it leaves the building in a shape your provider can read. Office exports to the formats European teams actually use, not a proprietary blob you have to wrangle.

• DATEV for German payroll, so a Steuerberater or a payroll bureau can ingest the run without re-keying.
• A Croatian format for teams paying in Croatia, built for the local provider chain rather than bolted on.
• Generic CSV as the honest fallback, so a run is never trapped in Office. If your provider has its own template, you still have clean, structured data to map.

The export is the handoff to the statutory calculation. Office gets the inputs right and hands them over in a format the next system trusts. That is the boundary, and it is a deliberate one.

Retention, because the run does not stop mattering when it closes

Payroll records are not yours to delete on a whim. European law expects them kept for years, and a tax audit can ask for them long after the people in them have moved on. A locked run in Office stays put, with its inputs intact and its audit trail attached, for as long as you are required to keep it.

That retention is not a filing cabinet you maintain by hand. It is a property of the record. When an auditor or an accountant asks what was paid in a given period and why, the answer is already assembled: the hours, the absence, the gross, the lock, the export, and who did each of those things.

Compliance that watches the calendar so a licence never lapses

Payroll and compliance are usually treated as separate departments. They should not be. A pay run for a delivery team is only clean if the people in it are actually allowed to work the way they were paid to. A licence that lapsed mid-month is a payroll problem dressed as a compliance one.

Office tracks licences, permits and certifications with their expiry dates, and it surfaces what is about to lapse before it does. Missing items are detected rather than discovered. When Office and Fleet by Elevera share one source of truth, compliance even governs scheduling: someone whose qualification has expired is not quietly rostered onto a job they can no longer legally do.

The cheapest compliance problem is the one you fix the week before it happens. The expensive one is the email from a regulator about the week after.

The accountant gets a window, not a seat

Here is the small thing that turns out to be a big thing. When tax season comes, the usual move is to hand your accountant a login. A full seat. The keys to the building, so they can pull the one report they actually need.

Office does not work that way. Your external accountant or Steuerberater gets token-scoped, read-only access: a window onto exactly the payroll data they are entitled to see, and nothing else. They cannot edit. They cannot wander into employee records that have nothing to do with the run. The access is scoped, logged in the audit trail, and revocable the moment the work is done.

• Read-only by construction, so an outside party can never alter a record they are only meant to review.
• Scoped to the data that matters, so handing over the year-end run does not mean handing over the whole organisation.
• Logged and revocable, so you can prove who saw what, and close the window the instant it is no longer needed.

This is least-privilege access applied to the one relationship where everyone usually shrugs and over-shares. Your accountant gets everything they need to do their job and nothing they do not. You can read more about how that isolation is built on our security page.

Where prep turns into peace of mind

None of this is glamorous, and that is rather the point. A clean pay run is one you do not have to think about after you lock it. The hours were real and approved. The absence was settled. The compliance was current. The export matched the provider. The accountant saw exactly what they needed through a window you control. The record will still be there, intact, when an auditor asks for it in three years.

That is the peace of mind that follows clean prep. Not the absence of work, but the absence of doubt. If you want to see how the pieces fit, the closed loop with Fleet is where compliance and payroll stop being two jobs, and the pricing page lays out what it costs per employee, with no surprises in the small print.