Transmission of Data (IJG)

transmission-data-ijg.pdf

English

(1.91 MB - PDF)

PURPOSE

This document describes the actions related to the Transmission of Data procedure for IJG Programmes as described in Annex VII and Article 42 of the CPR.

REGULATIONS

More details regarding the regulation of the Transmission of Data can be found in the "About SFC2021" section of the portal.

ROLES

Roles involved in the Transmission of Data are:

MS Managing Authority (MSMA)

Record Transmission of Data

Upload Transmission of Data Documents

Consult Transmission of Data

Delete Transmission of Data

Validate Transmission of Data

Prepare Transmission of Data for send to EC

Send Transmission of Data

Request by MS for a Review of Transmission of Data

Cancel Transmission of Data

Create New Version of a Transmission of Data

MS Audit Authority (MSAA)

Consult Transmission of Data

FUNDS

ERDF

ESF+

JTF

Workflow

This section shows the lifecycle to create and manage a Transmission of Data .

Click here to see the Transmission of Data workflow diagram in high resolution.

Create a Transmission of Data

Remark

The User is an identified User and has the role of MS Managing Authority with Update rights (MSMAu).

When creating a new Transmission of Data , it does not yet exist.

The Programme is managed on the User’s Node.

There is already an adopted Programme version at Commission level.

The version number is a concatenation of the Submission Year and of the month of the cut-off-date of the Transmission of Data Submission Period (ex. 202212). This version number is selected by the User at creation of the Transmission of Data. The work version number is automatically provided by the system and is 0. The following Submission Periods and related Version numbers exist, starting from 31/01/2022, but not before the first adoption date of the Programme, and ending on 31/01/2030:

YYYY03 with cut-off-date 31/03 to be submitted by 30/04 of YYYY
YYYY06 with cut-off-date 30/06 to be submitted by 31/07 of YYYY
YYYY08 with cut-off-date 31/08 to be submitted by 30/09 of YYYY
YYYY10 with cut-off-date 31/10 to be submitted by 30/11 of YYYY
YYYY12 with cut-off-date 31/12 to be submitted by 31/01 of YYYY+1

The Source language is copied from the last version of the Programme at Commission level.

To create the Transmission of Data , go to the Monitoring menu and select the Transmission of data (IJG) option:

In the search screen click on the Create button to create a new Transmission of Data :

You are redirected to the Transmission of Data Creation Wizard:

Select the following information:

(1) Select a CCI Number.

The CCI list contains all submitted IJG Programmes managed at the User’s Node, and which contain Funds for which the User is registered (Withdrawn versions excluded).

The list returns the CCI, and the Programme English Title retrieved from the last submitted version of the Programme.

(2) Select a Version.

The Version list contains all Transmission of Data versions which do not yet exist for the CCI, with a submission cut-off-date smaller than the current date and a first adoption date of the Programme smaller than the current date. The list is in ascending order. Although the submission deadlines are defined in the regulation they don’t need to be respected. This means that a Transmission of Data can only be created after the cut-off-date of a Submission Period, but also after the deadline of the Submission Period.

(3) Click on Create.

The status of the Transmission of Data is Open.

Remark

For IJG, the following tables foreseen in the official template (Annex VII) will be available in the different submission periods:

Submission by

T10

T11

T12

31/01

30/04

31/07

x(1)

x(2)

30/09

30/11

(1) Material Deprivation Common (EMCO) and Programme Specific Output Indicators not editable in that period

(2) Material Deprivation Common (EMCR) and Programme Specific Result Indicators not editable in that period

The following tables foreseen in the official template (Annex VII) will be available for the IJG module:

Module

T10

T11

T12

IJG

ERDF ESF+ CF JTF

ERDF CF JTF

ESF+

ERDF CF JTF

ESF+

ERDF ESF+ CF
JTF

On Create, the initial Transmission of Data structure is created and a Table of Content (ToC)/Navigation Tree is presented, so the User can continue to populate the structured data of the Transmission of Data.

The Transmission of Data version is linked to the last adopted version of the Programme in force at the cut-off-date.

The Status date of the Adopted by MS version will only be used in case there is no ‘MS amending decision entry into force date’ and when it is not a ‘Clerical or editorial amendment’.

The records of Tables 1, 5, 6, 8, 9, 10 are automatically created and populated with the data of the linked Programme version.

The achievement values (non-programme data) are updated with achievement data from the previous submitted Transmission of Data version. See the different Table requirements for the Table specific logic.

The Tables 2 and 12 will be directly copied from the previous submitted Transmission of Data version. After copying, table 2 for Specific Objective ESO4.13 needs to be updated by setting the Intervention field to 164 (The only code allowed for material deprivation) and the values for Dimensions 2 to 8 should be nullified).

The Officials in Charge are copied from the previous Transmission of Data version of the same Programme, when existing.

Record/Edit the Transmission of Data

Remark

The User is an identified User and has the role of MS Managing Authority with Update rights (MSMAu).

When editing a version of a Transmission of Data , its status is Open, Validated, Ready to send or Sent at the level of the Member State or Review requested by MS and currently resides on the User's Node.

General

Version Information

Note

The Version Information contains information on the identification and status of the Transmission of Data Version like the CCI, the Programme Title in English, the Version Number, the Status and the Node where it currently resides, and the Programme Version it is linked to.

This section is not editable.

Officials in Charge

Note

Officials in Charge can be updated at any time, independent from the status of the Transmission of Data .

Commission Officials (email domain "ec.europa.eu") can only be created/updated/deleted by Commission Users.

The Officials in Charge are copied from the previous Transmission of Data version of the same Programme, when existing.

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 Transmission of Data since it was created, for example:

Documents

Note

The Documents list shows all documents uploaded against this version of the Transmission of Data 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.

Only unsent documents can be deleted. Once a document has been sent to the Commission it cannot be deleted.

The following documents will be foreseen:

Description	Internal Code	Non-Integral (1)	Integral (2)	System (3)	Required (4)
Other Member State Document	TOD.OM	X
Snapshot of data before send	SNP.TODSNT		X	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

Uploading & Sending Documents

Note

Only unsent documents can be deleted. Once a document has been sent to the Commission it cannot be deleted.

Multiple documents can be uploaded in the Transmission of Data .

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 Transmission of Data 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 Transmission of Data .

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.

