This disclosure asks an organisation to explain how it oversees tax matters in practice. The focus is on the systems, controls and responsibilities that shape tax decision-making, including who is accountable, how tax risks are identified and managed, and how tax governance is embedded in the organisation’s wider control environment.
In practical terms, the report should describe the approach across the organisation as a whole, not just a few well-known sites or a single business unit. The useful question is whether the tax governance framework applies consistently across operations, and how it helps the organisation manage tax-related risk in a structured way.
This LRA educational guidance supports disclosure preparation. For the exact requirements, always refer to the official GRI source.
A quick mental checklist before you prepare this disclosure — tick each as you settle it.
Key datapoints to prepare
How to prepare it
Request the tax governance and control evidence
Translate the disclosure into an internal business question — then adapt it to your organisation's own language.
Use your organisation’s own labels first (for example, tax policy, control map, risk register, speak-up route, assurance pack), then map them to the disclosure wording during drafting. Keep the request in the language your tax, finance, legal, and governance teams already use.
Please provide the GRI 207-2 evidence for tax governance, control, risk management, concerns mechanisms, and assurance.
Why it fails: It uses framework language only, so the owner has to translate the ask before they can act. It also does not say which internal records, systems, or named roles to pull, so the response is likely to be incomplete or inconsistent.
Please send the current tax policy or equivalent, the named person or committee that oversees tax, the way tax is built into business processes, the tax risk log and review cadence, the check used to confirm controls are working, the route for raising tax-related concerns, and any external assurance note for tax disclosures. Use your team’s own terms and include document name, version/date, owner, and file link.
Notes that turn data into a disclosure
LRA training templates — adapt them to your organisation, and check the official source before sign-off.
Explain the basis used to describe the tax governance setup, including how roles, controls, risk handling, concern-raising routes and any external assurance were identified and summarised.
Set out what the disclosure tells readers about how tax is overseen, who is accountable, how tax is embedded in the organisation, and how confidence in the information is supported.
If the description changes from one period to the next, note whether that reflects a change in governance, control design, risk handling, reporting routes or the scope of assurance rather than a change in tax outcomes.
Preparation tools & forms
Professional preparation tools for GRI 207-2 — free with an LRA Community membership. Register once (it's free) and every download unlocks, together with the Disclosure Library, templates and the LRA AI-assistant.
For each claim, check the evidence
Evidence pack to prepare
Common reporting gaps
Mistakes to avoid when collecting the data
Where judgement is often needed
Illustrative examples
Synthetic, written by LRA — not from a company report, not text from any standard.
*Synthetic example for training only.* We describe a tax control set that sits under our finance policy, with board oversight through the audit committee and day-to-day ownership by the group tax lead, who reports into the chief financial officer. Tax thinking is built into budgeting, pricing, acquisitions, and country filings through written procedures, staff training, and quarterly reviews; we track risks by jurisdiction, log issues in a register, and test controls through internal review and periodic management checks. - We assess whether the control set is working through self-assessments, internal audit testing, and sign-off from finance leaders, while staff can raise tax-related conduct concerns through our ethics line, whistleblowing route, and direct escalation to the audit committee chair. - For this disclosure, an external firm reviewed the tax narrative and selected data points, and its limited assurance statement is referenced in our annual report appendix.
This example shows how a reporter can explain who owns tax oversight, how tax is built into operations, how risks and controls are monitored, how concerns can be raised, and how the disclosure was externally checked, without using the standard’s wording.
*Synthetic example for training only.* Our tax approach is set out in a group policy that the board approves, with the finance director responsible for delivery and the risk committee receiving regular updates. We embed that approach through approval limits, project-stage tax reviews, country-by-country filing calendars, and training for finance and commercial teams; tax exposures are identified through a risk map, monitored through monthly dashboards, and escalated where controls or filings fall behind. - We check compliance by combining control testing, internal audit work, and management review of exceptions, and people may report concerns about conduct or integrity through our speak-up channel, the ethics mailbox, or direct contact with the chair of the risk committee. - An independent assurance provider reviewed the disclosure package and issued a separate assurance statement, which we refer to in the sustainability section of our annual report.
This example illustrates a different reporting style and governance set-up, while still covering the same required points: control design, ownership, embedding, risk management, compliance checks, speak-up routes, and external assurance.
How companies report GRI 207-2
Real reports where this topic is disclosed. These are report practice, not exact disclosure templates to copy.

Scenarios to work through
A group has a written tax policy, but the finance team says the board only sees tax matters when a problem has already escalated. The tax lead also cannot point to any named person who owns oversight of the tax approach.
A business has a tax risk register, but it was last updated 18 months ago and only lists transfer pricing. Local teams handle VAT and payroll tax issues informally, with no common method for spotting or tracking them.
The company has annual internal audit testing of tax controls, but the tax team cannot explain how the results are used, and there is no evidence that failures lead to action plans or reporting to leadership.
Employees can raise ethics concerns through a general whistleblowing line, but the tax team has never publicised that route for tax-related conduct issues. An external assurance provider has reviewed the tax disclosures, but the draft report does not mention the assurance statement anywhere.
Related framework references
How this disclosure maps across the major reporting frameworks.
Questions this page answers
Start with the datapoints listed on the page: tax control framework, tax accountability lead, how tax is embedded in the business, tax risk management, tax control review, tax concern channels, and the tax assurance process. The page also gives a step-by-step preparation section to help you turn those inputs into a draft.
Use the page’s plain-language explainer and the listed datapoints to decide what your organisation can evidence for the disclosure. The page is designed to help you define the scope and methodology before you write the draft.
The page points you to a tax accountability lead and to tax being embedded in the business, so ownership may sit with tax but need input from other functions. Use the preparation section to assign responsibilities before you start collecting evidence.
The page includes six assurance claims to verify, each with claim, risk and evidence prompts, plus an evidence pack with five items. Use those sections to build a file that shows what was claimed, what could go wrong, and what supports the disclosure.
The evidence pack is there to help you assemble the core documents and records needed for assurance readiness. It sits alongside the assurance claims so you can check that the evidence matches the claim and the risk being addressed.
The page lists common reporting gaps and mistakes so you can spot weak points before finalising the disclosure. Use that section as a pre-submission check against your draft and evidence pack.
The page includes draft-output support with visualisation ideas, narrative starters and a GRI content-index line. Use those to move from collected data and evidence into a short draft narrative and a structured index entry.
The page’s narrative starters are meant to help you write from the data you do have, while the common gaps section helps you identify what is still missing. Keep the draft aligned to the evidence you can actually support.
They show how a disclosure can be presented in practice, including a quantitative table where relevant. Treat them as illustrative only and use them to shape your own wording and layout, not as a template to copy.
The page says ESRS G1 (Business Conduct) is the closest correspondence, so the same data may be reusable across both. Check the specific reporting needs separately, but use the page to organise the underlying tax data and evidence once.
The Download Centre includes a Prep & Assurance workbook in .xlsx format and a printable Library Card in .pdf format. Use the workbook to organise preparation and assurance, and the card for a quick reference copy.
Get your GRI 207-2 tools — free
Your preparation tools are free for LRA Community members and students. Register once (it's free) and your download starts right away — plus the Disclosure Library, templates and the LRA AI-assistant.
You're in — your download is starting
Your file is downloading now. Your Community Cabinet — with the Disclosure Library, templates and the LRA AI-assistant — is ready too.
Open your Cabinet →