You are the supplier, not the reporter Enter it once Basic or Comprehensive

Custom VSME software for supply chain requests

You are not covered by the CSRD, but your customers are. And they need value chain data, so each customer sends you their own questionnaire, in their own format, with their own deadline. Forty questionnaires a year that largely ask the same thing. The VSME exists to replace all of them with a single answer.

Why the questions end up with you

Companies that report under the CSRD also have to say something about their value chain. They don't know this on their own, so they ask their suppliers. That is legitimate, and for you it is a burden nobody designed: every customer asks the same questions slightly differently, in their own portal or spreadsheet, with their own definition of what a scope or a unit is.

The VSME is the European standard meant to put an end to this. It was developed by EFRAG, the same organisation behind the ESRS, and consists of two modules: a Basic Module with eleven disclosures, of which B1 and B2 are general and B3 to B11 cover the basic indicators, and a more extensive module for those who want or need to provide more. On 30 July 2025, the European Commission adopted a recommendation to use it as the basis for voluntary SME reporting, precisely to reduce the number of separate requests.

There is something else going on. With the Omnibus and the proposed threshold of a thousand employees, a large group of companies falls outside the mandatory CSRD, and they still need a way to share sustainability information because their customers and financiers ask for it. So don't expect the questions to disappear; expect them to look more and more like the VSME. The standard and the recommendation are available from RVO.

The request you answer with the VSME stems from your customer's own due diligence obligation. What that obligation entails since Omnibus I, and why it focuses on direct suppliers in particular, is explained on CSDDD software.

If you also buy from suppliers yourself, the same question arises one link further down. You record your observations of your own suppliers with the supplier visit app.

How we build this

The question is not how you report, but how you can reuse the same data several times without looking it up again. That is what we design around.

1
Comparing the requests side by side

Gather the questionnaires you completed over the past year. In practice, seventy to eighty per cent turn out to ask the same thing in different words, and that overlap is the entire business case.

2
Determining the data source for each indicator

Where your energy consumption, your staffing figures and your waste streams come from. Assigning a single source to each indicator matters more than the indicator itself, because otherwise you'll report a different figure next year for the same question.

3
Basic Module first

Every sprint ends with something you can check yourself, and we start with the eleven disclosures of the Basic Module. That is what most customers ask for; you can always expand later.

4
Working through a real request

We take the last questionnaire you received and answer it from the system. Whatever doesn't come out of it is exactly what still needs to be captured.

What the software actually does

Everything revolves around a single dataset that serves multiple requests. The other components exist to keep that dataset filled and up to date.

One dataset per reporting year

The indicators from the core module, with their value, unit, source and calculation method. If you give two customers the same figure, you also give them the same supporting evidence.

Map questionnaires to your own indicators

A question from customer A and a question from customer B that mean the same thing point to the same indicator. That turns completing a questionnaire into a matter of assigning answers rather than researching them again.

Answer history per customer

What you reported to whom, and when. It may look like admin until a customer asks next year why a figure has changed and you need to be able to explain the difference.

Data from your own systems

Energy bills, headcount, waste streams and mileage are already recorded somewhere. Retyping them is where errors creep in, and it costs time all over again every year.

Customer deadlines tracked

Every customer has its own deadline, and these rarely coincide with your own year-end close. A single calendar showing what is due and when avoids the two-day scramble before the deadline.

See what you don't know

Some questions you can't answer, and that is a legitimate answer, provided you give it deliberately. The system flags those items instead of leaving them blank, so you can choose what you will start measuring this year.

Who we build for

How much this weighs on you depends on how many customers are asking and how much you produce yourself. Four situations.

Suppliers in manufacturing

You supply larger manufacturers and OEMs that all fall under the CSRD. This is the group that receives the most questionnaires and where the overlap between lists is greatest. If you supply the food chain, those questions often come together with certification requirements; see IFS and BRCGS audit file.

Trade and distribution

You sit between producer and customer, so you receive questions that are really about your supplier. That makes passing information on part of the job, and you will want a questionnaire side of your own as well. The figures usually come from your ERP.

Service providers and contractors

In tenders and framework contracts, sustainability questions come back as an award criterion. Here it is not about reporting but about being able to give a credible answer on time.

Advisers and accountants

