Minijobber annual earnings limit
Updated
by
Daniel Sjögren
What this rule does
A Minijobber's tax-free status depends entirely on staying under a set of earnings limits. Go over them and the status can be revoked retroactively, with tax and social insurance consequences for the employee and the employer.
The Minijobber Annual Earnings Limit rule keeps that from happening quietly. It watches an employee's earnings across the whole assessment period — not just the month in front of you — and flags a violation while the shift is still being scheduled. In the Schedule Compliance rule catalogue it belongs to the Working Time category.
Who this is for
Schedulers and managers in Germany who plan employees on Minijob contracts.
The limits the Quinyx compliance rule protects
The worked examples in this article use €603, the figure in force from 1 January 2026. Because the limit is set in law and moves with the statutory minimum wage, check the Minijob-Zentrale page above before quoting any figure here as current. Quinyx never hard-codes the limit in any case: the rule always reads it from the Cost Limit settings on the employee's agreement template.
Check | What it does |
Annual earnings | Adds up actual earnings (time punches and absences) and simulated earnings (shifts without a time punch) across the assessment period. Over the pro-rated limit for that period, and a violation is raised. |
Double monthly limit cap | A hard ceiling. No single month may be scheduled to exceed 2× the monthly limit (€1,206 in the example). |
Safe earnings enforcement | Optional, and strongly recommended. Checks whether the employee has over-earned relative to today's date. Someone earning €700 a month from January to June looks fine against a full-year limit — but if they leave in June they have already broken the six-month pro-rated limit. This check flags that risk early. |
Configuration
The rule reads the Cost Limit settings on the employee's Agreement Template. Four things have to be right, or the rule cannot produce a correct result:
- Salary — the agreement must have a salary configured. It is the basis for tracking earnings.
- Cost periods — must be 1 calendar month, starting on the 1st. If this is not exact, the rule skips validation rather than return a wrong answer.
- Cost period values — should also start on the 1st of the month.
- Salary types — need Salary cost configured, and
Include in total costmust be enabled. This one is easy to miss.
Severity and enforcement
Quinyx does not ship this rule with a fixed severity. The super user or admin who adds it to a rule set chooses how a breach behaves — whether it stops the action outright or warns the scheduler and lets them continue. Both options are available, and neither is imposed as a default you have to work around, so how strictly the rule bites is a configuration decision, taken per rule.
That "per rule" matters here more than usual: because a rule set can hold several of these rules, each carries its own severity, and a violation takes the severity of the specific rule whose period it breaches.
Assessment period: calendar year or rolling
Each Minijobber Annual Earnings Limit rule is configured with one of two assessment-period types:
- Calendar year — 1 January to 31 December. Each calendar year in which the employee has a shift is assessed on its own, pro-rated to the months of Minijob status in that year.
- Rolling (12 months) — a rolling 12-month window anchored to the later of the employment start and the agreement start, then tiled forward in consecutive 12-month blocks.
When the monthly cap changes
If the limit changes partway through an assessment period — for example, the legal limit is raised — Quinyx does not blend the old and new limits inside one window. The period is split at the effective date of the change, so each sub-period is assessed against the single limit that applied throughout it.
- The sub-period before the change ends the day before the new limit takes effect.
- For rolling rules, the sub-period after the last change is re-anchored: it becomes a fresh 12 months starting from the change date, clamped to the employment and agreement end dates — not just the remainder of the original block.
- For calendar-year rules, the split divides the year at the change date. Calendar boundaries are unaffected.
Employees with several agreements
An employee may hold several agreements over time — renewals, re-hires — and across different agreement templates. An agreement template has no start or end date of its own; the individual agreements carry the dates. The rule handles this as follows:
- Grouped by template first. Cost-limit values belong to an agreement template, so intervals are generated per template and split only at that template's boundaries. One template's limit change can never split another's.
- Contiguous same-template agreements form one assessment period. Agreements on the same template that overlap, touch end-to-end, or are bridged by further same-template agreements are treated as one continuous span.
- A gap starts a new assessment period. A gap of at least one day on a template, which no other agreement on that same template fills, breaks the timeline: agreements after the gap begin a new, independent assessment period with its own rolling anchor. Overlapping or abutting agreements never create a break.
- Earnings are counted across all templates. Intervals are generated per template, but the earnings totalled against each interval are the employee's combined earnings for those months — they are not filtered by which template or agreement produced them.
Which actions trigger the check
Creating or updating shifts, copying shifts, rolling out base schedules, shift offer requests, shift swaps, booking shifts (assigning an employee to an open shift), and unassignment-approval requests.
It does not currently trigger when deleting a shift, or when editing shifts inside a base schedule template.
Before you rely on totals
To keep the schedule fast to work in, Quinyx uses a hybrid calculation. Live salary calculation only runs for shifts inside a window of 62 days in the past and 90 days in the future, relative to the shifts being edited — the same approach Time Tracker transactions use.
Anything outside that window has to have been transferred to payroll (non-preliminary) for the rule to see it. If earlier months have not been transferred, those hours are not counted, and the totals will be lower than reality.
Good to know / FAQ
Does the rule distinguish between salary types — base pay versus night surcharges?
Not currently. The rule counts all salary types that produce costs in Quinyx. German law allows certain SFN-Zuschläge (Sunday, holiday and night surcharges) to be excluded from the Minijob limit, but this version includes them in the total. Salary-type filtering is planned for a future update.
I have configured the Cost Limits, but I see no violations. Why?
Check three things:
- Is the Minijobber Annual Earnings Limit rule added to the rule set used by that agreement?
- Are Cost Limits and salary types actually configured on that employee's agreement, and does the agreement have a base salary?
- Is the Salary basis setting enabled for every absence reason type that should contribute to costs?
What happens if a Minijobber becomes a regular employee mid-year?
The limits apply strictly to the months they held Minijob status — meaning an agreement whose agreement template used a rule set containing the Minijobber Annual Earnings Limit rule. Each assessment interval is clamped to the Minijob agreement span, so months outside it are not assessed, and from the day they move to a regular contract, Quinyx stops applying the validation to their new earnings. Note that within a Minijob assessment window, all of the employee's earnings in those months count — including earnings from a concurrent non-Minijob agreement — because earnings are not filtered per template.
Does the rule apply to shifts I have already scheduled?
Yes. Whenever you create or update a shift, the rule validates the total earnings for the whole period — it looks back at the period's data to check that the new shift does not break the limit.
