Mitarbeiter Auswertung

Verwaltung → Auswertung → Mitarbeiter Auswertung

One row per employee, for one month. This screen answers: “How does each person stand this month — target met? Flexitime balance? Account balances? Remaining holiday?”

It is also the place where the month is calculated, closed and exported to DATEV. There is deliberately no employee filter — you always see every person visible to you.

The columns

Column	Meaning
Pers.Nr.	Personnel number.
Name	The employee’s search abbreviation.
Abteilung	Shown as a badge. Without an assignment, a red Nicht Zugeordnet appears.
Zeiten	Ist / Soll (actual / target). Red if the target has not been reached; green if it has been exceeded.
Gleitzeit	The balance for the month. Red if negative.
Normalzeit	Total of the Normalzeit portions.
Fehlzeit	Total of the evaluated absences (Urlaub, Krank …).
Konto 1 to Konto 3	Account balances including the carry-over from the previous month.
Urlaubskonto	Remaining holiday in days — not in hours.

Two different kinds of time

Soll, Ist, Gleitzeit and Fehlzeit are month-based — they start at zero every month.

Konto 1–Konto 3 and Urlaubskonto are cumulative — they carry the balance over from the previous month. An account balance of 12,50 is therefore not a monthly figure but the total balance.

How time values are displayed is your choice under Einstellungen: either as Normalstunden (01:30) or as Industrieminuten (1,50). The choice applies to every view. The Urlaubskonto does not follow it — holiday is kept in days and stays a decimal figure.

By default, the list is grouped by Abteilung.

The month: calculating and closing

Badges in the top right show the state of the selected month:

Badge	Meaning
Korrigierbar (yellow)	The last closed month. Only Nachkorrektur is still possible.
Abgeschlossen (red)	The month is closed. No full editing any more.

Berechnen

The Berechnen button recalculates the monthly result for all employees. It is locked when the month is closed.

Berechnen only works forwards

A month can only be recalculated if it lies strictly after the last Monatsabschluss. It is not only the closed month itself that is locked, but every month before it. Otherwise you get „Der Monat ist bereits abgeschlossen. Das Ergebnis kann nicht neu berechnet werden.”

If a calculation is already running, the system reports „Es wird bereits eine Berechnung im Hintergrund ausgeführt.” — in that case, wait.

Monat abschließen

In the ⋮ Aktionen menu → Monat abschließen.

No gaps, strictly in order

You can close only the month directly following the last closure. No skipping, no gaps. If the entry is greyed out, the selected month is not next in line.

A closure cannot be undone here, but under Stammdaten → Abrechnung → Monatsabschluss via the context-menu entry Aufheben. See Monatsabschluss.

DATEV-Export

In the ⋮ Aktionen menu → DATEV-Export. This opens a dialog with three target formats:

Tile	Meaning
DATEV (LuG)	Lohn und Gehalt (payroll and salary).
DATEV (LODAS)	LODAS.
DATEV-Profile	Export via the configured export profiles.

The monthly result is updated automatically before the export. The result is a file Zeiterfassung_Export_JJJJMM.dat.

Correcting

The context menu of a row depends on whether the month is open.

Month open:

Group	Entry	Purpose
Buchungskonten	Umbuchen	Move time from one account to another, using an Umbuchungsschlüssel (transfer key).
Korrektur	Urlaubskonto	Correct holiday days directly.
Korrektur	Konto 1, Konto 2, Konto 3	Correct the account balance directly.

Month closed and it is the last one: only Nachkorrektur.

Month closed, but not the last one: no context menu.

What you enter in the dialog

Umbuchung and Korrektur share the same two fields: the amount you enter on the left, and the target amount on the right. The dialog works the latter out as amount × Faktor itself, which is why the field cannot be typed into. Bemerkung is a mandatory field — no transfer without a reason.

The unit follows the account

Zeitkonten in hours, Urlaub in days

• Konto 1 / 2 / 3 → you enter a time.
• Urlaubskonto → you enter days.

For an Umbuchung the chosen Umbuchungsschlüssel decides: as soon as the Urlaubskonto sits on either of its two sides — as the source or as the target — you are entering days. For a Korrektur it is the account you picked in the context menu.

The field adjusts itself, but the figure stays ambiguous: 3 in a holiday field is three holiday days, 3 in a time field is three hours. If changing the Schlüssel changes the unit, the amount is cleared — so that three hours do not silently become three days.

Time cannot be transferred into holiday

An Umbuchungsschlüssel that connects a Zeitkonto with the Urlaubskonto cannot be booked — hours and days of leave are different quantities. The dialog says so and locks Speichern as soon as you select such a Schlüssel.

How you may write it

Time fields (Konto 1–3) understand both notations — regardless of which one you picked under Einstellungen:

Input	Meaning
1:45, 01:45	one hour and 45 minutes
1,75, 1.75	the same, as decimal hours
2	two hours
-1:30, -1,5	subtract one and a half hours
25:00	25 hours — durations beyond a single day are allowed

A trailing h or Std is tolerated. The value is then displayed in your chosen format. Whatever the field cannot read is discarded and the last valid value restored — an unreadable entry is therefore never booked silently.

Day fields (Urlaubskonto) take a plain decimal figure:

