Disclosure LibraryPractitioner guidance for every reporting disclosure
Home Disclosure Library ESRS ESRS G1 G1-6
ESRS G1: Business Conduct · 2026-5010-final
Disclosure Requirement G1-6

Payment Practices

Practical guidance for preparing this disclosure. Use this card to identify datapoints, verify claims and organise supporting evidence. For exact requirements, always refer to the official EFRAG source.

Dr Ross Kurinko, Sustainability Reporting Trainer
Reviewed by Dr Ross Kurinko · Sustainability Reporting Trainer LRA educational guidance · Not issued or endorsed by EFRAG
To prepare this disclosure
Disclosure focus

This disclosure asks an organisation to explain how it pays its suppliers and other business partners in practice. The focus is on whether payment terms are clear, consistently applied and managed responsibly, including how quickly invoices are settled and whether there are any patterns of late payment, disputed payments or other issues that could affect counterparties’ cash flow.

In practical terms, the reporting should cover the organisation’s real payment behaviour across the business, not just a few well-run sites or a single flagship operation. The useful question is whether payment practices are embedded across relevant operations and purchasing arrangements, and whether the organisation can describe any significant differences by geography, business unit or supplier type.

This LRA educational guidance supports disclosure preparation. For the exact requirements, always refer to the official EFRAG source.

Before you start

A quick mental checklist before you prepare this disclosure — tick each as you settle it.

Preparation

Key datapoints to prepare

Datapoint What to capture Evidence hint Owner
Standard payment period Record the usual number of days the business allows before a supplier invoice is due for payment. Credit terms in the ERP, supplier master records, contract templates, or approved purchasing terms. Procurement / Accounts Payable
Small supplier terms Capture whether the business applies any different payment conditions for smaller suppliers, and what those conditions are. Supplier policy, procurement terms, supplier onboarding documents, or contract clauses for smaller vendors. Procurement / Supplier Management
Invoices paid on time Capture the share of payments made within the agreed payment period, using the same population and timing basis as the payment-term data. Accounts payable ageing report, payment run data, and KPI dashboard showing invoices settled within terms. Accounts Payable / Finance
Late payment cases Capture the count of individual instances where payment was made after the agreed due date, for the reporting period. Exception report from accounts payable, overdue invoice log, or aged payables analysis with case-level counts. Accounts Payable / Finance
+ Show G1-6 sub-elements (LRA working checklist)

How to prepare it

1Set the reporting boundary first: decide which business units, legal entities, and supplier relationships are in scope for this disclosure, and make sure the same scope is used for every figure and narrative you report.
2Agree the definitions before you start counting: specify what you will treat as standard payment terms, what qualifies as SME-specific terms, what counts as an on-time payment, and what you will count as a case for the period.
3Pull together the source records: gather contract terms, invoice and payment logs, ageing reports, and any case-tracking records needed to support the four datapoints.
4Calculate and draft the disclosure: record the payment-term days and any SME-specific terms in text form, then compile the percentage of payments made on time and the number of cases for the reporting period.
5Explain any exclusions or changes: note any parts of the business or supplier base left out, any changes in method or scope from the prior period, and any assumptions used to bridge gaps in the records.
6Check the final output against the source requirements: confirm that each required datapoint is present, the wording matches the underlying evidence, and the reported scope, definitions, and calculations are consistent throughout.
Request the data

Request payment-practice data from Accounts Payable

Translate the disclosure into an internal business question — then adapt it to your organisation's own language.

How do we pay suppliers in practice, including standard payment timing, any special terms for smaller suppliers, the share of invoices paid on time, and the number of late-payment cases in the reporting period?

Use your organisation’s own labels first, then map them to the reporting fields. For example, if you talk about suppliers, vendors, invoices, settlement runs, or small-business terms internally, keep that language in the request and only translate it afterwards for reporting.

Weak request

Please provide the ESRS G1-6 payment practices metrics for the reporting period.

Why it fails: This uses framework language only, so the owner may not know which internal reports, definitions, or systems to pull from. It also leaves out the boundary, timing basis, category labels, and supporting evidence needed to check the figures.

Better request

Please pull the AP report for [reporting period] covering [entity / business unit] and send the usual supplier payment timing, any separate timing for smaller suppliers, the share of invoices paid within terms, and the number of late-payment cases. Include the source system, the definitions you use internally, and any exceptions or manual overrides, plus the supporting extract.

