Simpler payroll ready for audit at all times

Yes, payroll is highly automated. Working time, absences, and contract changes flow in from the other modules, so nothing is re-keyed; you press Calculate, review the summary, and approve. The country-specific tax engine applies the right brackets and rates automatically for each employee's Legal Entity, along with any custom payroll items and standing instructions you have configured. Different register types: regular monthly, advance, intermediate, accrual, corrective, can run in parallel within the same period without colliding.

Hermetis generates SEPA payment files in the ISO 20022 standard, which you upload to your bank. All of an employee's eligible payments for the period. Regular salary, advances, intermediate runs are consolidated into a single transfer, and each transaction is marked as paid when the payment register closes, which removes the duplicate-payment failure mode. Withholdings such as alimony and garnishments are paid to their correct recipients (court, bailiff) through dedicated payment registers on the same governed cadence.

Payroll results are consolidated by GL account and cost centre to match your chart of accounts and exported to your finance system (for example SAP, Visma, Navision). Consolidation runs as a separate post-calculation step that does not alter the payroll results themselves, which keeps segregation of duties intact, and every consolidated posting can be traced back to the specific employees, periods, and transactions behind it. The month-end handoff to finance becomes a file load rather than a manual matching exercise.

Each deduction, alimony, a writ of execution, a training claw-back, is registered as a document with its own validity period, recipient, and statutory caps (for example Latvia's non-deductible minimums), and the system applies it automatically every run with built-in priority rules. Amounts are recalculated each month, including when salary changes, and deductions stop on the right date so there is no over-deducting after a court order expires. Each is settled to the correct recipient through a dedicated payment register.

A backdated change triggers automatic retroactive recalculation. There is no separate recalculation cycle to schedule and the specialist does not rebuild prior periods by hand. The original payroll result transactions are preserved side by side with the recalculated ones for the same period, both kept in the Payroll Ledger, and the difference is carried as a corrective transaction in the current period. Payslips show the effect of the recalculation, and nothing in payroll history is silently overwritten.

Tax rates and thresholds live in calculation tables rather than in code, and Hermetis maintains them as part of the standard product lifecycle. Legislative updates are pre-applied in quarterly major releases, so customers don't configure tax rates themselves. This ships compliance as data rather than as a per-change consultant project. Customers still validate that the maintained configuration fits their circumstances, making compliance a shared, auditable posture.

Yes. Each Legal Entity runs fully isolated its own scope, period, and payment execution. So every country keeps its own statutory context and calendar. Closing a register, payment register, or period locks that data against modification, and an exceptional reopen is available as a governed, audit-logged action when a corrected source document arrives late.

There is end-to-end traceability from source data through payroll input records, registers, and result transactions to payment and financial consolidation, so any number in the general ledger can be followed back to the employees and periods behind it. Result transactions are immutable once created, the Payroll Ledger is the single source of truth independent of any register's lifecycle, and ad-hoc inquiries can filter the ledger by period, employee, payroll item, register, or organisational attribute without exporting to a spreadsheet.