{"id":4010,"date":"2026-03-24T13:36:50","date_gmt":"2026-03-24T13:36:50","guid":{"rendered":"https:\/\/www.brasser-accounting.de\/?post_type=glossar&#038;p=4010"},"modified":"2026-05-12T10:12:28","modified_gmt":"2026-05-12T10:12:28","slug":"eltham","status":"publish","type":"glossar","link":"https:\/\/www.brasser-accounting.de\/en\/glossar\/elstam\/","title":{"rendered":"Electronic payroll tax deduction details"},"content":{"rendered":"<nav class=\"toc\" aria-label=\"Table of Contents\">\n      <h2>Table of Contents<\/h2>\n      <ol>\n        <li><a href=\"#einleitung\">Brief definition<\/a><\/li>\n        <li><a href=\"#einordnung\">Classification<\/a><\/li>\n        <li><a href=\"#inhalte\">Contents<\/a><\/li>\n        <li><a href=\"#pruefungslogik\">Process logic<\/a><\/li>\n        <li><a href=\"#pruefungszeitraum\">Ongoing changes<\/a><\/li>\n        <li><a href=\"#ablauf\">Procedure<\/a><\/li>\n        <li><a href=\"#praxis\">Case studies<\/a><\/li>\n        <li><a href=\"#finanzielle-wirkung\">Effect<\/a><\/li>\n        <li><a href=\"#dauer-kommunikation\">Roles &amp; Communication<\/a><\/li>\n        <li><a href=\"#fehlerquellen\">Sources of error<\/a><\/li>\n        <li><a href=\"#kontrollen\">Controls<\/a><\/li>\n        <li><a href=\"#checkliste\">Checklist<\/a><\/li>\n        <li><a href=\"#faq\">FAQ<\/a><\/li>\n        <li><a href=\"#fazit\">Conclusion<\/a><\/li>\n      <\/ol>\n    <\/nav>\n\n<section id=\"einleitung\">\n<div class=\"snippet info\">\n          <h3>Brief definition<\/h3>\n  <p><strong>ELStAM<\/strong> stands for <em>Electronic wage tax deduction features<\/em>. This refers to the electronically provided characteristics that employers need for the correct calculation and deduction of income tax in payroll accounting.<\/p>\n<\/div>\n<p>The ELStAM include in particular <strong>Tax bracket<\/strong>, <strong>Child allowances<\/strong>, <strong>Church tax feature<\/strong>, <strong>Allowances<\/strong> and that <strong>Factorisation method<\/strong>. The data will be provided electronically \u2013 however, its correct application is an organisational task within the company.<\/p>\n<\/section>\n      <section id=\"einordnung\">\n<h2>Classification<\/h2>\n<p>ELStAM are not a \u201eform issue\u201c but a core component of monthly payroll. They determine how much income tax is withheld and remitted. Errors have an immediate impact: on employees' net pay, on correction efforts, and on the audibility of your payroll.<\/p>\n<p>The key principle here is a sober one: even if the features are provided electronically, the responsibility for correct retrieval, adoption, and ongoing updating remains with the employer.<\/p>\n<\/section>\n      <section id=\"inhalte\">\n<h2>ELStAM steht f\u00fcr \"Elektronische Lohnsteuerabzugsmerkmale\" und umfasst folgende Merkmale:\n\n*   **Steuerklasse:** Bestimmt die H\u00f6he des Lohnsteuerabzugs.\n*   **Kinderfreibetr\u00e4ge:** Ber\u00fccksichtigung von Freibetr\u00e4gen f\u00fcr Kinder.\n*   **Kirchensteuerpflicht:** Angabe, ob eine Kirchensteuerpflicht besteht.\n*   **Faktorverfahren:** Bei unverheirateten Eltern zur Aufteilung des Freibetrags.\n*   **Arbeitslohnkapselung:** Schutz des Lohnsteuerabzugs vor missbr\u00e4uchlicher \u00c4nderung.\n*   **Daten zur Sozialversicherung:** Grundlegende Daten, die f\u00fcr die Sozialversicherung relevant sind.\n*   **Weitere individuelle Merkmale:** Zum Beispiel ein Pausch- und Kromberg-Freibetrag.\n\nDiese Merkmale werden elektronisch gespeichert und vom Arbeitgeber im Lohnabrechnungsprogramm abgerufen, um den korrekten Lohnsteuerabzug zu berechnen.<\/h2>\n<p>In practice, these characteristics are particularly relevant:<\/p>\n<ul>\n  <li><strong>Tax bracket<\/strong> (e.g. I, II, III, IV, V, VI)<\/li>\n  <li><strong>Child allowances<\/strong><\/li>\n  <li><strong>Church tax feature<\/strong> (Church tax liable yes\/no, state if applicable)<\/li>\n  <li><strong>Allowances<\/strong> (e.g. registered tax allowances)<\/li>\n  <li><strong>Factorisation method<\/strong> (under tax class IV\/IV with factor)<\/li>\n<\/ul>\n<p>These features are applied in the billing system. Even small discrepancies can lead to incorrect tax deductions \u2013 and thus to queries, corrections, or audit findings.<\/p>\n<\/section>\n      <section id=\"pruefungslogik\">\n<h2>Payroll process logic<\/h2>\n<p>A practical ELStAM process consists of clear steps:<\/p>\n<ol>\n  <li><strong>New entry:<\/strong> Record master data, correctly store identification data, initiate retrieval.<\/li>\n  <li><strong>Initial invoice<\/strong> Check that the features are present and plausible (tax class, church tax, child allowances).<\/li>\n  <li><strong>Monthly routine:<\/strong> Before month-end, check and, if necessary, accept change notifications.<\/li>\n  <li><strong>Documentation<\/strong> Retrievable and change records should be stored in a traceable manner (logs, system extracts).<\/li>\n  <li><strong>Special cases<\/strong> Handle multiple employments, changes of status, or factor procedures with additional control.<\/li>\n<\/ol>\n<div class=\"snippet tip\">\n  <p class=\"title\">Practice tip<\/p>\n  <p>The greatest lever is not \u201emore control\u201c, but <strong>a fixed routine<\/strong>New joiner check, month-end close check, and clear responsibility for queries.<\/p>\n<\/div>\n<\/section>\n      <section id=\"pruefungszeitraum\">\n<h2>Why ELStAM are not \u201edone once and for all\u201c<\/h2>\n<p>ELStAM can change during the year \u2013 for example, due to changes in tax classes, adjustments to allowances, or the church tax indicator. Companies therefore require a process that reliably detects and promptly processes changes.<\/p>\n<p>Organisational note: ELStAM are not a one-off retrieval upon hiring, but an ongoing data stream. Without defined controls before month-end closing, changes are often only noticed when employees inquire or an audit reveals discrepancies.<\/p>\n<\/section>\n      <section id=\"ablauf\">\n<h2>Typical process for changes<\/h2>\n<p>When ELStAM change, a clear procedure is recommended:<\/p>\n<ul>\n  <li><strong>Detect change<\/strong> Regularly check system notes \/ change logs.<\/li>\n  <li><strong>Plausibilise<\/strong> Does the change fit the facts (e.g. tax class after marriage)?<\/li>\n  <li><strong>Implement<\/strong> Apply features and use for the billing month.<\/li>\n  <li><strong>Document<\/strong> Briefly note when the change was implemented.<\/li>\n<\/ul>\n<p>In practice, documentation is often the bottleneck. If it later needs to be determined when what data was available, clean archiving is crucial.<\/p>\n<\/section>\n      <section id=\"praxis\">\n<h2>Case studies<\/h2>\n\n<h3>Practical Case 1: Change of tax class not taken into account<\/h3>\n<p>An employee changes their tax class during the year. The change is available electronically, but is not taken into account in the payroll. Result: incorrect income tax deduction, corrected payroll and additional reconciliation effort with the employee.<\/p>\n\n<h3>Case Study 2: Multiple Employment \/ Tax Class VI<\/h3>\n<p>When you have multiple employments, it can become relevant to assign tax class VI. If this is not handled correctly, incorrect deductions will occur, leading to frequent queries. Organisationally, a clear routine for clarifying secondary employments upon hiring and when changes occur is important.<\/p>\n\n<h3>Case Study 3: Factor Method (IV\/IV with Factor)<\/h3>\n<p>The factoring procedure requires a clean transfer of the factor. If the factor is not taken into account, deviations in the current tax burden will occur. Often, it is not the calculation that is difficult, but the <em>Procedural handling<\/em> and current affairs.<\/p>\n<\/section>\n      <section id=\"finanzielle-wirkung\">\n<h2>Financial and organisational impact<\/h2>\n<p>ELStAM errors are rarely \u201ejust a tax issue\u201c. In practice, they lead to:<\/p>\n<ul>\n  <li>Queries and dissatisfaction among employees (net amount differs)<\/li>\n  <li>Correction calculations and additional runs<\/li>\n  <li>Increased effort in communication and documentation<\/li>\n  <li>to a higher audit risk, because deviations must be traceable<\/li>\n<\/ul>\n<p>A robust routine is particularly worthwhile with many employees or complex remuneration components, as small errors can otherwise multiply.<\/p>\n<\/section>\n      <section id=\"dauer-kommunikation\">\n<h2>Duration, Communication and Roles within the Company<\/h2>\n<p>ELStAM problems often arise at interfaces: entry, changes, exit. That's why a clear division of roles is important:<\/p>\n<ul>\n  <li><strong>Competence<\/strong> Who checks new entries and who checks changes before the month-end closing?<\/li>\n  <li><strong>Communication<\/strong> How can queries about tax features be answered factually without \u201emonth-end panic\u201c?<\/li>\n  <li><strong>Documentation<\/strong> Where are retrieval logs and change records stored?<\/li>\n<\/ul>\n<p>Companies with defined responsibilities experience ELStAM adjustments as routine. Without defined responsibilities, changes are made \u201eon the side\u201c \u2013 and that's precisely where typical errors occur.<\/p>\n<\/section>\n      <section id=\"fehlerquellen\">\n<h2>Typical sources of error<\/h2>\n<ul>\n  <li><strong>Delayed retrieval<\/strong> upon new entry (characteristics are not correct on the first billing)<\/li>\n  <li><strong>Changes will not be applied<\/strong> (Tax class change, allowances, church tax indicator)<\/li>\n  <li><strong>Log-off missing<\/strong> On exit (unnecessary messages \/ queries)<\/li>\n  <li><strong>Special cases without additional control<\/strong> (Multiple employment, factor method)<\/li>\n  <li><strong>No documentation<\/strong> (later unclear when data was available)<\/li>\n<\/ul>\n<div class=\"snippet warn\">\n  <p class=\"title\">Note<\/p>\n  <p>In exams, not only mistakes are relevant, but also the <strong>Comprehensibility<\/strong>. If documentation is missing, a situation is often unnecessarily \u201eblown out of proportion\u201c.<\/p>\n<\/div>\n<\/section>\n      <section id=\"kontrollen\">\n<h2>Controls and prevention<\/h2>\n<p>Three simple control points have proven effective:<\/p>\n<ul>\n  <li><strong>Onboarding Check:<\/strong> Retrieve features, check plausibility, secure storage.<\/li>\n  <li><strong>End-of-month check:<\/strong> Check change lists, apply changes, document briefly.<\/li>\n  <li><strong>Special case check:<\/strong> Multiple employments, factor methods or special configurations with a four-eyes principle.<\/li>\n<\/ul>\n<p>Many companies also choose to outsource in order to increase process stability. However, it remains crucial that changes and special cases are reported internally in a timely manner.<\/p>\n<\/section>\n      <section id=\"checkliste\">\n<h2>Practice checklist<\/h2>\n<ul>\n  <li>Are ELStAM retrieved immediately for new joiners?<\/li>\n  <li>Is there a documented testing routine for changeovers before month-end?<\/li>\n  <li>Are retrieval logs and change records verifiably archived?<\/li>\n  <li>Is there a clear area of responsibility (including representation)?<\/li>\n  <li>Are special cases examined separately (multiple employment, factor procedure)?<\/li>\n<\/ul>\n<\/section>\n      <section id=\"faq\">\n<h2>FAQ<\/h2>\n<div class=\"snippet info\">\n        <h3>ELStAM steht f\u00fcr Elektronische LohnSteuerAbzugsMerkmale.<\/h3>\n        <p>ELStAM are the electronic wage tax deduction characteristics that employers require for correct wage tax calculation.<\/p>\n      <\/div>\n\n<div class=\"snippet info\">\n        <h3>Who is responsible for the correct application?<\/h3>\n        <p>The employer. Even if the characteristics are provided electronically, retrieval, adoption, and application must be done correctly.<\/p>\n      <\/div>\n\n<div class=\"snippet info\">\n        <h3>What features are particularly important?<\/h3>\n        <p>In particular, tax class, child allowances, church tax indicator, allowances and the factor method.<\/p>\n      <\/div>\n\n<div class=\"snippet info\">\n        <h3>What are typical sources of error?<\/h3>\n        <p>Late retrieval, changes not taken over, missed sign-off and special cases without additional checks.<\/p>\n      <\/div>\n\n<div class=\"snippet info\">\n        <h3>Are ELStAMs subject to examination?<\/h3>\n        <p>Yes. In payroll tax audits, checks are carried out to see whether the correct characteristics have been applied and whether changes have been verifiably documented.<\/p>\n      <\/div>\n<\/section>\n      <section id=\"fazit\">\n<h2>Conclusion<\/h2>\n<p><strong>ELStAM<\/strong> are the central foundation of every payroll. Errors rarely arise from complicated tax issues, but from a lack of process stability.<\/p>\n<p>Businesses with clearly defined processes, documented controls, and organised filing significantly minimise risks. Structure creates security.<\/p>\n<\/section>\n\n      <footer class=\"author\">\n        <strong>Author<\/strong><br\/>\n        Editing of Brasser Accounting Solutions Ltd<br\/>\n        <p class=\"note\">This glossary entry is for general information only.<\/p>\n      <\/footer>","protected":false},"template":"","glossar-kategorien":[18],"class_list":["post-4010","glossar","type-glossar","status-publish","hentry","glossar-kategorien-lohnbuchhaltung"],"_links":{"self":[{"href":"https:\/\/www.brasser-accounting.de\/en\/wp-json\/wp\/v2\/glossar\/4010","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.brasser-accounting.de\/en\/wp-json\/wp\/v2\/glossar"}],"about":[{"href":"https:\/\/www.brasser-accounting.de\/en\/wp-json\/wp\/v2\/types\/glossar"}],"wp:attachment":[{"href":"https:\/\/www.brasser-accounting.de\/en\/wp-json\/wp\/v2\/media?parent=4010"}],"wp:term":[{"taxonomy":"glossar-kategorien","embeddable":true,"href":"https:\/\/www.brasser-accounting.de\/en\/wp-json\/wp\/v2\/glossar-kategorien?post=4010"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}