German Lohnsteuerbescheinigung
Deadline: 4-Week HR Checklist

What the February 28 deadline actually requires

The obligation is spelled out in § 41b Abs. 1 EStG: at the end of the calendar year, the employer must close each employee’s Lohnkonto — the wage account that tracks every monthly payroll transaction for that person — and transmit a specific set of data to the tax authority electronically. This transmission is not a form you fill out. It is a machine-readable dataset sent through the ELSTER portal (the official electronic tax platform of the Bundeszentralamt für Steuern), authenticated by a digital certificate that the employer must have obtained in advance.

Each Lohnsteuerbescheinigung must include, at minimum: the employee’s Steuer-ID (tax identification number under § 139b AO), the Bruttoarbeitslohn (total gross salary including bonuses and benefits-in-kind), the einbehaltene Lohnsteuer (total wage tax withheld), the Solidaritätszuschlag, Kirchensteuer where applicable, and the full breakdown of Sozialversicherungsbeiträge — pension, health, unemployment, and long-term care insurance contributions. The transmission also carries the Bescheinigungszeitraum (the exact period during the calendar year the employee was on payroll) and indicator codes: Großbuchstabe U for uninterrupted employment and S for one-time special payments.

This is not a summary document. It is a legally significant dataset that the Finanzamt will cross-reference against the employee’s own tax return. Discrepancies trigger inquiries. Errors in transmission require a correction process under § 41c EStG that is deliberately restrictive — once the certificate is marked as transmitted, changes can only be made under narrow conditions. Getting it right before pressing send is not best practice. It is the only practice that avoids months of administrative cleanup.

Why the payroll year-end rush hits differently

Year-end accounting closes the books. Year-end payroll produces one legal document for every single person on the roster. For a company with 150 employees, that is 150 Lohnsteuerbescheinigungen, each pulling data from 12 monthly payroll runs, each of which may have involved mid-year tax class changes, one-time bonuses, parental leave adjustments, or corrections that were applied in month 7 but traced back to month 3.

Three pressures converge in this window. Volume pressure: one certificate per employee, not one per department. Coordination pressure: roughly 60% of German SMEs run payroll through a Steuerberater who uses DATEV as their core platform. The Steuerberater does not generate the certificates on your schedule — they generate them in their own January/February queue, which also includes annual financial statements, Umsatzsteuer-Voranmeldungen, and every other client’s year-end obligations. Setting an internal handoff deadline of mid-February is not paranoia; it is recognition that Steuerberater offices have a workload spike in exactly these weeks. Compliance pressure: the Finanzamt can issue a Zwangsgeld (coercive fine) for failure to transmit, and employees who do not receive their certificates on time cannot file their own Steuererklärung — putting the employer in the position of blocking an employee’s tax refund.

For companies running payroll in-house with Lexware, Sage, or SAP, the coordination pressure shifts from Steuerberater dependency to internal software proficiency. Lexware lohn+gehalt handles the full Lohnsteuerbescheinigung generation and ELSTER transmission pipeline internally, but the software’s year-end module must be updated, tested, and run correctly. A version mismatch between the payroll module and the ELSTER transmission module — something that happens more often than any vendor’s support page admits — can delay transmission by days at exactly the wrong moment.

Week 4 (February 1–7): Close January payroll and complete the Lohnkonten

The Lohnsteuerbescheinigung is created from the Lohnkonto. The Lohnkonto cannot be closed until the January payroll run is complete. This dependency means the clock starts the moment the January Gehaltsabrechnung is finalized — typically the last working day of January or the first few days of February. If January payroll is late, every subsequent step compresses.

This week has three deliverables. First, complete the January payroll run including all corrections for employees whose tax class changed during the year, who received one-time payments in December, or whose employment status changed (entry, exit, parental leave, sick leave beyond six weeks). Every monthly payroll correction that was deferred during the year surfaces here — the Lohnkonto close is the last opportunity to fix it before the annual data is locked.

