Objections to a post-control report allow the funding recipient to challenge the project control findings before the institution takes further action concerning the project. Preparing them requires an analysis of the allegations raised, the project documentation and the legal grounds on which the institution bases its finding of a breach.
What is a post-control report?
A post-control report is prepared after a project control has been completed. It sets out the findings of the institution conducting the control and indicates whether any irregularities relating to project implementation or the use of funds were identified. Read more about a CBA control and a KAS audit.
Of particular importance are findings in which the institution challenges specific expenditure, the manner in which a procurement procedure was conducted, the implementation of a task, the achievement of project indicators or compliance with other obligations arising from the project documentation. A post-control report may also contain recommendations and indicate the potential consequences of the identified deficiencies.
Before preparing objections to a post-control report, it is necessary to establish:
- which elements of project implementation have been challenged,
- what factual circumstances the institution has relied on,
- which obligation it considers to have been breached,
- which documents and legal provisions it relies on as the basis for that obligation,
- what financial consequences the institution attaches to its finding.
The answers to these questions determine the scope of the further analysis.
Does a post-control report mean repayment of funding?
Not necessarily. A post-control report is not an administrative decision ordering repayment of funding. Depending on the stage at which the project control was carried out, however, it may constitute an important step leading to expenditure being challenged, a reduction in funding, the imposition of a financial correction or the initiation of proceedings for repayment of funds.
Many funding recipients mistakenly assume that because a post-control report “is not a decision”, no response is required. In fact, this is often the stage at which the institution formally presents its position on the project for the first time and identifies the activities or expenditure it considers irregular. A post-control report may therefore have significant consequences for the subsequent course of the case, as it is often at this stage that the institution signals the possibility of taking further action aimed at recovering the funds.
What is the deadline for submitting objections to a post-control report?
The procedure for submitting objections depends on the legal basis for the particular project control. For controls conducted under the implementation legislation for the 2021–2027 financial perspective, Article 27 provides for a period of 14 days from service of the post-control report in which to submit signed and reasoned objections. At the funding recipient’s request, submitted before that period expires, the institution may extend the deadline for a specified period. The implementation legislation applicable to the 2014–2020 financial perspective provided for an analogous 14-day period.
Before preparing objections, however, the legal basis for the particular project control, the relevant provisions of the grant agreement and the instructions contained in the post-control report should always be checked.
If the deadline for submitting objections is already running, it is important to determine promptly which of the institution’s allegations concern factual matters and which concern their legal assessment, and to gather documents created during project implementation. The Law Firm supports funding recipients in reviewing post-control reports and preparing objections.
How to prepare objections to a post-control report?
Objections to a post-control report should address the institution’s specific findings and explain why a particular allegation is not supported by the project documentation, the funding conditions or the legal provisions applicable to the case.
1. Identify precisely what the allegation concerns
A post-control report may address several separate issues, such as the manner in which a procurement procedure was conducted, the eligibility of expenditure, implementation of a task, a project modification or the achievement of project indicators. Each of these findings requires a separate assessment.
The first step is to identify the specific event that the institution considers irregular, the documents on which it based its finding and the consequences it attributes to the identified deficiency. Only then can it be assessed whether the dispute concerns the course of events, the content of the relevant obligation or the legal assessment of a particular action.
2. Check the source of the funding recipient’s obligation
The post-control report should identify the basis from which the institution derives the obligation allegedly breached by the funding recipient. This may be a provision of law, the funding agreement, the approved application for funding, the rules of the call for proposals, guidelines or another document applicable to the project.
A general reference to the “eligibility rules” or the “project implementation conditions” is not sufficient to assess whether the allegation is justified. The specific content of the obligation and the version of the relevant document in force when the activity in question was carried out must be identified. This is particularly important in projects implemented over several years, where guidelines, programme documentation or agreement templates may change over time.
3. Reconstruct the actual course of the project
The assessment of the project control findings should be based on documentation created during project implementation. Relevant materials may include the funding agreement and its amendments, the approved application for funding, payment applications, correspondence with the institution, procurement documentation, minutes, invoices, reports and documents relating to project modifications.
It is particularly important to compare the contents of the post-control report with information previously provided by the funding recipient to the institution. An issue identified during the project control as a breach may previously have been described in a payment application, discussed with the project officer or reflected in documents already contained in the case file.
The objections should therefore present the course of events in a manner consistent with the existing documentation. Explanations prepared only after the project control may be compared with the funding recipient’s earlier statements and documents.
4. Separate the factual findings from their legal assessment
In many cases, the problem does not lie in an incorrect finding as to what actually happened. The dispute concerns the legal significance that should be attributed to those facts.
For example, the institution may correctly establish that a particular change was introduced without an amendment to the funding agreement. A separate analysis is required, however, to determine whether the change actually required such an amendment, what notification obligations were laid down in the project documentation and whether the way in which the funding recipient and the institution acted during project implementation is relevant to the assessment of the change. Similarly, the mere fact that expenditure was incurred in a particular manner does not in itself mean that it was ineligible. The applicable eligibility conditions must be identified and it must then be determined whether they were actually breached.
Well-prepared objections should therefore identify precisely which factual findings the funding recipient challenges and which it accepts but considers to have a different legal significance.
5. Examine the link between the breach and the financial consequence
Identifying a deficiency does not end the analysis. If the institution links it to expenditure being declared ineligible, a reduction in funding, a financial correction or a potential demand for repayment of funds, the legal basis for that consequence should also be examined.
Relevant factors include the nature of the obligation that was breached, its connection with the expenditure being financed and the effect of the identified deficiency on the proper use of public funds. In EU-funded projects, the assessment may also require determining whether the conditions for classifying the event as an irregularity are met and whether it had, or could potentially have had, an impact on the Union budget.
Objections to a post-control report may therefore challenge both the finding that a breach occurred and the financial consequence that the institution seeks to derive from that breach.
6. Link each argument to specific documents
Documents attached to objections to a post-control report should substantiate the specific circumstances relevant to each allegation. The number of attachments is of little significance if it is not clear what each document is intended to prove.
A clearly structured position makes it possible to link each allegation raised by the institution with the funding recipient’s response and with the document supporting that response. It also facilitates subsequent assessment of the case if the project control findings become the basis for further action concerning a reduction in funding or repayment of funding. If an allegation concerns several items of expenditure or several periods, it is worth addressing them separately in the objections and linking each one to a specific document and argument.
What happens after objections are submitted?
After receiving objections to a post-control report, the institution reassesses the control findings to the extent challenged by the funding recipient. It reviews the arguments and documents submitted and, where it considers this necessary, may request additional explanations or documents or carry out further control activities.
This stage may result in the earlier findings being amended, the funding recipient’s position being accepted in part, or the assessment set out in the post-control report being upheld. The institution then prepares the final post-control report or presents its position on the objections submitted.
For the funding recipient, the key issue is which findings remain in place after the objections have been considered and what consequences the institution attaches to them. If the institution continues to challenge particular expenditure, the manner in which the project was implemented or compliance with obligations arising from the funding conditions, the project control findings may form the basis for further action concerning a reduction in funding, a financial correction or repayment of funds.
Why do objections to a post-control report matter for the subsequent proceedings?
Objections are the funding recipient’s first formally structured response to the project control findings. If the matter develops further and leads to a demand for repayment of funds, the arguments presented at the project control stage remain part of the case file.
It is therefore important how the funding recipient describes the course of the project, explains its actions and relates them to the project documentation and funding conditions. Any subsequent position will usually also be assessed against what was presented immediately after the project control.
Well-prepared objections to a post-control report make it possible, already at this stage, to organise the disputed issues, identify the documents supporting the funding recipient’s position and distinguish disputes concerning the facts from disputes concerning the interpretation of the grant agreement, guidelines or applicable legislation. This remains important even if the institution does not uphold the objections, as it helps maintain consistency of the arguments at subsequent stages of the case.
Summary
Receiving a post-control report marks the beginning of a stage at which the project control findings may still be challenged before the institution takes further action concerning the financing of the project.
In practice, it is worth breaking down each allegation raised by the institution into several elements. For example, if the institution states that a project modification was introduced without the required amendment, it is necessary to determine separately whether the modification actually occurred, which document was said to require such an amendment, which version of that document was applicable at the relevant time, and what financial consequence the institution attaches to the absence of the amendment. The objections to the post-control report should address each of these elements of the allegation. Merely demonstrating that the project was implemented correctly may not be sufficient where the institution challenges compliance with a specific procedural obligation.
Preparing objections to a post-control report therefore requires identifying the substance of each allegation, the source of the obligation attributed to the funding recipient, the applicable version of the project documentation and the actual course of project implementation. The link between the identified breach and the financial consequence asserted by the institution also requires a separate assessment.
The more serious the deficiencies identified during the project control, the more important it is to prepare the objections with a view to the fact that they may be revisited if proceedings concerning repayment of funding are subsequently initiated. See also: How to avoid repayment of funding.
Have you received a demand for repayment of funding, a post-control report or an administrative decision? See how the Law Firm supports recipients of public funding in matters concerning project controls and repayment of funding: Services – project controls and repayment of funding.