(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 & Send.

Remark

Integral document types will only display the Save button and will be sent when the Transmission of Data 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 Transmission of Data .

Sending an unsent non-integral document

Note

Only unsent documents can be deleted. Once a document has been sent to the Commission it cannot be deleted.

Once the document and attachment(s) have been uploaded click on the Edit icon in the row containing the unsent document:

Click on Save & Send to send the document to the Commission:

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

Note

Only unsent documents can be deleted. Once a document has been sent to the Commission it cannot 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 Transmission of Data . It can be used as a type of 'chat' between the Member State and Commission.

All Users who have Read permission on the Transmission of Data will be able to read all observations in the conversation.

All Users who have Update permission on the Transmission of Data will be able to send an observation and participate in the conversation.

All observations are kept against the specific version of the Transmission of Data .

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 Save to save the information.

Table 1

Note

The records are automatically foreseen from the linked Programme version. There is a record for each distinct Priority (non-Technical Assistance and Technical Assistance), Specific Objective (only for non-Technical Assistance), Fund [and Category of Region] combination in Programme Table 4, plus a record for each Priority dedicated to Material Deprivation (ESO4.13) which doesn’t have a Table 4.

The “Category of region” column will only be shown for IJG Programmes containing ERDF or ESF+.

The JTF records do not have the detail per JTF Allocation Type.

The “Basis for calculation” will be the one defined against the Priority, Fund [and Category of Region], as it doesn’t exist at Specific Objective level.

The “Total financial allocation” in column 6 should always be without Technical Assistance.

The “Total financial allocation” in column 6 will be the Total amount per Priority, Specific Objective (only for non-Technical Assistance), Fund [and Category of Region] from Programme Table 4, divided by the following co-financing rate:

For IJG Art.36(4) programmes, this co-financing rate will be the one defined against the Priority, Fund [and Category of Region] in Programme Table 11 Column (f). For JTF it will be the one at the level of the total JTF, so not per JTF Allocation Type.
For IJG Art.36(5) programmes, this co-financing rate will be the one defined against the Priority, Fund [and Category of Region] in Programme Table 11 Column (h). For JTF this calculation will be done at the level of the total JTF, so not per JTF Allocation Type.

For Material Deprivation (ESO4.13) which doesn’t have a Table 4, the “Total financial allocation” needs to come from Programme Table 11 where there is no Specific Objective, but the Priority is dedicated to only Material Deprivation (ESO4.13) anyway:

For IJG Art.36(4) programmes, the “Total financial allocation” = Programme Table 11 (e).
For IJG Art.36(5) programmes, the “Total financial allocation” = Programme Table 11 ((b)+(i)) / (h).

The “Co-financing rate” in column 7 will be the one defined against the Priority, Fund [and Category of Region] in Programme Table 11 (IJG) (Column (f) for TA 36(4) and (h) for TA 36(5)). For JTF it will be the one at the level of the total JTF, so not per JTF Allocation Type.

The “Proportion of the total financial allocation covered with selected operations (%)” is calculated ((column 8/column 6)*100) and is persisted.

The “Proportion of the total financial allocation covered by eligible expenditure declared by beneficiaries (%)” is calculated ((column 11/column 6)*100) and is persisted.

All editable fields are mandatory. This will not be checked in the form but in validation rule 125.

Click on the Edit button to enter the values in the table:

The Edit details pop-up window appears:

Enter the following:

(1) Enter the Total eligible cost of selected operations (EUR).

(2) Enter the Contribution from the funds to selected operations (EUR).

(3) Enter the Total eligible expenditure declared by beneficiaries.

(4) Enter the Number of selected operations.

(5) Click on Save to save the information.

Table 2

Remark

The data in Table 2 can be entered manually (1) or via the import of an Excel file (2). An Import button is foreseen to allow the import of Table 2 data from a correctly formatted Excel file template available here on our Portal.

The import will delete all existing records and add all records from the Excel. When not all records from the Excel file could be imported successfully, the following alert will be displayed “Not all records from the Excel file were imported because the format was not correct or because the codes do not exist”, followed by the list of none imported records.

Note

The “Category of region” column will only be shown for IJG Programmes containing ERDF or ESF+.

A subtotal per Fund and Category of Region and a grand total are foreseen on the 3 Financial data columns.

All fields are mandatory when applicable.

Click on the Add button to enter the values manually in the table (1) or click on the down arrow to Import from Excel (2):

The Edit details pop-up window appears:

Enter or select the following:

(1) Select the Priority, Specific Objective, Fund [and Category of Region].

The list of Priority, Specific Objective, Fund [and Category of Region] combinations comes from the linked Programme version. For JTF they will not contain the JTF Allocation Type. The list contains a record for each distinct Priority, Specific Objective, Fund [and Category of Region] combination in Programme Table 4, plus one for each Priority dedicated to Material Deprivation (ESO4.13) which doesn’t have a Table 4.

(2) Select the Intervention field.

For non-Technical Assistance Priorities, the Intervention Field list will contain all non-Technical Assistance Intervention Fields valid for the Priority’s Specific Objective and Fund. For Technical Assistance Priorities, the Intervention field list will contain all Technical Assistance Intervention Fields.

(3) Select the Form of support.

The Form of support list contains all Forms of support (FIN). The field is mandatory for non-Technical Assistance Priorities, and optional for Technical Assistance Priorities. For Priorities dedicated to Material Deprivation (ESO4.13), this field will be disabled.

(4) Select the Territorial delivery dimension.

The Territorial delivery dimension will contain all Territorial delivery mechanisms (TDM) used in the Programme for the Priority, Specific Objective, Fund and Category of Region. As there is no TDM in the Programme for Technical Assistance Priorities and for Priorities dedicated to Material Deprivation (ESO4.13), this field will be disabled in those cases.

(5) Select the Economic activity dimension.

The Economic activity dimension list will contain all Economic activities. For Priorities dedicated to Material Deprivation (ESO4.13), this field will be disabled.

(6) Select the Location dimension.

The Location dimension list will contain all region NUTS codes. For Priorities dedicated to Material Deprivation (ESO4.13), this field will be disabled.

(7) Select the ESF+ secondary theme.

The ESF+ secondary theme list will contain all ESF+ secondary themes (ESF) but will only be enabled on ESF+ Priorities. For Priorities dedicated to Material Deprivation (ESO4.13), this field will be disabled.

(8) Select the Gender equality dimension.

The Gender equality dimension list will contain all Gender equality values. For Priorities dedicated to Material Deprivation (ESO4.13), this field will be disabled.

(9) Select the Macro-regional and sea-basin dimension.

The Macro-regional and sea-basin dimension list will contain all Macro-regional and sea-basin strategies. For Priorities dedicated to Material Deprivation (ESO4.13), this field will be disabled.

(10) Enter the Total eligible cost of selected operations (EUR).

(11) Enter the Total eligible expenditure declared by beneficiaries.

(12) Enter the Number of selected operations.

(13) Click on Save to save the information.

Table 5

Note

The records for Programme Specific, Reserved and Common ERDF, CF and JTF Output Indicators are automatically foreseen from Table 2 of the linked Programme version, both for non-Technical Assistance and Technical Assistance Priorities. Additionally, when Common Output sub-Indicators (“of which”) have been defined for reporting, they will automatically be foreseen for the Indicators coming from Table 2. These Common Output sub-Indicators (“of which”) will not have a Milestone, nor a Target. Programme Specific and Reserved Indicators are always Main Indicators without sub-indicator.

Additionally, for JTF, all other Common ESF+ Output Indicators valid for the Specific Objective JSO8.1 and Fund JTF and not available in the Programme Table 2, will automatically be foreseen for each such Priority with Fund JTF and Specific Objective JSO8.1.

The “Category of region” column will only be shown for IJG Programmes containing ERDF.

For ERDF and CF, only columns 11, 12 and 13 are editable. Column 13 is always editable and optional.

For JTF, only columns 11, 12 and 13 are editable. Column 13 is always editable and optional.

Check this FAQ to see in what cases columns 11 and 12 are editable and to know what the formulas are used to calculate the values of “Implemented operations”.

Click on the Edit button to enter the values in the table:

The Edit details pop-up window appears:

Enter the following:

(1) Enter the Selected operations.

(2) Enter the Implemented operations.

(3) Enter the Comments if necessary.

(4) Click on Save to save the information.

Table 6

Note

All records for Programme Specific, Reserved and Common ESF+ Output Indicators available in Table 2 of the linked Programme version are automatically foreseen. Additionally, all other Common ESF+ Output Indicators valid for the Specific Objective and Fund, for each Priority, Specific Objective, Fund and Category of Region, not available in the Programme Table 2 will be automatically foreseen.

Only columns 9 (when a total target already exists in the Programme), 10 and 12 are editable. Column 12 is always editable and optional.

Check this FAQ to see in what cases columns 9 and 10 and their gender breakdown are editable and mandatory/optional and to know what formulas are used to calculate the values.

The check on mandatory fields will not be done in the form but in validation rules 130 and 131.

Click on the Edit button to enter the values in the table:

The Edit details pop-up window appears:

Enter the following:

(1) Enter the values for Target (2029).

(2) Enter the values for Values achieved to date…

(3) Enter the Comments if necessary.

(4) Click on Save to save the information.

Remark

The system assumes that for Output Indicators, the Target values and Achievement values are always in absolute numbers.

The Achievement ratio is always displayed as a nominal value, not as a percentage.

On save, when Specific Objective is not ESO4.12, the system will calculate and overwrite the achievement per gender and total for EECO01. Should be EECO02 + EECO04 + EECO05.

Table 8

Note

All records are automatically foreseen.

Only columns 4 and 5 are editable under the sub-indicators (“of which”). Column 4 is mandatory, column 5 is optional.

The formula to calculate the value for column 4 of indicator RCO01 = RCO01a+RCO01b+RCO01c+RCO01d.

Click on the Edit button to enter the values in the table:

The Edit details pop-up window appears:

Enter the following:

(1) Enter the Number of enterprises net of multiple support by…

(2) Enter the Comments if necessary.

(3) Click on Save to save the information.

Table 9

Note

The records are automatically foreseen from Table 3 of the linked Programme version. Additionally, when Common Result sub-Indicators (“of which”) have been defined for reporting, they will automatically be foreseen for the Indicators coming from Table 3. These Common Result sub-Indicators (“of which”) will not have a Baseline, nor a Target from the Programme.

Additionally, for JTF, all other Common ESF+ Result Indicators valid for the Specific Objective JSO8.1 and Fund JTF and not available in the Programme Table 3, will automatically be foreseen for each such Priority with Fund JTF and Specific Objective JSO8.1.

For ERDF and CF, only columns 11, 12, 13, 14 and 15 are editable. Column 15 is always editable and optional.

For JTF, only columns 11, 12, 13, 14 and 15 are editable. Column 15 is always editable and optional.

Check this FAQ to see in which cases columns 11, 12, 13 and 14 are editable and to know what formulas are used to calculate the values of “Implemented operations”.

The check on mandatory fields will not be done in the form but in validation rules 134 to 137.

Click on the Edit button to enter the values in the table:

The Edit details pop-up window appears:

Enter the following:

(1) Enter the value for Baseline under Selected operations.

(2) Enter the value for Planned achievements under Selected operations.

(3) Enter the value for Baseline under Implemented operations.

(4) Enter the value for Achieved under Implemented operations.

(5) Enter the Comments if necessary.

(6) Click on Save to save the information.

Table 10

Note

All records for Programme Specific, Reserved and Common ESF+ Result Indicators available in Table 3 of the linked Programme version are automatically foreseen. Additionally, all other Common ESF+ Result Indicators valid for the Specific Objective and Fund, for each Priority, Specific Objective, Fund and Category of Region and without Output Indicator for target setting, not available in the Programme Table 3 will be automatically foreseen. This means that in the end a Result Indicator with an Output Indicator for target setting defined in the Programme, will have two records in this Table 10, one with the Output Indicator as basis for target setting and one without the Output indicator as basis for target setting.

Only columns 10 (when a total target already exists in the Programme), 11 and 13 are editable. Column 13 is always editable and optional.

Check this FAQ to see in which cases columns 10 and 11 and their gender breakdown are editable and mandatory and to know what formulas are used to calculate the values.

The check on mandatory fields will not be done in the form but in validation rules 138 and 139.

Click on the Edit button to enter the values in the table:

The Edit details pop-up window appears:

Enter the following:

(1) Enter the values for Target (2029).

(2) Enter the Values achieved to date...

(3) Enter the Comments if necessary.

(4) Click on Save to save the information.

Remark

Programme Specific Result Indicators can be qualitative. In that case the columns 10-T and 11-T will be alphanumeric instead of numeric.

For Quantitative Indicators under Specific Objectives ESO4.1 to ESO4.12, the “Measurement unit of indicator” and the “Measurement unit of target” will also contain between round brackets the “Term” defined against the indicator in the Programme.

The Achievement ratio is always displayed as a nominal value, not as a percentage.

When the Indicator has a decreasing target, then the Achievement ratio needs to be inverted (= 1 / Achievement ratio).

In the Print, the “Decreasing target” will not be shown.

Table 12

Note

The “Category of region” column will only be shown for IJG Programmes containing ERDF or ESF+.

Per record, only one Product + Grants can be encoded. Therefore, from the moment the Eligible expenditure for one Product is encoded, all the fields of the other Products (Loans, Guarantees, Equity) are nullified and disabled. And from the moment the Eligible expenditure of one Product is nullified, the values in the other fields of the Product are also nullified and all fields are enabled. Grants are always enabled.

Encode multiple records for the same ‘Priority, Fund , Specific Objective, Category of region, Product’ is allowed.

Click on the Add button to enter the values in the table:

The Edit details pop-up window appears:

Enter or select the following:

(1) Select a priority, specific objective combination.

The list of Priority, Specific Objective, Fund [and Category of Region] combinations comes from the linked Programme version. For JTF they will not contain the JTF Allocation Type.

(2) Enter the values for Eligible expenditure by product.

The check on eligible expenditure amount will consider zero as a valid amount.

(3) Enter the values for Amount of private and public resources mobilised in addition to the contribution from the funds.

(4) Enter the values for Management cost and fees for holding funds depending on the financial product operating within the holding fund structure.

From the moment a Product value is encoded/nullified in the Management costs and fees for holding funds, the Type (D=Direct award or C=Competitive tender) must be selected/nullified.

(5) Enter the values for Management cost and fees for specific funds (set-up either with or without the holding fund structure) by financial product.

From the moment a Product value is encoded/nullified in the Management costs and fees for specific funds, the Type (D=Direct award or C=Competitive tender) must be selected/nullified.

(6) Enter the values for Other.

The field For guarantees, total value of … is only enabled/disabled when Eligible expenditure for Guarantees has been encoded/nullified.

(7) Click on Save to save the information.

Validate the Transmission of Data

Remark

The Transmission of Data can be validated at any time, when the current version is in status Open and resides at the User’s Node.

To validate the Transmission of Data , the User must have the role of MS Managing Authority with Update or Send rights (MSMAu/s).

Click on the Validate button to validate the Transmission of Data :

Remark

An Error will block you from sending the Transmission of Data . The error(s) should be resolved and the Transmission of Data must be revalidated. Note that a Warning does not block you from sending the Transmission of Data .

The system validates the following information:

Code	Severity	Validation Rule
001	Warning	Validate that at least one official in charge of the Member State exists.
002	Error	Validate that the CCI code matches the following regular expression: For IJG (……16..PR…\|……16..TA…\| ……05..PR…\|……05..TA…) For ETC (….TC16….…) For EMFAF (……14MFPR…) For AMIF, ISF and BMVI (……65AMPR…\|……65ISPR…\|……65BVPR…) (Implicit in web).
003	Error	Validate that the programme is already adopted by the Commission (Implicit in web).
004	Warning	Validate when Transmission of Data work version is 0, that the current date for submission period YYYY12 is smaller or equal than 31/01/YYYY+1, for submission period YYYY03 is smaller or equal than 30/04/YYYY, for submission period YYYY06 is smaller or equal than 31/07/YYYY, for submission period YYYY08 is smaller or equal than 30/09/YYYY, for submission period YYYY09 is smaller or equal than 31/10/YYYY, for submission period YYYY10 is smaller or equal than 30/11/YYYY.
005	Warning	Validate when submission period is YYYY06 or YYYY12 for IJG and ETC programmes in table 12 that eligible expenditure by product is provided (positive, zero, but not null) for financial instruments corresponding to a form of support defined in table 2 (02 = equity or quasi-equity, 03 = Loans, 04 = guarantees, 05 = grants within an FI operation) for the same priority, specific objective, fund, [category of region].
006	Error	Validate when submission period is YYYY06 or YYYY12 for IJG and ETC programmes in table 12 that no eligible expenditure by product is provided for financial instruments not corresponding to a form of support defined in table 2 (02 = equity or quasi-equity, 03 = Loans, 04 = guarantees, 05 = grants within an FI operation) for the same priority, specific objective, fund, [category of region].
007	Warning	Validate when submission period is YYYY06 or YYYY12 in table 2 that the total eligible expenditure declared by beneficiaries per priority, specific objective, Fund, category of region and form of support (only 02, 03, 04 and 05) is within +/- 20% range of the sum of the corresponding eligible expenditure + eligible MCFs in table 12.
008	Warning	Validate when submission period is YYYY06 or YYYY12 in table 12 when it contains eligible expenditure for grants within a FI operation (at line level), that it also contains eligible expenditure for either equity or quasi-equity or loans or guarantees.
009	Warning	Validate when submission period is YYYY06 or YYYY12 in table 11 that baseline is 0 for main indicators.
012	Error	Validate in table 2 that for each form of support row, the total eligible cost of selected operations and the total eligible expenditure declared by beneficiaries is positive, zero, but not null.
013	Warning	Validate for IJG/ETC in table 1 when “Total eligible costs of selected operations” is > 0 that “Number of selected operations” is > 0.
014	Error	Validate for IJG/ETC in table 1 when “Number of selected operations” is > 0 that “Total eligible costs of selected operations” is > 0.
015	Warning	Validate in table 2 when “Total eligible costs of selected operations” is > 0 that “Number of selected operations” is > 0.
016	Error	Validate in table 2 when “Total eligible costs of selected operations” is > 0 that “Number of selected operations” is > 0.
017	Warning	Validate in table 1 when “Total eligible expenditure declared by beneficiaries” is > 0 that “Total eligible costs of selected operations” is >= “Total eligible expenditure declared by beneficiaries”.
018	Warning	Validate in table 2 when “Total eligible expenditure declared by beneficiaries” is > 0 that “Total eligible costs of selected operations” is >= “Total eligible expenditure declared by beneficiaries”.
019	Error	Validate when submission period is YYYY06 or YYYY12 in table 6 per priority, specific objective, category of region and gender that the value achieved for EECO02 is >= EECO03.
020	Error	Validate when submission period is YYYY06 or YYYY12 in table 6 per priority, specific objective, category of region and gender that the value achieved for EECO06+EECO07+EECO08 is <= EECO01.
021	Error	Validate when submission period is YYYY06 or YYYY12 in table 6 per priority, specific objective, category of region and gender that the value achieved for EECO09+EECO10+EECO11 is = EECO01.
022	Error	Validate when submission period is YYYY06 or YYYY12 in table 6 per priority, specific objective, category of region and gender that the value achieved for EECO12 is <= EECO01.
023	Error	Validate when submission period is YYYY06 or YYYY12 in table 6 per priority, specific objective, category of region and gender that the value achieved for EECO13 is <= EECO01.
024	Error	Validate when submission period is YYYY06 or YYYY12 in table 6 per priority, specific objective, category of region and gender that the value achieved for EECO14 is <= EECO01.
025	Error	Validate when submission period is YYYY06 or YYYY12 in table 6 per priority, specific objective, category of region and gender that the value achieved for EECO15 is <= EECO01.
026	Error	Validate when submission period is YYYY06 or YYYY12 in table 6 per priority, specific objective, category of region and gender that the value achieved for EECO16 is <= EECO01.
027	Error	Validate when submission period is YYYY06 or YYYY12 in table 6 per priority, specific objective, category of region and gender that the value achieved for EECO17 is <= EECO01.
028	Error	Validate when submission period is YYYY06 or YYYY12 in table 6 per priority, specific objective and category of region, when gender breakdown has been encoded (different from 0), that for programme specific indicators and reserved indicators, the total achieved value equals the sum of male, female and non-binary achieved values.
029	Error	Validate when submission period is YYYY06 or YYYY12 in table 6 per priority, specific objective, category of region and gender that the value achieved for ESCO02 is <= ESCO01.
030	Error	Validate when submission period is YYYY06 or YYYY12 in table 6 per priority, specific objective, category of region and gender that the value achieved for ESCO03 is <= ESCO01.
031	Error	Validate when submission period is YYYY06 or YYYY12 in table 6 per priority, specific objective, category of region and gender that the value achieved for ESCO04 is <= ESCO01.
032	Error	Validate when submission period is YYYY06 or YYYY12 in table 6 per priority, specific objective, category of region and gender that the value achieved for ESCO05 is <= ESCO01.
033	Error	Validate when submission period is YYYY06 or YYYY12 in table 6 per priority, specific objective, category of region and gender that the value achieved for ESCO06 is <= ESCO01.
034	Error	Validate when submission period is YYYY06 or YYYY12 in table 6 per priority, specific objective, category of region and gender that the value achieved for ESCO07 is <= ESCO01.
035	Error	Validate when submission period is YYYY06 or YYYY12 in table 6 per priority, specific objective, category of region and gender that the value achieved for ESCO08 is <= ESCO01.
036	Error	Validate when submission period is YYYY06 or YYYY12 in table 6 per priority, specific objective, category of region and gender that the value achieved for ESCO02+ESCO03+ESCO04 is <= ESCO01.
037	Error	Validate when submission period is YYYY06 or YYYY12 in table 6 per priority, specific objective and category of region that the total value achieved for EMCO01 is >= EMCO02+EMCO05.
038	Error	Validate when submission period is YYYY06 or YYYY12 in table 6 per priority, specific objective and category of region that the total value achieved for EMCO02 is = EMCO03+EMCO04.
039	Error	Validate when submission period is YYYY06 or YYYY12 in table 6 per priority, specific objective and category of region that the total value achieved for EMCO03 is <= EMCO02.
040	Error	Validate when submission period is YYYY06 or YYYY12 in table 6 per priority, specific objective and category of region that the total value achieved for EMCO04 is <= EMCO02.
041	Error	Validate when submission period is YYYY06 or YYYY12 in table 6 per priority, specific objective and category of region that the total value achieved for EMCO05 is = EMCO06+EMCO07+EMCO08.
042	Error	Validate when submission period is YYYY06 or YYYY12 in table 6 per priority, specific objective and category of region that the total value achieved for EMCO06 is <= EMCO05.
043	Error	Validate when submission period is YYYY06 or YYYY12 in table 6 per priority, specific objective and category of region that the total value achieved for EMCO07 is <= EMCO05.
044	Error	Validate when submission period is YYYY06 or YYYY12 in table 6 per priority, specific objective and category of region that the total value achieved for EMCO08 is <= EMCO05.
045	Error	Validate when submission period is YYYY06 or YYYY12 in table 6 per priority, specific objective and category of region that the total value achieved for EMCO10 is <= 100%.
046	Error	Validate when submission period is YYYY06 or YYYY12 in table 6 per priority, specific objective and category of region that the total value achieved for EMCO11 is <= 100%.
047	Error	Validate when submission period is YYYY06 or YYYY12 in table 10 per priority, specific objective, category of region and gender that the value achieved for EECR01 not linked to a target is <= EECO04 in table 6.
048	Error	Validate when submission period is YYYY06 or YYYY12 in table 10 per priority, specific objective, category of region and gender that the value achieved for EECR02 not linked to a target is <= EECO01 in table 6.
049	Error	Validate when submission period is YYYY06 or YYYY12 in table 10 per priority, specific objective, category of region and gender that the value achieved for EECR03 not linked to a target is <= EECO01 in table 6.
050	Error	Validate when submission period is YYYY06 or YYYY12 in table 10 per priority, specific objective, category of region and gender that the value achieved for EECR04 not linked to a target is <= EECO02+EECO04 in table 6.
051	Error	Validate when submission period is YYYY06 or YYYY12 in table 10 per priority, specific objective, category of region and gender that the value achieved for EECR05 not linked to a target is <= EECO02+EECO04 in table 6.
052	Error	Validate when submission period is YYYY06 or YYYY12 in table 10 per priority, specific objective, category of region and gender that the value achieved for EECR06 not linked to a target is <= EECO05 in table 6.
053	Error	Validate when submission period is YYYY06 or YYYY12 in table 10 per priority, specific objective, category of region and gender, for common result indicators and for programme specific result indicators with a measurement unit term = Number, that the value achieved for the result indicator is <= value achieved for the reference output indicator in table 6.
054	Error	Validate when submission period is YYYY06 or YYYY12 in table 10 per priority, specific objective and category of region, when gender breakdown has been encoded (different from 0), that for programme specific indicators and reserved indicators, with a term of the indicator’s measurement unit equal to ‘number’, the total achieved value equals the sum of male, female and non-binary achieved values.
055	Error	Validate when submission period is YYYY06 or YYYY12 in table 10 per priority, specific objective, category of region and gender that the value achieved for EECR01, EECR02, EECR03, EECR04, EECR05 and EECR06 without a target is >= than the value achieved for EECR01, EECR02, EECR03, EECR04, EECR05 and EECR06 with a target.
056	Error	Validate when submission period is YYYY06 or YYYY12 in table 10 per priority, specific objective and category of region that the total value achieved for EMCR01 is >= EMCR02+EMCR03+EMCR05.
057	Error	Validate when submission period is YYYY06 or YYYY12 in table 10 per priority, specific objective and category of region that the total value achieved for EMCR02 is <= EMCR01.
058	Error	Validate when submission period is YYYY06 or YYYY12 in table 10 per priority, specific objective and category of region that the total value achieved for EMCR03 is <= EMCR01.
059	Error	Validate when submission period is YYYY06 or YYYY12 in table 10 per priority, specific objective and category of region that the total value achieved for EMCR05 is <= EMCR01.
060	Error	Validate when submission period is YYYY06 or YYYY12 in table 10 per priority, specific objective and category of region that the total value achieved for EMCR06 is <= EMCR01.
061	Error	Validate when submission period is YYYY06 or YYYY12 in table 10 per priority, specific objective and category of region that the total value achieved for EMCR07 is <= EMCR01.
062	Error	Validate when submission period is YYYY06 or YYYY12 in table 10 per priority, specific objective and category of region that the total value achieved for EMCR08 is <= EMCR01.
063	Error	Validate when submission period is YYYY06 or YYYY12 in table 10 per priority, specific objective and category of region that the total value achieved for EMCR09 is <= EMCR01.
064	Error	Validate when submission period is YYYY06 or YYYY12 in table 10 per priority, specific objective and category of region that the total value achieved for EMCR10 is >= EMCR11+EMCR12+EMCR14.
065	Error	Validate when submission period is YYYY06 or YYYY12 in table 10 per priority, specific objective and category of region that the total value achieved for EMCR11 is <= EMCR10.
066	Error	Validate when submission period is YYYY06 or YYYY12 in table 10 per priority, specific objective and category of region that the total value achieved for EMCR12 is <= EMCR10.
067	Error	Validate when submission period is YYYY06 or YYYY12 in table 10 per priority, specific objective and category of region that the total value achieved for EMCR14 is <= EMCR10.
068	Error	Validate when submission period is YYYY06 or YYYY12 in table 10 per priority, specific objective and category of region that the total value achieved for EMCR15 is <= EMCR10.
069	Error	Validate when submission period is YYYY06 or YYYY12 in table 10 per priority, specific objective and category of region that the total value achieved for EMCR16 is <= EMCR10.
070	Error	Validate when submission period is YYYY06 or YYYY12 in table 10 per priority, specific objective and category of region that the total value achieved for EMCR17 is <= EMCR10.
071	Error	Validate when submission period is YYYY06 or YYYY12 in table 10 per priority, specific objective and category of region that the total value achieved for EMCR18 is <= EMCR10.
072	Error	Validate when submission period is YYYY06 or YYYY12 in table 10 per priority, specific objective and category of region that the total value achieved for EMCR19 is >= EMCR20+EMCR21+EMCR22.
073	Error	Validate when submission period is YYYY06 or YYYY12 in table 10 per priority, specific objective and category of region that the total value achieved for EMCR20 is <= EMCR19.
074	Error	Validate when submission period is YYYY06 or YYYY12 in table 10 per priority, specific objective and category of region that the total value achieved for EMCR21 is <= EMCR19.
075	Error	Validate when submission period is YYYY06 or YYYY12 in table 10 per priority, specific objective and category of region that the total value achieved for EMCR22 is <= EMCR19.
076	Error	Validate when submission period is YYYY06 or YYYY12 in table 10 per priority, specific objective and category of region that the total value achieved for EMCR24 is <= EMCR19.
077	Error	Validate when submission period is YYYY06 or YYYY12 in table 10 per priority, specific objective and category of region that the total value achieved for EMCR25 is <= EMCR19.
078	Error	Validate when submission period is YYYY06 or YYYY12 in table 10 per priority, specific objective and category of region that the total value achieved for EMCR26 is <= EMCR19.
079	Error	Validate when submission period is YYYY06 or YYYY12 in table 10 per priority, specific objective and category of region that the total value achieved for EMCR27 is <= EMCR19.
080	Error	Validate in table 1 for non-ESF+ that “Total eligible cost of selected operations (EUR)” per Fund and category of region is equal to the total eligible cost of selected operations per Fund and category of region from table 2
081	Warning	Validate in table 1 that “Contribution from the funds to selected operations (EUR)” is <= than “Total eligible cost of selected operations (EUR)”.
082	Warning	Validate in table 1 that “Total eligible cost of selected operations (EUR)” is <= than “Total financial allocation by fund and national contribution (EUR)”.
083	Error	Validate in table 1 that no negative value is encoded for “Number of selected operations”.
084	Error	Validate in table 2 that no negative value is encoded for “Number of selected operations”
085	Warning	Validate when submission period is YYYY06 or YYYY12 in table 5 for non-JTF ESF+ common indicators, that “Selected operations [dd/mm/yy]” are <= than “Target 2029”.
086	Warning	Validate when submission period is YYYY06 or YYYY12 in table 9 for non-JTF ESF+ common indicators, that “Planned achievements” of “Selected operations [dd/mm/yy]” are <= than “Target 2029”.
087	Warning	Validate when submission period is YYYY06 or YYYY12 in table 5 that “Implemented operations [dd/mm/yy]” are <= than “Target 2029”.
088	Warning	Validate when submission period is YYYY06 or YYYY12 in table 9 that “Achieved” of “Implemented operations [dd/mm/yy]” are <= than “Target 2029”.
089	Error	Validate when submission period is YYYY06 or YYYY12 in table 5 that no negative value is encoded for “Selected operations” and “Implemented operations”.
090	Error	Validate when submission period is YYYY06 or YYYY12 in table 8 that no negative value is encoded for “Number of enterprises”.
091	Error	Validate in table 2 for non-ESO4.13 specific objective that the intervention field encoded for ESF+, ERDF, CF and JTF exists also within the table 4 of the programme nevertheless of priority, Fund or specific objective.
092	Error	Validate in table 1 that the “Total eligible expenditure declared by beneficiaries” per Fund and category of region is equal to the “Total eligible expenditure declared by beneficiaries” per Fund and category of region from table 2.
093	Warning	Validate in table 1 that the “Total eligible expenditure declared by beneficiaries” is <= than the “Total financial allocation by Fund and national contribution”.
094	Warning	Validate when submission period is YYYY06 or YYYY12 in table 5 for non-JTF ESF+ common indicators, that “Selected operations [dd/mm/yy]” are >= than “Implemented operations [dd/mm/yy]”.
095	Warning	Validate when submission period is YYYY06 or YYYY12 in table 9 for non-JTF ESF+ common indicators, that “Achieved” of “Implemented operations [dd/mm/yy]” is <= than “Planned achievements” of “Selected operations [dd/mm/yy]”.
096	Warning	Validate when submission period is YYYY06 or YYYY12 in table 9 for non-JTF ESF+ common indicators, that “Baseline” of “Implemented operations [dd/mm/yy]” is <= than “Baseline” of “Selected operations [dd/mm/yy]”.
097	Error	Validate in when submission period is YYYY06 or YYYY12 table 6 per priority, specific objective, category of region and gender that the value achieved for EECO01= EECO02 + EECO04 + EECO05.
098	Error	Validate in table 3 for AMIF and BMVI that the type of intervention encoded in column 3 exists also within the table 3 of the related programme and specific objective.
099	Error	Validate in table 3 for ISF that the type of intervention encoded in column 4 exists also within the table 3 of the related programme and specific objective.
100	Error	Validate in table 3 that the code for the “Type of intervention (Table 3 of Annex VI)” in column 5 corresponds to the type of action of the “Co-financing rate (%)” in column 2.
101	Warning	Validate in Table 3 that row Total per Specific Objective for “Total eligible cost of selected operations” (column 8), “Contribution from the funds to selected operations” (column 9) and “Total eligible expenditure declared by beneficiaries” (column 11) are always <= than “Total financial allocation from the fund and national contribution” (column 7).
102	Error	Validate in table 3 that for each row, the “Total eligible cost of selected operations” (column 8) and the “Total eligible expenditure declared by beneficiaries” (column 11) is positive, zero, but not null.
103	Error	Validate in table 3 when “Total eligible costs of selected operations” (column 8) is > 0 that “Number of selected operations” (column 13) is > 0.
104	Error	Validate in table 3 when “Number of selected operations” (column 13) is > 0 that “Total eligible costs of selected operations” (column 8) is > 0.
105	Error	Validate in table 3 that the “Contribution from the funds to selected operations (EUR)” (column 9) is <= than “Total eligible cost of selected operations (EUR)” (column 8).
106	Warning	Validate in table 3 that “Total eligible cost of selected operations (EUR)” (column 8) is <= than “Total financial allocation from the Fund and national contribution (EUR)” (column 7).
107	Warning	Validate in table 3 that the “Total eligible expenditure declared by beneficiaries” (column 11) is <= than the “Total financial allocation from the Fund and national contribution (EUR)” (column 7).
108	Warning	Validate in table 3 when “Total eligible expenditure declared by beneficiaries” (column 11) is > 0 that “Total eligible costs of selected operations” (column 8) is >= “Total eligible expenditure declared by beneficiaries” (column 11).
109	Error	Validate in table 3 that no negative value is encoded for “Number of selected operations” (column 13).
110	Error	Validate when submission period is YYYY06 or YYYY12 in table 6 under non-material deprivation (non ESO4.13), for programme specific indicators, reserved indicators and common indicators requiring gender breakdown (CommonIndicatorEsf.genderBreakdown=true), and used in the programme, and having a gender target different from 0, that the sum of the gender targets equals the total target.
111	Error	Validate when submission period is YYYY06 or YYYY12 in table 10 under non-material deprivation (non ESO4.13), for quantitative programme specific indicators, reserved indicators and common indicators requiring gender breakdown (CommonIndicatorEsf.genderBreakdown=true), and used in the programme, and having a gender target different from 0, and with a term of the indicator’s measurement unit for target equal to ‘number’, that the sum of the gender targets equals the total target.
112	Error	Validate in table 1 that the “Total eligible expenditure declared by beneficiaries” per priority and specific objective is equal to the “Total eligible expenditure declared by beneficiaries” per priority and specific objective from table 4.
113	Error	Validate when submission period is YYYY06 or YYYY12 in table 12 when “For guarantees, total value of loans, equity or quasi-equity investments in final recipients guaranteed with programme resources and actually disbursed to final recipients” is > 0, that the eligible expenditure for guarantee is > 0.
114	Warning	Validate when submission period is YYYY06 or YYYY12 in table 12 when grants are selected for ‘Eligible expenditure by product”, that the amount declared for grants is <= than the amount declared for the financial product loans or equities.
115	Error	Validate when submission period is YYYY06 or YYYY12 in table 12 when a product value exists for management costs and fees for holding funds, that a type (D=Direct award or C=Competitive tender) is selected.
116	Error	Validate when submission period is YYYY06 or YYYY12 in table 12 when a product value exists for management costs and fees for specific funds, that a type (D=Direct award or C=Competitive tender) is selected.
123	Error	Validate when submission period is YYYY06 or YYYY12 in table 5 for JTF ESF+ common indicators for participants (EECO01-11) that no value has been encoded for selected operations (Implicit in web).
124	Error	Validate when submission period is YYYY06 or YYYY12 in table 9 for JTF ESF+ common indicators for participants (EECR01-04) that no value has been encoded for selected operations and for the baseline for implemented operations (Implicit in web).
125	Error	Validate in table 1 that per row columns 8, 9, 11 and 13 have each a value.
126	Error	Validate when submission period is YYYY06 or YYYY12 in table 5 that column “Selected operations” (11) has a value for ERDF, CF and EMFAF main indicators without sub-indicator (“of which”), ERDF, CF and EMFAF main indicators with sub-indicator (“of which”) and without formula, ERDF, CF and EMFAF main indicators with sub-indicator (“of which”) and with formula, JTF main OERDFCF indicators without sub-indicator (“of which”), JTF main OERDFCF indicators with sub-indicator (“of which”) and without formula, JTF main OERDFCF indicators with sub-indicator (“of which”) and with formula.
127	Error	Validate when submission period is YYYY06 or YYYY12 in table 5 having no JTF that column “Implemented operations” (12) has a value for Main indicators without sub-indicator (“of which”), Main indicators with sub-indicator (“of which”) and without formula, Sub-indicators (“of which”).
128	Error	Validate when submission period is YYYY06 or YYYY12 in table 5 having JTF that column “Implemented operations T” (12) has a value for Main ERDF/CF indicators without sub-indicator (“of which”), Main ERDF/CF indicators with sub-indicator (“of which”) and without formula, ERDF/CF sub-indicators (“of which”).
129	Error	Validate when submission period is YYYY06 or YYYY12 in table 5 having JTF that column “Implemented operations” (12) has a value per gender for ESF+ indicators.
130	Error	Validate when submission period is YYYY06 or YYYY12 in table 6 that column “Values achieved” (10) has a value per gender for common indicators requiring gender breakdown (CommonIndicatorEsf.genderBreakdown = true).
131	Error	Validate when submission period is YYYY06 or YYYY12 in table 6 that column “Values achieved T” (10) has a value for Non-material deprivation programme specific and reserved indicators, Non-material deprivation Common indicators not requiring gender breakdown (CommonIndicatorEsf.genderBreakdown = false), Material deprivation indicators (only for submission period YYYY12).
132	Error	Validate when submission period is YYYY06 or YYYY12 in table 7 that column “Values achieved” (9) has a value for Main indicator without sub-indicator (“of which”) and without formula, Main indicator with sub-indicator (“of which”) and without formula, Main indicator with sub-indicator (“of which”), with formula and optional breakdown having no achieved value (null) in all sub-indicators, Sub-indicator (“of which”) without formula and with mandatory breakdown, Sub-indicator (“of which”) without formula, with optional breakdown and sub-indicator achieved value not null.
133	Error	Validate when submission period is YYYY06 or YYYY12 in table 8 that column “Number of enterprises net of multiple support by …” (4) has a value.
134	Error	Validate when submission period is YYYY06 or YYYY12 in table 9 that columns “Selected operations - Baseline” (11) and “Selected operations - Planned achievements” (12) have a value for ERDF, CF and EMFAF main indicators without sub-indicator (“of which”), ERDF, CF and EMFAF main indicators with sub-indicator (“of which”) and without formula, ERDF, CF and EMFAF main indicators with sub-indicator (“of which”) and with formula, JTF main RERDFCF indicators without sub-indicator (“of which”), JTF main RERDFCF indicators with sub-indicator (“of which”) and without formula, JTF main RERDFCF indicators with sub-indicator (“of which”) and with formula.
135	Error	Validate when submission period is YYYY06 or YYYY12 in table 9 having no JTF that columns “Implemented operations - Baseline” (13) and “Implemented operations - Achieved” (14) have a value for Main indicators without sub-indicator (“of which”), Main indicators with sub-indicator (“of which”) and without formula, Sub-indicators (“of which”).
136	Error	Validate when submission period is YYYY06 or YYYY12 in table 9 having JTF that columns “Implemented operations - Baseline” (13) and “Implemented operations – Achieved T” (14) have a value for Main ERDF/CF indicators without sub-indicator (“of which”), Main ERDF/CF indicators with sub-indicator (“of which”) and without formula, ERDF/CF sub-indicators (“of which”).
137	Error	Validate when submission period is YYYY06 or YYYY12 in table 9 having JTF that column “Implemented operations” (14) has a value per gender for ESF+ indicators.
138	Error	Validate when submission period is YYYY06 or YYYY12 in table 10 that column “Values achieved” (11) has a value per gender for common indicators requiring gender breakdown (CommonIndicatorEsf.genderBreakdown = true).
139	Error	Validate when submission period is YYYY06 or YYYY12 in table 10 that column “Values achieved T” (11) has a value for Non-material deprivation programme specific and reserved indicators, Non-material deprivation Common indicators not requiring gender breakdown (CommonIndicatorEsf.genderBreakdown = false), Material deprivation indicators (only for submission period YYYY12).
140	Error	Validate when submission period is YYYY06 or YYYY12 in table 11 that column “Values achieved” (10) has a value for Main indicator without sub-indicator (“of which”) and without formula, Main indicator with sub-indicator (“of which”) and without formula, Main indicator with sub-indicator (“of which”), with formula and optional breakdown having no achieved value (null) in all sub-indicators, Sub-indicator (“of which”) without formula and with mandatory breakdown, Sub-indicator (“of which”) without formula, with optional breakdown and sub-indicator achieved value not null.
141	Warning	Validate when submission period is YYYY06 or YYYY12 in table 12 when financial product is guarantees and grants are selected for ‘Eligible expenditure by product”, that the amount declared for grants <= than the amount for “for guarantees, total value of loans, equity or quasi-equity investments in final recipients guaranteed with programme resources and actually disbursed to final recipients”.
142	Error	Validate in table 2 that at least one record exists for each Priority/Fund/Specific Objective/Category of Region combination of table 1 with total eligible costs of selected operations > 0.
143	Error	Validate when submission period is YYYY06 or YYYY12 in table 12 that ‘Eligible expenditure by product’ contains only one Product (‘Loan’, ‘Guarantee’ or ‘Equity or quasi-equity’) per each record.
144	Error	Validate when submission period is YYYY06 or YYYY12 in table 6 per priority, specific objective, category of region and gender for reserved indicator EECO02+04 that the achieved value equals the sum of the achieved values of the composing common output indicators EECO02 and EECO04.
145	Error	Validate when submission period is YYYY06 or YYYY12 in table 6 per priority, specific objective, category of region and gender for reserved indicator EECO02+05 that the achieved value equals the sum of the achieved values of the composing common output indicators EECO02 and EECO05.
146	Error	Validate when submission period is YYYY06 or YYYY12 in table 6 per priority, specific objective, category of region and gender for reserved indicator EECO02+04+05 that the achieved value equals the sum of the achieved values of the composing common output indicators EECO02, EECO04 and EECO05.
147	Error	Validate when submission period is YYYY06 or YYYY12 in table 6 per priority, specific objective, category of region and gender for reserved indicator EECO06+07 that the achieved value equals the sum of the achieved values of the composing common output indicators EECO06 and EECO07.
148	Error	Validate when submission period is YYYY06 or YYYY12 in table 6 per priority, specific objective, category of region and gender for reserved indicator EECO09+10 that the achieved value equals the sum of the achieved values of the composing common output indicators EECO09 and EECO10.
149	Error	Validate when submission period is YYYY06 or YYYY12 in table 6 per priority, specific objective, category of region and gender for reserved indicator EECO10+11 that the achieved value equals the sum of the achieved values of the composing common output indicators EECO10 and EECO11.
150	Error	Validate when submission period is YYYY06 or YYYY12 in table 6 per priority, specific objective, category of region and gender for reserved indicator EECO09+10+11 that the achieved value equals the sum of the achieved values of the composing common output indicators EECO09, EECO10 and EECO11.
151	Error	Validate when submission period is YYYY06 or YYYY12 in table 6 per priority, specific objective, category of region and gender for reserved indicator EECO03+04 that the achieved value equals the sum of the achieved values of the composing common output indicators EECO03 and EECO04.
152	Error	Validate for EMFAF in table 2 when “Total eligible costs of selected operations” is > 0 that “Number of selected operations” is > 0.
153	Error	Validate for EMFAF in table 1 when “Number of selected operations” is > 0 that “Total eligible costs of selected operations” is > 0.
154	Error	Validate in table 2 when specific objective is ESO4.13 that the intervention field code is 164 and that all other categorisation dimensions are null.
155	Error	Validate in table 2 that the ESF+ secondary theme 09 (not applicable) is not combined with any other ESF+ secondary theme codes.
156	Error	Validate when submission period is YYYY06 or YYYY12 in table 10 per priority, specific objective, category of region and gender, for programme specific result indicators with a measurement unit term = Percentage and linked to an output indicator, that the value achieved for the result indicator is <= 100.

An example of a validation window:

You can check the list of validation results at any time throughout the Transmission of Data :

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 Transmission of Data becomes Validated.

Prepare Transmission of Data for send to EC

Remark

The Prepare for Send can occur when a User on the highest MS Node wants to indicate that the Transmission of Data version can be prepared for sending to the Commission, once the Validation Errors have been removed and the status is Validated or Sent (from a lower Node).

To prepare the send of the Transmission of Data , the User must have the role of of Member State Managing Authority with Update or Send rights (MSMAu/s) for the funds managed by the Programme.

Click on the Prepare for send to EC button to prepare to send the Transmission of Data to the Commission:

The system will ask you to confirm the send action:

Click on Confirm to confirm.

The status of the Transmission of Data is set to Preparing for send to EC.

Send the Transmission of Data

Remark

The Send can occur when a User wants to send its recorded data on a Transmission of Data version to the Commission or to an upper Node.

The Transmission of Data can only be sent once the Validation Errors have been removed and the status is Ready To Send or Sent (from a lower node).

The "4 eyes principle" must be respected. Therefore, the User sending must be different from the User who last validated.

To send the Transmission of Data , the User must have the role of MS Managing Authority with Update rights (MSMAu).

The Sending will have to be electronically signed in accordance with Directive 1999/93/EC.

Click on the Send button to send the Transmission of Data 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 Transmission of Data version has been sent to the Commission or to an upper Node. When sent, the status is set to Sent.

Remark

When on the highest MS node, different versions of the generated “Snapshot before send” document will be available so that the sender can first verify what will be send to the Commission:

A version containing the untranslated content with the template in the Source language.
When the Source language is different from English, a version containing the untranslated content with the template in English.
When the Source language is different from English, a version containing a machine translation of the content in English with the template in English.

Request by MS for a Review of Transmission of Data

Remark

The Transmission of Data can only be revised by MS when a lower Node exists and the status is Sent (to a higher MS node), Open, Validated, Ready to Send or Review requested by MS.

This action can be used when a User wants to request a review for the Transmission of Data version sent by the Member State/Region because it is incomplete or incorrect.

To request a review for the Transmission of Data version, the User must have the role of MS Managing Authority with Update rights (MSMAu).

Follow the steps to request a review for a Transmission of Data by MS:

Select the following:

(1) Select the icon with 3 vertical dots.

(2) Click on the Request review button to request revision from the lower Node.

The system will ask you to confirm the request for revision:

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 Transmission of Data will be changed to Review requested by MS and the sender is notified of the action and its reason.

Delete the Transmission of Data

Remark

The Transmission of Data can only be deleted when:

it resides on the owner Node
the status is Open, Validated, Ready to Send or Review requested by MS
it has never been sent to the Commission before
it has no sent documents attached.

To delete the Transmission of Data , 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 Transmission of Data from the system:

Select the following:

(1) Select the icon with 3 vertical dots.

(2) Click on the Delete button to remove the Transmission of Data 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 Transmission of Data .

Cancel the Transmission of Data

Remark

The Transmission of Data can only be cancelled when a Transmission of Data version with documents was sent to the Commission and without any previous work version in status Review requested by EC. The notification utility will be called to notify the Commission of the cancel of the version.

The Cancel of a Transmission of Data is final, meaning that once cancelled there is no more possibility to submit a ToD for that submission period. There is no create new version when the last version is cancelled.

The Cancel of a ToD is only there for the exceptional case when the Programme is stopped and an already created ToD needs to be deleted but can't because there is already a ToD document sent.

The Transmission of Data version must currently reside on the User's Node and its status is Open, Validated, Ready to send or Review requested by MS and contains a sent Document and has no previous working version of the same major version in status Review requested by EC.

To cancel the Transmission of Data , the User must have the role of MS Managing Authority with Update rights (MSMAu).

Follow the steps to cancel the Transmission of Data from the system:

Select the following:

(1) Select the icon with 3 vertical dots.

(2) Click on the Cancel button to cancel the Transmission of Data 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 Transmission of Data .

On success, the status of the Transmission of Data will be changed to Cancelled.

Create a New Version of the Transmission of Data

Remark

A new version of the Transmission of Data needs to be created when on the last version of the submission period a review was requested by the Commission, or can be created when the Member State feels the need to send a reviewed version.

A new version of the Transmission of Data can only be created when the last working version for submission periods with indicator data (YYYY06, YYYY12) is in status Review requested by EC or when the last working version for submission periods without indicator data (YYYY03, YYYY08 and YYYY10) ) is in status Sent to the Commission.

To create a new version, the User must have the role of MS Managing Authority with Update rights (MSMAu).

Click on the Create button to create a new version of the Transmission of Data :

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 Transmission of Data .

On success, a new version of the Transmission of Data has been created as a copy of the last version, with a version number identical to the previous and a working version number incremented by one. Its status is set to Open.