Confirmed corruption incidents and actions taken
Measurement answer
What this metric measures
Distinct corruption incidents substantiated under the organization's declared confirmation process, with incident nature and response actions retained as non-additive attributes.
Specification
Metric specification
- Result format
- Structured table
- Unit
- Distinct confirmed corruption incidents
- Reporting basis
- Reporting period
- Aggregation
- Add only non-overlapping records after applying the stated identity and deduplication controls
- Pillar
- Governance
- Topic
- Business conduct and compliance
- Controlled domain
- Governance and business conduct
- Entity type
- Metric
Reporting boundary
Exclude allegations and investigations that remain unconfirmed. Deduplicate one incident across people, actions and any linked public legal matters.
Cross-library identity
Library mappings and variants
These links compare quantity, population, boundary, period, unit, denominator, aggregation, dimensions, and method edition. Partial relationships are navigation aids only and never authorize observation reuse.
- Aggregate relationshipPartial relationship; observations remain separate.Nature of confirmed incidents of corruption — GRI 205-3, paragraph a
- Aggregate relationshipPartial relationship; observations remain separate.Status of incidents and actions taken 4061 profile — GRI 406-1, paragraph b
- Aggregate relationshipPartial relationship; observations remain separate.Status of incidents and actions taken 4111 profile — GRI 411-1, paragraph b
- Aggregate relationshipPartial relationship; observations remain separate.Total confirmed incidents of corruption count — GRI 205-3, paragraph a
Verified source occurrences
Framework coverage
This is one canonical metric. The bindings below show every verified framework occurrence without creating duplicate metric pages. Edition, disclosure, role, and relationship remain source-specific.
- Adopting DisclosureGRI 406-1
GRI Standards
- Publisher
- Global Reporting Initiative
- Edition
- Files published 19 June 2025; entry point dated 23 June 2025
- Requirement
- Not Specified
- Relationship
- Component Of
- Mapping outcome
- Cross Library Link
- Source locator
- GRI 406-1, paragraph b; taxonomy entry point dated 23 June 2025
- Adopting DisclosureGRI 411-1
GRI Standards
- Publisher
- Global Reporting Initiative
- Edition
- Files published 19 June 2025; entry point dated 23 June 2025
- Requirement
- Not Specified
- Relationship
- Component Of
- Mapping outcome
- Cross Library Link
- Source locator
- GRI 411-1, paragraph b; taxonomy entry point dated 23 June 2025
- Adopting DisclosureGRI 205-3
GRI Standards
- Publisher
- Global Reporting Initiative
- Edition
- Files published 19 June 2025; entry point dated 23 June 2025
- Requirement
- Not Specified
- Relationship
- Component Of
- Mapping outcome
- Cross Library Link
- Source locator
- GRI 205-3, paragraph a; taxonomy entry point dated 23 June 2025
- Adopting DisclosureGRI 205-3
GRI Standards
- Publisher
- Global Reporting Initiative
- Edition
- Files published 19 June 2025; entry point dated 23 June 2025
- Requirement
- Not Specified
- Relationship
- Component Of
- Mapping outcome
- Cross Library Link
- Source locator
- GRI 205-3, paragraph a; taxonomy entry point dated 23 June 2025
- Adopting DisclosureSource evidence
GRI Standards
- Publisher
- Global Reporting Initiative
- Edition
- 2016
- Requirement
- Not Specified
- Relationship
- Defines Disclosure
- Mapping outcome
- Direct Evidence
- Source locator
- Disclosure 205-3, PDF page 10; confirmed-incident definition, PDF page 11
Value structure
Dimensions and units
- Unit
- Distinct confirmed corruption incidents
- Reporting basis
- Reporting period
Unit meaning: A non-negative count of incidents meeting the organization's explicit confirmation rule; actions, dismissals and terminations are attributes rather than additional incidents.
Table fields and units
- Incident identity
- Confirmation basis
- Confirmation date
- Incident nature
- Employee action
- Business-partner action
- Legal-case link
Published dimensions
- incident identity
- confirmation process
- confirmation date
- incident nature
- employee action
- business-partner action
- public legal case link
- reporting period
- privacy state
Disclosure method
Formula information
- Status
- Not applicable
- Formula type
- Structured Disclosure
Disclosure form
No single formulaPopulate the structured fields from qualifying source observations and retain each field-level unit, boundary, status, and method; do not collapse the disclosure into one calculated value.
Verified sources
Evidence and status sources
Sustopedia checked each record-specific claim directly against primary publisher material. Labels distinguish current measurement authority from future compatibility and corroborative, legal, edition, or method status context. Corroborative evidence can support a stated limitation but cannot establish the core measurement by itself.
Measurement evidence
- Measurement evidenceChecked 15 August 2026
GRI 205: Anti-corruption 2016
- Publisher
- Global Reporting Initiative
- Edition
- 2016
- Locator
- Disclosure 205-3, PDF page 10; confirmed-incident definition, PDF page 11
Supports: Supports the confirmed corruption incident population and associated action states.
Open official source
Use with context
Interpretation boundaries
Method disclosures required
Source-edition basis: GRI 205: Anti-corruption 2016, current effective edition at the research cutoff.
- Define the confirmation process and incident identity.
- Exclude open allegations and investigations from confirmed count.
- Keep response actions and public legal outcomes as separately typed fields.
Record-specific limitations
- Substantiation does not necessarily mean conviction or public legal finding.
- The count does not measure corruption prevalence, loss, remedy quality or control effectiveness.
Interpret this metric with the stated reporting boundary, period convention, value shape, and unit. Results prepared with different boundaries or conventions may not be directly comparable.
Measurement evidence supports the core record-specific claims described above. Corroborative evidence can support limitations, while compatibility and status sources provide their separately labelled context. None of these cards by itself determines an organisation's legal applicability, filing readiness, assurance status, or compliance conclusion.