- 2 Priorities
- 3 Financial Plan
- 3.1 Transfers and contributions
- Table 15A to InvestEU by year
- Table 15B to InvestEU summary
- Justification
- Table 16A to instruments by year
- Table 16B to instruments summary
- Justification
- Table 17A between funds by year
- Table 17B between funds summary
- Justification
- Table 21 to REPowerEU
- 3.2 JTF
- 3.3 Transfers between categories of region
- 3.4 Transfers back
- 3.5 Table 10 Financial appropriations by year
- 3.6 Table 11 Total financial allocations by priority & fund
Programme (IJG)
PURPOSE
This document describes the specifications related to Programming under the Investment for Jobs and Growth and goal (IJG) and more specific those related to the Programmes for ERDF, CF, ESF+ and JTF.
REGULATIONS
More details regarding the regulation of the Programme IJG can be found in the "About SFC2021" section of the portal.
ROLES
Roles involved in the Programme IJG are:
MS Managing Authority (MSMA) | Record the Programme IJG Upload the Programme IJG Documents Consult the Programme IJG Return Programme IJG by MS for Modification Delete the Programme IJG Validate the Programme IJG Prepare the Programme IJG for send to EC Send the Programme IJG Cancel the Programme IJG Create New Version of the Programme IJG |
MS Audit Authority (MSAA) | Consult the Programme IJG |
As can be seen in the table above, the main role involved in the Programme IJG creation is MS Managing Authority. To create the Programme IJG the User is an identified User and has the role of MS Managing Authority with Update rights (MSMAu) for all the funds covered by the Programme.
FUNDS
ERDF | CF | JTF | ESF+ |
Workflow
This section shows the lifecycle to create and manage a Programme IJG. There is no modifying the Programme IJG once it has been submitted. The Commission cannot change a Programme IJG, only respond.
Click here to see the Programme IJG workflow diagram in high resolution.
Create the Programme IJG
Remark | The User is an identified User and has the role of MS Managing Authority with Update rights (MSMAu) for the Funds that are covered by the Programme. A CCI number must have been Allocated by the Commission in order for you to create a Programme IJG. |
IMPORTANT! | When there is no Partnership Agreement, or no choice made yet in the Partnership Agreement, the User will not be allowed to create the Programme and an alert message in red will be shown: “The choice of the form of the Union contribution to technical assistance (Article 36(4) or Article 36(5) CPR) has not yet been made in the partnership agreement. Therefore, you cannot yet create your programme”. When a choice was made, the User needs to be aware and needs to be sure this is a final choice. This choice is for all MS Programmes and cannot be modified during the Programming period. An alert message in red will be shown: “Attention: Before creating your programme, please make sure the choice of the form of the Union contribution to technical assistance has been intentionally made in the Partnership Agreement and is final. Changing this choice in the Partnership Agreement after creation of this programme will require a delete and a re-create of this programme, resulting in a total loss of all already encoded data on the programme.” “For the outermost regions only” is enabled for Member States with outermost regions (OutermostRegion). When the User doesn't have edit permission for a Fund, the Fund checkbox will be disabled. The Cohesion Fund checkbox will be disabled for Member States not covering the Cohesion Fund. Programme amendment following the mid-term review (Article 18(3) CPR) is only available when Programme has been previously adopted by the Commission. |
To access the Programme IJG go to the Programming menu and select the Programme IJG option:
In the search screen click on the Create button to create a new Programme IJG:
You are redirected to the Programme IJG Creation Wizard:
Enter or select the following information:
(1) Select the CCI Number
The CCI list contains all allocated IJG (ERDF, CF, ESF+ and JTF) CCIs for the Country of the User's Node and which contain the Funds for which the User is registered (The User needs update permission for all Funds covered by the CCI). If the CCI code is not in the list, the User can request a new CCI via the CCI Request form.
(2) Modify or Enter the Title.
The ‘Title in EN’ field is always present. For each of the official languages of the MS different from English an extra Title field will be present.
(3) Select the First Year and the Last Year.
First Year is pre-filled with 2021 and Last Year with 2027. Both fields can be updated but First Year needs to be smaller or equal than Last Year and between 2021 and 2027.
(4) Select the Funds.
When the BudgetSource of the CCI indicates multiple Funds ‘FF’, the system will foresee checkboxes for the Funds ‘ERDF’, ‘CF’, ‘ESF+’ and ‘JTF’, and will check the Funds checked in the CCI Request. When the BudgetSource of the CCI indicates a mono-Fund, the system will only foresee and check the relevant Fund (‘RF’=>’ERDF’, ‘SF’=>’ESF+’, ‘CF’=>’CF’, ‘JTF’=>’JT’) and it will not be updateable. At least one Fund needs to be selected.
(5) Select the Source language.
(6) Enter any additional Comments.
(7) Click on Create to confirm creation of the the Programme IJG.
The status of the Programme IJG is Open.
Remark | The initial Programme IJG structure is created, and a Table of Content (ToC)/Navigation Tree is presented, so the User can enter the structured data of the Programme IJG. The system will automatically:
|
Record/Edit the Programme IJG
General
This section includes the header data to identify the main characteristics of the Programme IJG.
Version Information
Note | The Version Information contains information on the identification and status of the Programme IJG like the CCI, the Title, the Version Number, the Status, the Node where it currently resides and eventually the Decision information. It also shows the results of the last validation done on this Programme version. The Eligibility Period will automatically be set to 01/01/2021-31/12/2029 when creating the first version. |
Click on the Edit button to access the edit form to modify the information.
The Edit form appears:
Enter or select the following information:
(1) Select the CCI.
CCI can only be updated when Version 1. But it can only be replaced by a CCI with the same BudgetSource or a multi-Fund BudgetSource (FF), and the same ObjectSubType. The CCI list contains all allocated CCIs of the same BudgetSource and of the multi-Fund BudgetSource (FF), and of the same ObjectSubType for the Country of the User's Node and which contain the Funds for which the User is registered (User needs edit permission for all Funds covered by the CCI).
(2) Enter the Title in English.
(3) Enter the Title in (other language).
For each of the official languages of the MS different from English an extra Title field will be present.
(4) Select the First year and Last year.
In Version 1, First Year is pre-filled with 2021 and Last Year with 2027. Both fields can be updated. In subsequent versions, only the Last Year can be extended up until 2027.
(5) Select the Funds concerned.
When version = 1 or ( > 1 but never adopted), when the BudgetSource of the CCI indicates multiple Funds ‘FF’, the system will foresee the Funds ‘ERDF’, ‘CF’, ‘ESF+’ and ‘JTF’. When the BudgetSource of the CCI indicates a mono-Fund, the system will only foresee the relevant Fund ( ‘RF’=>’ERDF’, ‘SF’=>’ESF+’, ‘CF’=>’CF’, ‘JTF’=’JT’) and it will not be updateable. When programme has been previously adopted by the Commission, then the system will foresee all the Funds ‘ERDF’, ‘CF’, ‘ESF+’ and ‘JTF’. This is to allow merging of Programmes covering different Funds. At least one Fund needs to be selected.
When version > 1, Funds existing in the previous adopted major version cannot be unselected.
When unselecting a Fund selected in the current major version, all Fund related information will be deleted. Refer to the Remark below for more information.
(6) Select the Source language.
(7) Enter any additional Comments.
(8) Click on Save to save the information.
This section will apply if the Programme version is greater than 1 and contains the Amendment and Decision info:
Enter or select the following information:
(1) Select Yes or No if Non substantial transfer (Article 24(5) CPR) applies or not.
(2) Select Yes or No if Clerical or editorial corrections (Article 24(6) CPR) applies or not.
(3) Select Yes or No if the amendment is Approved by monitoring committee.
(4) Select Yes or No if Programme amendment is following the mid-term review (Article 18(3) CPR).
Programme amendment following the mid-term review (Article 18(3) CPR) is only available when Programme has been previously adopted by the Commission and no MTR 18(4) object version exists for this programme, statuses “Programme amendment requested” and “Withdrawn at the request of the MS” excluded.
The programme amendment following mid-term review (18(3) CPR) should be set only in case an amendment is required based on the assessment of the outcome of the mid-term review. Where, as a result of the mid-term review, the Member State considers that the programme does not need to be amended, the flexibility amounts can be confirmed in accordance with Article 18(4) CPR. For this purpose, please use the MTR module in SFC 2021.
(5) Enter the MS amending decision number.
(6) Enter the MS amending decision entry into force date.
(7) Select the Source language.
(8) Select Yes or No if For the outermost regions only.
(9) Enter any additional Comments.
(10) Click on Save to save the information.
Note | Non-substantial transfer (art. 24(5)), Clerical or editorial corrections (art.24(6)), Approved by monitoring committee, MS amending decision number and MS amending decision entry into force date are only available when programme has been previously adopted by the Commission. Non-substantial transfer (art. 24(5)), MS amending decision number and MS amending decision entry into force date need to be filled in when the MS wants to create a version containing modifications which do not require a Commission Decision. This kind of version will automatically be set to Adopted by MS when sent to the Commission and when only non-decisional parts of the Programme have been modified, or when it is impossible to verify that only minor changes have been applied then after sending to the Commission, the Commission will be able to set the status to Adopted by MS. When MS amending decision number/MS amending decision entry into force date is not null then MS amending decision entry into force date/MS amending decision number should not be null and Non-substantial transfer should be true. Non-substantial transfer (art. 24(5)) and Clerical or editorial corrections (art.24(6)) are exclusive. If needed, under the non-substantial transfer also clerical corrections are allowed. |
Remark | When unselecting a Fund selected in the current major version, all Fund related information will be deleted. An alert message to avoid accidental loss of information will inform the User at the moment of save. The following information referring to the Fund will be removed:
|
Region Coverage
Note | On entering this page, the country button corresponding to the Country of the management Node of the programme will be focussed and the corresponding available Regions will be shown. The 2019 NUTS codes will be used (Established by Regulation (EC) No 1059/2003 as amended by Commission Regulation (EC) No 2019/1755). |
Click on the Edit button to modify the Regions Covered:
The Select Regions pop-up window appears:
Enter or select the following information:
(1) Click on the Add country button to add additional countries.
(2) Choose the Region(s) that pertain(s) to the Programme.
(3) Click on Save to save the information.
Officials in Charge
Note | Officials in Charge can be updated at any time, independent from the status of the Programme IJG. Commission Officials (email domain "ec.europa.eu") can only be created/updated/deleted by Commission Users. |
Click on the Add button
to add a new official in charge.
Clicking on the Edit icon
of a row will allow you to modify the information of this official.
Clicking on the Delete icon
of a row will allow you to delete the official in charge selected.
Click on the Add button to add a new Official in Charge:
The Edit details pop-up window appears:
Enter or select the following information:
(1) Enter the Name.
(2) Enter the Email.
The format of the Email address will be validated by the system and should be unique.
(3) Enter the Phone number.
(4) Select the Language.
(5) Enter the Valid from and Valid until dates.
The Valid until date should be greater than the Valid from date.
(6) Click on Save to save the information.
History
This section shows all the actions that have been taken on the Programme IJG since it was created, for example:
Documents
Note | The Documents list shows all documents uploaded against this version of the Programme IJG by Member State and by Commission. Member State Users see all their own Documents and the sent Commission Documents. Commission Users see all their own documents, unsent Integral Member State Documents and sent Member State Documents. |
The following documents will be foreseen:
Description | Internal Code | Non-Integral (1) | Integral (2) | System (3) | Required (4) |
Other Member State Document | PRG.OM | X |
|
|
|
Snapshot of data before send | SNP.PRGSNT |
| X | X | X |
Legal Entity Form | PRG.LEF | X |
|
|
|
Bank Account Identification Form (5) | PRG.BAI | X |
|
|
|
MS Request to withdraw programme version | PRG.WIR | X |
|
|
|
MS Request to return programme version for modification | PRG.RER | X |
|
|
|
Supplementary Information | PRG.SUP |
| X |
|
|
TJTP Supplementary Information (6) | PRG.TJTPS |
| X | X |
|
Use of enhanced proportionate arrangements (7) | PRG.UEPA | X |
|
|
|
Description of the management and control system (8) | PRG.DMC |
|
|
| X |
Mid-term review assessment (9) | PRG.MTRA |
| X |
| X |
(1) Document can be sent at any time
(2) Document will be automatically sent when the Object is sent
(3) Document automatically created by the system
(4) Document required in the system before a next action can be executed
(5) PRG.BAI is required to verify and register new bank account details
(6) Documents of this type will be a copy of the linked TJTP version(s) TJTP.TJTPS documents
(7) ‘Use of enhanced proportionate arrangements (PRG.UEPA)’ can be sent by MSAA Users with update and send permissions
(8) PRG.DMC documents will only be available in the document type list, and can only be created when a PRG.ERDMC exists
(9) PRG.MTRA is only required when the amendment type is MTR Article 18(3)
Uploading & Sending Documents
Multiple documents can be uploaded in the Programme IJG.
Clicking on the Add button
will open a pop-up window allowing you to add a new document type with attachments.
Selecting a document row and clicking on the View icon
will allow you to view the document information.
Selecting a document row and clicking on the Edit icon
will allow you to modify the document information. If a document of type 'Other Member State Document' must be sent, you can select the edit icon in order to send the document.
Selecting a document row and clicking on the Delete icon
will allow you to delete the document and all attachements.
Remark | Integral Documents (Official Proposal etc) are only sent - together with the encoded data – once the Programme IJG is sent to the EC. Referential/non-integral Documents (ie. 'Other Member State Document') can be sent at any time independently of the status of the Programme IJG. The 'Other Member State Document' type demands a manual submission (they are NOT sent automatically when the object is sent to the EC). A non-integral document is only visible to the Commission when the SENT DATE is visible. |
Click on the Add button to add a new document:
The Edit document details pop-up window appears:
Enter or select the following information:
(1) Enter a Document title for your Document.
(2) Select a Document type.
The Document Type list in the edit screen will contain all non-System Integral and non-Integral Document Types from the Document Group.
(3) Enter a Document date.
The system automatically fills the field with todays date, but this can be modified.
(4) Enter a Local reference.
(5) Click on the Add button to add a new attachment:
You can add multiple attachments by clicking on the Add button.
You can remove unwanted attachments by selecting the attachment and clicking on the Remove button.
The Attached files window becomes editable:
Enter or select the following information:
(1) Enter a Title for your attachment.
(2) Select the Type of the document.
It is possible to select from these 4 types: Annex, Cover Letter, Main or Translation.
(3) Select the Language of the document.
(4) Click on Browse to select the file that you want to add as an attachment.
(5) After the attachments are uploaded click on Save.
Remark | Integral document types will only display the Save button and will be sent when the Programme IJG is sent to the Commission. Non-integral document types (such as ‘Other Member State Documents’) will display the Save button and a Save & Send button, and must be sent independently of the Programme IJG. |
Sending an unsent non-integral document
Once the document and attachment(s) have been uploaded click on the Edit icon in the row containing the unsent document:
Click on Confirm to send the document to the Commission. For completing this action, the User will be redirected to the EU Login signature page:
Remark | The Save & Send button will only be shown for documents which are not integral part of the Object and after at least one attachment was added. |
Deletion of an unsent document
Remark | Only unsent documents can be deleted. |
In the row of a previously uploaded unsent document click on the Delete icont to delete the document and associated attachments:
A confirmation window appears:
Click on OK to confirm deletion. Click on Cancel to return to the document section.
Observations
Note | This section is used to provide any relevant information to the Programme . It can be used as a type of 'chat' between the Member State and Commission. All Users who have Read permission on the Programme will be able to read all observations in the conversation. All Users who have Update permission on the Programme will be able to send an observation and participate in the conversation. All observations are kept against the specific version of the Programme. The observation is added below the Observations box and includes the username, the date and time of the post. |
Click on the Add button to add an observation:
The Add new observation screen appears:
Enter the following:
(1) Enter an observation.
(2) Click on Add to save the information.
1 Strategy
Description of Strategy
Click on the Edit button to enter the information:
The Edit details window appears:
Enter or select the following:
(1) Enter the text in the text box provided.
(2) Click on Save to save the information.
Table 1 PO and SO justification
Click on the Add button to add information in the table:
The Add row pop-up window appears:
Enter or select the following:
(1) Select the Specific Objective or ESF+ Dedicated Priority.
The Specific Objective list will contain all combinations valid for the Funds covered by the Programme (based on the selected Funds in the Programme Version page).
The ESF+ dedicated priority list will only be enabled when the Programme covers ESF+ (based on the selected Funds in the Programme Version page) and it will only contain ESF+ dedicated priority types, no ERDF/CF dedicated priority types.
(2) Enter a Justification.
(3) Click on Save to save the information.
Remark | Neither a Specific Objective nor an ESF+ Dedicated Priority can be deleted when it is used under a Priority in the Programme. In update mode, the Specific Objective cannot be modified. |
2 Priorities
2.1 Non-TA priorities
Click on the Add button to add a row of information to this table.
Click on the Edit icon to modify the information in a row.
Click on the Delete icon to remove the information in a row.
Click on the Add button to add a new priority axis:
The Add row pop-up window appears:
Enter or select the following:
(1) Enter the ID.
(2) Enter the Order by.
The Order by field indicates in which order the priority will be displayed in the Table of Contents.
(3) Enter the Title.
(4) Select the Dedicated priority type.
The Dedicated priority type list will only be shown when the Programme covers ESF+ and/or ERDF and/or CF, and will only contain the non-ESF+ types and the types selected in Table 1 (Table 1 doesn’t contain non-ESF+ types).
(5) Select Yes or No whether the entire priority promotes the socio-economic integration of third country nationals (Article112(7)).
(6) Select Yes or No whether the priority is dedicated to investments supporting the STEP objectives.
(7) Select Yes or No whether the priority is dedicated to RESTORE.
(8) Click on Save to save the information.
Remark | In subsequent versions of the Programme (>1), Priorities created in earlier adopted versions
On Delete of a Priority, all Priority related information will be deleted. An alert message to avoid accidental loss of information will inform the User at the moment of save. The following information referring to the Priority will be removed:
To avoid loss of data, modifying the Dedicated Priority Type ‘Most deprived under specific objective ESO.4.13 (point (xi) of Article 4(1) of the ESF+ regulation)’ to another or none Dedicated Priority type will not be allowed when there is already data encoded in Section 2.A.2 for this Dedicated Priority Type. “The entire priority promotes the socio-economic integration of third country nationals” and the “Priority dedicated to investments supporting the STEP objectives” will not be shown in the Print. |
2.1.1 Priority
Click on the Add button to add a row of information to this table.
Click on the Edit icon to modify the information in a row.
Click on the Delete icon to remove the information in a row.
Click on the Add button above the Specific Objectives table to add the information:
The Add row pop-up window appears:
Enter or select the following:
(1) Select the Fund.
The Fund list contains all Funds covered by the Programme as indicated in the Programme Version page, except when the Priority is a Dedicated Priority, then only the Funds valid for the Dedicated Priority Type are listed.
(2) Select the Specific Objective.
For non-Dedicated Priorities, the Specific Objective list is limited to the Specific Objectives selected in Table 1 and relevant for the Fund selected above. For Dedicated Priorities, the Specific Objective list is limited to Specific Objectives relevant to their Dedicated Priority Type. When adding a new Specific Objective to a Priority, the list is limited to Specific Objectives of the same Policy Objective. A Priority can only relate to 1 Policy Objective. For the new dedicated ERDF STEP priorities, the list of SO will be limited to the Specific Objectives 1.6 and 2.9 and for the new dedicated CF STEP priorities, the list of SO will be limited to the Specific Objective 2.9 in case they are already selected in table 1. For the new dedicated ERDF/CF RESTORE priorities, the list of SO will be limited to the Specific Objective 2.10 in case they are already selected in table 1.
(3) Click on Save to save the information.
Remark | The new existence of a distinct Fund/Specific Objective combination for whatever Priority will automatically create records for Thematic Enabling Conditions and their related Criteria, valid for this Fund/Specific Objective combination in the Enabling Conditions Table 12, if not yet exists. The disappearance of the last occurrence of a distinct Fund/Specific Objective combination for whatever Priority will automatically delete the records for Thematic Enabling Conditions valid for this Fund/Specific Objective combination and not valid for other Fund/Specific Objective combinations existing in this Programme, in the Enabling Conditions Table 12. On Delete of a Priority/Fund/Specific Objective combination, all Priority/Fund/Specific related information will be deleted. An alert message to avoid accidental loss of information will inform the User at the moment of save. The following information referring to the Priority/Fund/Specific Objective will be removed:
|
Click on the Add button above the Funds, categories of region and calculation basis for Union support table to add the information.
The Add row pop-up window appears:
Enter or select the following:
(1) Select the Fund.
The Fund list will contain all Funds covered by the Programme as indicated in the Programme Version page, except when the Priority is a Dedicated Priority, then only the Funds valid for the Dedicated Priority Type are listed. When the Programme covers only one Fund, this value is set by default.
(2) Select the Category of region.
The Category of Region List will contain all entries valid for Programme Country and the Fund selected above. It is only mandatory for ERDF and ESF+. When Funds ERDF and/or ESF+ are covered, they should at least have one Category of Region. For ERDF and ESF+, the 'Outermost or Northern Sparsely Populated Region' will only be shown for France, Spain, Portugal, Sweden and Finland.
(3) Select the Calculation basis for union support.
(4) Click on Save to save the information.
Remark | Priority/Fund/Category of Region combinations adopted in a previous version can never be deleted or updated. Only their Calculation Basis can be updated. Therefore, in this case, only the Calculation Basis field will be updateable. Editing will be blocked when there is already information specified under the Priority, Specific Objective. On Save (Insert /Delete), the system will automatically maintain the records in:
|
2.1.1.1 Fund, Specific objective
2.1.1.1.1 Interventions of the Fund
Click on the Edit button to enter the information:
The Edit details pop-up window appears:
Enter or select the following:
(1) Enter the text in the text box provided.
(2) Click on Save to save the information.
Click on the Edit button to enter the information:
The Edit details pop-up window appears:
Enter or select the following:
(1) Enter the text in the text box provided.
(2) Click on Save to save the information.
Equality, inclusion and non-discrimination
Click on the Edit button to enter the information:
The Edit details pop-up window appears:
Enter or select the following:
(1) Enter the text in the text box provided.
(2) Click on Save to save the information.
Click on the Edit button to enter the information:
The Edit details pop-up window appears:
Enter or select the following:
(1) Enter the text in the text box provided.
(2) Click on Save to save the information.
Interregional, cross-border and transnational actions
Click on the Edit button to enter the information:
The Edit details pop-up window appears:
Enter or select the following:
(1) Enter the text in the text box provided.
(2) Click on Save to save the information.
Click on the Edit button to enter the information:
The Edit details pop-up window appears:
Enter or select the following:
(1) Enter the text in the text box provided.
(2) Click on Save to save the information.
2.1.1.1.2 Indicators
Click on the Add button to add a row of information to this table.
Click on the Edit icon to modify the information in a row.
Click on the Delete icon to remove the information in a row.
Note | There are three types of Output Indicators: Common output indicator, Programme specific reserved output indicator and New Programme specific output indicator. Depending of the selection there are different ways to complete the form correctly. See all the possibilities below. The Programme Specific Reserved Output Indicator radio and list will only be shown when there are reserved output indicators for the Specific Objective. A Programme Specific Output Indicator can only be deleted when not used anymore in any other record of the Output Indicator Table in any version of this Programme. |
Remark | As the STEP regulation does not include new common indicators for the JTF, the Commission would like to suggest to the managing authorities to use programme specific ones mirroring the ones for ERDF/CF (same code with ‘a’ at the end): |
Click on the Add button above the Priority Indicator table to add a new output indicator:
The Add row pop-up window appears:
When the option Common Output Indicator is selected:
Enter or select the following:
(1) Select the Common Output Indicator from the list.
The Common Output Indicator list contains all Common Output Indicators for the Fund and Specific Objective.
(2) Select the Category of region.
The Category of Region list contains all Categories of Region defined against the Priority and Fund. When the Priority and Fund covers only one Category of Region, this value is set by default. Category of Region is only enabled for ERDF and ESF+.
(3) Enter the Milestone(2024).
(4) Enter the Target (2029).
(5) Click on Save to save the information.
When the option Programme Specific reserved Output indicator is selected:
Note | The Programme Specific Reserved Output Indicator radio and list will only be shown when there are reserved output indicators. This is only applicable for the ESF+ Specific Objective or JTF indicators mirroring the STEP ERDF and CF indicators. |
Enter or select the following:
(1) Select the Programme Specific Reserved Output Indicator from the list.
The Programme Specific Reserved Output Indicator list contains all Reserved Output Indicators for the Fund and Specific Objective.
(2) Select the Category of region.
The Category of Region list contains all Categories of Region defined against the Priority and Fund. When the Priority and Fund covers only one Category of Region, this value is set by default. Category of Region is only enabled for ERDF and ESF+ and is mandatory.
(3) Enter the Milestone (2024).
(4) Enter the Target (2029).
(5) Click on Save to save the information.
When the option Programme Specific Output indicator is selected you must first Define a Programme Specific Output Indicator:
Note | The Programme Specific Output Indicators table contains all previously defined Programme Specific Output Indicators, independently from Priority, Specific Objective or Fund. Programme Specific Output Indicators are defined ones and can then be used under different Priorities, Specific Objectives and Funds. A Programme Specific Output Indicator can only be deleted when not used anymore in any other record of the Output Indicator Table in any version of this Programme. |
Click on the Add button above the Programme Specific Indicators table to add a new Programme Specific output indicator:
The Add row pop-up window appears:
Enter or select the following:
(1) Enter the ID.
A Programme Specific Output Indicator code should be different from any Programme Specific Reserved Indicator code and from any Common Indicator code.
(2) Enter the Order by.
The Order by field indicates in which order the indicator will be displayed in the Table.
(3) Enter the Title.
(4) Enter the Measurement Unit.
(5) Click on Save to save the information.
Click on the Add button above the Priority Indicator table to add the Programme Specific output indicator:
The Add row pop-up window appears:
Enter or select the following:
(1) Select the Programme Specific Output Indicator from the list.
The Programme Specific Output Indicators are maintained by the Member State per Programme and are defined once and can then be used under different Priorities, Specific Objectives and Funds. In the edit page, only one of them must be selected. The table contains all previously defined Programme Specific Output Indicators, independently from Priority, Specific Objective or Fund.
(2) Select the Category of region.
The Category of Region list contains all Categories of Region defined against the Priority and Fund. When the Priority and Fund covers only one Category of Region, this value is set by default. Category of Region is only enabled for ERDF and ESF+ and is mandatory.
(3) Enter the Milestone (2024).
(4) Enter the Target (2029).
(5) Click on Save to save the information.
Click on the Add button to add a row of information to this table.
Click on the Edit icon to modify the information in a row.
Click on the Delete icon to remove the information in a row.
Note | There are two types of Result Indicators: Common Result indicator and New Programme specific result indicator. Depending of the selection there are different ways to complete the form correctly. See all the possibilities below. A Programme Specific Result Indicator can only be deleted when not used anymore in any other record of the Result Indicator Table in any version of this Programme. |
Click on the Add button above the Priority Indicators table to add a new Result indicator:
The Add row pop-up window appears:
When the option Common Result Indicator is selected:
Enter or select the following:
(1) Select the Common Result Indicator from the list.
The Common Result Indicator list contains all Common Result Indicators for the Fund and Specific Objective, which can be used in Programmes.
(2) Select the Category of region.
The Category of Region list contains all Categories of Region defined against the Priority and Fund. When the Priority and Fund covers only one Category of Region, this value is set by default. Category of Region is only enabled for ERDF and ESF+ and is mandatory.
(3) Enter the Baseline or reference value.
(4) Enter the Target (2029).
The Target field doesn’t exist under ESF+ Specific Objective ESO4.13.
(5) Enter a First reference year and a Last reference year.
When specifying a Reference Year range, the “from” year should be smaller than the “to” year.
(6) Enter the Source of data.
(7) Enter any additional Comments.
(8) Click on Save to save the information.
Remark | The Programme Specific Reserved Result Indicator radio and list will only be shown when there are reserved result indicators for the Specific Objective. The following fields are only shown under ESF+ Specific Objectives ESO4.1 to ESO4.12:
|
When the option Programme Specific Result indicator is selected you must first Define a Programme Specific Result Indicator:
Note | A Programme Specific Result Indicator can only be deleted when not used anymore in any other record of the Result Indicator Table in any version of this Programme. |
Click on the Add button above the Programme Specific Indicators table to add a new programme specific result indicator:
The Add row pop-up window appears:
Enter or select the following:
(1) Enter the ID.
A Programme Specific Result Indicator code should be different from any Programme Specific Reserved Indicator code and from any Common Indicator code.
(2) Enter theOrder by.
The Order by field indicates in which order the indicator will be displayed in the Table.
(3) Enter the Title.
(4) Enter the Measurement Unit
(5) Select the tick box whether the indicator is qualitative.
(6) Click on Save to save the information.
Click on the Add button above the Priority Indicator table to add the Programme Specific result indicator:
The Add row pop-up window appears:
Enter or select the following:
(1) Select the Programme Specific Result Indicator from the list.
The Programme Specific Result Indicators are maintained by the Member State per Programme and are defined once and can then be used under different Priorities, Specific Objectives and Funds. In the edit page, only one of them must be selected. The table contains all previously defined Programme Specific Result Indicators, independently from Priority, Specific Objective or Fund.
(2) Select the Category of region.
The Category of Region list contains all Categories of Region defined against the Priority and Fund. When the Priority and Fund covers only one Category of Region, this value is set by default. Category of Region is only enabled for ERDF and ESF+ and is mandatory.
(3) Enter the Baseline or reference value.
(4) Enter the Target (2029).
The Target field doesn’t exist under ESF+ Specific Objective ESO4.13.
(5) Enter a First reference year and a Last reference year.
When specifying a Reference Year range, the “from” year should be smaller than the “to” year.
(6) Enter the Source of data.
(7) Enter any additional Comments.
(8) Click on Save to save the information.
Remark | The following fields are only shown under ESF+ Specific Objectives ESO4.1 to ESO4.12 and for quantitative indicators:
|
2.1.1.1.3 Breakdown by type of intervention
Click on the Add button to add the information:
The Add row pop-up window appears:
Enter or select the following:
(1) Select the Category of region.
The Category of Region list will contain all Categories of Regions covered by the Priority and the Fund. If the Priority and Fund covers only one Category of Region, this value is set by default.
(2) Select the Code from the list.
The Code list of Intervention Fields will contain all non-Technical Assistance Intervention Fields valid for the Priority’s Specific Objective and Fund.
(3) Enter the Amount (EUR).
(4) Click on Save to save the information.
Click on the Add button to add the information:
The Add row pop-up window appears:
Enter or select the following:
(1) Select the Category of region.
The Category of Region list will contain all Categories of Regions covered by the Priority and the Fund. If the Priority and Fund covers only one Category of Region, this value is set by default.
(2) Select the Code from the list.
The Code list of Intervention Fields will contain all non-Technical Assistance Intervention Fields valid for the Priority’s Specific Objective and Fund.
(3) Enter the Amount (EUR).
(4) Click on Save to save the information.
Click on the Add button to add the information:
The Add row pop-up window appears:
Enter or select the following:
(1) Select the Category of region.
The Category of Region list will contain all Categories of Regions covered by the Priority and the Fund. If the Priority and Fund covers only one Category of Region, this value is set by default.
(2) Select the Code from the list.
The Code list of Intervention Fields will contain all non-Technical Assistance Intervention Fields valid for the Priority’s Specific Objective and Fund.
(3) Enter the Amount (EUR).
(4) Click on Save to save the information.
Click on the Add button to add the information:
The Add row pop-up window appears:
Enter or select the following:
(1) Select the Category of region.
The Category of Region list will contain all Categories of Regions covered by the Priority and the Fund. If the Priority and Fund covers only one Category of Region, this value is set by default.
(2) Select the Code from the list.
The Code list of Intervention Fields will contain all non-Technical Assistance Intervention Fields valid for the Priority’s Specific Objective and Fund.
(3) Enter the Amount (EUR).
(4) Click on Save to save the information.
Click on the Add button to add the information:
The Add row pop-up window appears:
Enter or select the following:
(1) Select the Category of region.
The Category of Region list will contain all Categories of Regions covered by the Priority and the Fund. If the Priority and Fund covers only one Category of Region, this value is set by default.
(2) Select the Code from the list.
The Code list of Intervention Fields will contain all non-Technical Assistance Intervention Fields valid for the Priority’s Specific Objective and Fund.
(3) Enter the Amount (EUR).
(4) Click on Save to save the information.
2.1.1 Priority (ESF+ SO)
Click on the Add button to add a row of information to this table.
Click on the Edit icon to modify the information in a row.
Click on the Delete icon to remove the information in a row.
Click on the Add button above the Specific Objectives table to add the information:
The Add row pop-up window appears:
Enter or select the following:
(1) Select the Fund.
The Fund list contains all Funds covered by the Programme as indicated in the Programme Version page, except when the Priority is a Dedicated Priority, then only the Funds valid for the Dedicated Priority Type are listed.
(2) Select the Specific Objective.
For non-Dedicated Priorities, the Specific Objective list is limited to the Specific Objectives selected in Table 1 and relevant for the Fund selected above. For Dedicated Priorities, the Specific Objective list is limited to Specific Objectives relevant to their Dedicated Priority Type. When adding a new Specific Objective to a Priority, the list is limited to Specific Objectives of the same Policy Objective. A Priority can only relate to 1 Policy Objective.
(3) Click on Save to save the information.
Remark | The new existence of a distinct Fund/Specific Objective combination for whatever Priority will automatically create records for Thematic Enabling Conditions and their related Criteria, valid for this Fund/Specific Objective combination in the Enabling Conditions Table 12, if not yet exists. The disappearance of the last occurrence of a distinct Fund/Specific Objective combination for whatever Priority will automatically delete the records for Thematic Enabling Conditions valid for this Fund/Specific Objective combination and not valid for other Fund/Specific Objective combinations existing in this Programme, in the Enabling Conditions Table 12. On Delete of a Priority/Fund/Specific Objective combination, all Priority/Fund/Specific related information will be deleted. An alert message to avoid accidental loss of information will inform the User at the moment of save. The following information referring to the Priority/Fund/Specific Objective will be removed:
|
Click on the Add button above the Funds, categories of region and calculation basis for Union support table to add the information.
The Add row pop-up window appears:
Enter or select the following:
(1) Select the Fund.
The Fund list will contain all Funds covered by the Programme as indicated in the Programme Version page, except when the Priority is a Dedicated Priority, then only the Funds valid for the Dedicated Priority Type are listed. When the Programme covers only one Fund, this value is set by default.
(2) Select the Category of region.
The Category of Region List will contain all entries valid for Programme Country and the Fund selected above. It is only mandatory for ERDF and ESF+. When Funds ERDF and/or ESF+ are covered, they should at least have one Category of Region. For ERDF and ESF+, the 'Outermost or Northern Sparsely Populated Region' will only be shown for France, Spain, Portugal, Sweden and Finland.
(3) Select the Calculation basis for union support.
(4) Click on Save to save the information.
Remark | Priority/Fund/Category of Region combinations adopted in a previous version can never be deleted or updated. Only their Calculation Basis can be updated. Therefore, in this case, only the Calculation Basis field will be updateable. Editing will be blocked when there is already information specified under the Priority, Specific Objective. On Save (Insert /Delete), the system will automatically maintain the records in:
|
2.1.1.2 ESF+ Specific objective
2.1.1.2.1 Interventions of the Funds
Click on the Edit button to enter the information:
The Edit details pop-up window appears:
Enter or select the following:
(1) Enter the text in the text box provided.
(2) Click on Save to save the information.
Click on the Edit button to enter the information:
The Edit details pop-up window appears:
Enter or select the following:
(1) Enter the text in the text box provided.
(2) Click on Save to save the information.
Click on the Edit button to enter the information:
The Edit details pop-up window appears:
Enter or select the following:
(1) Enter the text in the text box provided.
(2) Click on Save to save the information.
Criteria for selection of operations
Click on the Edit button to enter the information:
The Edit details pop-up window appears:
Enter or select the following:
(1) Enter the text in the text box provided.
(2) Click on Save to save the information.
2.1.1.2.2 Indicators
Click on the Add button to add a row of information to this table.
Click on the Edit icon to modify the information in a row.
Click on the Delete icon to remove the information in a row.
Note | There are three types of Output Indicators: Common output indicator, Programme specific reserved output indicator and New Programme specific output indicator. Depending of the selection there are different ways to complete the form correctly. See all the possibilities below. The Programme Specific Reserved Output Indicator radio and list will only be shown when there are reserved output indicators for the Specific Objective. A Programme Specific Output Indicator can only be deleted when not used anymore in any other record of the Output Indicator Table in any version of this Programme. |
Click on the Add button above the Priority Indicator table to add a new output indicator:
The Add row pop-up window appears:
When the option Common Output Indicator is selected:
Enter or select the following:
(1) Select the Common Output Indicator from the list.
The Common Output Indicator list contains all Common Output Indicators for the Fund and Specific Objective.
(2) Select the Category of region.
The Category of Region list contains all Categories of Region defined against the Priority and Fund. When the Priority and Fund covers only one Category of Region, this value is set by default. Category of Region is only enabled for ERDF and ESF+.
(3) Click on Save to save the information.
Remark | Under ESF+ Specific Objective ESO4.13, Milestone and Target do not exist. |
When the option Programme Specific reserved Output indicator is selected:
Note | The Programme Specific Reserved Output Indicator radio and list will only be shown when there are reserved output indicators. |
Enter or select the following:
(1) Select the Programme Specific Reserved Output Indicator from the list.
The Programme Specific Reserved Output Indicator list contains all Reserved Output Indicators for the Fund and Specific Objective.
(2) Select the Category of region.
The Category of Region list contains all Categories of Region defined against the Priority and Fund. When the Priority and Fund covers only one Category of Region, this value is set by default. Category of Region is only enabled for ERDF and ESF+ and is mandatory.
(3) Click on Save to save the information.
Remark | Under ESF+ Specific Objective ESO4.13, Milestone and Target do not exist. |
When the option Programme Specific Output indicator is selected you must first Define a Programme Specific Output Indicator:
Note | The Programme Specific Output Indicators table contains all previously defined Programme Specific Output Indicators, independently from Priority, Specific Objective or Fund. Programme Specific Output Indicators are defined ones and can then be used under different Priorities, Specific Objectives and Funds. A Programme Specific Output Indicator can only be deleted when not used anymore in any other record of the Output Indicator Table in any version of this Programme. |
Click on the Add button above the Programme Specific Indicators table to add a new Programme Specific output indicator:
The Add row pop-up window appears:
Enter or select the following:
(1) Enter the ID.
A Programme Specific Output Indicator code should be different from any Programme Specific Reserved Indicator code and from any Common Indicator code.
(2) Enter the Order by.
The Order by field indicates in which order the indicator will be displayed in the Table.
(3) Enter the Title.
(4) Enter the Measurement Unit.
(5) Click on Save to save the information.
Click on the Add button above the Priority Indicator table to add the Programme Specific output indicator:
The Add row pop-up window appears:
Enter or select the following:
(1) Select the Programme Specific Output Indicator from the list.
The Programme Specific Output Indicators are maintained by the Member State per Programme and are defined once and can then be used under different Priorities, Specific Objectives and Funds. In the edit page, only one of them must be selected. The table contains all previously defined Programme Specific Output Indicators, independently from Priority, Specific Objective or Fund.
(2) Select the Category of region.
The Category of Region list contains all Categories of Region defined against the Priority and Fund. When the Priority and Fund covers only one Category of Region, this value is set by default. Category of Region is only enabled for ERDF and ESF+ and is mandatory.
(3) Click on Save to save the information.
Remark | Under ESF+ Specific Objective ESO4.13, Milestone and Target do not exist. |
Click on the Add button to add a row of information to this table.
Click on the Edit icon to modify the information in a row.
Click on the Delete icon to remove the information in a row.
Note | There are two types of Result Indicators: Common Result indicator and New Programme specific result indicator. Depending of the selection there are different ways to complete the form correctly. See all the possibilities below. A Programme Specific Result Indicator can only be deleted when not used anymore in any other record of the Result Indicator Table in any version of this Programme. |
Click on the Add button above the Priority Indicators table to add a new Result indicator:
The Add row pop-up window appears:
When the option Common Result Indicator is selected:
Enter or select the following:
(1) Select the Common Result Indicator from the list.
The Common Result Indicator list contains all Common Result Indicators for the Fund and Specific Objective, which can be used in Programmes.
(2) Select the Category of region.
The Category of Region list contains all Categories of Region defined against the Priority and Fund. When the Priority and Fund covers only one Category of Region, this value is set by default. Category of Region is only enabled for ERDF and ESF+.
(3) Enter the Baseline or reference value.
(4) Enter a First reference year (mandatory) and a Last reference year (not mandatory).
When specifying a Reference Year range, the “from” year should be smaller than the “to” year.
(5) Enter the Source of data.
(6) Enter any additional Comments.
(7) Click on Save to save the information.
Remark | The Target field doesn’t exist under ESF+ Specific Objective ESO4.13. |
When the option Programme Specific Result indicator is selected you must first Define a Programme Specific Result Indicator:
Note | A Programme Specific Result Indicator can only be deleted when not used anymore in any other record of the Result Indicator Table in any version of this Programme. |
Click on the Add button above the Programme Specific Indicators table to add a new programme specific result indicator:
The Add row pop-up window appears:
Enter or select the following:
(1) Enter the ID.
A Programme Specific Result Indicator code should be different from any Programme Specific Reserved Indicator code and from any Common Indicator code.
(2) Enter the Order by.
The Order by field indicates in which order the indicator will be displayed in the Table.
(3) Enter the Title.
(4) Enter the Measurement Unit.
(5) Select the tick box whether the indicator is qualitative.
(6) Click on Save to save the information.
Click on the Add button above the Priority Indicator table to add the Programme Specific result indicator:
The Add row pop-up window appears:
Enter or select the following:
(1) Select the Programme Specific Result Indicator from the list.
The Programme Specific Result Indicators are maintained by the Member State per Programme and are defined once and can then be used under different Priorities, Specific Objectives and Funds. In the edit page, only one of them must be selected. The table contains all previously defined Programme Specific Result Indicators, independently from Priority, Specific Objective or Fund.
(2) Select the Category of region.
The Category of Region list contains all Categories of Region defined against the Priority and Fund. When the Priority and Fund covers only one Category of Region, this value is set by default. Category of Region is only enabled for ERDF and ESF+ and is mandatory.
(3) Enter the Baseline or reference value.
(4) Enter a First reference year (mandatory) and a Last reference year (not mandatory).
When specifying a Reference Year range, the “from” year should be smaller than the “to” year.
(5) Enter the Source of data.
(6) Enter any additional Comments.
(7) Click on Save to save the information.
Remark | The Target field doesn’t exist under ESF+ Specific Objective ESO4.13. |
2.2 TA priorities
Click on the Add button to add a row of information to this table.
Click on the Edit icon to modify the information in a row.
Click on the Delete icon to remove the information in a row.
Click on the Add button to add a new priority axis:
The Add row pop-up window appears:
Enter or select the following:
(1) Enter the ID.
(2) Enter the Order by.
The Order by field indicates in which order the priority will be displayed in the Table of Contents.
(3) Select the Type from the list.
The Type list contains 2 values: Article 36(4) and Article 37.
(4) Enter the Title.
(5) Click on Save to save the information.
Remark | In subsequent versions of the Programme (>1), TA Priorities created in earlier adopted versions
On Delete of a TA Priority, all TA Priority related information will be deleted. An alert message to avoid accidental loss of information will inform the User at the moment of save. The following information referring to the TA Priority will be removed:
|
2.2.1 Priority
Note | This section refers to technical assistance priorities of type Article 36(4) created in section 2.2. |
Click on the Add button to add a row of information to this table.
Click on the Edit icon to modify the information in a row.
Click on the Delete icon to remove the information in a row.
Click on the Add button to add the TA priority information:
The Add row pop-up window appears:
Enter or select the following:
(1) Select the Fund.
The Fund list will contain all Funds covered by the Programme as indicated in the Programme Version page. When the Programme covers only one Fund, this value is set by default.
(2) Select the Category of region.
The Category of Region List will contain all entries valid for Programme Country and the Fund selected above. It is only mandatory for ERDF and ESF+. When Funds ERDF and/or ESF+ are covered, they should at least have one Category of Region. For ERDF and ESF+, the 'Outermost or Northern Sparsely Populated Region' will only be shown for France, Spain, Portugal, Sweden and Finland.
(3) Select the Calculation Basis for Union Support.
(4) Click on Save to save the information.
Remark | Priority/Fund/Category of Region combinations adopted in a previous version can never be deleted or updated. Only their Calculation Basis can be updated. Therefore, in this case, only the Calculation Basis field will be updateable. Editing will be blocked when there is already information specified under the Priority, Specific Objective. On Save (Insert /Delete), the system will automatically maintain the records in:
|
2.2.1.1 Intervention from the funds
Types of Actions
Click on the Edit button to enter the information:
The Edit details pop-up window appears:
Enter or select the following:
(1) Enter the text in the text box provided.
(2) Click on Save to save the information.
Main target groups
Click on the Edit button to enter the information:
The Edit details pop-up window appears:
Enter or select the following:
(1) Enter the text in the text box provided.
(2) Click on Save to save the information.
2.2.1.2 Indicators
Table 2 Output indicators
Click on the Add button to add a row of information to this table.
Click on the Edit icon to modify the information in a row.
Click on the Delete icon to remove the information in a row.
Note | Technical Assistance Priorities cannot use Common Indicators. Only Programme Specific Output Indicators can be defined under a Technical Assistance Priority. The Programme Specific output indicator must be pre-defined in the Programme Specific Indicators table before it can be selected in the Priority Indicators table. A Programme Specific Output Indicator can only be deleted when not used anymore in any other record of the Output Indicator Table in any version of this Programme. |
Click on the Add button above the Programme Specific Indicators table to add a new Programme Specific output indicator:
The Add row pop-up window appears:
Enter or select the following:
(1) Enter the ID.
A Programme Specific Output Indicator code should be different from any Programme Specific Reserved Indicator code and from any Common Indicator code.
(2) Enter the Order by.
The Order by field indicates in which order the indicator will be displayed in the Table.
(3) Enter the Title.
(4) Enter the Measurement Unit.
(5) Click on Save to save the information.
Click on the Add button above the Priority Indicator table to add the Programme Specific output indicator:
The Add row pop-up window appears:
Enter or select the following:
(1) Select the Programme Specific Output Indicator from the list.
The Programme Specific Output Indicators are maintained by the MS per Programme. In this edit page, only one of them must be selected.
The Programme Specific Output Indicators table contains all previously defined Programme Specific Output Indicators, independently from Priority, Specific Objective or Fund. Programme Specific Output Indicators are defined ones and can then be used under different Priorities, Specific Objectives and Funds.
(2) Select the Fund from the list.
The Fund list contains all Funds covered by the TA Priority. When the Priority covers only one Fund, this value is set by default.
(3) Select the Category of region.
The Category of Region list contains all Categories of Region defined against the Priority and Fund. When the Priority and Fund covers only one Category of Region, this value is set by default. Category of Region is only enabled for ERDF and ESF+.
(4) Enter the Milestone(2024).
(5) Enter the Target (2029).
(6) Click on Save to save the information.
2.2.1.3 Breakdown by type of intervention
Table 4 Intervention field
Click on the Add button to add the information:
The Add row pop-up window appears:
Enter or select the following:
(1) Select the Fund.
The Fund list contains all Funds covered by the TA Priority. When the Priority covers only one Fund, this value is set by default.
(2) Select the Category of region.
The Category of Region list will contain all Categories of Regions covered by the Priority and the Fund. If the Priority and Fund covers only one Category of Region, this value is set by default. The field is only enabled for ERDF and ESF+.
(3) Select the Code from the list.
The Code list of Intervention Fields will contain all Technical Assistance Intervention Fields.
(4) Enter the Amount (EUR).
(5) Click on Save to save the information.
Table 7 ESF+ secondary themes
Click on the Add button to add the information:
The Add row pop-up window appears:
Enter or select the following:
(1) Select the Fund.
The Fund list contains all Funds covered by the TA Priority. When the Priority covers only one Fund, this value is set by default.
(2) Select the Category of region.
The Category of Region list will contain all Categories of Regions covered by the Priority and the Fund. If the Priority and Fund covers only one Category of Region, this value is set by default.
(3) Select the Code.
The Code list of Intervention Fields will contain all Technical Assistance Intervention Fields.
(4) Enter the Amount (EUR).
(5) Click on Save to save the information.
Table 8 Gender equality
Click on the Add button to add the information:
The Add row pop-up window appears:
Enter or select the following:
(1) Select the Fund.
The Fund list contains all Funds covered by the TA Priority. When the Priority covers only one Fund, this value is set by default.
(2) Select the Category of region.
The Category of Region list will contain all Categories of Regions covered by the Priority and the Fund. If the Priority and Fund covers only one Category of Region, this value is set by default.
(3) Select the Code.
The Code list of Intervention Fields will contain all Technical Assistance Intervention Fields.
(4) Enter the Amount (EUR).
(5) Click on Save to save the information.
2.2.2 Priority
Note | This section refers to technical assistance priorities of type Article 37 created in section 2.2. |
Click on the Add button to add a row of information to this table.
Click on the Edit icon to modify the information in a row.
Click on the Delete icon to remove the information in a row.
Click on the Add button to add the information:
The Add row pop-up window appears:
Enter or select the following:
(1) Select the Fund.
The Fund list will contain all Funds covered by the Programme as indicated in the Programme Version page. When the Programme covers only one Fund, this value is set by default.
(2) Select the Category of region.
The Category of Region List will contain all entries valid for Programme Country and the Fund selected above (CountryRegionCategory)(FundRegionCategory). It is only mandatory for ERDF and ESF+. When Funds ERDF and/or ESF+ are covered, they should at least have one Category of Region. For ERDF and ESF+, the 'Outermost or Northern Sparsely Populated Region' will only be shown for France, Spain, Portugal, Sweden and Finland.
(3) Select the Calculation Basis for Union Support.
(4) Click on Save to save the information.
2.2.2.1 Description
Click on the Edit button to enter the information:
The Edit details window appears:
Enter or select the following:
(1) Enter the text in the text box provided.
(2) Click on Save to save the information.
2.2.2.2 Breakdown by type of intervention
Table 4 Intervention field
Click on the Add button to add the information:
The Add row pop-up window appears:
Enter or select the following:
(1) Select the Fund.
The Fund list contains all Funds covered by the TA Priority. When the Priority covers only one Fund, this value is set by default.
(2) Select the Category of region.
The Category of Region list will contain all Categories of Regions covered by the Priority and the Fund. If the Priority and Fund covers only one Category of Region, this value is set by default. The field is only enabled for ERDF and ESF+.
(3) Select the Code from the list.
The Code list of Intervention Fields will contain all Technical Assistance Intervention Fields.
(4) Enter the Amount (EUR).
(5) Click on Save to save the information.
Table 7 ESF+ secondary themes
Click on the Add button to add the information:
The Add row pop-up window appears:
Enter or select the following:
(1) The Fund is always ESF+ by default.
(2) Select the Category of region.
The Category of Region list will contain all Categories of Regions covered by the Priority and the Fund. If the Priority and Fund covers only one Category of Region, this value is set by default.
(3) Select the Code.
The Code list of Intervention Fields will contain all Technical Assistance Intervention Fields.
(4) Enter the Amount (EUR).
(5) Click on Save to save the information.
Table 8 Gender equality
Click on the Add button to add the information:
The Add row pop-up window appears:
Enter or select the following:
(1) Select the Fund.
The Fund list contains all Funds covered by the TA Priority. When the Priority covers only one Fund, this value is set by default.
(2) Select the Category of region.
The Category of Region list will contain all Categories of Regions covered by the Priority and the Fund. If the Priority and Fund covers only one Category of Region, this value is set by default.
(3) Select the Code.
The Code list of Intervention Fields will contain all Technical Assistance Intervention Fields.
(4) Enter the Amount (EUR).
(5) Click on Save to save the information.
3 Financial Plan
3.1 Transfers and contributions
Note | This page is only available for amendments (= versions > 1). Any inconsistencies between the options ticked and the data available in the contribution and transfer tables will be checked by validation rules. |
Click on the Edit button to enter the information:
The Edit details pop-up window appears:
Enter or select the following:
(1) Select the tick box to choose the type of transfers and/or contribution.
(2) Click on Save to save the information.
Table 15A to InvestEU by year
Note | This page is only available for amendments (= versions > 1). |
Click on the Add button to add the information:
The Add row pop-up window appears:
Enter or select the following:
(1) Select the Contribution from fund.
The From Fund list contains all Funds covered by the Programme, JTF excluded. When the Programme covers only one Fund, this value is set by default.
(2) Select the Category of Region.
The Category of Region list will contain all Categories of Regions covered by the Fund in the Programme, Outermost Regions excluded. If the Programme Fund covers only one Category of Region, this value is set by default. Category of Region is only enabled for ERDF and ESF+.
(3) Enter the To InvestEU window.
The InvestEU list will contain all InvestEU windows as described in Article 7(a)-(d) of the InvestEU Regulation.
(4) Enter the amounts for the years 2021 - 2027.
(5) Click on Save to save the information.
Table 15B to InvestEU summary
This is a summary screen of the contributions to InvestEU and is non-editable:
Justification
Click on the Edit button to edit the information:
The Edit details pop-up window appears:
Enter the following:
(1) Enter the text in the text box provided.
(2) Click on Save to save the information.
Table 16A to instruments by year
Note | This page is only available for amendments (= versions > 1). |
Click on the Add button to add the information.
The Add row pop-up window appears:
Enter or select the following:
(1) Select the Transfer from fund.
The From Fund list contains all Funds covered by the Programme, JTF excluded. When the Programme covers only one Fund, this value is set by default.
(2) Select the Category of Region.
The Category of Region list is only available for ERDF and ESF+ and will contain all Categories of Regions covered by the Fund in the Programme, Outermost Regions excluded. If the Programme Fund covers only one Category of Region, this value is set by default.
(3) Enter the To Instrument.
The Instrument list will contain all instruments.
(4) Enter the amounts for the years 2021 - 2027.
(5) Click on Save to save the information.
Table 16B to instruments summary
This is a summary screen of the transfers to instruments under direct or indirect management and is non-editable:
Justification
Click on the Edit button to edit the information:
The Edit details pop-up window appears:
Enter the following:
(1) Enter the text in the text box provided.
(2) Click on Save to save the information.
Table 17A between funds by year
Note | This page is only available for amendments (= versions > 1). |
Click on the Add button to add the information:
The Add row pop-up window appears:
Enter or select the following:
(1) Select the From fund.
The From Fund list contains all Funds covered by the Programme, JTF excluded. When the Programme covers only one Fund, this value is set by default.
(2) Select the From Category of region.
The From Category of Region list will contain all Categories of Regions covered by the From Fund in the Programme, Outermost Regions excluded. If the Programme Fund covers only one Category of Region, this value is set by default. From Category of Region is only enabled for ERDF and ESF+.
(3) Enter the To fund.
The To Fund list contains Funds ERDF, ESF+, CF, EMFAF, AMIF, ISF, BMVI.
(4) Select the To Category of region.
The To Category of Region list will contain all possible Categories of Regions of the To Fund, Outermost Regions excluded.
(5) Enter the amounts for the years 2021 - 2027.
(6) Click on Save to save the information.
Remark | From and To Fund must be different. Transfers between ERDF and ESF+ must be within the same Category of Region. |
Table 17B between funds summary
This is a summary screen of the transfers between ERDF, ESF+ and Cohesion Fund or to another Fund or Funds and is non-editable:
Justification
Click on the Edit button to edit the information:
The Edit details pop-up window appears:
Enter the following:
(1) Enter the text in the text box provided.
(2) Click on Save to save the information.
Table 21 to REPowerEU
Note | This page is only available for amendments, when the Programme was previously adopted by the Commission. |
Click on the Add button to add the information:
The Add row pop-up window appears:
Enter or select the following:
(1) Select the From fund.
The From Fund list contains all Funds covered by the Programme, JTF excluded. When the Programme covers only one Fund, this value is set by default.
(2) Select the Category of region.
The Category of Region list will contain all Categories of Regions covered by the Fund in the Programme, Outermost Regions excluded. If the Programme Fund covers only one Category of Region, this value is set by default.
(3) Enter the annual amounts.
(4) Click on Save to save the information.
Remark | Category of Region is only enabled for ERDF and ESF+ and is mandatory. Fund is mandatory. |
3.2 JTF
Table 3.2.1 Table 18 JTF prior to transfer
Note | A record is automatically foreseen for each Priority covering JTF (also for Technical Assistance). |
Click on the Edit button to edit the information.
The Edit details pop-up window appears:
Enter the following:
(1) Enter the JTF allocation amounts without decimals.
(2) Click on Save to save the information.
Table 3.2.2 Transfers to JTF
Remark | Any inconsistencies between the options ticked and the data available in the JTF transfer tables will be checked by validation rules. |
Click on the Edit button to edit the information:
The Edit details pop-up window appears:
Enter or select the following:
(1) Tick the Transfer to JTF that apply.
(2) Click on Save to save the information.
Table 18A within programme by year
Click on the Add button to add the information:
The Add row pop-up window appears:
Enter or select the following:
(1) Select the Transfer from fund.
The From Fund list contains Funds ERDF and ESF+ when covered by the Programme. When the Programme covers only one Fund, this value is set by default.
(2) Select the Category of region.
The Category of Region list will contain all Categories of Regions covered by the Fund in the Programme, Outermost Regions excluded. If the Programme Fund covers only one Category of Region, this value is set by default.
(3) Enter the To JTF Priority.
The JTF Priority list will contain all Priorities covering JTF, also Technical Assistance.
(4) Enter the annual amounts for the years 2021 – 2027 without decimals.
(5) Click on Save to save the information.
Table 18B within programme summary
This is a summary table and is non-editable:
Table 18C from other programmes by year
Transfer of ERDF and ESF+ resources from other programme(s) to the Just Transition Fund (JTF) in this programme.
Click on the Add button to add the information:
The Add row pop-up window appears:
Enter or select the following:
(1) Select the Transfer from fund.
The From Fund list contains Funds ERDF and ESF+. When the Programme covers only one Fund, this value is set by default.
(2) Select the Category of Region.
The Category of Region list will contain all Categories of Regions covered by the selected Fund for the Country of the Programme, Outermost Regions excluded. If the Programme Fund covers only one Category of Region, this value is set by default.
(3) Enter the To JTF priority.
The JTF Priority list will contain all Priorities covering JTF, also Technical Assistance.
(4) Enter the annual amounts for the years 2021 – 2027 without decimals.
(5) Click on Save to save the information.
Table 18D from other programmes summary
This is a summary table and is non-editable:
Justification
Click on the Edit button to edit the information:
The Edit details pop-up window appears:
Enter the following:
(1) Enter the text in the text box provided.
(2) Click on Save to save the information.
3.3 Transfers between categories of region
Table 19A within programme
Transfers between categories of region at the mid-term review, within the programme.
Click on the Add button to add the information:
The Add row pop-up window appears:
Enter or select the following:
(1) Select the From Category of region.
The From Category of Region list will contain all Categories of Regions covered by the Fund in the Programme, Outermost Regions excluded.
(2) Select the To Category of region.
The To Category of Region list will contain all Categories of Regions covered by the Fund in the Programme, Outermost Regions excluded..
(3) Enter the annual amounts for the years 2025 – 2027 without decimals.
(4) Click on Save to save the information.
Table 19B to other programmes
Transfers between categories of region at the mid-term review, to other programmes.
Click on the Add button to add the information:
The Add row pop-up window appears:
Enter or select the following:
(1) Select the From category of region.
The From Category of Region list will contain all Categories of Regions covered by the Fund in the Programme, Outermost Regions excluded.
(2) Select the To category of region.
The To Category of Region list will contain all Categories of Region, Outermost Regions excluded.
(3) Enter the annual amounts for the years 2025 – 2027 without decimals.
(4) Click on Save to save the information.
3.4 Transfers back
Table 20A by year
Note | The User must choose between the options From Instrument or From InvestEU window. |
Click on the Add button to add the information:
The Add row pop-up window appears:
Enter or select the following:
(1) Select either From Instrument or From InvestEU window.
The From Instrument list will contain all Instruments.
The InvestEU list will contain all InvestEU windows as described in Article 7(a)-(d) of the InvestEU Regulation.
(2) Select the To fund.
The To Fund list contains all Funds covered by the Programme, JTF excluded. When the Programme covers only one Fund, this value is set by default.
(3) Select the Catgory of region.
The Category of Region list will contain all Categories of Regions covered by the Fund in the Programme, Outermost Regions excluded. If the Programme Fund covers only one Category of Region, this value is set by default.
(4) Enter the annual amounts for the years 2021 – 2027 without decimals.
(5) Click on Save to save the information.
Table 20B Summary
This is a summary table and is non-editable:
3.5 Table 10 Financial appropriations by year
Remark | A record will be automatically foreseen for each Fund (when JTF, foresee one record for allocation type Article 3, one for allocation type Article 4, and one additional record for Article 7 related to Article 3 and one for Article 7 related to Article 4) and Category of Region covered by the Programme and defined in previous pages. Table 10 should not contain decimals. Refer to Validation Rule 58 for more information. |
Click on the Edit button to edit the information:
The table becomes editable:
Enter or select the following:
(1) Enter the annual Amount for all editable cells.
The Annual plan is presented for all years between First Year and Last Year.
(2) Click on Save to save the information.
Remark | The Years 2026 and 2027 contain an Amount without flexibility and a Flexibility Amount. Their Annual Total (Amount without flexibility + Flexibility Amount) is calculated by the system but persisted. For JTF Article 4 and JTF Article 7 related to Article 4 there is no flexibility. |
3.6 Table 11 Total financial allocations by priority & fund
Remark | The Priority plan is presented for all Priority, Fund (when JTF, one for each of the 2 allocation types Art.3 and Art.4) and Category of Region combinations defined in this Programme. Table 11 should not contain decimals. Refer to Validation Rules 59 and 60 for more information. |
Click on the Edit button to edit the information:
The table becomes editable:
Enter or select the following:
(1) Enter the amount for Less flexibility amount (g).
(2) Enter the amount for Flexibility amount (h).
(3) Enter the amount Public (c).
(4) Enter the amount Private (d).
(5) Enter the co-financing rate – Article 112(7) where is applicable.
(6) Click on Save to save the information.
Remark | JTF Article 7 is not required in Table 11. For JTF Article 4, there is no flexibility. A JTF Total row will be foreseen and calculated per JTF priority. The Private column is disabled when the basis for calculation of Union support is “Public”. The “Co-financing rate – Article 112(7)” is only enabled for Priorities promoting the socio-economic integration of third country nationals, and doesn’t need a calculated Total nor Grand Total. |
4 Table 12 Enabling Conditions
Note | For each of the Criteria of the Enabling Conditions, the User must indicate if it was fulfilled or not. The Reference and the Justification are only mandatory when the Criterion was fulfilled. |
Click on the Edit button to edit the information:
The table becomes editable:
Enter or select the following:
(1) Select the tick-box to confirm that the Criterion was Fulfilled.
(2) Enter a Reference, only if the Criterion was fulfilled.
(3) Enter a Justification.
(4) Click on Save to save the information.
5 Programme authorities
Table 13 Authorities
Edit the Managing Authority, Audit Authority or Body which receives payments details.
Click on the Edit icon to edit the Managing Authority, Audit Authority or Body which received payments from the Commission details:
The Edit details pop-up window appears:
Enter or select the following:
(1) Enter the Name of the Institution.
(2) Enter a Contact Name.
(3) Enter a Position.
(4) Enter an Email.
(5) Click on Save to save the information.
Add the Body which received payments (Technical Assistance) or the Accounting function details.
Click on the Add button to edit the Managing Authority, Audit Authority or Body which received payments from the Commission details:
The Add row pop-up window appears:
Enter or select the following:
(1) Select the Programme Authority.
(2) Enter the Name of the institution.
(3) Enter a Contact Name.
(4) Enter a Position.
(5) Enter an Email.
(6) Click on Save to save the information.
Table 13A Repartition of reimbursed amounts
Note | The User needs the role of MS Managing Authority with Update rights (MSMAu) to update the Authorities (Table 13). A record will be automatically foreseen in Table 13A for each “Body which receives payments from the Commission in case of technical assistance pursuant to Article 36(5)” defined in Table 13. The percentage points should be an integer between 1 and 100. On the last Programme version, Authorities (Table 13A) can be updated at any time, independent from the status of the Programme version. Updating the Authorities (Table 13A) will not change the Status. When updating the Programme Authority (Table 13A) when the Programme Version is on the Commission Node, generate an event to inform the Commission the Programme Authority (Table 13A) was updated. The Table records and the Edit button will be shown when there is more than 1 record. |
Click on the Edit button to edit the information:
The table becomes editable:
Enter or select the following:
(1) Enter the percentage by body.
(2) Click on Save to save the information.
Remark | The percentage points should be integers between 1 and 100. |
6 Partnership
Click on the Edit button to edit the information:
The Edit details pop-up window appears:
Enter the following:
(1) Enter the text in the text box provided.
(2) Click on Save to save the information.
7 Communication & visibility
Click on the Edit button to edit the information:
The Edit details pop-up window appears:
Enter the following:
(1) Enter the text in the text box provided.
(2) Click on Save to save the information.
8 Table 14 Use of unit costs, lump sums, flat rates…
Note | If the User would like to insert Appendix II for Article 37 TA for IJG Programs which are not only dedicated to TA priorities, a separate document type ‘Other Member State document’ can be added as Appendix II is not available in structured form for TA schemes. |
Click on the Edit button to edit the information:
The Edit details pop-up window appears:
Enter or select the following:
(1) Select the tick-box to make your choice between Intended use of Articles 94 & 95 CPR.
(2) Click on Save to save the information.
Remark | When checking the Article 94 option, a ToC entry for Appendix 1 will be created with 1 default Operation Type 1 and 1 default Indicator 1. When checking the Article 95 option, a ToC entry for Appendix 2 will be created with 1 default Operation Type 1. When un-checking the Article 94 option, an alert will be issued saying “Indicating that you will not make use of Article 94 will remove Appendix 1 and all its data” OK/Cancel. On OK, all data on Appendix 1 will be deleted and the Appendix ToC will be removed. When un-checking the Article 95 option, an alert will be issued saying “Indicating that you will not make use of Article 95 will remove Appendix 2 and all its data” OK/Cancel. On OK, all data on Appendix 2 will be deleted and the Appendix ToC will be removed. |
Appendix 1
A Summary
Note | The records are automatically foreseen by the system by crossing the Programme structure (Priority, Fund, Category of Region, Specific Objective) with the Operation Type detail (Operation Type, Specific Objective(s), Indicator) based on their common Specific Objective(s). Part A will automatically take information from part B and create the summary table broken down by Priority/Fund/Category of Region/Specific Objective/Operation Type and Indicator triggering reimbursement. Therefore, the number of lines in table A will depend on the particularity of the SCO scheme(s) included in Appendix 1. There are four fields that need to be manually introduced in Part A i.e. “Estimated proportion of the total financial allocation within the priority to which the SCO will be applied”, “Code for the type of operation”, “Code for the indicator triggering reimbursement” and “SCO non applicable” |
Click on the Edit button to edit the information:
The Edit details pop-up window appears:
Enter the following:
(1) Enter the percentage for Estimated proportion of the total financial allocation within the priority to which the SCO will be applied in% (estimate).
The sum of the Estimated Proportion % per Priority must be lower than or equal to 100. This will be checked by a Validation rule (VAL.074). This field is mandatory. The information to be provided is at the level of each line of Part A. If there are several lines for the same SCO within a priority axis, then the sum of all these lines must be equal to the estimated proportion of the total financial allocation within the priority to which the SCO will be applied.
(2) Enter the Code for the Type(s) of operation covered.
The Operation Type Code list contains all Intervention Field codes (and their description) valid for the Specific Objective, Fund and selected in Table 4 for that Priority, Fund, Category of Region, Specific Objective. This field is mandatory.
If an SCO scheme applies to all/a significant number of types of interventions in the programme, choose one type of intervention in Part A (if possible, the most relevant one for the SCO scheme) and indicate, in part B (under Description of operations), all the other types of interventions covered by the SCO scheme.
(3) Enter the Code for the Indicator triggering reimbursement.
The Indicator Code list contains all Common Indicator codes (and their description), Output and Result, already used in Tables 2 and 3, for the Priority, Fund, Category of Region, Specific Objective combination.
This field is mandatory when the SCO uses common indicators (to be selected from the drop-down list). The field should be left empty in case the SCO uses programme specific indicators.
This field is not mandatory for Material Deprivation (ESO4.13) which doesn’t have a Table 4.
(4) Select the tick box to indicate whether the SCO is non applicable.
It is possible that one Specific Objective covers multiple Priorities and/or Funds and/or Categories of region, but some of these Priorities and/or Fund and/or Categories of region are not concerned by a proposed SCO scheme in Appendix 1. However, Part A of Appendix 1 will create separate lines for each Priority/Fund/Category of region covered by the given Specific Objective (i.e. even for those which are not part of SCO scheme). In such case, tick the box in column SCO non applicable for those Priorities/Funds/Categories of region for which the SCO scheme does not apply.
When SCO is set to be non-applicable, the Estimated Proportion %, the Intervention Field Code and the Indicator Code are removed.
(5) Click on Save to save the information.
B Detail
Remark | There is a single Part B for all SCOs schemes, types of operations and indicators included in the Appendix I. The levels of the type of operations and the indicators can be repeated as many times as needed. The Operation Type Short Title is needed to enable the User to link an Intervention Field Code to the Operation Type in Appendix 1 Part A. For each Operation Type created/deleted, an entry is created/deleted in the ToC. There should be at least 1 Operation Type and that one can never be deleted. |
Edit the existing Operation Type “1”.
Click on the Edit icon
to edit the default Operation Type “1”:
The Edit details pop-up window appears:
Enter the following:
(1) Enter the Operation type short title in the text box provided.
Include a meaningful short title, not just a number, as this information is needed to enable the User to link an Intervention Field Code in part A to the Operation Type in Part B.
(2) Click on Save to save the information.
Add a new Operation Type.
Click on the Add button
to add a new operation type:
The Add row pop-up window appears:
Enter the following:
(1) Enter the Operation type short title in the text box provided.
Include a meaningful short title, not just a number, as this information is needed to enable the User to link an Intervention Field Code in part A to the Operation Type in Part B.
(2) Click on Save to save the information.
Operation type
Click on the Edit button to edit the information:
The Edit details pop-up window appears:
Enter or select the following:
(1) The Operation type short title is the one created previously, the field can be edited if necessary.
If the same SCO covers different types of operations, add one row for each type of operation to which the SCO is applied.
(2) Select the tick box to confirm that The managing authority received support from an external company to set out the simplified costs.
(3) Enter the Name of external company.
(4) Enter the Description of the operation.
Include the eligible activities, beneficiaries, expected outputs, duration, as well as the operation’s contribution to the achievement of the objectives of the programme. Please, also indicate the timeline for implementation i.e. envisaged starting date of the selection of operations and envisaged final date of their completion.
If applicable, do not forget to indicate all the types of interventions in the programme covered by the SCO scheme (see explanations above in Part A - Code for the Type(s) of operation covered).
(5) Select the Specific objective(s) that the operation type refers to by moving them from the left column to the right one.
The Specific Objective list contains all Specific Objectives used under Programme Priorities.
Under each operation type one or several specific objectives can be selected.
(6) Enter the amount for Total amount (national and Union) expected to be reimbursed by the Commission on this basis.
This field should provide information with regard to the amount (national and EU) expected to be reimbursed for all the SCO (s) under a given operation type (and, if need be, under the different SO to which the operation type applies).
(7) Click on Save to save the information.
Indicators
Remark | For each Indicator created/deleted, an entry is created/deleted in the ToC under its Operation Type. There should be at least 1 Indicator and that one can never be deleted. If an operation encompasses several SCOs for different categories of costs, different projects or successive phases of an operation, additional rows have to be added for each indicator triggering reimbursement (Indicator: 1, Indicator: 2 …) and filled in the relevant information under fields 3 to 11. The levels of the indicators can be repeated as many times as needed. |
Edit the existing Indicator “1”.
Click on the Edit icon
to edit the default Indicator “1:
The Edit details pop-up window appears:
Enter the following:
(1) Enter the Indicator triggering reimbursement in the text box provided.
(2) Click on Save to save the information.
Add a new Indicator.
Click on the Add button
to add a new Indicator:
The Add row pop-up window appears:
Enter the following:
(1) Enter the Indicator triggering reimbursement in the text box provided.
(2) Click on Save to save the information.
Indicator: details
Click on the Edit button to edit the information:
The Edit details pop-up window appears:
Enter or select the following:
(1) The Indicator triggering reimbursement is the one created previously, the field can be edited.
(2) Enter the Unit of measurement for the indicator triggering reimbursement.
(3) Select the SCO type.
The SCO Type list contains all SCO Types (Lump sum, Unit cost, Flat rate).
(4) Enter the Amount per unit of measurement or percentage (for flat rates) of the SCO.
This field allows entering a free text, as it might be that a programme has two or more different amounts per unit of measurement (or % for flat rates). The maximum allowed is 1 000 characters.
(5) Enter the Categories of costs covered by the unit cost, lump sum or flat rate in the text box provided.
(6) Select Yes or No for Do these categories of costs cover all eligible expenditure for the operation?
If no, provide further information on the costs not covered by the SCO scheme in the above field Categories of costs covered by the unit cost, lump sum or flat rate.
(7) Enter the Adjustment(s) method in the text box provided.
If applicable, indicate the frequency, cut-off date and timing of the adjustment and make a clear reference to a specific indicator (including a link to the website where this indicator is published, if applicable).
(8) Enter the Verification of the achievement of the units delivered in the text box provided.
Describe what document(s)/system will be used to verify the achievement of the units delivered; what will be checked and by whom during management verifications, as well as what arrangements will be made to collect and store relevant data/documents.
(9) Enter the Possible perverse incentives, mitigating measures and the estimated level of risk (high/medium/low) in the text box provided.
Explain if there are any potential negative implications on the quality of the supported operations and, if so, what measures (e.g. quality assurance) will be taken to offset this risk.
(10) Click on Save to save the information.
C Calculation
1 Source of data
Note | There is a single Part C for all SCOs schemes and types of operations included in Appendix 1. This section has to be filled in with relevant information for each SCO scheme included in Appendix 1 and assessed by the national audit authority. The assessment of the national audit authority has to be uploaded in SFC under the section General -> Documents. Due to the limitation of characters in the fields of part C (8 000 characters/field), the information provided should be a short summary of the more detailed information that is included in the audit authority assessment. If deemed necessary, other supporting documentation can be uploaded in the system via the same section General -> Documents. |
Click on the Edit button to edit the information:
The Edit details pop-up window appears:
Enter the following:
(1) Enter the text in the text box provided.
(2) Click on Save to save the information.
2 Relevance
Click on the Edit button to edit the information:
The Edit details pop-up window appears:
Enter the following:
(1) Enter the text in the text box provided.
(2) Click on Save to save the information.
3 Calculations
Click on the Edit button to edit the information:
The Edit details pop-up window appears:
Enter the following:
(1) Enter the text in the text box provided.
(2) Click on Save to save the information.
4 Ensurance
Click on the Edit button to edit the information:
The Edit details pop-up window appears:
Enter the following:
(1) Enter the text in the text box provided.
(2) Click on Save to save the information.
5 Assessment
Click on the Edit button to edit the information:
The Edit details pop-up window appears:
Enter the following:
(1) Enter the text in the text box provided.
(2) Click on Save to save the information.
Appendix 2
A Summary
Note | For non-TA Programmes, the records are automatically foreseen by the system by crossing the Programme structure (Priority, Fund, Category of Region, Specific Objective) with the Operation Type detail (Operation Type, Specific Objective(s)) based on their common Specific Objective(s). For TA Programmes, the records are automatically foreseen by the system by crossing the Programme structure (Technical Assistance Article 37 Priorities, Fund, Category of Region) with the Operation Types. Appendix 2 is created on the basis of the specific objectives in the programme. However, in the case of a Technical Assistance priority in a non-TA programme, there are no specific objectives linked to it in the programme. Therefore, if Article 37 CPR is used under a TA priority in a non-TA programme, Appendix 2 cannot be filled in directly in SFC (as structured data). In this situation, the Member State is requested to fill in, in word format, Appendix 2 of Annex V to the programme template as provided in the CPR and send it to the Commission via SFC2021 under the General -> Documents section, using the document type ‘Other Member State document’. Appendix 2 is created on a different basis for the TA programmes. Therefore, if Article 37 CPR is used under a TA programme which has no specific objectives itself, the Appendix 2 can be filled in in a structured format directly in SFC2021 (i.e. no need to upload a word version as ‘Other Member State document’). |
Click on the Edit button to edit the information:
The Edit details pop-up window appears:
Enter the following:
(1) Enter The amount covered by the financing not linked to costs.
The Amount Covered is mandatory for applicable FNLC records only, the Intervention Field Code is mandatory except for Material Deprivation (ESO4.13) which doesn’t have a Table 4 and for non-applicable FNLC records.
(2) Enter the Code for the Type(s) of operation covered.
The Operation Type Code list contains all Intervention Field codes valid for the Specific Objective, Fund.
For non-TA Programmes, the Operation Type Code list contains all Intervention Field codes (and their description) valid for the Specific Objective, Fund and selected in Table 4 for that Priority, Fund, Category of Region, Specific Objective. For TA Programmes, the Operation Type Code list contains all Technical Assistance Intervention Field codes (and their description) selected in Table 4 for that Technical Assistance Article 37 Priority.
(3) Enter the Code for the Indicator triggering reimbursement.
The Indicator Code list contains all Common Indicator codes, Output and Result, already used in Tables 2 and 3, for the Priority, Specific Objective combination.
For non-TA Programmes, the Indicator Code list contains all Common Indicator codes (and their description), Output and Result, already used in Tables 2 and 3, for the Priority, Fund, Category of Region, Specific Objective combination. For TA Programmes, since there are no Indicator Tables for Technical Assistance Article 37, the Indicator Code list will be empty.
(4) Select the tick box whether the FNLC is non applicable.
When FNLC is set to be non-applicable, the Amount Covered, the Intervention Field Code and the Indicator Code are removed.
(5) Click on Save to save the information.
B Detail
Remark | The Operation Type Short Title is needed to enable the User to link an Intervention Field Code in part A to the Operation Type in Part B. For each Operation Type created/deleted, an entry is created/deleted in the Table of Contents (ToC). There should be at least 1 Operation Type and that one can never be deleted. |
Edit existing Operation Type “1”.
Click on the Edit icon
to edit the default Operation Type “1”:
The Edit details pop-up window appears:
Enter the following:
(1) Enter the Operation type short title in the text box provided.
(2) Click on Save to save the information.
Add a new Operation Type.
Click on the Add button
to add a new operation type:
The Add row pop-up window appears:
Enter the following:
(1) Enter the Operation type short title in the text box provided.
(2) Click on Save to save the information.
Operation type
Remark | The Operation Type Short Title is needed to enable the User to link an Intervention Type Code in Part A to the Operation Type in Part B. |
Click on the Edit button to edit the information:
The Edit details pop-up window appears:
Enter or select the following:
(1) The Operation type short title is the one created previously, the field can be edited.
(2) Enter the Description of the operation.
(3) Select the Specific objective(s) that the operation type refers to by moving them from the left column to the right one.
The Specific Objective list contains all Specific Objectives used under Programme Priorities. For TA Programmes this list will be empty.
(4) Enter the Conditions to be fulfilled or results to be achieved in the text box provided.
(5) Select the Deadline for fulfilment of conditions or results to be achieved.
(6) Enter the Indicator definition in the text box provided.
(7) Enter the Unit of measurement for conditions to be fulfilled/results to be achieved triggering reimbursement by the Commission in the text box provided.
(8) Click on Add deliverable (if applicable) to add a new record in the table.
(9) Enter the fields for each record.
In the field Amounts(EUR), you should indicate the Union funding.
(10) Select the Envisaged type of reimbursement method used to reimburse the beneficiary or beneficiaries from the list.
The Reimbursement Method list contains all Reimbursement methods (Reimbursement of eligible costs actually incurred, Unit cost, Lump sum, Financing not linked to costs).
(11) Enter the Total amount (including Union and national funding).
(12) Enter the Adjustment(s) method.
(13) Enter the Verification of the achievement of the result or condition (and where relevant, the intermediate deliverables).
(14) Enter the Use of grants in the form of financing not linked to costs.
(15) Enter the Arrangements to ensure the audit trail. Please list the body(ies) responsible for these arrangements.
(16) Click on Save to save the information.
Appendix 3
Click on the Edit button to edit the information:
The Edit details pop-up window appears:
Enter or select the following:
(1) Enter the text in the text box provided.
(2) Click on Save to save the information.
TJTP
Note | This section will only be enabled when JTF is selected. |
Click on the Edit button to select a TJTP Version:
A drop-down menu appears:
Enter or select the following:
(1) Select the TJTP Version from the list.
The TJTP version list will contain the last version of all completed TJTP versions of the Country of the Programme, plus the ones already selected, ordered by TJTP reference. The ones selected and the deprecated ones will not be visible in the list.
Remark | Selecting a TJTP version from the drop down list will add it to the selected ones when the TJTP was not yet selected. When in the TJTP version list, there is a more recent version of an already selected TJTP, then selecting that more recent version will replace the old selection. |
(2) Click on Save to save the information.
Validate the Programme IJG
Remark | The Programme IJG can be validated at any time, when the current version is in status Open. The User can edit and revalidate as many times as necessary before sending. To validate the Programme, the User must have the role of Member State Managing Authority with Update access (MSMAu). |
Click on the Validate button to validate the Programme IJG.
Remark | An Error will block you from sending the Programme IJG. The error(s) should be resolved and the Programme IJG must be revalidated. Note that a Warning does not block you from sending the Programme IJG. |
The system validates the following information:
Code | Severity | Validation Rule |
001 | Error | Validate that the “First year” and the “Last year” are = 2021 and = 2027. |
002 | Error | Validate for version 1 when the BudgetSource of the CCI indicates a mono-Fund, that only that Fund is selected (‘RF’=>’ERDF’, ‘SF’=>’ESF+’, ‘CF’=>’CF’, ‘JTF’=>’JT’) (Implicit in web). |
003 | Error | Validate when programme was once adopted by EC and Non-substantial transfer (Article 24(5) CPR) is true that MS amending decision number and MS amending decision entry into force date are not null, and when Non-substantial transfer (Article 24(5) CPR) is false that MS amending decision number and MS amending decision entry into force date are null. |
004 | Error | Validate when programme was once adopted by EC that no Funds are removed compared to the previous adopted version. |
005 | Error | Validate that there is at least one record in the NUTS regions covered by the programme. |
006 | Error | Validate in table 1 that the specific objectives selected are valid for the Fund(s) covered by the programme (SpecificObjectiveFund) (Implicit in web). |
007 | Warning | Validate for version 1 when the BudgetSource of the CCI indicates a multi-Fund, that more than one Fund is selected. |
008 | Error | Validate in table 1, when ESF+ dedicated priorities are selected that the programme covers the ESF+ (Implicit in web). |
009 | Error | Validate when programme was once adopted by EC that no dedicated priority is removed from table 1 compared to the previous adopted version. |
010 | Error | Validate that the specific objectives selected in table 1 are used under a priority. |
011 | Error | Validate that the dedicated ESF+ priorities selected in table 1 are used under a priority. |
012 | Error | Validate that the programme contains at least one priority. |
013 | Error | Validate when programme was once adopted by EC that no priorities are removed compared to the previous adopted version. |
014 | Error | Validate in table 13 that one and only one “Managing authority” record exists and that all three mandatory fields “name of institution”, “contact name” and “email” are filled in (not empty) (Implicit in web). |
015 | Error | Validate in table 13 that one and only one “Audit authority” record exists and that all three mandatory fields “name of institution”, “contact name” and “email” are filled in (not empty) (Implicit in web). |
016 | Error | Validate in table 13 that one and only one “Body which receives payments from the Commission” record exists and that all three mandatory fields “name of institution”, “contact name” and “email” are filled in (not empty) (Implicit in web). |
017 | Warning | Validate that at least one official in charge of the Member State exists. |
018 | Error | Validate that the CCI code matches the following regular expression: (……16..PR…|……16..TA…|……05..PR…|……05..TA…) (Implicit in web). |
019 | Error | Validate when programme was once adopted by EC that the “First Year” is not modified compared to the previous adopted version (Implicit in web). |
020 | Error | Validate when programme was once adopted by EC that the “Last Year” is not decreased compared to the previous adopted version. |
021 | Error | Validate when programme was once adopted by EC that the dedicated priority type of a priority has not been modified compared to the previous adopted version (Implicit in web). |
022 | Error | Validate when programme was never adopted by EC, that “non-substantial transfer (Article 24(5) CPR)” and “Clerical or editorial corrections (Article 24(6) CPR)” and “Approved by monitoring committee” are false (Implicit in web). |
023 | Error | Validate that all integral documents have at least one attachment with a length > 0. |
024 | Error | Validate that a dedicated priority only covers the Fund it relates to (Implicit in web). |
025 | Error | Validate that all specific objectives covered by a priority relate to the same policy objective/JTF specific objective. |
026 | Error | Validate that an ESF+ dedicated priority refers to an ESF+ dedicated priority types selected in table 1 (Implicit in web). |
027 | Error | Validate that a non-dedicated priority only refers to specific objectives selected in table 1 (Implicit in web). |
028 | Error | Validate when programme was once adopted by EC that no priority, Fund, category of region combinations are removed compared to the previous adopted version. |
029 | Error | Validate that “Title in EN” was provided. |
030 | Error | Validate that the Fund, category of region combinations in PriorityFundRegionCategory are valid (CountryRegionCategory) (FundRegionCategory) (Implicit in web). |
031 | Error | Only for MS with chosen option technical assistance pursuant to Article 36(4) in section 5 of PA: Validate in each of the dimensions tables:
that the total per Fund and category of region under each priority is equal to the equivalent “union contribution (incl. flexibility amount)” in table 11. |
032 | Error | Only for MS with chosen option technical assistance pursuant to Article 36(5) in section 5 of PA: Validate in each of the dimensions tables:
that the total per Fund and category of region under each priority is equal to the equivalent “union contribution without TA pursuant to Article 36(5) + flexibility amount without TA pursuant to Article 36(5)” in table 11. |
033 | Error | Validate for non-TA priorities in dimensions table 4 that the intervention fields are valid for the priority’s specific objective and Fund (SpecificObjectiveFundDimension) (Implicit in web). |
034 | Error | Validate for TA priorities in dimension table 4 that the intervention fields are valid for the technical assistance (InterventionField.isTechnicalAssistance) and • for Art. 36(4) TA only uses codes 179-182 • for Art. 37 TA only uses code 182. |
035 | Error | Validate in table 7 (dimension 6 ESF+ secondary theme) that only Fund ESF+ is used. |
036 | Error | Validate in table 13 that the record(s) “Body which receive payments from the Commission in case of technical assistance pursuant to Article 36(5) CPR” can be only exist for the MS which chose option of technical assistance pursuant to Article 36(5) in section 5 of PA (Implicit in web). |
037 | Warning | Validate when this programme has never been adopted and exists in table 9A/9B of the last Partnership Agreement sent to the Commission that in table 11 of this programme the total Union contribution per Fund and category of region equals the equivalent total in table 9A/9B of that Partnership Agreement version: For PA table 9B, the equivalent amounts in programme table 11 are under following fields:
For PA table 9A, the equivalent amounts in programme table 11 are under following fields: Union contribution in table 9A = Union contribution in table 11. |
038 | Error | Validate for version 1 that the Partnership Agreement of the country of the programme has already been sent to the Commission. |
039 | Error | Validate in table 2 for non-TA priorities financed by ERDF/CF/JTF/ESF+ (section 2.1.1.1.2) that there is at least one output indicator defined or selected per priority and specific objective, except for Material Deprivation dedicated priority and specific objective ESO4.13. |
040 | Error | Validate in table 2 for non-TA priorities that the common output indicators are valid for the Fund and specific objective (GoalSpecificObjectiveFundIndicator) and with CommonIndicator.useInProgramme true (Implicit in web). |
041 | Error | Validate in table 2 that programme specific indicator codes are different from any reserved or common indicator codes (Implicit in web). |
042 | Error | Validate in table 3 that there is at least one result indicator defined or selected per priority and specific objective. |
043 | Error | Validate in table 3 that the common result indicators are valid for the Fund and specific objective (GoalSpecificObjectiveFundIndicator) and with CommonIndicator.useInProgramme true (Implicit in web). |
044 | Error | Validate in table 3 that programme specific indicator codes are different from any reserved or common indicator codes (Implicit in web). |
045 | Error | Validate when programme was once adopted by EC that the TA type of a TA priority has not been modified compared to the previous adopted version (Implicit in web). |
046 | Error | Validate when programme was never adopted by EC, that section 3.1 Transfers and contributions have not been set (ticked) (Implicit in web). |
047 | Error | Validate when programme was never adopted by EC, that table 15A has no amounts (is completely empty) (Implicit in web). |
048 | Error | Validate when programme was never adopted by EC, that table 16A has no instruments (Implicit in web). |
049 | Error | Validate when programme was never adopted by EC, that table 17A has no amounts (is completely empty) (Implicit in web). |
050 | Error | Validate when programme was never adopted by EC, that table 19A has no amounts (is completely empty) (Implicit in web). |
051 | Error | Validate when programme covers JTF that the table 11 (financial plan by priority) contains records for JTF allocation types Article 3 and Article 4 (Implicit in web). |
052 | Error | Validate when programme doesn’t cover JTF that the table 11 (financial plan by priority) doesn't contain records for JTF (Implicit in web). |
053 | Error | Validate when programme doesn’t cover JTF that the table 10 (financial plan by year) doesn’t contain records for JTF (Implicit in web). |
054 | Error | Validate when programme covers JTF that the table 10 (financial plan by year) contains records for JTF allocation types Article 3 and Article 4, and for Article 7 related to Article 3 and Article 7 related to Article 4 (Implicit in web). |
055 | Error | Validate that table 10 (financial plan by year) contains records for all the Funds, categories of region defined in the programme, sections 2.1.1, 2.2.1 and 2.2.2 (PriorityFundRegionCategory) (Implicit in web). |
056 | Warning | Validate that table 10 (financial plan by year) contains Union Support >0 for all the years between 2022 and “Last year”. Doesn’t apply for flexibility amounts (to be filled in only for 2026, 2027). Doesn’t apply for JTF Article 4, JTF Article 7 related to Article 4 resources and JTF Article 7 related to Article 3 resources (JTF Article 4 and JTF Article 7 related to Article 4 to be filled in only for 2021, 2022, 2023, if any under programme). |
057 | Error | Validate that table 10 (financial plan by year) doesn't contain records for Fund, category of region combinations not defined in the programme (Implicit in web). |
058 | Error | Validate in table 10 that the annual amounts have no decimals. |
059 | Error | Validate in table 11 where Article 36(4) TA was chosen in the Partnership Agreement, that the Union contribution less the flexibility amount (g), the flexibility amount (h), the national public contribution (c) and the national private contribution (d) have no decimals. |
060 | Error | Validate in table 11 where Article 36(5) TA was chosen in the Partnership Agreement, that the Union contribution without TA (b), the Union contribution for TA (c), the flexibility amount without TA (i), the flexibility amount for TA (j), the national public contribution (e) and the national private contribution (f) have no decimals. |
061 | Error | Validate that table 11 (financial plan by priority) contains records for all priority, Fund, category of region combinations defined in the Programme (PriorityFundRegionCategory) (Implicit in web). |
062 | Error | Validate that the table 11 (financial plan by priority) doesn't contain records for priority, Fund, category of region combinations not defined in the programme (PriorityFundRegionCategory) (Implicit in web). |
063 | Error | Validate the consistency of the total Union contribution (without flexibility amount) at Fund/category of region level between the financial plans in table 10 and table 11. (the only difference is the allocation under Article 7 for JTF: table 11 amount = table 10 amount – JTF 7) |
064 | Error | Validate the consistency of the total flexibility amount at Fund/category of region level between the financial plans in table 10 and table 11 (the only difference is the allocation under Article 7 for JTF: table 11 amount = table 10 amount – JTF 7) |
065 | Error | Validate for non-TA programmes that in table 12 that there is a record for all horizontal enabling conditions and their criteria, and for all thematic enabling conditions and their criteria valid for the Fund/specific objective combinations covered by the programme (EnablingConditionFundSpecificObjective) (Implicit in web). |
066 | Error | Validate in table 12 that there is no record for thematic enabling conditions and their criteria which are not valid for the Fund/specific objective combinations covered by the programme (EnablingConditionFundSpecificObjective) (Implicit in web). |
067 | Error | Validate in table 13A (if more than one record) for each body which receives payments from the Commission in case of technical assistance pursuant to Article 36(5) that the portion in percentage points is provided (not empty; it should be > 0 and ≤ 100). |
068 | Error | Validate when JTF is selected that a TJTP version is selected. |
069 | Error | Validate for version 1 that table 20 has no amounts (is completely empty) (Implicit in web). |
070 | Error | Validate for each selected TJTP version, that it is the last completed version of that TJTP (Implicit in web). |
071 | Warning | Validate for version 1 that record “Title in national language(s)” was filled in (not empty). |
072 | Error | Validate in table 3, for priorities with Union contribution > 0 in table 11, for each common result indicator under ERDF/CF/JTF when a baseline validator exists (baselineValidator), that the baseline value is compliant (zero, equal or higher than zero, higher than zero) |
073 | Error | Validate in appendix 1.A (when appendix 1 exists) that the intervention field code is one of the selected ones in table 4 under the relevant priority, specific objective, Fund, [category of region]. |
074 | Error | Validate in appendix 1.A (when appendix 1 exists) for applicable SCO records, that the sum of the estimated proportion % per priority is lower than or equal to 100. |
075 | Error | Validate in appendix 1.B that the specific objective(s) were used under a priority. |
076 | Error | Validate in appendix 1.B that there is at least one indicator for an operation type. |
077 | Error | Validate in appendix 2.A (when appendix 2 exists) that the intervention field code is one of the selected ones in table 4 under the relevant priority, [specific objective], Fund, [category of region]. |
078 | Error | Validate for non-TA programmes that the following text fields are not empty : Introductory table: CCI, Title in EN, First Year, Last year, Fund concerned 1. Programme strategy (text field + Justification summary for each SO/ESF+ dedicated priority in table 1) 2.1.1 Title of the priority for each non-TA priority in programme 2.1.1.1.1 All 6 text fields for each selected SO (The related types of actions; The main target groups; Actions safeguarding equality; inclusion and non-discrimination; Indication of the specific territories targeted; including the planned use of territorial tools; The interregional, cross-border and transnational actions ; The planned use of financial instruments) 6. Partnership (Text field) 7. Communication and visibility (Text field) |
079 | Error | Validate for TA programmes that the following text fields (and tables) are not empty: Introductory table: CCI, Title in EN, First Year, Last year. 1. Programme strategy (Text field only (the table 1 is not applicable/should not be editable for TA) 2.2.1 Only for each Art. 36(4) TA priority (if exists in programme): 2.2.1.1 Both text fields (The related types of actions; The main target groups) 2.2.2 Only for each Art. 37 TA priority (if exists in the programme) – 2.2.2.1 Description text field 6. Partnership (Text field) 7. Communication and visibility (Text field) |
080 | Error | Validate that TA Programmes have no data in Sections: Table 1 in section 1. Programme strategy Whole section 2.1 Priorities other than the technical assistance Whole section 4 on enabling conditions (not to be editable under TA programmes) Record “Where applicable, body or bodies which receive payments from the Commission in case of TA pursuant to Article 36(5)” in table 13 – not possible to add or delete for 36(4) TA programme Table 12 Enabling conditions. |
081 | Error | Validate in table 10 for each category of region covered by the programme, that the total Union contribution across all IJG programmes (containing the given category of region) does not exceed the financial allocations per country and per this category of region as communicated to the MS after applying all (1) the contributions and transfers at PA level (first adopted version) (table 2B, 3B, 4B, 5B, 7), (2) all the contributions and transfers (done at programme amendment level, regardless of the categories of regions included) in all programmes for the MS in tables 15B, 16B, 17B, 19A and 19B (mid-term review) and 20B and the transfers of ERDF/ESF+ to JTF in table 18 B and 18D in all programmes for the MS (regardless of the categories of regions included). |
082 | Error | Validate in table 10 for each Fund covered by the programme, that the total Union contribution across all IGJ programmes (containing the given Fund) does not exceed the financial allocations per country and per this Fund as communicated to the MS after applying (1) all the contributions and transfers at PA level (first adopted version) (table 2B, 4B, 5B, 7), (2) all the contributions and transfers at programme amendment level (all programmes for MS - regardless of the Funds included - in tables 15B, 16B, 17B and 20B) and (3) the transfers of ERDF/ESF+ to JTF in table 18 B and 18D at programme level (in all programmes - regardless of the Funds included - for MS). |
083 | Error | Validate that each Fund covered by the programme (based on the Fund flags in the general version info) is used by at least one priority (PriorityFundRegionCategory). |
084 | Error | Validate that PartnershipAgreementVersion.art364Ta equals ProgrammeVersionIjg.art364Ta and that PartnershipAgreementVersion.art365Ta equals ProgrammeVersionIjg.art365Ta |
085 | Error | Validate that in tables 4, 5, 6, 7 (ESF+ only) and 8, for priorities with Union contribution > 0 in table 11, at least one record exists. |
086 | Error | Validate for non-TA priorities in section 2.1.1.1.3, that the total amount (EUR) per priority, specific objective, Fund, [category of region] is the same in all dimensions tables 4, 5, 6 and 8. |
087 | Warning | Validate in Table 10 when non-JTF that the flexibility amount per year, Fund and category of region equals the amount without flexibility in both 2026 and 2027 with an accepted deviation of +/-1 EUR. |
088 | Warning | Validate in Table 10 when JTF Article 3 or JTF Article 7 related to Article 3,that the flexibility amount per year equals the amount without flexibility in both 2026 and 2027 with an accepted deviation of +/-1 EUR. |
089 | Error | Validate when Appendix 1 exists that all applicable SCO records of part A summary, except for Material Deprivation (ESO4.13), have an intervention field code and that this intervention code is selected in table 4 of the programme. |
090 | Error | Validate when Appendix 2 exists that all applicable SCO records of part A summary, except for Material Deprivation (ESO4.13), have an intervention field code and that this intervention code is selected in table 4 of the programme. |
091 | Error | Validate in table 13 for each “Body which receives payments from the Commission in case of TA pursuant to Article 36(5)” that all three mandatory fields “name of institution”, “contact name” and “email” are filled in (not empty) (Implicit in web). |
095 | Error | Validate in Table 3 and for Specific Objectives = ESO.4.13, that there is at least one Result Indicator defined or selected with a baseline/reference value |
096 | Error | Validate for non-TA Priorities that all Funds defined in PriorityFundRegionCategory also exist in NonTaPriorityFundSpecificObjectiveIjg |
097 | Error | Validate for non-TA Priorities that all Funds defined in NonTaPriorityFundSpecificObjectiveIjg also exist in PriorityFundRegionCategory |
098 | Error | Validate when in table 14 ‘unit cost’ was chosen, that appendix 1 has at least 1 operation type. |
099 | Error | Validate when in table 14 ‘financing not linked to costs’ was chosen, that appendix 2 has at least 1 operation type. |
100 | Error | Validate that specific objectives of dedicated priority types ICT (RSO1.5) and UM (RSO2.8) are only used under a dedicate priority of that type. |
101 | Error | Validate that dedicated priorities only cover specific objectives valid for their dedicated priority type (Combinations available in SpecificObjectiveFund) (Implicit in web). |
102 | Warning | Validate when this programme has never been adopted and exists in table 9A/9B of the last Partnership Agreement sent to the Commission that in table 11 of this programme the total national contribution per Fund and category of region is equal to the equivalent total in table 9A/9B of that Partnership Agreement version. |
103 | Warning | For ESF+ specific objectives (a)-(l) (ESO4.1-ESO4.12), validate that the reference value is positive for each result indicator with a quantitative target. |
104 | Warning | In table 3, for ESF+ specific objective (m) (ESO4.13), validate that the reference value is positive for each quantitative result indicator. |
105 | Error | Validate that the total allocation (without flexibility) for each type of resources under JTF (except for the allocation under Article 7 JTF) in section 3.5 table 10 equals the equivalent union contribution per JTF and type of resources in section 3.6 table 11. |
106 | Error | Validate that the total flexibility amount for each type of resources under JTF (except for the allocation under Article 7 JTF) in section 3.5 table 10 equals the equivalent flexibility amount per JTF and type of resources in section 3.6 table 11. |
107 | Error | Validate in table 13A (if more than 1 record) that the sum of all percentage points (across all records) is equal to 100. |
108 | Error | Validate for non-TA programmes with intended use of Article 94 in section 8 (ticked “yes” in table 14) that the Member State filled in all mandatory fields in Appendix 1. |
109 | Warning | Validate for non-TA programmes with intended use of Article 95 in section 8 (ticked “yes” in table 14) that the Member State filled in all mandatory fields in Appendix 2. |
110 | Error | Validate in table 14 for TA programmes that the managing authority ticked “no” for intended use of Article 94. |
111 | Error | Validate in table 14 for TA programmes without any TA priority pursuant to Art. 37 that the managing authority ticked “no” for intended use of Article 95. |
112 | Error | Validate in table 14 for programmes with TA priority(ies) pursuant to Art. 37 that the managing authority ticked “yes” for intended use of Article 95. |
113 | Error | Validate for programmes with Art. 37 TA with mandatory ticked “yes” on Article 95 in table 14 that the Member State filled in all mandatory fields in Appendix 2 for Art. 37 TA (the SO column is not obligatory in this case). |
114 | Error | Validate for non-TA ERDF, CF, ESF+ programmes that Appendix 3 is filled in. |
115 | Error | Validate when ‘for outermost regions only’ is selected that the country of the programme has outermost regions and that the region coverage contains only outermost regions’ NUTS codes. |
116 | Error | Validate when programme was once adopted that “Approved by monitoring committee” was selected when “Non-substantial transfer (Article 24(5) CPR)” and “Clerical or editorial corrections (Article 24(6) CPR)” have not been selected, or when “Non-substantial transfer (Article 24(5) CPR)” was selected. Exclude programmes containing only material deprivation dedicated priorities (Technical assistance priorities excluded). |
117 | Error | Validate when programme was once adopted that “Non-substantial transfer (Article 24(5) CPR)” and “Clerical or editorial corrections (Article 24(6) CPR)” are not both selected. |
118 | Error | Validate in table 2 for TA priorities financed by ERDF/CF/JTF/ESF+ that there is at least one output indicator defined or selected per priority. |
119 | Warning | Validate in section 2.1.1.1.2 table 2 for non-TA priorities financed by ERDF/CF/JTF that there is at least one common output indicator selected per priority and specific objective. |
120 | Error | Validate in section 2.1.1.1.2 and section 2.2.1.2 table 2 for non-TA and TA priorities financed by ERDF/CF/JTF/ESF+ and with Union contribution > 0 in table 11, for each output indicator that the target is higher than zero and at least equal to the milestone. |
121 | Error | Validate in table 2 for each output indicator under non-TA and TA priorities financed by ERDF/CF/JTF/ESF+ (sections 2.1.1.1.2, 2.2.1.2) that the milestone was filled in for all indicators which have a target. |
122 | Error | Validate in table 2 for each output indicator under non-TA and TA priorities financed by ERDF/CF/JTF (sections 2.1.1.1.2, 2.2.1.2 – if any) that the target was filled in. |
123 | Warning | Validate in table 3 that there is (at least) one common result indicator selected per priority and specific objective for all Funds except ESF+. |
124 | Error | Validate in table 3 for non-TA priorities with Union contribution > 0 in table 11, for each common result indicator that the target is higher than zero, except for ESF+ SO (m). |
126 | Warning | Validate in table 3 for each result indicator with a target for all Funds that the baseline or reference value is provided (can be also 0). |
128 | Error | Validate in table 3 that source of data is provided for each result indicator for all Funds. |
129 | Error | Validate in table 11, for each category of region under ERDF priority in each MS/programme using TA according to Art. 36(5) as chosen in PA, except: • programmes in CY, DK, IE, LU, MT, AT (having derogations from standard % in accordance with Art. 36(5)(b)(v)), and • programmes in ES, FR, PT that concern only outermost regions (having derogations from standard % in accordance with Art. 36(5)(b)(vii)) (i.e., this rule is valid only for ES, FR, PT programmes with unticked corresponding box in introductory table), that the “Union contribution for TA pursuant to Article 36(5)” divided by the “Union contribution without TA pursuant to Article 36(5)”, i.e., I/(b), is 3,5% (between 3,45% and max. 3,5%). |
130 | Error | Validate in table 11, for each category of region under ESF+ priority in each MS/programme using TA according to Art. 36(5) as chosen in PA, except: • programmes in CY, DK, IE, LU, MT, AT (having derogations from standard % in accordance with Art. 36(5)(b)(v)), • programmes in ES, FR, PT that concern only outermost regions (having derogations from standard % in accordance with Art. 36(5)(b)(vii)) (i.e., this rule is valid only for ES, FR, PT programmes with unticked corresponding box in introductory table), and • programmes dedicated to addressing material deprivation (i.e., that include only such dedicated priorities with ticked corresponding box - ESF+ specific objective (m) - in section 2.1.1 of the programme) having derogations from % in accordance with Art. 36(5)(b)(iii), that the “Union contribution for TA pursuant to Article 36(5)” divided by the “Union contribution without TA pursuant to Article 36(5)”, i.e., (c)/(b), is 4% (between 3.95% and max. 4%). |
131 | Error | Validate in table 11, for each category of region under ESF+ priority in each programme dedicated to addressing material deprivation (i.e. that includes only such dedicated priorities with ticked corresponding box - ESF+ specific objective (m) - in section 2.1.1 of the programme) and using TA according to Art. 36(5) as chosen in PA, except: • programmes in CY, DK, IE, LU, MT, AT (having derogations from standard % in accordance with Art. 36(5)(b)(v)), and • programmes in ES, FR, PT that concern only outermost regions (having derogations from standard % in accordance with Art. 36(5)(b)(vii) (i.e., this rule is valid only for ES, FR, PT programmes with unticked corresponding box in introductory table), that the “Union contribution for TA pursuant to Article 36(5)” divided by the “Union contribution without TA pursuant to Article 36(5)”, i.e., (c)/(b), is 5% (between 4.95% and max. 5%). |
132 | Error | Validate in table 11, for each type of resources under JTF priority in each MS/programme using TA according to Art. 36(5) as chosen in PA, except: • programmes in ES, FR, PT that concern only outermost regions (having derogations from standard % in accordance with Art. 36(5)(b)(vii)) (i.e., this rule is valid only for ES, FR, PT programmes with unticked corresponding box in introductory table), that the “Union contribution for TA pursuant to Article 36(5)” divided by the “Union contribution without TA pursuant to Article 36(5)”, i.e., (c)/(b), is 4% (between 3.95% and max. 4%). |
133 | Error | Validate in table 11, for each CF priority in each MS/programme using TA according to Art. 36(5) as chosen in PA, except: • programmes in CY, MT (having derogations from standard % in accordance with Art. 36(5)(b)(v)), and • programmes in PT that concern only outermost regions (having derogations from standard % in accordance with Art. 36(5)(b)(vii)) (i.e. this rule is valid only for PT programmes with unticked corresponding box in introductory table), that the “Union contribution for TA pursuant to Article 36(5)” divided by the “Union contribution without TA pursuant to Article 36(5)”, i.e., I/(b), is 2.5% (between 2,45% and max. 2,5%). |
134 | Error | Validate in table 11, for each category of region under ERDF/ESF+ priority in each programme in CY, DK, IE, LU, MT, AT if these Member States have chosen TA according to Art. 36(5) in their PA, that the “Union contribution for TA pursuant to Article 36(5)” divided by the “Union contribution without TA pursuant to Article 36(5)”, i.e., I/(b), is 6% (between 5,95% and max. 6%). |
135 | Error | Validate in table 11, for each CF priority in each programme in CY and MT, if these Member States have chosen TA according to Art. 36(5) in their PA, that the “Union contribution for TA pursuant to Article 36(5)” divided by the “Union contribution without TA pursuant to Article 36(5)”, i.e., I/(b), is 6% (between 5,95% and max. 6%). |
136 | Error | Validate in table 11, for each category of region under ERDF priority in each ES, FR, PT programme that concerns only outermost regions (i.e., only for ES, FR, PT programmes with ticked corresponding box in introductory table), if these Member States have chosen using TA according to Art. 36(5) in PA, that the “Union contribution for TA pursuant to Article 36(5)” divided by the “Union contribution without TA pursuant to Article 36(5)”, i.e., I/(b), is 4,5% (between 4,45% and max. 4,5%) (i.e. + 1 pp to standard %). |
137 | Error | Validate in table 11, for each category of region under ESF+ priority in each ES, FR, PT programme that concerns only outermost regions (i.e., only for ES, FR, PT programmes with ticked corresponding box in introductory table), if these Member States have chosen using TA according to Art. 36(5) in PA, except: • programmes dedicated to addressing material deprivation (i.e., that include only such dedicated priorities with ticked corresponding box – ESF+ specific objective (m) – in section 2.1.1 of the programme) having derogations from % in accordance with Art. 36(5)(b)(iii), that the “Union contribution for TA pursuant to Article 36(5)” divided by the “Union contribution without TA pursuant to Article 36(5)”, i.e. I/(b), is 5% (between 4.95% and max. 5%) (i.e. + 1 pp to standard %). |
138 | Error | Validate in table 11, for each category of region under ESF+ priority in each ES, FR, PT programme that concerns only outermost regions (i.e., only for ES, FR, PT programmes with ticked corresponding box in introductory table) and is dedicated to addressing material deprivation (i.e. includes only such dedicated priorities with ticked corresponding box – ESF+ specific objective (m) – in section 2.1.1 of the programme), if these Member States have chosen using TA according to Art. 36(5) in PA, that the “Union contribution for TA pursuant to Article 36(5)” divided by the “Union contribution without TA pursuant to Article 36(5)”, i.e. I/(b), is 6% (between 5,95% and max. 6%) (i.e. + 1 pp to standard %). |
139 | Error | Validate in table 11, for each CF priority (if any) in each PT programme that concerns only outermost regions (i.e., with ticked corresponding box in introductory table), when PT has chosen using TA according to Art. 36(5) in PA, that the “Union contribution for TA pursuant to Article 36(5)” divided by the “Union contribution without TA pursuant to Article 36(5)”, i.e., I/(b), is 3.5% (between 3,45% and max. 3,5%) (i.e. + 1 pp to standard %). |
140 | Error | Validate in table 11, for each type of resources under JTF priority (if any) in each ES, FR, PT programme, that concerns only outermost regions (i.e., only for ES, FR, PT programmes with ticked corresponding box in introductory table), when these Member States have chosen using TA according to Art. 36(5) in PA: that the “Union contribution for TA pursuant to Article 36(5)” divided by the “Union contribution without TA pursuant to Article 36(5)”, i.e., I/(b), is 5% (between 4,95% and max. 5%) (i.e. + 1 pp to standard %). |
141 | Error | Validate in table 11, for each ES, FR, PT programme that concerns only the outermost regions (with ticked corresponding box in the introductory table), when these Member States/programmes have chosen using TA according to Art. 36(4) in PA and when the Fund is relevant for the MS: that the Union contribution of ERDF/CF for TA pursuant to Article 36(4) does not exceed the respective % [4.5, 3.5%] * total ERDF/CF allocation in that programme. |
142 | Warning | Validate in table 11, for each ES, FR, PT programme that concerns only the outermost regions (with ticked corresponding box in the introductory table), when these Member States/programmes have chosen using TA according to Art. 36(4) in PA: • Except ESF+ programmes dedicated to addressing material deprivation (i.e., including only such dedicated priorities with ticked corresponding box – ESF+ specific objective (m) – in section 2.1.1 of the programme) having derogations from % in accordance with Art. 36(4)(b)(iii),
that the Union contribution of ESF+ for TA pursuant to Article 36(4) does not exceed 5% * total ESF+ allocation in that programme. |
143 | Error | Validate in table 11, for each ES, FR, PT ESF+ programme that concerns only the outermost regions (with ticked corresponding box in the introductory table) and is dedicated to addressing material deprivation (i.e. includes only such dedicated priorities with ticked corresponding box – ESF+ specific objective (m) – in section 2.1.1 of the programme; having derogations from % in accordance with Art. 36(4)(b)(iii)), when these Member States/programmes have chosen using TA according to Art. 36(4) in PA, that the Union contribution of ESF+ for TA pursuant to Article 36(4) does not exceed 6% * total ESF+ allocation in that programme. |
144 | Error | Validate in table 11, for each ES, FR, PT programme that concerns only the outermost regions (with ticked corresponding box in the introductory table), when these Member States/programmes have chosen using TA according to Art. 36(4) in PA and when the Fund is relevant for the programme, that the Union contribution of JTF for TA pursuant to Article 36(4) does not exceed the 5% * total JTF allocation in that programme. |
145 | Error | Validate in table 11, for each ESF+ programme that is dedicated to addressing material deprivation (i.e. includes only such dedicated priorities with ticked corresponding box – ESF+ specific objective (m) – in section 2.1.1 of the programme; having derogations from % in accordance with Art. 36(4)(b)(iii)), when these Member States/programmes have chosen using TA according to Art. 36(4) in PA, except: • ES, FR, PT ESF+ programmes that concern only the outermost regions (with ticked corresponding box in the introductory table), if any, that the Union contribution of ESF+ for TA pursuant to Article 36(4) does not exceed 5% * total ESF+ allocation in that programme (i.e. after application of all contributions and transfers, if any). |
146 | Error | Validate in table 11, for ESF+ priorities dedicated to support to the most deprived persons (with at least one ticked of two respective boxes under 2.1.1) and not dedicated to RESTORE that the co-financing rate is 90% (between 89,99% and max. 90%). in accordance with Article 10 of ESF+ Regulation. |
147 | Error | Validate in table 11, for ESF+ priorities dedicated to social innovative actions (with ticked respective box under 2.1.1) and not dedicated to STEP, that the co-financing rate is maximum 95% in accordance with Article 14 of ESF+ Regulation. |
148 | Warning | Validate in table 11, for ESF+ priorities dedicated to social innovative actions (with ticked respective box under 2.1.1) and not dedicated to STEP/RESTORE, that the sum of ESF+ Union contribution corresponding to priorities with 95% co-financing (between 94.95% and max. 95%) in accordance with Article 14 of ESF+ Regulation is not higher than 5 % of the total ESF+ Union contribution as communicated to the MS. |
149 | Error | Validate in table 11, for CF priorities that are NOT (entirely) delivered through community-led local development (i.e. CLLD codes from table 3, Annex I CPR {09, 10, 11, 12,13,14,15,16} are not solely used for that priority in table 6 of programme) and not dedicated to STEP/RESTORE, that the co-financing rate is maximum 85%. |
150 | Error | Validate in table 11, for CF priorities that are entirely (100%) delivered through community-led local development (i.e., only the CLLD codes {09,10,11,12,13,14,15,16} are used under that priority in table 6) and not dedicated to STEP/RESTORE, that the co-financing rate is maximum 95% (i.e. + 10 pp to standard rate). |
151 | Error | Validate in table 11, for less developed regions under the ERDF and ESF+ priorities (except ESF+ dedicated priorities to the most deprived and social innovative actions, i.e., this rule valid only for priorities with the unticked all 3 boxes in Section 2.1.1 on dedicated priorities to support to the most deprived persons (2) and to social innovative actions (1)), that are NOT (entirely) delivered through community-led local development (i.e. CLLD codes {09, 10, 11, 12,13,14,15,16} are not solely used for that priority in table 6) and not dedicated to STEP/RESTORE, that the co-financing rate is maximum 85%. |
152 | Error | Validate in table 11, for less developed regions under the ERDF and ESF+ priorities, that are entirely (100%) delivered through community-led local development (i.e. only the CLLD codes {09, 10, 11, 12,13,14,15,16} are used under that priority in table 6) and not dedicated to STEP/RESTORE, that the co-financing rate is maximum 95% (i.e. + 10 pp to standard rate). |
153 | Error | Validate in table 11, for transition regions under ERDF and ESF+ priorities (except ESF+ dedicated priorities to the most deprived and social innovative actions, i.e., this rule valid only for priorities with unticked all 3 boxes in Section 2.1.1 on dedicated priorities to support to the most deprived persons (2) and to social innovative actions (1)) that are NOT (entirely) delivered through community-led local development (i.e., CLLD codes {09,10,11,12,13,14,15,16} are not solely used for that priority in table 6) and not dedicated to STEP/RESTORE, in programmes that do not include any of: a) 7 specific transition regions (BG41, CZ02, CZ03, CZ06, EE00, PL41, PL51) having derogations from standard rates in accordance with Art. 112(3)(b); and b) 2 outermost transition regions (ES70, FRY2) having derogations from standard rates in accordance with Art. 112(3), that the co-financing rate is maximum 60%. |
154 | Error | Validate in table 11, for transition regions under ERDF and ESF+ priorities (except ESF+ dedicated priorities to the most deprived and social innovative actions, i.e., this rule valid only for priorities with unticked all 3 boxes in Section 2.1.1 on dedicated priorities to support to the most deprived persons (2) and to social innovative actions (1)) that are entirely (100%) delivered through community-led local development (i.e. only the CLLD codes {09, 10, 11, 12,13,14,15,16} are used under that priority in table 6) and not dedicated to STEP/RESTORE, in programmes that do not include any of: a) 7 specific transition regions (BG41, CZ02, CZ03, CZ06, EE00, PL41, PL51) having derogations from standard rates in accordance with Art. 112(3)(b); and b) 2 outermost transition regions (ES70, FR42) having derogations from standard rates in accordance with Art. 112(3), that the co-financing rate is maximum 70% (i.e. + 10 pp to standard rate). |
155 | Error | Validate in table 11, for more developed regions under ERDF and ESF+ priorities (except ESF+ dedicated priorities to the most deprived and social innovative actions, i.e., this rule valid only for priorities with unticked all 3 boxes in Section 2.1.1 on dedicated priorities to support to the most deprived persons (2) and to social innovative actions (1)) that are NOT (entirely) delivered through community-led local development (i.e. CLLD codes {09,10,11,12,13,14,15,16} are not solely used for that priority in table 6) and not dedicated to STEP/RESTORE, in programmes that do not include any of 5 specific more developed regions (DEA3, DEB1, DED5, LT01, PL91) having derogations from standard rates in accordance with Art. 112(3)(d), that the co-financing rate is maximum 40%. |
156 | Error | Validate in table 11, for more developed regions under ERDF and ESF+ priorities (except ESF+ dedicated priorities to the most deprived and social innovative actions, i.e., this rule valid only for priorities with unticked all 3 boxes in Section 2.1.1 on dedicated priorities to support to the most deprived persons (2) and to social innovative actions (1)) that are entirely (100%) delivered through community-led local development (i.e. only the CLLD codes {09, 10, 11, 12,13,14,15,16} are used under that priority in table 6) and not dedicated to STEP/RESTORE, in programmes that do not include any of 5 specific more developed regions (DEA3, DEB1, DED5, LT01, PL91) having derogations from standard rates in accordance with Art. 112(3)(d), that the co-financing rate is maximum 50% (i.e. + 10 pp to standard rate). |
157 | Error | Validate in table 11, for JTF priorities that are NOT (entirely) delivered through community-led local development (i.e. CLLD codes {09,10,11,12,13,14,15,16} are not solely used for that priority in table 6) and not dedicated to STEP, that the co-financing rate for JTF total is maximum 85%. |
158 | Error | Validate in table 11, for JTF priorities that are entirely (100%) delivered through community-led local development (i.e. only the CLLD codes {09, 10, 11, 12,13,14,15,16} are used under that priority in table 6) and not dedicated to STEP, that the co-financing rate for JTF total is maximum 95%. |
159 | Warning | Validate in table 11, for more developed regions under the ERDF, ESF+ priorities (except ESF+ dedicated priorities to the most deprived and social innovative actions; i.e., this rule valid only for priorities with unticked all 3 boxes in Section 2.1.1 on dedicated priorities to support to the most deprived persons (2) and to social innovative actions (1)) that are NOT (entirely) delivered through community-led local development (i.e. CLLD codes from table 3, Annex I CPR {09,10,11,12,13,14,15,16} are not solely used for that priority in table 6 of programme) and not dedicated to STEP/RESTORE, in DE programmes including any of 3 specific more developed regions (DEA3, DEB1, DED5 - having derogations from standard rate in accordance with Art. 112(3)(d)) and any other more developed region (DE11, DE12, DE13, DE14, DE21, DE22, DE23, DE24, DE25, DE26, DE27, DE30, DE50, DE60, DE71, DE72, DE73, DE91, DE92, DE94, DEA1, DEA2, DEA4, DEA5, DEB3, DEC0, DEF0 - having standard rate in accordance with Art. 112(3)(e)), that the co-financing rate is maximum 40%. |
160 | Warning | Validate in table 11, for more developed regions under the ERDF, ESF+ priorities (except ESF+ dedicated priorities to the most deprived and social innovative actions; i.e., this rule valid only for priorities with unticked all 3 boxes in Section 2.1.1 on dedicated priorities to support to the most deprived persons (2) and to social innovative actions (1)) that are entirely (100%) delivered through community-led local development (i.e. only the CLLD codes {09, 10, 11, 12,13,14,15,16} are used under that priority in table 6) and not dedicated to STEP/RESTORE, in DE programmes including any of 3 specific more developed regions (DEA3, DEB1, DED5 - having derogations from standard rates in accordance with Art. 112(3)(d)) and any other more developed region (DE11, DE12, DE13, DE14, DE21, DE22, DE23, DE24, DE25, DE26, DE27, DE30, DE50, DE60, DE71, DE72, DE73, DE91, DE92, DE94, DEA1, DEA2, DEA4, DEA5, DEB3, DEC0, DEF0 - having standard rate in accordance with Art. 112(3)(e)), that the co-financing rate is maximum 50% (+10 p.p. to standard rate for more developed region). |
161 | Error | Validate in table 11, for transition regions under the ERDF, ESF+ priorities (except ESF+ dedicated priorities to the most deprived and social innovative actions; i.e., this rule valid only for priorities with unticked all 3 boxes in Section 2.1.1 on dedicated priorities to support to the most deprived persons (2) and to social innovative actions (1)) that are NOT (entirely) delivered through community-led local development (i.e. CLLD codes {09,10,11,12,13,14,15,16} are not solely used for that priority in table 6) and not dedicated to STEP/RESTORE, in programmes including any of 7 specific transition regions (BG41, CZ02, CZ03, CZ06, EE00, PL41, PL51) having derogations from standard rates in accordance with Art. 112(3)(b), that the co-financing rate is maximum 70%. |
162 | Error | Validate in table 11, for transition regions under the ERDF, ESF+ priorities (except ESF+ dedicated priorities to the most deprived and social innovative actions) that are entirely (100%) delivered through community-led local development (i.e. only the CLLD codes {09, 10, 11, 12,13,14,15,16} are used under that priority in table 6) and not dedicated to STEP/RESTORE, in programmes including any of 7 specific transition regions (BG41, CZ02, CZ03, CZ06, EE00, PL41, PL51) having derogations from standard rates in accordance with Art. 112(3)(b), that the co-financing rate is maximum 80% (+10 p.p. to standard rate for specific transition regions). |
163 | Error | Validate in table 11, for more developed regions under the ERDF, ESF+ priorities (except ESF+ dedicated priorities to the most deprived and social innovative actions; i.e., this rule valid only for priorities with unticked all 3 boxes in Section 2.1.1 on dedicated priorities to support to the most deprived persons (2) and to social innovative actions (1)) that are NOT (entirely) delivered through community-led local development (i.e. CLLD codes {09,10,11,12,13,14,15,16} are not solely used for that priority in table 6) and not dedicated to STEP/RESTORE, in programmes including any of 5 specific more developed regions (DEA3, DEB1, DED5, LT01, PL91) having derogations from standard rates in accordance with Art. 112(3)(d), that the co-financing rate is maximum 50%. |
164 | Error | Validate in table 11, for more developed regions under the ERDF, ESF+ priorities (except ESF+ dedicated priorities to the most deprived and social innovative actions; i.e., this rule valid only for priorities with unticked all 3 boxes in Section 2.1.1 on dedicated priorities to support to the most deprived persons (2) and to social innovative actions (1)) that are entirely (100%) delivered through community-led local development (i.e. only the CLLD codes {09, 10, 11, 12,13,14,15,16} are used under that priority in table 6) and not dedicated to STEP/RESTORE, in programmes including any of 5 specific more developed regions (DEA3, DEB1, DED5, LT01, PL91) having derogations from standard rates in accordance with Art. 112(3)(d), that the co-financing rate is maximum 60% (+10 p.p. to standard rate for specific more developed regions). |
166 | Error | Validate for all programmes in all MS (except ES, FR, PT) that the box in the last row of introductory table (Programme under IJG Goal for the outermost regions only) is unticked (not editable). (implicit in web) |
167 | Warning | Validate in table 11 for transition regions under the ERDF, ESF+ priorities (except ESF+ dedicated priorities to the most deprived and social innovative actions; i.e., this rule valid only for priorities with unticked all 3 boxes in Section 2.1.1 on dedicated priorities to support to the most deprived persons (2) and to social innovative actions (1)) that are NOT (entirely) delivered through community-led local development (i.e. CLLD codes from table 3, Annex I CPR {09,10,11,12,13,14,15,16} are not solely used for that priority in table 6 of programme) and not dedicated to STEP/RESTORE, in ES, FR programmes including any of 2 transition outermost regions (ES70 or FRY2 – having derogations from standard rate) and any other ES or FR transition region (ES11, ES12, ES13, ES23, ES41, ES52, ES53, ES62, FRL0, FRM0 – having standard rate), that the co-financing rate is maximum 60%. |
168 | Warning | Validate in table 11 for transition regions under the ERDF, ESF+ priorities (except ESF+ dedicated priorities to the most deprived and social innovative actions; i.e., this rule valid only for priorities with unticked all 3 boxes in Section 2.1.1 on dedicated priorities to support to the most deprived persons (2) and to social innovative actions (1)) that are entirely (100%) delivered through community-led local development (i.e. only the CLLD codes {09, 10, 11, 12,13,14,15,16} are used under that priority in table 6) and not dedicated to STEP/RESTORE, in ES, FR programmes including any of 2 transition outermost regions (ES70 or FRY2 – having derogations from standard rate) and any other ES or FR transition region (ES11, ES12, ES13, ES23, ES41, ES52, ES53, ES62, FRL0, FRM0 – having standard rate), that the co-financing rate is maximum 70% (+10 p.p. to standard rate for transition region). |
169 | Error | Validate in table 11 for transition regions under the ERDF, ESF+ priorities (except ESF+ dedicated priorities to the most deprived and social innovative actions; i.e., this rule valid only for priorities with unticked all 3 boxes in Section 2.1.1 on dedicated priorities to support to the most deprived persons (2) and to social innovative actions (1)) that are NOT (entirely) delivered through community-led local development (i.e. CLLD codes {09,10,11,12,13,14,15,16} are not solely used for that priority in table 6) and not dedicated to STEP/RESTORE, in ES, FR programmes including any of 2 transition outermost regions (ES70 or FRY2 – having derogations from standard rate), that the co-financing rate is maximum 85%. |
170 | Error | Validate in table 11 for transition regions under the ERDF, ESF+ priorities that are entirely (100%) delivered through community-led local development (i.e. only the CLLD codes {09, 10, 11, 12,13,14,15,16} are used under that priority in table 6) and not dedicated to STEP/RESTORE, in ES, FR programmes including any of 2 transition outermost regions (ES70 or FRY2 – having derogations from standard rate), that the co-financing rate is maximum 95% (+10 p.p. to standard rate for outermost region). |
171 | Error | For Finish programmes including northern sparsely populated region (FI1D), validate in table 11 for northern sparsely populated region under the ERDF, ESF+ priorities (except ESF+ dedicated priorities to the most deprived and social innovative actions; i.e., this rule valid only for priorities with unticked all 3 boxes in Section 2.1.1 on dedicated priorities to support to the most deprived persons (2) and to social innovative actions (1)) that are NOT (entirely) delivered through community-led local development (i.e. CLLD codes {09,10,11,12,13,14,15,16} are not solely used for that priority in table 6) and not dedicated to STEP/RESTORE, that the co-financing rate is maximum 60%. |
172 | Error | For Finish programmes including northern sparsely populated region (FI1D), validate in table 11 for northern sparsely populated region under the ERDF, ESF+ priorities (except ESF+ dedicated priorities to the most deprived and social innovative actions; i.e., this rule valid only for priorities with unticked all 3 boxes in Section 2.1.1 on dedicated priorities to support to the most deprived persons (2) and to social innovative actions (1)) that are entirely (100%) delivered through community-led local development (i.e. only the CLLD codes {09, 10, 11, 12,13,14,15,16} are used under that priority in table 6) and not dedicated to STEP/RESTORE, that the co-financing rate is maximum 70%. |
173 | Error | For Swedish programmes including any of 2 northern sparsely populated regions (SE32, SE33), validate in table 11 for northern sparsely populated regions under the ERDF, ESF+ priorities (except ESF+ dedicated priorities to the most deprived and social innovative actions; i.e., this rule valid only for priorities with unticked all 3 boxes in Section 2.1.1 on dedicated priorities to support to the most deprived persons (2) and to social innovative actions (1)) that are NOT (entirely) delivered through community-led local development (i.e. CLLD codes {09,10,11,12,13,14,15,16} are not solely used for that priority in table 6) and not dedicated to STEP/RESTORE, that the co-financing rate is maximum 40%. |
174 | Error | For Swedish programmes including any of 2 northern sparsely populated regions (SE32, SE33), validate in table 11 for northern sparsely populated regions under the ERDF, ESF+ priorities (except ESF+ dedicated priorities to the most deprived and social innovative actions; i.e., this rule valid only for priorities with unticked all 3 boxes in Section 2.1.1 on dedicated priorities to support to the most deprived persons (2) and to social innovative actions (1)) that are entirely (100%) delivered through community-led local development (i.e. only the CLLD codes {09, 10, 11, 12,13,14,15,16} are used under that priority in table 6), and not dedicated to STEP/RESTORE, that the co-financing rate is maximum 50%. |
175 | Error | Validate that the total of the ERDF and ESF+ transfers to the JTF priority based on table 18A and 18C (whenever selected) does not exceed three times the amount of support from the JTF to that priority (MFF resources) prior to transfers based on table 18. |
176 | Error | Validate when one of the transfer to JTF flags are set, that the cumulative ERDF and the cumulative ESF+ transfers per Fund in all programmes of the MS based on table 18A and 18C (whenever selected) does not exceed 15% of the respective initial ERDF and ESF+ allocation to the Member State. |
178 | Error | Validate in case of additional transfers to the JTF (ProgrammeVersionIjg.internalTransferToJtf is true or ProgrammeVersionIjg.externalTransferToJtf is true), that the field ‘justification for the complementary transfer from ERDF and ESF+ based on the planned types of intervention’ is filled in. |
179 | Error | Validate in table 12 that “the reference to relevant documents” is provided for each criterion considered as fulfilled by Member State. |
180 | Error | Validate in table 12 that the “justification” is provided for each criterion considered as fulfilled by Member State. |
181 | Error | Validate in appendix 1.A (when appendix 1 exists) that the selected common indicator field code is one of the selected ones in tables 2 and 3 under the relevant priority, specific objective, fund, [category of region]. |
182 | Error | Validate in appendix 2.A (when appendix 2 exists) that the selected common indicator field code is one of the selected ones in tables 2 and 3 under the relevant priority, specific objective, fund, [category of region]. |
183 | Error | Validate when the first transfer box ‘Concerns internal transfer within the programme with JTF allocations’ is chosen under section 3.2.2 ‘Transfers to the JTF as complementary support’, that table 18A is filled in (at least one record with a value for the fields ‘Fund’, ‘category of region’, ‘JTF priority’ and for at least one of the years). |
184 | Error | Validate when the second transfer box ‘Concerns transfers from other programmes to the programme with JTF allocation’ is chosen under section 3.2.2 ‘Transfers to the JTF as complementary support’, that table 18C is filled in (at least one record with a value for the fields ‘Fund’, ‘category of region’, ‘JTF priority’ and for at least for one of the years). |
185 | Warning | Validate for each selected TJTP version, that it is the last version of that TJTP. |
186 | Error | Validate in appendix 2.B that the specific objective(s) were used under a priority. |
188 | Error | Validate in section 3.1 when programme amendment does not relate to contributions to InvestEU, that table 15A is empty. |
190 | Error | Validate in section 3.1 when programme amendment does not relate to transfers to instruments under direct or indirect management, that table 16A is empty. |
192 | Error | Validate in section 3.1 when programme amendment does not relate to transfers between ERDF, ESF+, Cohesion Fund or to another Fund or Funds, that table 17A is empty. |
193 | Error | Validate when the first transfer box ‘Concerns internal transfer within the programme with JTF allocations’ is not chosen under section 3.2.2 ‘Transfers to the JTF as complementary support’, that table 18A is empty. |
194 | Error | Validate when the second transfer box ‘Concerns transfers from other programmes to the programme with JTF allocation’ is not chosen under section 3.2.2 ‘Transfers to the JTF as complementary support’, that table 18C is empty. |
195 | Error | Validate in table 18A, that the category of region used to transfer from is covered by a NUTS region covered by this programme. |
196 | Error | Validate in table 18C, that the category of region used to transfer from is covered by a NUTS region covered by this programme. |
197 | Error | Validate in table 18 that the JTF allocation has no decimals. |
198 | Error | Validate in table 18A that the annual amounts have no decimals. |
199 | Error | Validate in table 18C that the annual amounts have no decimals. |
200 | Error | Validate in table 19A that the annual amounts have no decimals. |
201 | Error | Validate in table 19B that the annual amounts have no decimals. |
202 | Error | Validate in table 20A that the annual amounts have no decimals. |
203 | Error | Validate when appendix 1 exists, that in part A summary at least one record per operation type, specific objective, indicator is applicable. |
204 | Error | Validate when appendix 2 exists, that in part A summary at least one record per operation type, specific objective, indicator is applicable. |
205 | Error | Validate when appendix 1 exists, that in part A summary, the estimated proportion, the intervention field and the common indicator field are empty when the SCO record is not applicable (Implicit in web). |
206 | Error | Validate when appendix 2 exists, that in part A summary, the amount covered, the intervention field and the common indicator field are empty when the SCO record is not applicable (Implicit in web). |
207 | Error | Validate that table 10 (financial plan by year) doesn’t contain Union Support for 2021 (Must be 0). |
208 | Error | Validate in table 11 where Article 36(5) TA was chosen in the Partnership Agreement, that the Union contribution without TA (b), the Union contribution for TA (c), the flexibility amount without TA (i) and the flexibility amount for TA (j) are not empty. |
209 | Error | Validate in table 11 where Article 36(4) TA was chosen in the Partnership Agreement, that the Union contribution less flexibility amount (g) and the Union contribution flexibility amount (h) are not empty. |
210 | Error | Validate that a priority covering only the specific objective ESO4.13 is dedicated to support to the most deprived under specific objective set out in point (m) of Article 4(1) of the ESF+ Regulation. |
211 | Error | Validate in section 2.1.1.1.2 table 2 for non-TA priorities financed by ESF+ for each common output indicator that the target is higher than zero and at least equal to the milestone. Output indicators under specific objective ESO4.13 have no target and no milestone so are excluded from this rule. |
212 | Warning | Validate in section 2.1.1.1.2 and section 2.2.1.2 table 2 for non-TA and TA priorities financed by ESF+ for each programme specific output indicator that the target is at least equal to the milestone. Output indicators under specific objective ESO4.13 have no target and no milestone so are excluded from this rule. |
213 | Error | Validate in sections 2.1 and 2.2 that a priority has at least one Fund selected (PriorityFundRegionCategory). |
214 | Warning | Validate when this programme exists in table 9A/9B of the last Partnership Agreement sent to the Commission that table 11 of this programme contains at least a record for each Fund and category of region combination defined in table 9A/9B of that Partnership Agreement version. |
215 | Error | Validate in table 11 when programme (containing at least one of the following funds: ERDF, ESF+, CF and JTF) was once adopted and when Member State selected "YES" for "non substantial transfer (Article 24(5) CPR)" that if there is a change in "total Union contribution" under a priority (for a given Fund and a given category of regions) as compared to the previous version of the programme approved by the Commission, the "total Union contribution" of at least one other priority of the same Fund of the same programme and for the same category of regions has been changed and no new priority has been created in table 11. |
216 | Error | Validate in table 11 when programme (containing at least one of the following funds: ERDF, ESF+, CF and JTF) was once adopted and when Member State selected "YES" for "non substantial transfer (Article 24(5)CPR)" that the total amount per Fund and category of regions remain unchanged. |
217 | Error | Validate when programme was once adopted and when Member State selected "YES" for "clerical or editorial corrections (Article 24(6)CPR)" that there were no changes in table 10 and 11, as compared to the previous version approved by the Commission. |
218 | Error | Validate when programme was once adopted and when Member State selected "YES" for "non substantial transfer (Article 24(5) CPR)" that there were no changes in table 10, as compared to the previous version of the programme approved by the Commission. |
219 | Error | Validate when in section 3.1 "contribution to InvestEU" is selected that the annual amounts in Table 15A have no decimals. |
220 | Error | Validate when in section 3.1 "contribution to InvestEU" is selected that new contribution amounts are not recorded for years 2021 and 2022 in table 15A. |
221 | Error | Validate when in section 3.1 "contribution to InvestEU" is selected that the related justification text field is filled in as well (not empty). |
222 | Error | Validate when in section 3.1 “transfer to instruments under direct or indirect management” is selected that the annual amounts in table 16A have no decimals. |
223 | Error | Validate when in section 3.1 “transfer to instruments under direct or indirect management” is selected that the related justification text field is filled in as well (not empty). |
224 | Error | Validate when in section 3.1 at least one of the option - “transfer to instruments under direct or indirect management” or “contribution to InvestEU” is selected at programme amendment that for all Funds except EMFAF the sum of (1) the sum of "Totals" per Fund from table 16B (for all categories of regions together) for this programme and the last versions of all other programmes for the MS, cancelled and withdrawn excluded, and (2) "Total" per Fund (for all categories of regions together) from Table 4B of the Partnership Agreement (first adopted version) and (3) the sum of “Totals” per Fund ( |
225 | Error | Validate when in section 3.1 “transfer between ERDF, ESF+, Cohesion Fund or to another Fund or Funds” is selected that the annual amounts in table 17A have no decimals. |
226 | Error | Validate when in section 3.1 “transfer between ERDF, ESF+, Cohesion Fund or to another Fund or Funds” is selected that the related justification text field is filled in (not empty). |
227 | Error | When in section 3.1 “transfer between ERDF, ESF+, Cohesion Fund or to another Fund or Funds” is selected at programme amendment, validate for transfers |
228 | Error | For CZ only, validate for the transfers proposed between ERDF/ESF+/CF that the sum of (1) "Total" transfers from each Fund (ERDF/ESF+/CF: for all categories of regions together where applicable) in table 5B of the Partnership Agreement (first adopted version) and (2) the sum of "Total" transfers from each Fund (ERDF/ESF+/CF: for all categories of regions together where applicable) in table 17B under this programme and the last version of all the other programmes for the MS, cancelled and withdrawn excluded, does not exceed 30% of the initial allocation of each respective “giving” Fund as communicated to the MS. |
229 | Error | Except for CZ, validate for the transfers proposed between ERDF/ESF+/CF that the sum of (1) "Total" transfers from each Fund (ERDF/ESF+/CF: for all categories of regions together where applicable) in table 5B of the Partnership Agreement (first adopted version) and (2) the sum of "Total" transfers from each Fund (ERDF/ESF+/CF: for all categories of regions together where applicable) in table 17B under this programme and the last version of all the other programmes for the MS, cancelled and withdrawn excluded, does not exceed 25% of the initial allocation of each respective “giving” Fund as communicated to the MS. |
230 | Error | Validate before 1/7/2024 in table 11 when priority promotes the socio-economic integration of third country nationals, that the “Co-financing rate – Article 112(7)” is >= “Co-financing rate” and <= 100%. |
231 | Error | Validate that the cumulative ERDF and ESF+ allocation programmed in TCN priorities in all programmes of the MS does not exceed 5% of the cumulative initial ERDF and ESF+ allocation as it was communicated to the Member State. |
232 | Error | Validate in section 2.1 that a priority promoting the socio-economic integration of third country nationals only covers ERDF or ESF+. |
233 | Error | Validate when “The entire priority promotes the socio-economic integration of third country nationals” has been added to a priority compared to the previous adopted programme version, that “Non-substantial transfer” and “Clerical or editorial correction” are not set. |
235 | Error | Validate from 1/7/2024 onwards, for each priority in section 2.1, that the value in column ‘The entire priority promotes the socio-economic integration of third country nationals (article 112(7))’ was not changed, compared to the previous adopted version of the programme. |
236 | Error | Validate from 1/7/2024 onwards, for each previously adopted priority, fund, category of region in table 11, that the co-financing rate encoded in the column ‘Co-financing rate – Article 112(7))’ was not changed, compared to the previous adopted version of the programme. |
237 | Error | Validate from 1/7/2024 onwards, when priority promotes the socio-economic integration of third country nationals, for each new Fund or category of region compared to the previous adopted version of the programme that in table 11 no co-financing rate has been encoded in the column ‘Co-financing rate – Article 112(7)). |
238 | Error | Validate that the total of the resources contributing to the objectives set out in Article 21c(3) of Regulation (EU) 2021/241 (REPowerEU) in table 21 does not exceed 7,5% of the initial national allocation for each Fund |
239 | Error | Validate in section 3.1 when programme amendment relates to Funds contributing to the objectives set out in Article 21c(3) of Regulation (EU) 2021/241 (the relevant box is ticked), that table 21 contains at least one record with a positive amount in one of the years. |
240 | Error | Validate in section 3.1 when programme amendment does not relate to Funds contributing to the objectives set out in Article 21c(3) of Regulation (EU) 2021/241, that table 21 is empty. |
241 | Error | Validate in section 3.1 table 16A that there is no transfer to the “Instrument for the reinforcement of the European defence industry” in years 2026 and 2027. |
242 | Error | Validate that a previously adopted priority dedicated to STEP is still dedicated to STEP, compared to the previous adopted version. |
243 | Error | Validate that the cumulative ERDF and CF allocation programmed (for ETC also INTERREG, NDICI, IPA3 and OCTP funds are considered) in the dedicated priorities under these two Funds (using the specific objectives RSO1.6 and RSO2.9) in all IJG and ETC programmes of the MS does not exceed 20% of the cumulative initial ERDF allocation for IJG and ETC as it was communicated to the Member State. |
244 | Error | Validate when a priority uses specific objectives RSO1.6 or RSO2.9 that the dedicated to STEP flag is set. |
245 | Error | Validate in section 2.1 when a priority is dedicated to STEP and covers ERDF that in section 2.1.1 for ERDF only specific objectives RSO1.6 and/or RSO2.9 are selected. |
246 | Error | Validate in section 2.1 when a priority is dedicated to STEP and covers CF that in section 2.1.1 for CF only specific objective RSO2.9 is selected. |
247 | Error | Validate in table 2 for STEP priorities that per priority, specific objective, Fund and category of region, in case at least one of the indicators RCO125-RCO127 is selected, at least two of the indicators: RCO01 and one of RC002, RC003, RCO04 is used as well. |
248 | Error | Validate in table 2 for STEP priorities that per priority, specific objective, Fund and category of region, in case at least one of the indicators RCO125-RCO127 is selected, his target/the sum of their target is <= than the target for RCO01 (in case it exists). |
249 | Error | Validate in table 2 for STEP priorities that per priority, specific objective, Fund and category of region, in case at least one of the indicators RCO125-RCO127 is selected, his target/the sum of their target is <= than the target/the sum of their targets for RCO02-RCO04 (in case at least one of them exist). |
250 | Warning | Validate that a JTF priority using only one or more of these intervention fields: 145a, 145b, 188, 189, 190, 191, 192, 193 in table 4 of section 2.1.1.1.3 is dedicated to STEP. |
251 | Error | Validate when “Priority dedicated to investments supporting the STEP objectives” has been added to a new or existing priority compared to the previous adopted programme version, that “Non-substantial transfer” and “Clerical or editorial correction” are not set. |
252 | Error | Validate in section 2.1 when a priority is dedicated to STEP that it doesn’t have a dedicated priority type MD12 nor MD13. |
253 | Error | Validate in section 2.1.1 that a priority dedicated to STEP doesn’t use specific objectives ESO4.12 and ESO4.13. |
254 | Warning | Validate in section 2.1 when a priority was previously adopted and marked in the current version as STEP, that also in the previous adopted version it was marked as STEP. |
255 | Error | Validate when programme was never adopted by EC, that “Programme amendment following the mid-term review (Article 18(3) CPR)” is not set (Implicit in web). |
256 | Error | Validate when “Programme amendment following the mid-term review (Article 18(3) CPR)” is set, that also “Approved by monitoring committee” is set and that “Non-substantial transfer (Article 24(5) CPR)” and “Clerical or editorial corrections (Article 24(6) CPR)” are not set and that “MS amending decision number” and “MS amending decision entry into force date” are null. |
257 | Error | Validate when “Programme amendment following the mid-term review (Article 18(3) CPR)” is set, that the “Mid-term review assessment” (PRG.MTRA) is uploaded in the system with at least one attachment with length > 0. |
258 | Error | Validate when a “Mid-term review assessment” (PRG.MTRA) exists, that the “Programme amendment following the mid-term review (Article 18(3) CPR)” is set. |
259 | Error | Validate when “Programme amendment following the mid-term review (Article 18(3) CPR)” is set, that no mid-term review article 18(4) object version exists for this programme, statuses “Programme amendment requested” and “Withdrawn at the request of the MS” excluded. |
260 | Error | Validate when “Programme amendment following the mid-term review (Article 18(3) CPR)” is set, that the mid-term review period is still enabled (“prgijg.allow.midtermreview” is true). |
261 | Error | Validate for non-CF Member States, when transfer(s) from the less development regions (LDR) are proposed in the programme section 3.3 - in Table 19A and/or Table 19B, that the sum of (1) the total of all transfers from the LDR in table 3A of the first adopted Partnership Agreement and (2) the total of all transfers from the LDR in Table 19A (within the programme) and in Table 19B (to other programmes) in section 3.3 under this programme and under the last versions of all other programmes for the MS, cancelled and withdrawn excluded, is not higher than 5% of the initial allocation for LDR as communicated to the MS. |
262 | Error | Validate for CF Member States, when transfer(s) from the less development regions (LDR) are proposed in the programme section 3.3 - in Table 19A and/or Table 19B, that the sum of (1) the total of all transfers from the LDR in table 3A of the first adopted Partnership Agreement and (2) the total of all transfers from the LDR in Table 19A (within the programme) and in Table 19B (to other programmes) in section 3.3 under this programme and under the last versions of all other programmes for the MS, cancelled and withdrawn excluded, is not higher than 15% of the initial allocation for LDR as communicated to the MS. |
263 | Error | Validate when transfer(s) from the transition regions (TR) to the more developed regions (MDR) are proposed in the programme section 3.3 - in Table 19A and/or Table 19B, that the sum of (1) the total of all transfers from the TR to the MDR in table 3A of the first adopted Partnership Agreement and (2) the total of all transfers from the TR to the MDR in Table 19A (within the programme) and in Table 19B (to other programmes) in section 3.3 under this programme and under the last versions of all other programmes for the MS, cancelled and withdrawn excluded, is not higher than 5% of the initial allocation for TR as communicated to the MS. |
264 | Error | Validate when Programme amendment following the mid-term review (Article 18(3) CPR)” is not set, that section 3.3 “Transfers between categories of regions resulting from the mid-term review” (Tables 19A and 19B) was not modified compared to the previous version. |
265 | Error | Validate when initial programme version (x.0), where x is the same as the current programme version, was created after 2024, that in table 4 no new intervention field 056 was added, compared to the latest programme version sent to the Commission in 2024 and currently in status 'Adopted by EC' or 'Adopted by MS'. |
266 | Error | Validate when initial programme version (x.0), where x is the same as the current programme version, was created after 2024, that in table 4 the amounts - under the (existing) intervention field 056 - were not increased, compared to the latest programme version sent to the Commission in 2024 and currently in status 'Adopted by EC' or 'Adopted by MS'. |
267 | Error | Validate when a priority uses specific objective RSO2.10 that the dedicated to RESTORE flag is set. |
268 | Error | Validate that an ERDF, CF and ERDF+CF priority dedicated to RESTORE only covers specific objective RSO2.10. |
269 | Error | Validate that a priority dedicated to RESTORE can cover only ERDF, CF, ERDF+CF or only ESF+. |
270 | Error | Validate that an ERDF, CF and ERDF+CF priority dedicated to RESTORE is not also dedicated to any other dedicated priority type, nor to STEP and TCN. |
271 | Error | Validate that an ESF+ priority dedicated to RESTORE is not also dedicated to STEP and TCN. |
272 | Error | Validate in table 11, for priorities dedicated to RESTORE (with ticked respective box under 2.1.1) that the co-financing rate is maximum 95% in accordance with Article 3 of ERDF/CF Regulation and Article 12 of ESF+ Regulation. |
273 | Error | Validate that the cumulative ERDF, CF and ESF+ allocation programmed in RESTORE priorities in all programmes of the MS does not exceed 10% of the cumulative initial ERDF and ESF+ allocation as it was communicated to the Member State. |
274 | Error | Validate when a RESTORE priority has been added compared to the previous adopted programme version, that “Non-substantial transfer” and “Clerical or editorial correction” are not set. |
275 | Error | Validate that a previously adopted priority dedicated to RESTORE is still dedicated to RESTORE, compared to the previous adopted version. |
276 | Error | Validate that a priority not dedicated to RESTORE and adopted in a previous version did not become dedicated to RESTORE. |
277 | Warning | Validate that an ESF+ priority dedicated to RESTORE is not also a dedicated priority type for “Social innovation”. |
278 | Error | Validate in table 11, for ESF+ priorities dedicated to support to the most deprived persons (with at least one ticked of two respective boxes under 2.1.1) and dedicated to RESTORE that the co-financing rate is between 90% and 95% in accordance with Article 10 and 12 of ESF+ Regulation. |
An example of a validation window:
You can check the list of validation results at any time throughout the Programme IJG:
To see the last validation results:
(1) Click on one of the 4 categories: All results, Passed, Warning, Error.
(2) The list of latest validation results for the chosen category is displayed.
After all errors have been resolved the status of the Programme IJG becomes Validated.
Prepare Programme IJG for send to EC
Remark | The Prepare for Send can occur when a User on the highest MS Node wants to indicate that the Programme IJG version can be prepared for sending to the Commission, once the Validation Errors have been removed and the status is Validated. To prepare the send of the Programme, the User must have the role of Member State Managing Authority with Update or Send access (MSMAu or MSMAs) for the funds managed by the Programme. |
Click on the Prepare for send to EC button to prepare to send the Programme IJG to the Commission:
The system will ask you to confirm the send action:
Click on Confirm to confirm.
The status of the Programme IJG is set to Preparing for send to EC.
Remark | When on the highest MS node, a ‘Snapshot’ document will be available in all official MS languages in the Documents section so that the sender can first verify what will be sent to the Commission. |
Send the Programme IJG
Remark | The Programme IJG can only be sent once the Validation Errors have been removed and the status is Ready To Send. The "4 eyes principle" must be respected. Therefore, the User sending must be different from the User who last validated. To send the Programme IJG, the User must have the role of Member State Managing Authority with Send access (MSMAs) for all the concerned funds. The Sending of information by a Member State to the Commission should be electronically signed in accordance with Directive 1999/93/EC. Sending of the different objects is generating a snapshot document and after the sending an acknowledge document is generated by the European Commission. |
Click on the Send button to send the Programme IJG to the Commission or to an upper Node:
The system will ask you to confirm the send action:
Click on Confirm to confirm.
On success, the Programme version has been sent to the Commission or to an upper Node. When sent to an upper Member State Node, the status is set to Sent. When sent to the Commission and when it concerns a Minor modification, the status is set to Adopted by MS else the status is set to Sent. A Minor modification is a modification which does not modify data which is part of the Commission Decision and for which the Member State has indicated that it does not concern a Major Amendment.
Remark | The automatic transition to Adopted by MS will not be implemented unless the requirements for it are 100% clear. When on the highest MS node, a ‘Snapshot before send’ document will be available in all official MS languages so that the sender can first verify what will be sent to the Commission:
When on the highest MS node and TJTP version(s) is/are selected which contain ‘TJTP Supplementary Information’ document(s), these documents are copied into this Programme version as integral ‘TJTP Supplementary Information’ document(s) and sent with this send action. |
Return the Programme IJG by MS for Modification
Remark | The Programme IJG can only be returned by MS for modification when a lower Node exists and the status is Sent (to a higher MS node), Open, Validated, Ready to Send or Returned by MS for modification. This action can be used when a User wants to return the Programme version sent by the Region because it is incomplete or incorrect and needs to be modified. The notification utility will be called to notify the return to the Region. To return the Programme IJG by MS for modification, the User must have the role of Member State Managing Authority with Update access (MSMAu). |
Follow the steps to Return Programme IJG by MS for Modification:
Select the following:
(1) Select the icon with 3 vertical dots.
(2) Click on the Return button to Return Programme IJG by MS for Modification.
The system will ask you to confirm the Return Programme IJG by MS for Modification action:
Enter the following:
(1) Enter the Reason in the text box provided.
(2) Click on Confirm to save the information.
On success, the status of the Programme will be changed to status Returned by MS for Modification and the sender is notified of the return and its reason.
Delete the Programme IJG
Remark | The Programme IJG can only be deleted when:
To delete the Programme, the User must have the role of Member State Managing Authority with Update access (MSMAu). The delete is a physical delete and cannot be recovered! |
Follow the steps to remove the Programme IJG from the system:
Select the following:
(1) Select the icon with 3 vertical dots.
(2) Click on the Delete button to remove the Programme IJG from the system.
The system will ask you to confirm the delete action:
Click on Confirm to confirm or click on Cancel to return to the Programme IJG.
Cancel the Programme IJG
Remark | The Programme IJG can only be cancelled when a Programme version with documents was sent to the Commission or with a previous version returned by the Commission, before it reaches a first Adoption by the Commission. The notification utility will be called to notify the Commission of the cancel of the version. The Programme version must currently reside on the User's Node and its status is Open or Validated or Ready to send or Returned by MS for modification and has never been adopted by the Commission and (contains a sent Document or when version=1.0 has a sent referring Document linked to it). To cancel the Programme, the User must have the role of Member State Managing Authority with Update access (MSMAu). |
Follow the steps to cancel the Programme IJG from the system:
Select the following:
(1) Select the icon with 3 vertical dots.
(2) Click on the Cancel button to cancel the Programme IJG from the system.
The system will ask you to confirm the cancel action:
Click on Confirm to confirm or click on Cancel to return to the Programme IJG.
On success, the status of the Programme will be changed to Cancelled.
Create a New Version of the Programme IJG
Remark | A new version of the Programme IJG can only be created when the last version is in status Adopted by EC, Adopted by MS, Not Adopted by EC, Returned to MS with official observations, Returned to MS with technical/outstanding comments, Returned to MS with remaining/follow-up observations, Withdrawn at the request of the MS or Cancelled. When the status of the last version is different from Withdrawn at the request of the MS, a new version of the Programme will be created as a copy of the last version. Its status will be set to Open and the version number will be incremented by one when the previous version was adopted (by MS or by EC) (ex. 1.0 -> 2.0) or the working version will be incremented by one when the previous version was returned by the Commission for modification or cancelled (ex. 1.0 -> 1.1). When the status of the last version is Withdrawn at the request of the MS and the User has chosen to create the new version based on the withdrawn version or on the last adopted version, then the version will be incremented by one (ex. 1.0 -> 2.0). When the status of the last version is Not Adopted by EC then the new version should be based on the last adopted version by EC or MS, when these exists, else on the last version, and the version should be incremented by one (ex. 1.0 -> 2.0). To create a new version of the Programme, the User must have the role of Member State Managing Authority with Update access (MSMAu) for the funds managed by the Programme. |
Click on the Create button to create a new version of the Programme IJG:
The system will ask you to confirm the creation of a new version:
Click on Confirm to confirm. Click on Cancel to return to the Programme IJG.
A new version of the Programme IJG has been created as a copy of the last version. Its status is set to Open.
Request to Withdraw the Programme IJG
Remark | The Member State must request to withdraw the Programme IJG by uploading a document called MS Request to withdraw programme version. The Programme IJG version is in a status Sent, Returned to MS with official observations, Returned to MS with technical/outstanding comments or Returned to MS with remaining/follow-up observations at the level of the Commission, or in a status Open, Validated, Ready to send, Returned by MS for modification or Cancelled at the owner node of the Member State and has previously been sent to the Commission. This scenario occurs when at the request of the Member State the Commission withdraw a Programme Version and stop the amendment procedure. To withdraw the Programme, the User must have the role of Member State Managing Authority with Update and Send access (MSMAu, MSMAs). |
Go to the Documents section and click on the Add button to add the MS Request to withdraw Programme IJG version document type:
The Member State must request to withdraw the Programme by selecting the withdraw document and entering the mandatory information:
Enter or select the following information:
(1) Select the MS Request to withdraw Programme IJG version Document Type.
(2) Enter a Document Date.
The system automatically fills the field with todays date, but this can be modified.
(3) Enter a Document Title for your Document.
(4) Enter a Local reference.
(5) Click on the Add button to add a new attachment:
You can add multiple attachments by clicking on the Add button.
You can remove unwanted attachments by selecting the attachment and clicking on the Remove button.
The Attached files window becomes editable:
Enter or select the following information:
(1) Enter a Title for your attachment.
(2) Select the Type of the document.
It is possible to select from these 4 types: Annex, Cover Letter, Main or Translation
(3) Select the Language of the document.
(4) Click on Browse to select the file that you want to add as an attachment.
(5) After the attachments are uploaded click on Save & Send to save and send the document.
Remark | Withdrawals are subject to confirmation by the Commission. After the document is uploaded, it is up to the Commission User to perform the withdrawal action and stop the amendment procedure. On success, the Programme version status will be set to Withdrawn at the Request of the MS. |