Payroll

DATEV and StoTax without rework

Monthly closure, wage types and surcharges from rules, export for DATEV LODAS, Lohn und Gehalt or StoTax, via API on request. The 70-day and Minijob limits are checked before the export, not after.

Exports to
  • DATEV
  • StoTax

Your own test environment in minutes. No credit card, ends automatically.

AI plausibility check of time entries: findings per entry before approval
Powerful features

From check-in to the payroll office in one run

Approved hours become wage types, limits are checked, the file goes into the payroll system. Nothing is entered again at the payroll office.

70-day short-term employment check in EVENTRA: distribution, projection and progress per employee

70-day limit per person

Worked days from recorded hours, across all events of the year. Whoever approaches the limit is in the list before the export.

  • Days from hours, not from the plan
  • Across all events and clients
  • Forecast to year end
Minijob limit in EVENTRA: monthly earnings threshold per employee with utilisation

Minijob limit per month

Earnings per month against the limit, decided per person: export automatically or review manually. The decision stays documented.

  • €603 limit in 2026
  • Decision per person
  • History across the months
70-day projection chart: employees closest to the limit

Forecast instead of surprise

Planned shifts and recorded days produce a forecast per person. Whoever would break the limit by season end is visible today.

  • Planned days included
  • Per person and event
  • Warning already in the shift plan
Before the export

The limit is in the list before it is broken

The 70-day view shows per person the worked days of the year, the planned days and the forecast. Whoever runs over the limit is flagged in the shift plan and before the export. The payroll office never receives a file it has to send back.

  • Worked and planned days per person
  • Forecast to season end
  • Warning in the plan and before the export
Learn more
70-day projection chart: employees closest to the limit
Month-end review

The month is read before it goes to payroll

At the press of a button EVENTRA computes seventeen markers and two drift values per time entry: night work, missing break, overlap, start and duration against the plan. The model reads which combinations matter for payroll and names three solid findings rather than twelve weak ones, each with evidence, pseudonymised. The Minijob decision per person stays yours alongside.

  • Markers deterministic, findings from the model
  • M1, M2, M3 instead of names in the prompt
  • Minijob decision per person, documented
Learn more
Minijob limit in EVENTRA: monthly earnings threshold per employee with utilisation
Payroll systems

Two payroll systems, one month-end

Map wage types once per payroll system. From then on your payroll office gets exactly what it works with: a DATEV file, a push via API or a StoTax file.

DATEV

DATEV LODAS and Lohn und Gehalt

Master data and payroll data leave separately, as a file or straight into the client via the DATEV API. Missing personnel numbers, IBANs or activity keys are flagged before the export.

  • Both products, wage types mapped per product
  • Push via API, no file and no upload
  • Master data and payroll data separated
  • Missing mandatory fields flagged before the export
StoTax

StoTax

Master data, changes and times go to the payroll office as a StoTax file. You enter the employer number once, EVENTRA assigns the personnel numbers, and the payroll type applies per payroll month.

  • File for the StoTax import
  • Personnel numbers assigned consecutively
  • Payroll type per month, not per person
  • Mandatory fields checked before the export
Data flow

From check-in to the payroll office

Every check-in becomes a time entry, rules turn it into wage types and supplements, limits and patterns are checked before the export, and the payroll office receives its file or the data via API.

Payroll data flow: check-ins are matched to time entries, rules produce wage types and supplements, the 70-day and mini-job limits and the month-end check run before the export, the file goes to the payroll office as LODAS, Lohn und Gehalt or StoTax or via API.Check-ins09:58 in14:02 break18:12 outapp, QR codeor terminalTime entries09:58 – 14:0214:32 – 18:127.7 h netmatched tothe shiftWage typesNight25 %Sunday50 %Public holiday125 %supplements from rules,set once per systemKICheck70 days64 / 70Mini-job590 / 633 €3 findingsevidence per entrybefore approvalFile or APILODASLohn und GehaltAPI pushFileMaster dataPayroll dataper payroll systemPayrollDone
Supplements and limits are rules; the month-end check names findings with evidence. Nothing is exported before your approval.

The monthly closure in four steps

From the approved hours to the file in the payroll system.

Approve hours

Only approved hours go into the closure, open entries stay visible.

Check limits and patterns

70-day and Minijob limit per person, plus the findings of the month-end review. Decisions documented.

Map wage types

Surcharges and wage types from rules, stored once per payroll system.

Export or push

File for LODAS, Lohn und Gehalt or StoTax, or straight into DATEV via API.

70-day short-term employment check in EVENTRA: distribution, projection and progress per employee

What the payroll office receives

The facts of the export.

Payroll systems
3
DATEV push
API
Limits before the export
2
per person and payroll month
€3

Common questions about the export

Answered briefly, so you know what you will see in the demo.

Which payroll systems are supported?

DATEV LODAS and DATEV Lohn und Gehalt as a file or via API push, StoTax as a file. Master data and movement data are exported separately, wage types are mapped once per payroll system.

How is the 70-day limit counted?

From recorded hours: every calendar day with at least one approved time entry counts as a worked day, across all events of the calendar year. Planned shifts additionally feed the forecast.

What does the AI check before the export?

Per time entry, seventeen markers and two drift values are computed without a model: night work, missing break, overlap, start and duration deviation from the plan. The model only receives this condensed, pseudonymised overview and names the combinations that matter for payroll, with evidence. Correcting or exporting is done by you.

What happens when a person is above the Minijob limit?

The person is flagged in the monthly closure. You decide per person whether the hours are exported anyway or reviewed manually. The decision is stored with a date and traceable in later months.

Can the payroll office export by itself?

Yes. A payroll-office login sees the monthly closure and the export, but no shift plans or applications. The export contains master data, hours and wage types in the payroll system's format.
Get started

See the export for your payroll office

30 minutes with the founder. You leave with a sample file for your payroll software.

Your own test environment in minutes. No credit card, ends automatically.

See pricing