Input	Meaning
3	three holiday days
0,5, 0.5	half a holiday day
-1	subtract one holiday day

Dot and comma count equally as the decimal separator everywhere — the dot is quicker on the numeric keypad. There is no thousands separator in return: 1.5 is one and a half, not fifteen hundred.

Nachkorrektur

Only on the last closed month. You enter Konto 1, Konto 2, Konto 3 and Urlaubskonto directly — the same notations as above apply: the three accounts as a time, the Urlaubskonto in days. Negative values are allowed in all four fields.

Note

The Nachkorrektur writes directly into the monthly result and triggers no recalculation. Your values stay exactly as you entered them. In the Kontoverlauf (Auswertungen → Konten) the difference to the carried-forward balance shows up as a booking of type Nachkorrektur.

Typical cases

Which tool is the right one depends less on what is wrong than on whether the month is still open. The short version:

You want to …	Month open	Month closed
record a forgotten Fehlzeit	record the Fehlzeit, then Berechnen	reverse the close
straighten out an account balance	Korrektur → Konto/Urlaubskonto	reverse the close
move time between accounts	Umbuchen	reverse the close
remove a wrong booking	delete the Umbuchung in the drilldown	reverse the close

Case 1: Forgotten holiday in an open month

The easy case — and the one you want to reduce all the others to.

1. Planung → Fehlzeiten: record the holiday in the calendar.

2. Back in the Mitarbeiter Auswertung, select the month and press Berechnen.

3. Check the Urlaubskonto column. In the drilldown the booking then appears as an automatic row with source Tagesergebnis and target U.

Do not correct the Urlaubskonto by hand instead: the balance would be right, but the day itself stays empty — in the absence overview, in the wage types and in the DATEV export.

Case 2: Forgotten holiday in a closed month

The most common serious case. The thing to understand: the close locks the absences too. Up to the end of the most recent closed month the calendar accepts no change — it shows „Abgeschlossen bis TT.MM.JJJJ — keine Änderung möglich” at the top. So the days cannot simply be added afterwards; the close has to go first.

1. Stammdaten → Abrechnung → Monatsabschluss, row of the month concerned → context menu → Aufheben.

   An older month can only be reversed together with every later close — as long as a later one exists, the older month stays locked. The confirmation lists which months are opened in addition; only confirm once that list is acceptable to you.

2. Planung → Fehlzeiten: record the holiday now. The lock hint in the calendar has disappeared, or moved to an earlier month.

3. Back in the Mitarbeiter Auswertung: select each reopened month individually and in chronological order and press Berechnen. Reversing the close on its own recalculates nothing — without this step the frozen figures stay where they are.

4. Check the result: the Urlaubskonto column and the drilldown of the corrected month.

5. Close the months again in the same order — without gaps, each one the direct successor of the last close.

If the month has already gone to payroll

A DATEV export of the month concerned was produced from the old figures. After the correction a new export contains different values — agree with payroll whether the month is submitted again or the difference is carried in the following month.

Why not just correct the Urlaubskonto?

Because a corrected balance does not replace the missing day. The Fehlzeit is what the Tagesergebnis, the absence overview, the wage types and the export all build on; the Urlaubskonto is merely the result of it. A pure account correction leaves everything else wrong — and at the next Berechnen of an open month the two figures drift apart again.

Case 3: The remaining leave is wrong

Not every shortfall comes from a missing Fehlzeit — a carry-over from the previous year, a changed entitlement, a day paid out. Then the direct correction is the right one, because there is no day to record.

In an open month: row context menu → Korrektur → Urlaubskonto → enter the difference in days, with a reason. Then Berechnen.

Case 4: Time from one account to another

Context menu → Umbuchen, pick an Umbuchungsschlüssel, enter the amount. The Schlüssel brings source, target and factor with it; Schlüssel are created under Stammdaten → Abrechnung → Umbuchungsschlüssel.

If there is no suitable Schlüssel, the Korrektur on the target account is the more direct route — it books without a counter-account.

Case 5: Taking back a wrong Umbuchung

In the drilldown of the row, expand the Monatsumbuchungen panel and remove the booking with the delete icon. The icon only appears on manual bookings (Pos ≥ 1); the month is recalculated automatically afterwards.

Automatic bookings (Pos 0 or -1) cannot be deleted — they are recreated on every Berechnen. If one of them is wrong, the error is in the daily data, not in the booking.

Drilldown: where the numbers come from

The + on a row expands two panels.

Monatsumbuchungen — every booking that has changed the month:

Column	Meaning
Pos.	0 or -1 = automatic booking, ≥ 1 = manual booking.
Quelle / Ziel	From which account to which.
Zeit	The booked amount — in days as soon as the Urlaubskonto (U) is involved, otherwise as a time.
Bemerkung	Your reason.

A delete icon appears only for manual bookings (Pos ≥ 1). Automatic bookings are deleted and recreated on every Berechnen — manual bookings survive. That is why you cannot delete automatic bookings at all: they would come back with the next calculation anyway.

When you delete a transfer, the system asks for confirmation („Diese Aktion kann nicht rückgängig gemacht werden.”) and recalculates the month afterwards.

Lohnarten Ergebnis — the breakdown by wage type, with Typ, Summe and Tage.