Formal email template
Subject: Request for payment-practice data for [reporting period]

Hello [name/team],

We are preparing the sustainability reporting pack and need your help with the payment-practice information for [entity / business unit] covering [reporting period].

Please send the following in your own internal terms, with a short note explaining how each item is defined in your process:
- The usual payment timing used for suppliers
- Any different timing or terms used for smaller suppliers or equivalent internal category
- The share of invoices paid within the agreed timing
- The number of late-payment cases in the period

Please also include:
- The source system(s) used
- The boundary covered
- Any exclusions, overrides, disputes, or manual adjustments
- A copy of the supporting report or extract

A possible LRA training template is attached below for reference only; please adapt this to your organisation and check the source material before sign-off.

Thanks,
[preparer name]
Short Teams / Slack version
Hi [name], could you send the payment-practice data for [reporting period] for [entity/business unit]? Please use your own AP/supplier terms, and include the usual payment timing, any different terms for smaller suppliers, the share paid on time, and the number of late-payment cases, plus the source report and any exceptions. Thanks.
Industry examples
Manufacturing

Context. A plant-based group buys raw materials and indirect services through a central AP team.

Adapted request. Please send the AP extract for [reporting period] covering [group / site]. We need the normal supplier payment timing, any separate terms used for smaller suppliers, the share of invoices paid within terms, and the number of late-payment cases. Please include the ERP source, the internal definition of on-time payment, and any disputed or blocked invoices.

Example response. Attached: AP ageing report and payment-run export. Boundary: group finance. Standard timing: 45 days. Smaller-supplier timing: 30 days. On-time share: 92.4%. Late-payment cases: 18. Notes: 6 cases were blocked for dispute resolution; these are listed separately in the comments tab.

Retail

Context. A retailer pays a large supplier base through a shared services centre and tracks invoice performance by vendor group.

Adapted request. Please provide the shared-services report for [reporting period] covering [entity / business unit]. We need the usual vendor payment timing, any different timing for small suppliers, the percentage of invoices paid on time, and the count of late-payment cases. Please add the system extract, the vendor grouping used, and any manual payment holds.

Example response. Attached: invoice workflow dashboard export and AP summary. Boundary: UK retail operations. Standard timing: 30 days. Small-supplier timing: 14 days. On-time share: 88.1%. Late-payment cases: 27. Notes: 9 cases were delayed by stock-dispute holds; these are flagged in the extract.

Draft your disclosure

Notes that turn data into a disclosure

LRA training templates — adapt them to your organisation, and check the official source before sign-off.

Method note

We have used the payment terms applied in our contracts, including any separate arrangements for smaller suppliers, and measured punctuality using the share of invoices settled by the agreed date, with reported cases counted separately.

Context note

These figures show how quickly we ask suppliers to wait for payment, how often we meet those deadlines in practice, and how many payment-related issues were recorded during the period.

Fluctuation statement

If the figures move from one period to the next, we will explain whether that reflects changes in contract terms, supplier mix, payment processes, or the number of reported cases.

Content index entry
G1-6 Payment Practices — [location / page] / [notes]
Download Centre

Preparation tools & forms

Professional preparation tools for G1-6 — 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.

Free · Community members
Go deeper · G1-6
Learn to prepare this disclosure end-to-end

This guide covers one Disclosure Requirement. The ESRS / CSRD Reporting course walks the full European workflow — double materiality, datapoints, evidence and assurance — with exercises on your own data.

Available as Guided Flex, Live Cohort, 1:1 Expert Mentorship or Corporate Programme.

Assurance readiness

For each claim, check the evidence

