CSDDD vs German LkSG comparison Keep EU and German duties separate

CSDDD applies to EU and non-EU companies meeting the directive's employee, turnover, group-parent, franchise, or licensing criteria. The EU source states the general threshold as more than 1,000 employees and turnover above EUR 450 million, with special group and franchise/licensing routes.

German LkSG coverage must be checked under German law. This page does not publish German employee thresholds without a current official German source for the specific threshold claim.

Do not decide German LkSG coverage from a CSDDD scope memo. Create one scope memo per regime, then identify which entities appear in both.

CSDDD is Directive (EU) 2024/1760. It must be transposed into national law and does not reduce existing national human, employment, social, environmental, or climate provisions.

German LkSG is already a national law workstream. Do not treat CSDDD transposition planning as proof that German LkSG obligations are satisfied or replaced.

Keep a CSDDD transposition tracker and a German LkSG compliance register. Link shared supplier-risk evidence only after both legal bases are checked.

CSDDD uses a chain-of-activities concept. It covers own operations, subsidiaries, and business partners where related to the company's chains of activities, with mapping and in-depth assessment focused on areas where adverse impacts are most likely and severe.

German LkSG should not be described with CSDDD chain-of-activities wording. For German LkSG, verify the statutory supply-chain boundary and any direct or indirect supplier rules against German official material before publishing guidance.

Use one supplier map if practical, but label every node with the regime whose boundary brings it into review. A CSDDD chain-of-activities label is not automatically an LkSG supply-chain label.

CSDDD requires risk-based human rights and environmental due diligence: integrate due diligence into policies and risk management systems, identify and prioritise adverse impacts, prevent and mitigate potential impacts, bring actual impacts to an end or minimise them, provide remediation where required, engage stakeholders, monitor effectiveness, communicate publicly, and keep documentation.

German LkSG controls may use some of the same operational evidence, such as risk analysis records, supplier measures, remediation logs, and complaint handling, but the German control wording and trigger should stay tied to German law.

Build a crosswalk from control to source. Mark a control as reusable only when the same record satisfies both the CSDDD article-level need and the German LkSG requirement.

CSDDD requires regular monitoring of due diligence effectiveness at least every 12 months, public communication through an annual statement unless an exemption applies, and retention of due diligence compliance documentation for at least five years.

German LkSG reporting and documentation should be tracked on a separate German-law calendar. Do not import CSDDD's annual-statement, ESAP, or five-year documentation wording into an LkSG report without German source support.

Create one evidence index with separate columns for CSDDD article support, German LkSG support, owner, reporting output, retention basis, and last review.

CSDDD requires accessible, publicly available notification and complaints procedures with appropriate follow-up. Complaints may come from affected persons, their legitimate representatives, trade unions and workers' representatives, and experienced civil-society organisations for environmental impacts.

German LkSG complaint channels should be operated and described under the German-law procedure. Do not assume the CSDDD complainant categories, anonymity/confidentiality wording, or follow-up rights are identical.

Use a shared intake tool only if it clearly routes complaints to the correct regime and procedure. The intake record should capture which law applies, not just a generic complaint label.

CSDDD relies on Member State supervisory authorities with powers to require information, investigate, order cessation, impose penalties or interim measures, and publish penalty decisions. The directive also contains civil liability rules for certain damage caused by intentional or negligent failures to comply with specified obligations.

German LkSG enforcement should be checked under German law and the relevant German authority process. Do not copy CSDDD penalty caps, publication rules, or civil-liability language into LkSG guidance.

Keep enforcement response playbooks separate. Shared evidence can support both, but authority powers, response deadlines, penalty logic, and litigation exposure need regime-specific review.

CSDDD evidence should show the article-level basis for scope, chain-of-activities mapping, due diligence measures, complaints, monitoring, public communication, transition-plan work, and supervisory authority responses.

German LkSG evidence can be reused only where the same record also satisfies the German-law element. Supplier questionnaires, audit results, complaint records, and remediation logs need separate labels if they support both regimes.

Use one evidence repository, but not one legal conclusion. Every reused record should identify the source, obligation, owner, date, affected entity, supplier boundary, and publication or authority-use status.

CSDDD requires covered companies to adopt and put into effect a climate change transition plan aligned with the transition to a sustainable economy and the Paris Agreement 1.5 C objective, including targets, decarbonisation levers, investments and funding, and governance roles.

Do not add a German LkSG climate-transition-plan obligation by analogy. If a German entity also reports under another sustainability regime, handle that under the relevant reporting source, not under LkSG by assumption.

Keep the CSDDD transition-plan owner, data model, and approvals separate from German LkSG supplier due diligence records unless another source explicitly joins them.