Second, verify the Steuer-ID for every employee. The Steuer-Identifikationsnummer is the electronic ordering feature that links the employer’s transmission to the employee’s tax file at the Finanzamt. A typo in one digit of one Steuer-ID creates a certificate that cannot be matched — the Finanzamt will not reconcile it to the employee, and the employee cannot file their return with it. For new hires who joined during the year, cross-check the Steuer-ID against the original registration certificate the employee provided at onboarding. For employees who arrived from outside Germany, verify that the Steuer-ID has actually been issued — the Finanzamt can take 4–8 weeks to assign one after registration.

Third, run the preliminary payroll year-end reconciliation in your payroll software. DATEV and Lexware both provide year-end check routines that flag data inconsistencies before the Lohnsteuerbescheinigung is generated. Run them now, not in Week 1. A common output: employees whose total Bruttoarbeitslohn differs from the sum of 12 monthly gross payments by an amount that traces back to a benefit-in-kind (geldwerter Vorteil) recorded in one month but not reflected in the annual summary view. Fixing this in Week 1 means racing the calendar. Fixing it in Week 4 means having three weeks to correct it.

Week 3 (February 8–14): Full-year data audit and Steuerberater handoff

This is the cross-checking week. Every employee record is reviewed against the monthly payroll archives. The question is not “did the software calculate correctly?” — payroll software rarely makes arithmetic errors. The question is “did the input data match reality?”

Tax class changes are the most common source of discrepancies. When an employee marries, divorces, or changes their tax class combination from IV/IV to III/V (or vice versa), the employer receives updated ELStAM (elektronische Lohnsteuerabzugsmerkmale) data from the Finanzamt. If the update was applied in month 6 but should have been effective from month 4, the Lohnkonto may show the correct total but the Bescheinigungszeitraum breakdown will be wrong — and that is what the Finanzamt checks.

Employees who left mid-year need a Lohnsteuerbescheinigung covering only the period they were employed. Mid-year departures with severance payments (§ 41b Abs. 1 Satz 1 EStG: bei Beendigung eines Dienstverhältnisses) add a layer of complexity: the severance amount must appear under a specific tax treatment line (Großbuchstabe S for sonstige Bezüge), and if the employer applied the Fünftelregelung (the one-fifth rule for multi-year compensation, which was abolished from 1 January 2025 for employer-side withholding), the tax treatment may differ from what the employee expects.

Steuerberater handoff: if your company uses a Steuerberater, this is the week to deliver the reconciled data. Setting the handoff in Week 3 rather than Week 2 gives the Steuerberater two full working weeks to process, review, and return the certificates. Most Steuerberater will tell you they need one week. Most Steuerberater who tell you that are not accounting for the fact that three other clients delivered their data on the same day.

Week 2 (February 15–21): Generate certificates and review

The Lohnsteuerbescheinigungen are generated this week — either by the Steuerberater and returned to you for review, or by your in-house payroll software. If this is the first time you are seeing the actual certificates, something went wrong in Weeks 4 and 3. The review this week should be confirmation, not discovery.

For companies that process payroll in-house through Lexware or Sage, the certificate generation is a software function: the year-end module compiles the Lohnkonto data into the amtlich vorgeschriebener Datensatz (officially prescribed data format) specified by the BMF annual circular. The software will flag format errors — missing Steuer-ID, invalid date ranges — before transmission. It will not flag semantically wrong data. A Bruttoarbeitslohn of €48,000 for an employee whose annual salary is €52,000 is syntactically valid and will pass the format check. Only a human reviewer comparing the certificate against the December payslip will catch it.

The review process should be structured: one person generates the certificates, a second person reviews them. The reviewer checks a sample of at least 10% of certificates against the corresponding December Lohnabrechnungen, paying particular attention to the total Bruttoarbeitslohn and the sum of all deductions. For the highest-earning employees and for any employee with a mid-year status change, check 100%. An error on the Geschäftsführer’s certificate that surfaces during a Betriebsprüfung three years later is not a pleasant conversation.

Even with a Steuerberater handling the generation, this review step is yours. The Steuerberater’s DATEV output is only as accurate as the data you supplied. The Steuerberater is responsible for the correct application of tax law to the data. You are responsible for the correctness of the data itself. Those are two different liabilities.

Week 1 (February 22–28): ELSTER transmission and employee distribution