If you work for several SME clients, you need the same structure per client with a hard separation between them. If your client reports under the CSRD itself, CSRD reporting software is the right answer; this page is about the supplier that receives the questionnaire.

Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

Technology and integrations

The standard is still evolving: with the Omnibus, a revised version is expected to become the baseline from 2027. Everything related to the indicator structure should therefore be configurable and stored per version.

If you also want to carry out a traceable double materiality assessment, take a look at our double materiality tool.

Node.js / Python / .NET PostgreSQL Indicator set per standard version Link between question and indicator Source reference per value Integration with accounting, HR and energy data Answer history per customer Deadline tracking per customer Export to the common questionnaire formats Version history on every value Roles and authorisation Multiple entities or customers Audit logging Hosting in the EU

Why Appfront

Record once, reuse often

The gain is not in the report but in reusability. We link questions to your own indicators, so the fortieth questionnaire is less work than the first.

The same figure for everyone

Two customers receiving different figures for the same question is the risk nobody sees coming. One source per indicator prevents that.

Your customers' rhythm, not yours

The deadlines come from outside and are spread throughout the year. We build the calendar around them rather than around your own year-end close.

Honest about what this is not

The VSME is voluntary and not a certification. We are not sustainability consultants and do not decide which indicators are relevant to you; we build the system in which your answers are produced and stay substantiated.

Security and privacy

This data looks harmless, but it is not. Energy consumption, headcount and waste streams together reveal a lot about your size, your staffing and your cost structure, and you are handing them to customers who are also your negotiating counterparts. What you have disclosed to whom is therefore information you want to keep control of; the system shows per customer what has been shared and keeps those records separate.

There is also a people side to this. Absence, accidents and workforce composition are indicators that become easy to trace back to individuals when numbers are small: in a team of eight, an average is not anonymisation. We therefore build in a threshold below which a figure is not shared but marked as not reported, and you set that threshold. We also store every reported value with its date and source, so you can explain a difference between two years rather than having to reconstruct it. How we handle security ourselves is set out in our information security policy; external reports go through our coordinated vulnerability disclosure policy.

Frequently asked questions about the VSME

No, the VSME is a voluntary standard. The pressure comes not from legislation but from your supply chain: customers who report under the CSRD need data about their value chain and request it from you. The VSME exists to standardise those requests. Whether you start is therefore a commercial decision, not a compliance question.

The CSRD is an obligation for large and listed companies, with the ESRS as its standard. The VSME is voluntary, much shorter, and designed for SMEs that fall outside the CSRD but are still asked for data. If you report under the CSRD yourself, this is not the right page; see CSRD software.

Two modules. The Basic Module has eleven disclosures: B1 and B2 are overarching, and B3 to B11 are the basic indicators. There is also a more extensive module for those who want or need to provide more. In practice, most customers ask for the Basic Module; check the current version of the standard, as it is being revised.

No, and we have to be honest about that. Your customers will keep using their own portals. What changes is that you draw your answers from a single source instead of looking them up again for each list, and that you give everyone the same figure. Some customers now accept a VSME report instead of their own list; that is a conversation for you to have with them.

Then you state that, rather than leaving the field blank or estimating. The standard allows you not to report everything, and an honest "not measured" is defensible; an invented figure is not. The system flags those gaps so you can decide what to start measuring in the coming year.

Probably, and in your favour. With the proposed threshold of one thousand employees, a large group falls outside the mandatory CSRD, and those companies are also looking for a way to share data. A revised VSME is expected, which is likely to become the baseline from 2027. We therefore build the indicator structure to be configurable and stored per version.

Yes, and that is where the time savings are. Energy consumption comes from invoices, headcount from your HR system, mileage from your fleet records. What can be integrated depends on your software; we map that out beforehand. Where integration is not possible, manual entry remains an option, but only once. This runs through integrations.

That depends on how many indicators you want to track, how many customers you report to, and whether it needs to integrate with your administration. The core module with the answer history is usually quick to get working and delivers the most value; the integrations cost more. We give a well-founded estimate after the discovery phase.

Building VSME software?

Send us two questionnaires you completed this year. The number of questions that appear in both is usually the whole argument. We build this as a standalone application and as part of a broader custom software project. If you report yourself under the CSRD, CSRD reporting software is the right place.

Edit content