CSRD reporting software
Judged against the delegated act, not against a vendor list.
Do you need CSRD software at all?
The United Kingdom is outside the CSRD, so a UK company is never in scope by being British.
Since 18 March 2026 the scope test is a single cumulative one, and it is large.
The sentence everything follows from
An undertaking is in scope only if it exceeds both €450 million net turnover and 1,000 employees during the financial year.
A tool cannot put you in scope, and buying one does not make you a reporter.
And the year it starts to bite
Omnibus I applies to financial years beginning on or after 1 January 2027, so the consolidated text is ahead of the years it governs.
Who wrote the list you are reading?
Twelve ranking pages for this term were opened and read on 4 September 2026.
Four of them are published by a company that sells a product appearing on its own list.
The counter-example matters as much as the conflict
Socious sells a platform and ranks Workiva first, not itself. That is worth knowing before assuming every vendor list is self-serving.
Name the conflict where it exists, and the counter-example where it exists.
One page contradicts itself in a single screen
The QHSE Standard’s prose says its shortlist is “led by Tekmon, Quentic and Watershed”; its own numbered list runs Quentic, Sweep, Workiva, Enablon, Greenly, and does not contain Tekmon at all.
The numbers they still repeat.
Two of the twelve state a repealed threshold as current, on the same page as a different repealed threshold.
A percentage taken off the wrong baseline is not an estimate. It is a different number.
The datapoint arithmetic, done wrong
The ~1,144 figure is a total for a 2022 draft, so a mandatory-only percentage cannot be subtracted from it.
One page does exactly that and arrives at “around 320”, having also swapped the mandatory and total percentages.
The CSRD requirement no list tests for.
For a financial year starting in calendar 2026, an undertaking may apply one of three versions of the ESRS.
Article 2(2) then requires it to state which one it applied.
Why that is a software requirement, not a drafting note
A disclosure prepared under one version and a disclosure prepared under another are not interchangeable, and the file has to say which was used.
So the tool must carry a standard version against each disclosure and produce that statement.
Ask the vendor to show you the field. Not the roadmap — the field.
And from FY2027 the choice disappears
ESRS (2026) applies to financial years beginning on or after 1 January 2027, with no option.
A tool that hard-codes one version is fine for FY2027 and wrong for the year most readers are planning now.
What was deleted on 3 July.
The revised standards delete every voluntary datapoint, which is why the total figure is larger than the mandatory one.
61% is EFRAG’s figure for EFRAG’s own draft. The Commission then made thirteen categories of change.
What that means for a tool
Annex I is replaced in its entirety, so a datapoint library built against the 2023 annex is not a subset of the new one.
Ask when the library was rebuilt, not when it was “updated”.
Immaterial disclosure is now forbidden, not optional.
ESRS 1 ¶24 says an undertaking shall not disclose information prescribed by a disclosure requirement or datapoint if that information is not material.
EFRAG’s draft said “is not required to”. The Commission changed it deliberately.
The top-down route is an option, not a replacement
¶27 permits a top-down assessment; ¶28 preserves the bottom-up route, and the application guidance allows combining them.
A tool that only implements one of those has chosen your methodology for you.
“Complete” used to be a virtue in a reporting tool. Read ¶24 again.
Mappings that point at nothing.
Anticipated financial effects were removed from ESRS E2 to E5.
A tool still asking for E4-6 is asking for a paragraph that no longer exists.
The question to ask
Ask which ESRS version the mapping library targets, and what happens to a disclosure mapped to a deleted paragraph.
The honest answer is that it has to be re-mapped, not migrated.
What a CSRD assurer asks your tool to produce.
The opinion is a limited assurance engagement, and the empowerment to escalate to reasonable assurance was deleted.
Any page promising an escalation in 2028 is describing a provision that no longer exists.
The limb most tools ignore
The opinion covers the process carried out by the undertaking to identify the information reported, not only the information itself.
That is a requirement to keep an auditable record of the materiality assessment, not just its conclusions.
Taxonomy Article 8 disclosures sit inside the perimeter too.
And who signs is a national question
The statutory auditor is the default, but Articles 34(3) and 34(4) are member-state options for a different auditor or an accredited independent provider.
What it may ask your suppliers.
A reporter may not require a smaller undertaking in its value chain to provide more than the voluntary standard asks.
A supplier-portal module that asks for everything is a compliance risk, not a feature.
And it protects the opinion too
The assurance opinion must be prepared in a manner that fully respects that right, so an over-broad questionnaire reaches the assurer as well.
Why there is no price on this page.
The published figures disagree with each other, and one page disagrees with itself.
The one that contradicts itself
KnowESG gives a band of €20K to €200K in one place and €20K to €150K a few lines later, on the same page.
We have not verified any of these figures with any vendor, so we repeat them only as claims, attributed.
A range quoted from a page that contradicts itself is not a budget.
What to ask before you buy.
Every question below exists because a provision creates the requirement, and the provision is named.
Tick the ones a vendor can demonstrate rather than describe.
The six that are not in the instrument
Ask who owns the data if you leave, how a re-mapping is priced, and what happens in the year an annex is replaced again.
Ask for a reference from a company your size in your jurisdiction, and ask what the implementation actually cost that company.
If a vendor cannot show you the version field, it does not have one yet.
Our method, published.
Twelve ranking pages were opened and read in full on 4 September 2026, and every quotation on this page comes from one of them.
We rank nothing, because we have not tested the products.
What we did not do
We did not trial any platform, take a briefing, or accept a fee, so we make no claim about what any named product can do.
Buy against the act, not the list.
Then ask to see the field.
Why there is no CSRD software ranking here.
Ranking a product means testing it, and we have not tested any of them.
Publishing an order without a method is the defect this page spends its first act describing.
Doing it ourselves would be the same defect with better citations.
What we can do is name the requirements, cite each to its provision, and show you who wrote every other list.
What this page does not cover.
It does not price anything, recommend anything, or state what any named product is capable of.
It does not cover UK SRS tooling, which is a different regime with different standards and its own page.
No clients, no certifications, no accreditations, no affiliate fees.
Nor does it give the post-Omnibus population of in-scope companies, because no reliable figure exists and the one in circulation predates the reset.
CSRD reporting software: questions readers ask.
Every claim, and where it came from.
Requirements are cited to the provision that creates them; claims about other pages are quoted from those pages and linked.
Each entry says what kind of document it is — a directive, a delegated act, a recommendation, or a page published by somebody with something to sell.
Where a measure is adopted but not yet in force, it says so.
- Accounting Directive 2013/34/EU — consolidated text
- Directive (EU) 2026/470 — Omnibus I, Official Journal PDF
- Directive (EU) 2022/2464 — the CSRD
- C(2026) 5010 final — the revised ESRS
- Council 11667/26 — the transmitted delegated act
- C(2026) 5010 final — the Annex
- Delegated Regulation (EU) 2023/2772 — ESRS (2023)
- Commission Recommendation (EU) 2025/1710 — VSME
- Regulation (EU) 2020/852 — the Taxonomy Regulation
- Manglai — “7 best sustainability management software tools for the CSRD in 2026”
- The QHSE Standard — “CSRD Software Comparison — 2026 Top 5”
- Socious — “10 Platforms Ranked for CSRD, ISSB, and AI Automation”
- Watershed — “The best CSRD software in 2026: a buyer’s guide”
- tinyctl — “Best CSRD Compliance Software in 2026”
- KnowESG — “CSRD Compliance Software: Compare EU Reporting Tools”
Carried over, so no citation is lost
The fact record from which every entry is drawn is the cluster’s reference at uksrs.org.uk.