The transmission itself is the fastest step in the entire process. Once the certificates are finalized, the payroll software transmits the dataset to the Finanzamt through ELSTER in minutes. The bottleneck is not the upload. It is what happens when the transmission is rejected.

ELSTER authentication relies on a digital certificate that the employer must have obtained from the ELSTER portal in advance. If the certificate has expired — they typically have a validity period of three years — or if the certificate was issued to an employee who has since left the company, the transmission will fail. A replacement certificate requires a new ELSTER registration and can take up to two weeks to arrive by mail. Discovering an expired certificate on 25 February is a self-inflicted crisis. Verification that the ELSTER certificate is current should happen in Week 4, not now.

Assuming transmission succeeds, the Finanzamt returns a Transferticket — a confirmation number linking the employer’s submission to the tax authority’s system. This number must be recorded. If the Finanzamt later queries a specific certificate, the Transferticket is the reference that proves the transmission was made on time.

Employee distribution follows immediately. § 41b Abs. 1 Satz 3 EStG requires the employer to provide each employee with a printed or digital copy of their Lohnsteuerbescheinigung within a reasonable period. For digital distribution, ensure the delivery method is secure — an unencrypted PDF emailed to a personal address does not meet the GDPR standard for a document containing an employee’s Steuer-ID and full income history. Most companies distribute via a password-protected employee portal or as a printed document handed over in person. For employees on leave or working remotely, the printed version with registered post is the safest legal path.

One more check: for employees with Kirchensteuer obligations, verify that the Kirchensteuer line on their certificate matches their declared confession. An employee who left the church in November but whose certificate still shows Kirchensteuer for the full year has a legitimate complaint — and the correction under § 41c EStG will require a new transmission marked as geändert.

Common mistakes that trigger corrections — and why § 41c EStG makes them expensive

Not every error on a Lohnsteuerbescheinigung can be corrected. § 41c EStG allows retroactive changes to already-transmitted certificates only under specific conditions — primarily when the employee obtained amounts without a contractual claim and against the employer’s will. A simple data entry error that resulted in an incorrect Bruttoarbeitslohn does not qualify. In those cases, the correction path goes through the employee’s tax return: the employee declares the correct amount, the Finanzamt queries the discrepancy, and the employer must respond to the query with supporting documentation.

The mistakes that can be corrected under § 41c are narrow, but the mistakes that tend to occur are broad. The five most common:

1. Wrong tax class on the certificate. Happens when an employee’s ELStAM update was processed in the monthly payroll run but the Lohnkonto entry reflecting it was not correctly timestamped. The certificate shows the right tax withheld but under the wrong class. The Finanzamt will flag this.

2. Incorrect Bescheinigungszeitraum. An employee who joined on 15 March receives a certificate showing the calendar year 1 January – 31 December. The correct period is 15 March – 31 December. Software generates what you tell it to generate; this error traces back to the hire date not being entered correctly at onboarding.

3. Missing or duplicate certificates for employees with split-year employment. An employee leaves in June and joins a new employer in July. Both employers must issue a Lohnsteuerbescheinigung for their respective periods. The Steuer-ID is the same. If the first employer fails to issue, the employee cannot file a complete return.

4. Kirchensteuer mismatch. The employee’s confession status changed mid-year but the payroll system did not receive or apply the updated ELStAM data. The certificate reflects the old status.

5. Gross salary omits geldwerter Vorteil. Company car, gym membership, job ticket — these are taxable benefits-in-kind that must appear in the Bruttoarbeitslohn. If the payroll department did not receive confirmation of the benefit value from HR, it is omitted from the certificate. The Finanzamt cross-checks against employer social security declarations and will detect the discrepancy.

Every one of these errors is preventable with the four-week review cadence described above. Every one becomes materially harder to fix after transmission.

What happens when the deadline is missed

The penalty framework operates on two tracks. For the employer, the Finanzamt can issue a Zwangsgeld (coercive penalty payment) under § 328 AO to compel transmission. The amount is set at the Finanzamt’s discretion but is calibrated to be painful enough to produce compliance — typically starting at several hundred euros and escalating if transmission continues to be withheld.

