Timesheets and declarations are not requested in MSCA projects (contrary to other Horizon Europe actions based on actual costs). To prove that the researcher worked on their MSCA project, it is sufficient to present a contract with the host institution together with additional documents proving the fellow’s dedication to the project, if needed.

Moreover, declarations are not allowed by the auditors. REA has confirmed that the declaration on exclusive work is not applicable for audits carried out in MSCA ITN, IF and COFUND actions to determine time spent working on the action. It is expected this will continue in Horizon Europe.

As outlined in the H2020 Indicative Audit Programme, such evidence may include lab books, attendance lists, conference abstracts, library records, travel expenses, timesheets, reports to supervisor, meeting minutes, e-mail exchanges, etc. and other open sources (e.g. the internet) to see if the researcher worked on activities other than their  project. The auditors will also look at the researcher’s employment contract or corresponding agreement to see if it complies with Article 32 of the H2020 Annotated Model Grant Agreement, including but not limited to the obligation that the researcher works exclusively for the action.

Fellows need documentation in the form of a contract that shows the 50% commitment or something similar since MSCA does not typically operate with timesheets.

A COFUND project can be designed in many different ways and it is up to the beneficiary to decide how the researchers are funded. If the beneficiary wants to include a family allowance after the recruitment, it is OK, but it is not a formal requirement from the EC/ REA. It can of course be evaluated positively by the evaluators as clear support to offer the best conditions to the fellows. In addition, this would be unlikely, as in H2020 the MSCA rules did not foresee changes in the eligibility for family allowance during the fellowship duration.

“Partner Organisations” means both type of partners: associated or implementing.

Implementing partners have a bigger role, however, this was harmonised among the MSCA actions and associated partners are supposed to appear in part A for all actions. COFUND is the only action which has implementing partners and therefore it is slightly different.

This is up to the experts to assess; all networks are highly encouraged to follow what is explained in FAQ n 16721.

One single IERO/IO (all branches included) cannot receive more than 40% of the total EC contribution. The country where the IERO is based won’t be counting towards the 40% rule, but it is the IERO itself which is counting (as if the IERO was considered as a separate country, but using the country correction coefficients of their hosts). Example: In a project, if there are European Molecular Biology Laboratory (EMBL) German and French branches, the budget requested by both branches will count towards the 40% rule for EMBL’s share, while this specific budget will not count for France’s or Germany’s share of the budget.

The university must be included (either as an associated partner or associated partner linked to a beneficiary) and they must provide a Letter of Commitment even if they only award the degree and have no other task.

No, it is not.

Yes, it is possible as long as it is well described in the proposal. It will be assessed accordingly by the experts during the evaluations. However, this set-up should not be used to circumvent some other rules, like the 40% rule.

The deadlines and procedures are set out in the evaluation result letter. For more information on complaints about proposal rejection: https://webgate.ec.europa.eu/funding-tenders-opportunities/display/OM/Complaints+about+proposal+rejection.

Regarding header and footer content, there are no strict specifications in the template or the guiding materials. Applicants can include the proposal acronym and action type in the header if they wish. In the same logic, REA would not reject a proposal for not having included the grey part “EU Grants: Application form (HE MSCA PF): V1.1 – 05.05.2022” in the header.

This is a possible option:

“Call: HORIZON-MSCA-2022-PF-01-01 – [MSCA Postdoctoral Fellowships 2022 – EF]               ACRONYM” Or “Call: HORIZON-MSCA-2022-PF-01-01 – [MSCA Postdoctoral Fellowships 2022 – GF]               ACRONYM”

Тhey can list ‘submitted’ and ‘under review’, but they should be ignored by the reviewers. Under review/ submitted always means that they can still be rejected, so they cannot be seen as an accomplishment.

In cases where it is materially impossible to provide an employment contract due to exceptionally difficult circumstances (e.g. situations of war or armed conflict, natural disasters, etc.), an official letter from the employer, duly signed and stamped, stating the start and end dates, and describing the tasks performed by the employee could be accepted instead of the employment contract. In the particular case mentioned, it would be important to highlight that, in addition to the above, the letter should specify and quantify the time spent outside the main research activity so that the time spent not working in research could be deducted from the FTE experience in research.

In 2022 REA is keeping the same approach as for the 2021 call, meaning that the headings cannot be cut. The content in the template needs to be kept as such, without deleting the explanatory text in the parenthesis.

If a person leaves the EU for 12 months or longer, they lose the status of the long-term resident and the count starts from scratch. So if the period spent in the third country was 12 months or more, they are no longer considered long-term residents.

Timesheets and declarations are not requested in MSCA projects (contrary to other Horizon Europe actions based on actual costs). To prove that the researcher worked on their MSCA project, it is sufficient to present a contract with the host institution together with additional documents proving the fellow’s dedication to the project, if needed.

Moreover, declarations are not allowed by the auditors. REA has confirmed that the declaration on exclusive work is not applicable for audits carried out in MSCA ITN, IF and COFUND actions to determine time spent working on the action. It is expected this will continue in Horizon Europe.

As outlined in the H2020 Indicative Audit Programme, such evidence may include lab books, attendance lists, conference abstracts, library records, travel expenses, timesheets, reports to supervisor, meeting minutes, e-mail exchanges, etc. and other open sources (e.g. the internet) to see if the researcher worked on activities other than their  project. The auditors will also look at the researcher’s employment contract or corresponding agreement to see if it complies with Article 32 of the H2020 Annotated Model Grant Agreement, including but not limited to the obligation that the researcher works exclusively for the action.

Fellows need documentation in the form of a contract that shows the 50% commitment or something similar since MSCA does not typically operate with timesheets.

Organisations can only encode secondments that are eligible for EC funding. So organisations could encode the secondments going to the UK, but not those from the UK to a beneficiary. It is the dates included in the mobility declarations (previously researchers’ declarations) which are used for financial reporting.  

The researcher is eligible to participate, the change of status does not affect their eligibility.

The UK partners will be funded with the UKRI Horizon Europe Guarantee, in line with the original budget line. They will no longer be able to be included as a beneficiary but will need to become Associated Partners (APs).  Secondments to UK APs from Member States (MS) and/ or Associated Countries (AC) will be funded by the EC as originally foreseen in the proposal. Secondments from UK APs to MS/ AC/ other APs will be funded via UKRI, in line with the budget line and secondment plan in the proposal. Secondments from another AP to the UK will also be funded via UKRI.