Skip to content
EU DSA · EU-DSA-ART24-TRANSPARENCY-REPORTING

EU DSA DSA Articles 15, 24 and 42 — Distinct reporting duties

Assess reporting duties separately: Article 15 general transparency reports are at least annual, subject to its exclusion; Article 24(2) recipient counts are at least six-monthly; designated VLOPs/VLOSEs have enhanced at-least-six-monthly reporting under Article 42. Article 24(5) statements-of-reasons database submission is a separate duty.

HIGHRecord-keeping dutyTransparencyBinding regulationIn forceApplies from 17 February 2024

Where this comes from

Provision: DSA Articles 15, 24 and 42 — Distinct reporting duties

Instrument: EU Digital Services Act (Regulation 2022/2065)

Citation: DSA Articles 15, 24 and 42 — Distinct reporting duties

Text version: Regulation (EU) 2022/2065 (Digital Services Act), OJ L 277, 27.10.2022, as adopted (CELEX 32022R2065); no consolidated text exists on Cellar, consistent with the Regulation being unamended; text retrieved 2026-09-21.

Read the official text ↗

Who it applies to

It applies when all of these are true:

  • Service is an online platform
  • Service has users in the European Union
  • Service allows user-generated content

…unless:

  • Section 3 (Articles 20-28), with the exception of Article 24(3), does not apply to providers of online platforms that qualify as micro or small enterprises under Recommendation 2003/361/EC, nor, for the 12 months after losing that status, to providers that... (DSA Article 19(1)-(2) - Exclusion for micro and small enterprises (Section 3))

What engineering work it implies

Sample acceptance criteria Landfall generates for this obligation:

  • Assess reporting duties separately: Article 15 general transparency reports are at least annual, subject to its exclusion; online platforms MUST add to that report the Article 24(1) content - disputes submitted to out-of-court bodies with outcomes, median completion time and the share of body decisions implemented (24(1)(a)), and Article 23 suspensions distinguished by ground (24(1)(b)); Article 24(2) recipient counts are at least six-monthly and MUST be communicated to the Digital Services Coordinator or the Commission on request (24(3)); designated VLOPs/VLOSEs have enhanced at-least-six-monthly reporting under Article 42. Article 24(5) statements-of-reasons database submission is a separate duty. Article 19: Section 3, except Article 24(3), does not apply to micro or small enterprises unless designated a VLOP.
  • Document service role, Article 19/15 exclusions and designation before assigning each reporting task. Maintain separate reporting/count/submission schedules and apply the current reporting templates. Do not impose a blanket six-monthly general report on every platform.
  • Record the assessed scope, evidence and unresolved questions; completing this task is not a legal compliance determination.

Questions people ask

Does EU DSA DSA Articles 15, 24 and 42 — Distinct reporting duties apply to my service?
It applies when Service is an online platform; Service has users in the European Union; Service allows user-generated content. It does not apply where Section 3 (Articles 20-28), with the exception of Article 24(3), does not apply to providers of online platforms that qualify as micro or small enterprises under Recommendation 2003/361/EC, nor, for the 12 months after losing that status, to providers that... (DSA Article 19(1)-(2) - Exclusion for micro and small enterprises (Section 3)).
From when does this apply?
EU DSA DSA Articles 15, 24 and 42 — Distinct reporting duties applies from 17 February 2024. Its current status is: in force.

Find out whether this one lands on you

Landfall's pre-scan answers the applicability question above for your product in minutes, then turns every obligation that applies into traceable engineering tickets with a citation chain your auditors can follow.

Not legal advice. Landfall maps regulatory obligations to engineering work for planning purposes. Its verdicts are not legal advice and create no attorney-client relationship — verify with qualified counsel before relying on them.

What Landfall Is NOT

Critical Boundaries

Understanding these boundaries is essential before using this product. Misuse of this tool for purposes outside its scope may create legal, regulatory, or commercial risk for your organization.

NOT Legal Advice

This product does not provide legal advice and does not create an attorney-client relationship.

Interpretations are informational analysis, not legal counsel. Always consult qualified legal professionals for compliance decisions.

NOT a Risk Score

We do not quantify, calculate, or certify your compliance risk level.

No numerical risk rating, compliance percentage, or safety score. Risk assessment requires human judgment about your specific context.

NOT Runtime Enforcement

This is a planning and mapping tool, not a runtime enforcement system.

Does not integrate with your production systems. Does not block, filter, or enforce compliance in real-time. Implementation is your responsibility.

NOT Regulatory Approval

Using this tool does not mean you are compliant with any regulation.

No certification, seal of approval, or compliance guarantee. Regulators will evaluate your actual implementation, not your use of this tool.

NOT Authoritative Interpretation

Our interpretations are not binding and may differ from regulatory guidance.

Only regulators and courts provide authoritative interpretation. Our analysis reflects our reading of requirements, which may be incomplete or incorrect.

NOT a Safe Harbor

This tool does not shield you from enforcement actions or liability.

Documentation of your process is valuable, but does not constitute a legal defense. Compliance is ultimately your organization's responsibility.

NOT an AI Compliance Agent

AI features assist analysis but do not make compliance decisions for you.

AI-generated interpretations require human review and approval. Automated suggestions are starting points, not final answers.

NOT Complete Coverage

We do not cover all regulations, all obligations, or all jurisdictions.

Regulatory landscape is vast and evolving. Gaps in our coverage do not mean those requirements don't apply to you.

What This Tool IS:

  • A structured workflow for mapping regulatory requirements to implementation tasks
  • A documentation system for compliance decisions (audit trail)
  • A collaboration platform for compliance, legal, and engineering teams
  • An informational resource for understanding regulatory obligations