For late employee tax returns that are delayed because of a late Lohnsteuerbescheinigung, the penalty falls on the employee under the Verspätungszuschlag framework (§ 152 AO): a minimum of €25 per month of delay, or 0.25% of the assessed tax per month, whichever is higher. While the employee is technically responsible for filing on time, an employee who received their certificate in April after the February deadline can reasonably argue that the employer’s delay caused their late filing — and that argument tends to be received sympathetically by the Finanzamt, which simply redirects its inquiry to the employer.

The operational cost is often higher than the financial penalty. Every day spent on post-deadline corrections, employee complaints, and Finanzamt correspondence is a day not spent on the next payroll run. In a two-person HR team, that loss of capacity cascades into the next month.

Frequently asked questions

Does my company need a separate ELSTER certificate just for Lohnsteuerbescheinigung transmission?

Yes, if you handle payroll in-house. The ELSTER certificate used for Lohnsteuerbescheinigung transmission is the same certificate used for monthly Lohnsteuer-Anmeldungen (§ 41a EStG), so if you already file wage tax registrations through ELSTER, no separate registration is needed. If your Steuerberater handles all ELSTER transmissions, the certificate is managed on their side — but confirm that your Steuerberater’s certificate is current and covers your company’s Betriebsstättenfinanzamt. Certificates are Finanzamt-specific.

I noticed an error on a Lohnsteuerbescheinigung I already transmitted. Can I fix it?

It depends on the type of error and when you catch it. If the error falls under the narrow correction conditions of § 41c Abs. 1 EStG (primarily: employee obtained amounts without contractual claim and against your will), you can transmit a corrected certificate marked as geändert. For other errors, § 41c Abs. 4 EStG requires you to notify the Betriebsstättenfinanzamt immediately. The Finanzamt will then pursue the correction with the employee. The practical advice: catch errors during the four-week review window, before transmission. After transmission, the correction path involves the Finanzamt, the employee, and a paper trail that nobody wants.

We are a small company with 15 employees. Do we really need a four-week timeline?

The timeline scales down proportionally but the dependency chain does not. January payroll must still close before the Lohnkonten can be finalized. The Steuer-ID of every employee must still be verified. If your Steuerberater processes payroll for 200 clients, your 15 employees are still in a queue of 200. The four-week framework gives you structure; the actual time investment for 15 employees might be a few focused hours per week. The alternative — trying to do everything in the last week of February — leaves no room for the Steuer-ID typo that takes two days to resolve.

Can we distribute Lohnsteuerbescheinigungen entirely digitally?

Yes, under § 41b Abs. 1 Satz 3 EStG, electronic provision is permitted. The legal standard is that the employee must receive the certificate in a format they can access and store. Practically, this means: (1) provide the certificate through a password-protected employee portal, not an unencrypted email attachment; (2) confirm that the employee has actually accessed it — a read receipt or portal login log; (3) retain the certificate yourself for the six-year retention period under § 147 AO. A printed backup for employees who request it is advisable — not every employee has a printer at home, and a certificate needed for a bank loan application cannot be shown to a bank on a phone screen.

An employee joined in November. Do they need a full Lohnsteuerbescheinigung?

Yes. Every employee on payroll at any point during the calendar year receives a Lohnsteuerbescheinigung covering their actual employment period. For a November hire, the Bescheinigungszeitraum will be approximately 1 November – 31 December, and the Bruttoarbeitslohn will reflect only two months of salary. This certificate is still legally required, and the employee still needs it for their tax return — particularly if they held another job earlier in the year and need to consolidate income from two employers.

Next step: build the checklist into your payroll calendar

The February deadline arrives every year. The question is not whether you will meet it — German employers do. The question is whether the weeks leading up to it feel like a controlled process or a controlled panic. The difference traces back to one decision: treating 1 February as the real deadline, and treating the four weeks after as execution, not discovery.

For the full picture on how document extraction fits into the wider German wage tax workflow, see our guide to extracting German Lohnsteuerbescheinigung data to Excel. If you are processing certificates for more than a handful of employees, the batch processing approach covers how to handle multiple certificates in a single pass. And if you are still reconciling the time cost of manual payroll data entry, the cost analysis puts numbers on what those January and February hours are actually costing your team.