ClaimRiskEvidence to check
We set out the usual number of days we allow each main supplier group to be paid, using our own internal supplier categories and a documented cut-off date.An assurer will test whether the supplier groups are defined consistently, whether the day counts are based on the right contract terms, and whether the figure was calculated from the correct reporting period and population.Supplier policy or payment-terms schedule; category mapping used for the disclosure; source system extracts or contract samples showing agreed terms; calculation workbook; period-end population report; review sign-off showing the figure was checked before publication.
We included a separate late-payment measure for small suppliers where that issue is material for this business, and we based it on entity-specific records rather than a generic group-wide proxy.An assurer will probe whether the metric is genuinely specific to the reporting entity, whether the small-supplier population is defined and applied consistently, and whether the measure is material enough to justify inclusion.Materiality assessment or reporting memo; definition of the small-supplier population; source data and calculation method for the metric; evidence of any exclusions or adjustments; management review notes; audit trail linking the published number to underlying records.
We calculated the share of payments made within the stated payment window from the underlying payment ledger, and we checked that the numerator and denominator match the same scope.An assurer will test whether the percentage is mathematically correct, whether late and on-time payments are classified properly, and whether the scope of transactions used in the calculation matches the stated basis.Payment ledger extract; calculation sheet showing numerator, denominator and formula; reconciliation to the general ledger or AP sub-ledger; controls over data completeness and classification; evidence of review and approval before release.
Where we use a different payment period for small suppliers, we disclosed that separate day count and kept the basis for that distinction on file.An assurer will examine whether the separate term really applies to the small-supplier group, whether it differs from the terms used for other suppliers, and whether the distinction is supported by policy or contract evidence.Supplier terms policy; contract templates or sample agreements for small suppliers and other suppliers; internal guidance explaining the different treatment; category mapping; evidence that the disclosed day counts were reviewed against source documents.
We counted only the legal cases that were still open at the reporting date and related to overdue supplier payments, and we excluded matters that had already been closed.An assurer will check whether the count includes only live proceedings at the cut-off date, whether the cases are correctly linked to late-payment matters, and whether any duplicates or closed items were removed.Legal case register; correspondence from legal counsel; case status reports at period end; criteria used to define an open case; reconciliation between the legal register and the published count; sign-off from legal and finance teams.

Evidence pack to prepare

Common reporting gaps

Figures are stated without the supporting narrative, or narrative without figures.Scope is inconsistent between the text and the numbers.The reporting boundary is left undefined.Material changes since the previous period are not disclosed.Estimates and measured values are not distinguished.Source records for the figures are not identified.
Common gaps

Mistakes to avoid when collecting the data

Wrong data owner
Chasing the finance team alone can miss the contract or procurement owner who actually knows the payment terms and exception cases.
Framework language instead of business terms
Asking for the data in disclosure jargon can leave teams unsure whether you mean standard supplier terms, special SME terms, or late-payment cases.
No clear scope boundary
Pulling figures from every entity or region without first fixing the reporting perimeter can mix in payments that should sit outside the dataset.
+ Show 5 more

Where judgement is often needed

Set the reporting perimeter after acquisitions and disposals
Use one clear cut-off for bought-in or sold businesses, explain whether their supplier payment data is included for the full period or only from the change date, and keep the same approach across the four data points.
Decide which supplier groups count as in-scope
State how you treat borderline suppliers such as small firms, group entities, agents or other intermediaries, and explain any local rule you use to decide whether they sit inside the payment-practice population.
Handle country-by-country payment terms differences consistently
If contract terms vary by market, describe the rule used to combine them into one figure or split them by geography, and explain any local legal or commercial differences that affect the result.
+ Show 5 more
Examples

Illustrative examples

Synthetic, written by LRA — not from a company report, not text from any standard.

Illustrative (synthetic) example — Food processing

: we report how our supplier invoices are handled, including the standard payment window we use, whether smaller suppliers receive different terms, the share settled within the agreed date, and the count of late-payment cases. This is an illustrative disclosure for practitioner review, not a real company report.

Shows how to present supplier-payment practices in plain language, with a clear split between standard terms, SME-specific terms, punctual settlement performance, and the number of late-payment cases.

Illustrative supplier payment disclosure (days / % / count)
Agreed payment window (days)6045
Use of different terms for smaller suppliers01
Invoices paid by the due date (%)9288
Late-payment cases (count)125
Illustrative (synthetic) example — Construction materials

: we summarise our supplier-payment practice by showing the usual time allowed for payment, whether we apply a separate arrangement for smaller businesses, the proportion paid on time, and how many late-settlement cases we recorded. This is an illustrative disclosure for practitioner review, not a real company report.

Shows a second way to disclose the same payment information, using a different sector and different figures while keeping the same four data points.

Illustrative supplier payment disclosure (days / % / count)
Agreed payment window (days)7530
Use of different terms for smaller suppliers01
Invoices paid by the due date (%)8590
Late-payment cases (count)183
Company reportsReal published reports
Compare side by side →Get it free

How companies report G1-6 in practice

Real reports where this topic is disclosed. These are report practice, not exact disclosure templates to copy.

