{"id":4045,"date":"2026-03-24T13:36:51","date_gmt":"2026-03-24T13:36:51","guid":{"rendered":"https:\/\/www.brasser-accounting.de\/?post_type=glossar&#038;p=4045"},"modified":"2026-05-12T10:12:39","modified_gmt":"2026-05-12T10:12:39","slug":"notification-procedure","status":"publish","type":"glossar","link":"https:\/\/www.brasser-accounting.de\/en\/glossar\/sv-meldeverfahren\/","title":{"rendered":"Detergent process"},"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=\"#grundlagen\">Basics<\/a><\/li>\n        <li><a href=\"#begriffe\">Reports<\/a><\/li>\n        <li><a href=\"#prozess\">Process<\/a><\/li>\n        <li><a href=\"#praxis\">Practice<\/a><\/li>\n        <li><a href=\"#fehler\">Error<\/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>SV reporting procedure<\/strong> refers to the electronic reporting procedure for social security. Employers transmit employee data and reporting events in accordance with the specifications of the <strong>German pension insurance<\/strong> (Data Capture and Transmission Regulation).<\/p>\n          <p class=\"note\">The procedure is an mandatory part of every payroll: declarations must be processed completely, plausibly, and on time.<\/p>\n        <\/div>\n\n        <p>In practice, the social security reporting procedure is closely integrated with the monthly payroll. Many reports arise from typical events in the employment relationship (entry, exit, year-end closing, interruptions) and are transmitted electronically to the responsible receiving offices.<\/p>\n\n        <p class=\"note\">Closely related terms <a href=\"\/en\/glossary\/contribution-proof\/\">Contribution certificate<\/a>, <a href=\"\/en\/glossary\/eltham\/\">ELStAM<\/a>.<\/p>\n      <\/section>\n\n      <section id=\"grundlagen\">\n        <h2>Fundamentals: Purpose and Legal Framework<\/h2>\n        <p>The social security reporting procedure ensures that social insurance carriers receive the employee data required for insurance, contributions, and benefit claims in a standardised form. The technical and formal design complies with the requirements of the DE\u00dcV (Data Collection and Transmission Regulation) and the associated joint principles.<\/p>\n\n        <h3>What is conveyed in essence<\/h3>\n        <ul>\n          <li>Master data for the employee (e.g. insurance and personal data, where required)<\/li>\n          <li>Employment-related details (e.g. period, reason for notification, contribution-related characteristics)<\/li>\n          <li>Remuneration-related information, insofar as it is intended for the reporting requirement<\/li>\n        <\/ul>\n\n        <div class=\"snippet tip\">\n          <p class=\"title\">Motto<\/p>\n          <p>The SV reporting procedure is not an \u201eextra.\u201c It is the standardised digital channel through which employee data relevant to social security reliably flows to the social insurance institutions.<\/p>\n        <\/div>\n      <\/section>\n\n      <section id=\"begriffe\">\n        <h2>Typical messages in the electronic social security reporting procedure<\/h2>\n        <p>Which report is required depends on the specific event and the reason for reporting. In practice, the following types of reports are particularly common:<\/p>\n\n        <ul>\n          <li><strong>Registration<\/strong> upon commencing employment<\/li>\n          <li><strong>Deregistration<\/strong> upon termination of employment<\/li>\n          <li><strong>Annual report<\/strong> as a regular report for specific periods<\/li>\n          <li><strong>Interruption reports<\/strong> during longer interruptions (depending on the offence)<\/li>\n          <li><strong>Special reports<\/strong> in special constellations (depending on specifications\/industry)<\/li>\n        <\/ul>\n\n        <div class=\"snippet warn\">\n          <p class=\"title\">Important<\/p>\n          <p>Reporting reasons and datasets are strictly standardised. Even minor deviations (e.g. incorrect time period or implausible feature combinations) frequently lead to feedback or error logs.<\/p>\n        <\/div>\n      <\/section>\n\n      <section id=\"prozess\">\n        <h2>This is typically how electronic transmission works<\/h2>\n        <ol>\n          <li><strong>Database<\/strong> from payroll accounting (master and transaction data, reporting reason)<\/li>\n          <li><strong>Plausibility check<\/strong> through software\/test routines (mandatory fields, logical rules)<\/li>\n          <li><strong>Electronic submission<\/strong> to the responsible data reception office<\/li>\n          <li><strong>Feedback<\/strong> (Protocol\/Receipt) \u2013 Acceptance, Error or Need for Clarification<\/li>\n          <li><strong>Documentation<\/strong> (Filing of the report and feedback, traceable release\/version)<\/li>\n        <\/ol>\n\n        <h3>Transmission routes<\/h3>\n        <p>In practice, notifications are made either via a certified payroll accounting program or via system-tested input aids. Important: An input aid does not replace professional accounting \u2013 it merely supports the correct data record transmission.<\/p>\n\n        <p>As notifications are closely linked to ongoing billing, responsibilities and deadlines should be clearly defined \u2013 especially when billing or parts thereof are outsourced.<\/p>\n      <\/section>\n\n      <section id=\"praxis\">\n        <h2>Practice: Common Causes of Effort and Returns<\/h2>\n\n        <h3>1) Data arrives too late or is incomplete<\/h3>\n        <p>If an entry\/exit, health insurance change, or status change is only reported after the billing run, corrections will occur \u2013 often including re-reporting and subsequent expenses in the documentation.<\/p>\n\n        <h3>2) Unclear responsibilities<\/h3>\n        <p>Who provides the information, who checks it, who approves it? Unclear roles lead to queries, delays and, in the worst case, errors in reports and records.<\/p>\n\n        <h3>3) Missing documentation<\/h3>\n        <p>For queries or reviews, it is crucial that reports and feedback are filed in a traceable manner. This also applies to accompanying documents such as <a href=\"\/en\/glossary\/contribution-proof\/\">Contribution statements<\/a>.<\/p>\n\n        <div class=\"snippet tip\">\n          <p class=\"title\">Rule of thumb<\/p>\n          <p>The SV reporting procedure runs stably when cut-off dates, data sources, and release processes are clearly defined \u2013 and feedback is consistently processed.<\/p>\n        <\/div>\n      <\/section>\n\n      <section id=\"fehler\">\n        <h2>Typical error patterns<\/h2>\n\n        <h3>Implausible combinations<\/h3>\n        <p>A common reason for feedback is implausible combinations of periods, reporting reasons, and contribution-related characteristics. Clear verification steps before submission can help.<\/p>\n\n        <h3>Missing or incorrect key details<\/h3>\n        <p>With standardised datasets, missing mandatory fields or formal errors quickly lead to rejections. Therefore, it makes sense to review software test logs and systematically document clarifications.<\/p>\n\n        <div class=\"snippet warn\">\n          <p class=\"title\">Responsibility disclaimer<\/p>\n          <p>Even if a service provider supports or bills, the responsibility for correct and timely reports remains with the employer.<\/p>\n        <\/div>\n      <\/section>\n\n      <section id=\"checkliste\">\n        <h2>Checklist: Streamline the social insurance reporting process<\/h2>\n        <div class=\"snippet tip\">\n          <ul>\n            <li><strong>Set deadlines:<\/strong> By when do entries\/exits and changes need to be submitted?<\/li>\n            <li><strong>Define data sources<\/strong> Who provides what information (HR, time management, leadership)?<\/li>\n            <li><strong>Document test steps:<\/strong> What plausibilities are checked before submission?<\/li>\n            <li><strong>Edit feedback:<\/strong> Review logs, resolve errors promptly, secure filing.<\/li>\n            <li><strong>Provide evidence thoughtfully:<\/strong> e.g. <a href=\"\/en\/glossary\/contribution-proof\/\">Contribution certificate<\/a> and follow-up processes<\/li>\n            <li><strong>Check interfaces<\/strong> Keep handovers to the billing system\/archive\/financial accounting clean<\/li>\n            <li><strong>Organising storage:<\/strong> Archiving reports and feedback in a way that allows for traceability<\/li>\n          <\/ul>\n        <\/div>\n      <\/section>\n\n      <section id=\"faq\">\n        <h2>FAQ<\/h2>\n\n        <div class=\"snippet info\">\n        <h3>What is the SV registration procedure?<\/h3>\n        <p>The SV reporting procedure is the electronic reporting procedure for social security. Employers use it to submit standardised reports on employee-related events in accordance with the DE\u00dcV guidelines.<\/p>\n      <\/div>\n\n        <div class=\"snippet info\">\n        <h3>What does DE\u00dcV stand for?<\/h3>\n        <p>DE\u00dcV stands for the Data Collection and Transmission Regulation. It sets out the formal requirements for the electronic collection and transmission of data as part of the registration procedure.<\/p>\n      <\/div>\n\n        <div class=\"snippet info\">\n        <h3>What are some typical error messages?<\/h3>\n        <p>Typical examples include notifications of commencement, termination and annual returns, as well as notifications in the event of interruptions and special circumstances. The specific obligation depends on the reason for the notification.<\/p>\n      <\/div>\n\n        <h3>What role does ELStAM play in this?<\/h3>\n        <p><a href=\"\/en\/glossary\/eltham\/\">ELStAM<\/a> This relates to the payroll tax procedure. In practice, tax and social security matters run in parallel, but are dealt with under different procedures.<\/p>\n      <\/section>\n\n      <section id=\"fazit\">\n        <h2>Conclusion<\/h2>\n        <p>The SV reporting procedure is the standardised electronic channel for social insurance notifications. Those who clearly organise data sources, cut-off dates, checking steps and the processing of feedback reduce returns and stabilise the entire payroll process.<\/p>\n      <\/section>\n\n      <footer class=\"author\">\n        <strong>Author<\/strong><br\/>\n        the BAS editorial team<br\/>\n        <p class=\"note\">This glossary entry is for general information only.<\/p>\n      <\/footer>\n\n      <p class=\"disclaimer\">\n        Brasser Accounting Solutions GmbH is a specialised accounting service provider and part of a corporate group with Quint GmbH (tax consultancy\/auditing) and Service Place \u00c5rj\u00e4ng AB (Swedish tax office). BAS exclusively performs services according to \u00a7 6 No. 3 and 4 StBerG and does not provide tax or legal advice.\n      <\/p>","protected":false},"template":"","glossar-kategorien":[18],"class_list":["post-4045","glossar","type-glossar","status-publish","hentry","glossar-kategorien-lohnbuchhaltung"],"_links":{"self":[{"href":"https:\/\/www.brasser-accounting.de\/en\/wp-json\/wp\/v2\/glossar\/4045","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=4045"}],"wp:term":[{"taxonomy":"glossar-kategorien","embeddable":true,"href":"https:\/\/www.brasser-accounting.de\/en\/wp-json\/wp\/v2\/glossar-kategorien?post=4045"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}