Entity-specific disclosures

What it means in practice

Entity-specific disclosures should be read as a practical reporting term, where meaning depends on the reporting framework, boundary, evidence and user need.

In practice, users should name the source, scope, boundary and evidence behind the term. That makes entity-specific disclosures useful as a reference rather than a vague label.

Why it matters

Entity-specific disclosures matters because reporting work depends on consistent language across governance, data collection, assurance and public disclosure. Without context, the same term can be understood differently by preparers, reviewers and users.

Common misconception

A common error is to treat Entity-specific disclosures as a checklist item rather than a defined part of the reporting process. The stronger approach is to state the method, owner, evidence and review status.

Review questions

What source or framework gives the term authority? What boundary or role is being described? What evidence would a reviewer need before relying on the term?

How it is used

Standard setters, scheme owners, certification bodies, auditors and organisations seeking assurance use “Entity-specific disclosures” in standards, certification, conformity assessment, audits, controls and assurance engagements.

In each case, the user should state the named standard or scheme, version, scope, criteria, assurance level and competent decision-maker; otherwise, the same term may be applied to materially different situations. In this context, it refers to sustainability disclosures developed by an organisation to explain material matters that are not fully covered by general or sector standards.