Terna S.p.A.
Electric Utilities / IPP / Energy Traders · Italy · 2025
Open report →
Terna S.p.A.'s 2025 Annual Report provides a specific reported value related to payment terms, noting a comparison of days with 37 days in 2024 on page 370. The report mentions standard payment terms and payments made by bank transfer during 2025 (p.370), indicating some detail on payment practices. However, there is no clear or quotable evidence found elsewhere in the report regarding other narrative or numeric details for this disclosure.
Pirelli & C. S.p.A.
Automobiles and Components · Italy · 2025
Open report →
Pirelli & C. S.p.A.'s 2025 Annual Report does not provide any quotable evidence or specific data related to the disclosure on anti-corruption or anti-bribery measures, as no narrative or numeric information was found in the report. While the report includes extensive financial data on payables, borrowings, and provisions (pp. 636, 684, 707), these do not address the disclosure topic. Therefore, the report lacks clear information on confirmed cases of corruption or related metrics, leaving this disclosure area unaddressed.
Danone S.A.
Food Production — Animal Source · France · 2025
Open report →
Danone S.A.'s 2025 Universal Registration Document provides detailed information on payment terms used to calculate overdue payments, specifying contractual terms of 30 days from the end of the month and 60 days from the invoice date (p.161). The report also notes that there were no excluded invoices in dispute or not recognised, with zero number and amount of excluded invoices (p.161). However, there is no quotable evidence found regarding other narrative or numeric disclosures related to this topic elsewhere in the report.
✓ LRA AI Assistant · Human-in-the-loop
Dr Ross Kurinko
Ask Study Studio AI assistant about this disclosure
Get practical answers for your reporting context. Your first two answers are free — join LRA Community for free to continue without a limit.
TryHow do I prepare G1-6?What data do I need to collect?Where can I see a real-report example?What mistakes should I avoid?
2 free answers
Check your understanding

Scenarios to work through

A group has one standard supplier contract for larger vendors, but its procurement team also uses a shorter payment schedule for small and medium suppliers. The finance team can pull the usual settlement period from the contract system, but the SME arrangement sits in a separate policy note.

QWhich payment period should you describe, and how should you treat the SME-specific arrangement?
Reveal model answer →

At year-end, the accounts payable team has a dashboard showing that 87 out of 100 supplier invoices were settled by the agreed date. However, 12 of the late items were disputed invoices that were paused while the issue was resolved, and one was paid late because of a bank processing error.

QDo you present the 87% figure as-is, or do you need to think about how the late cases are counted?
Reveal model answer →

A preparer is compiling the narrative and sees 14 late-payment incidents in the ledger. Eight relate to invoices from one supplier, three are from another, and the rest are spread across smaller vendors. The team is unsure whether to report the total count only or also break it down further.

QWhat should you do with the count of late-payment cases?
Reveal model answer →

The sustainability team has drafted a note saying the company pays suppliers within 45 days on average, but the finance system shows that the contractual terms are 30 days for most suppliers and 60 days for a subset of strategic partners. The draft also mentions that SMEs are on 30-day terms.

QHow should you avoid mixing up the different payment measures in the final disclosure?
Reveal model answer →
Framework references

Related framework references

How this disclosure maps across the major reporting frameworks.

ESRS
G1-6
within ESRS G1: Business Conduct
Open official source →
Primary
Related & explore
Go deeper · G1-6
Learn to prepare this disclosure end-to-end

This guide covers one Disclosure Requirement. The ESRS / CSRD Reporting course walks the full European workflow — double materiality, datapoints, evidence and assurance — with exercises on your own data.

Available as Guided Flex, Live Cohort, 1:1 Expert Mentorship or Corporate Programme.

FAQ

Questions this page answers

For G1-6, what data do I need to gather before I draft the disclosure?+
How do I set the scope for G1-6 business conduct payment data?+
Who should own the G1-6 data collection for standard payment period and late payment cases?+
What evidence should I keep to support a G1-6 draft for assurance?+
What are the common mistakes people make when reporting G1-6?+
How do I use the G1-6 Prep & Assurance workbook?+
What should I put in the narrative for a G1-6 disclosure draft?+
Can I use the synthetic example disclosure on the G1-6 page as a template?+
Where can I find real company report examples for G1-6 business conduct?+
What does the G1-6 page give me to make the disclosure assurance-ready?+
How do I turn the G1-6 data into a draft disclosure quickly?+
More questions this page can help with
How this library is built 312 published reports indexed 63171 pages with page-level citations 247 practitioner guides