Draft This validator and the 2026 machine readable format are still in draft form, and are subject to change following feedback from platform providers and other partners.
ESG Reporting Template · Technical details · investeurope.eu · reframeventure.com
MRF Validator 2026with Reframe Venture

Technical details · How data moves

Dispute process

What happens when an MRF file exported from one platform cannot be imported into another, from normal troubleshooting through to dispute resolution by Invest Europe. All platforms should read and agree to this process.

Back to technical details Download PDF
Normal flow (90+% of the time) Small issue (rare) Medium issue (very rare) Dispute (extremely rare)
Manual communication between exporting platform and GP Manual communication between importing platform and GP Communication between all stakeholders
Invest Europe MRF dispute process flowchart. The step-by-step text version below describes every box and decision.
Invest Europe MRF dispute process. Select the diagram to open it at full size.

Step by step

In this example, a GP, ExampleVentures, exports its data from Platform A and needs to import it into Platform B, which its LP uses.

  1. The reporting request

    ExampleVentures receives a reporting request from an LP that uses Platform B.

    Does ExampleVentures use an Invest Europe approved provider?

    No Data is entered manually on Platform B. Success.
    Yes Continue below.

    Has ExampleVentures filled in the Invest Europe template on that provider (Platform A)?

    Yes Go to step 2.
    No Does ExampleVentures want to complete it on Platform A or Platform B?
    • Platform B: data is entered manually on Platform B. Success.
    • Platform A: ExampleVentures enters the data manually on Platform A, then goes to step 2.

  2. Create and validate the .csv in Platform A

    1. Create the .csv file in Platform A.
    2. Platform A validates the file, using logic as close to the Invest Europe validator code as possible.
    Invalid Platform A / ExampleVentures troubleshooting: Platform A explains the errors to the user and provides a way to resolve them. The user resolves the issues and creates the .csv again.
    Valid ExampleVentures downloads the .csv and uploads it to Platform B.

    Has it been successfully imported into Platform B?

    Yes Success.
    No Go to step 3.

  3. Import problems: small issue

    Can ExampleVentures fix the erroneous metrics in Platform B?

    Yes Success.
    No Platform B details the errors to the user and directs them to contact Platform A to resolve them.

    Platform A / ExampleVentures troubleshooting: ExampleVentures contacts Platform A with the issues.

    Does Platform A recognise the error?

    Yes Platform A fixes the error, and the process restarts from creating the .csv file in Platform A.
    No Go to step 4.

  4. Proving validity: medium issue

    Platform A uses the Invest Europe validator code to generate a summary proving the file's validity (a "certificate"), which the GP sends to Platform B.

    Platform B / ExampleVentures manual check:

    Is the certificate genuine, i.e. can it be replicated on Platform B's side?

    Yes The error must be on the import side. Platform B fixes the issue, and the file goes back through the import check.
    No Go to step 5.

  5. Dispute resolution

    Platform A / Platform B / Invest Europe dispute resolution:

    1. Platform B emails Platform A, copying in Invest Europe, with both certificates.
    2. Platform A explains its case.
    3. Invest Europe acts as the authority to resolve the dispute.

    Can either Platform A or Platform B fix it?

    Yes The platforms fix the issue, and the file goes back through the import check.
    No Data is entered manually on Platform B. Success.

Success: the data is in Platform B.

Generating a validity summary To produce the summary described in step 4, validate the file with this validator and use the Export results (.csv) button on the results page.