Annual Accounts and Management Declaration(s)
PURPOSE
This document describes the actions related to transmission in SFC2021 of the Annual Accounts and Management Declaration(s) related to EAGF and EAFRD by Member State to the Commission for each agricultural financial year (‘financial year’). The deadline for such transmission is the 15 February of the year following the financial year.
For ease of reading, the document will refer to ‘Annual Accounts and Management Declaration(s)’ module as only ‘Annual Accounts’ module.
This ‘Annual Accounts and Management Declaration(s)’ module is part of the ‘Assurance package’ that includes:
Annual Accounts
Annual performance report
Audit Opinion and Certification Body report
Management declarations of the Paying Agency (PA) and the Coordinating Body CoB, as relevant
An annual summary of the final audit reports (part of the Management Declaration of the PA)
REGULATIONS
The legal base establishing the transmission of the Annual Accounts and Management Declarations is Article 33 of Implementing Regulation (EU) 2022/128 and in particular paragraphs 1(a) and 1(d).
The transmission should be ensured by the Paying Agencies (and/or Coordinating Body, in case of several Paying Agencies), as mentioned in article 3(a) and 3(d) of the Financial Regulation (EU) 2021/2116.
ROLES
Roles involved in the Annual Accounts are:
MS Paying Agency (MSPA) | Consult Annual Accounts Record Annual Accounts and Management Declaration of the Paying Agency Sign Annual Accounts and Management Declaration of the Paying Agency Validate Annual Accounts Prepare Annual Accounts for send to EC Send Annual Accounts (with signature during submission) Request for Revised Annual Accounts by MS Delete Annual Accounts Cancel Annual Accounts Create New Version of Annual Accounts |
MS Coordination Body (MSCB), in case of several Paying Agencies | Consult Annual Accounts Record Management Declaration of the Coordinating Body Sign Management Declaration of the Coordinating Body Validate Annual Accounts Prepare Annual Accounts for send to EC Send Annual Accounts (with signature during submission) Request for revised Annual Accounts by MS |
MS Certification Authority (MSCT) | Consult Annual Accounts |
MS Managing Authority (MSMA) | Consult Annual Accounts |
FUNDS
EAGF | EAFRD |
Workflow
This section shows the lifecycle to create and manage the Annual Accounts.
Click here to see the Annual Accounts workflow diagram in high resolution.

Create the Annual Accounts
Remark | The User is an identified User and has the role of MS Paying Agency with Update rights (MSPAu) for all funds covered by the Paying Agency. When creating a new Annual Accounts, all existing versions (last working version) for the same CCI and Fund must be Sent to the Commission or Cancelled. Only one Annual Accounts per Paying Agency and Financial Period can be created. For this Annual Accounts, a new version can be created by the MS when the previous version has been requested for revision by EC. New: For Financial Year >=2025, Member States with a Coordinating Body must also create a separate 'Annual Accounts and Management Declaration(s)' version (created from their National/Coordinating Body node). This separate version should be used to submit the Management Declaration of the Coordinating Body to the European Commission. |
To create the Annual Accounts, go to the Execution menu and select the Annual Accounts and Management Declaration(s) option:

In the search screen click on the Create button to create a new Annual Accounts:

You are redirected to the Annual Accounts Creation Wizard:

Enter or select the following information:
(1) Select the Paying Agency.
The Paying Agency list contains all Paying agencies valid at the moment of the creation of the Annual Accounts, for the country for which the User is registered and for which an Annual Accounts is not yet created for this financial period. The list returns the Paying Agencies code and name.
(2) The Funds field is automatically filled and contains the Fund(s) (‘EAGF’; ‘EAFRD’ or ‘EAGF, EAFRD’) covered by the selected Paying Agency.
(3) Select the Financial period.
The first version (YYYY.0) of an Annual Accounts for a given Financial period can only be created and submitted during the Declaration period which is defined as the first day after the end of Financial period until 15/02 of the following year (for Financial period 2023 from 16/10/2022 to 15/10/2023, the Declaration period is 16/10/2023 to 15/02/2024).
For FY2023, the deadline will be 15/02/2024 at midnight.
Users cannot create/send this first version after the end of the Declaration period (= Submission deadline). MS will have to send a request for extension letter to EC (from a different SFC2021 menu because the letter could be also related to APR and CBR), and the European Commission will have to extend this Declaration period for this MS only (for the relevant document(s)). The request for extension has to be submitted by 5th February at the latest.
After the end of the Declaration period, in case of an Annual Accounts version is returned by EC for revision, MS will be able to create and submit a new version.
(4) The version and the Financial period are automatically prefilled by the system at the creation of a new Annual Accounts, depending on the opened Declaration period(s) and depending on the Annual Accounts already created.
(5) Enter the National reference if applicable.
(6) Enter the Comments if necessary.
(7) Select the Source language.
The source language will be used to automatically translate the PDF report generated during the ‘Prepare for send action’.
(8) Click on Create.
The status of the Annual Accounts is Open.
Remark | On Create, when the preconditions are met, the initial Annual Accounts 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 Annual Accounts. |
Record/Edit the Annual Accounts
Remark | The User is an identified User and has the role of MS Paying Agency or MS Coordination Body with Update rights (MSPAu/MSCBu). When editing a version of an Annual Accounts, its status is Open, Validated, Ready to send or Sent at the level of the Member State or Revision requested by MS and currently resides on the User's Node. The edition of the Annual Accounts (Annual Declaration (except confirmation check boxes), Difference Explanation, Debtor Ledger, Advances, and Financial Instruments) is only possible through the upload of XML files by MS. For Annual Accounts (AA) and Management Declaration Paying Agency (MDPA): Only EAGF MSPA users can upload AA and MDPA documents related to an EAGF Paying Agency Annual Accounts. Only EAFRD MSPA users can upload AA and MDPA documents related to an EAFRD Paying Agency Annual Accounts. EAFRD and EAGF MSPA users can upload AA and MDPA documents related to an EAGF/EAFRD Paying Agency Annual Accounts; or upload AA and MDPA documents related to an EAGF Paying Agency Annual Accounts; or upload AA and MDPA documents related to an EAFRD Paying Agency Annual Accounts. For Management Declaration Coordinating Body (MDCB): Only EAGF MSCB users can upload MDCB documents related to an EAGF Paying Agency Annual Accounts. Only EAFRD MSCB users can upload MDCB documents related to an EAFRD Paying Agency Annual Accounts. EAFRD and EAGF MSCB users can upload MDCB documents related to an EAGF/EAFRD Paying Agency Annual Accounts; or upload MDCB documents related to an EAGF Paying Agency Annual Accounts; or upload MDCB documents for related to an EAFRD Paying Agency Annual Accounts. |
General
This section includes the header data to identify the main characteristics of the Annual Accounts.
Version Information
Note | The Version Information contains information on the identification and status of the Annual Accounts Version like the Paying Agency code and name, the Fund(s), the Version Number, the Financial Period and also the Status, Status date, the Current node, Last modified date, and also the National reference, Comments and Source language. Information on Linked CAP plan like Title, CCI, version, Commission decision number/date and Eligibility dates are also displayed. The Version information for the Annual Accounts cannot be modified once the version has been created, only the National reference, the Source language and the Comments can be updated. |
Click on the Edit button to enter or modify the National reference, the Source language or the comments:

The Edit details pop-up window appears:

Enter or modify the following information if needed:
(1) Enter or modify the National reference.
(2) Modify the Source language.
(3) Enter or modify the Comments.
(4) 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 Annual Accounts. 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 Annual Accounts since it was created, for example:

Documents
Note | The Documents list shows all documents uploaded against this version of the Annual Accounts 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:
(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) This Letter is for the extension of deadline for Annual Accounts
Upload & Send Documents
Multiple documents can be uploaded in the Annual Accounts.
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 are only sent - together with the encoded/uploaded data – once the Annual Accounts 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 Annual Accounts. 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 related to the same part of the annual accounts by clicking on the Add button (e.g. separate files for the annual declaration of EAGF and EAFRD under the annual declaration file type).
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 Annual Accounts 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 Annual Accounts. |
Send 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. |
Delete 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.
Validate an uploaded XML document
Remark | The system automatically validates the XML documents during the upload phase. XML file(s) in status Error (E) cannot be submitted to the Commission. MS must correct these errors by uploading a new, corrected file (or by deleting it, if necessary). |
Find the list of all XML validation rules that apply when a User upload an XML file in the system:
All XML files (Document type = ACA.ANDE / ACA.DIEX / ACA.DL / ACA.ADV1 / ACA.ADV2 / ACA.ADV2B /ACA.FIN) | |||
Code | Severity | Description | Error Message |
ACA_XML_000 | Error | Validate file structure | XML file structure NOT correct, please upload a correct file |
ACA_XML_030 | Error | Validate amount format | Amount format NOT correct. Amount format ({{arg0}}) NOT correct. The format should be [N(15,2)](=Number 15/, or ./Number 2), please upload a corrected file. |
ACA_XML_040 | Error | Validate Financial period |
|
ACA_XML_060 | Error | Validate Paying Agency code |
|
ACA_XML_070 | Error | Validate Currency code | The Currency code is not correct, if should be ‘EUR”. For Debtor Ledger, it should be ‘EUR’ or ‘{{0}}’ |
ACA_XML_080 (doesn’t apply to ACA.DL and ACA.ADV2B and ACA.FA) | Error | Validate that the Budget codes are unique | The Budget code “{{arg0}}” is not unique |
Annual Declaration in XML (Document type = ACA.ANDE) | |||
Code | Severity | Description | Error Message |
ACA_XML_100 | Error | Validate Budget codes in Annual Declaration Details: for FY >= 2024, this validation rule will prevent the MS to declare the budget code related to the Technical Assistance (08 03 01 01 00 09 00000 0000 000 00 0), as the Technical Assistance will be automatically calculated by the system | The Budget code “{{arg0}}” is not valid. It should be related to a Planned Unit Amount inside CAP Strategic plan (27 digits) present in the EAGF or EAFRD CAP Strategic Plan nomenclature for this Financial Year. Or it should be present in the outside CAP Strategic plan nomenclature for this Financial Year. It should also be also defined in the relevant section of the XML file <annualdeclarationEAGF> or <annualdeclaratioEAFRD> |
ACA_XML_110 | Error | Validate that all EAGF Budget codes declared in the Monthly Declarations for this Financial year are also declared in Annual Declaration
Details: Column 4 for EAGF (the cumulative amounts for the financial year) and the last column for EAFRD (column 10’) In the error Message, display the first 10 missing EAGF budget codes | Budget codes (amounts <> 0) declared in the EAGF Monthly Declarations during this Financial Year should also be declared in this Annual Declaration (If nothing to declare, declare 0 amount for a Budget code)
Following EAGF Budget codes are missing: xxxxxxxxxxxx xxxxxxxxxxxx xxxxxxxxxxxxx |
ACA_XML_120 | Error | Validate that all EAFRD Budget codes declared in the Quarterly Declarations for this Financial year are also declared in Annual Declaration
Details: last column of the Quarterly Declaration for EAFRD (column 10’) In the error Message, display the first 10 missing EAFRD budget codes | Budget codes (amounts <> 0) declared in EAFRD Quarterly during this Financial Year should also be declared in the Annual Declaration (If nothing to declare, declare 0 amount for a Budget code)
Following EAFRD Budget codes are missing: xxxxxxxxxxxx xxxxxxxxxxxx xxxxxxxxxxxxx |
ACA_XML_130 | Error | Validate that the details provided are modifiable in this version. Details: In case,a revised version is requested by EC and the section is set as non-modifiable by EC | The details provided in annual declaration or difference explanation for the fund “{{arg0}}” are not modifiable. |
ACA_XML_140 | Error | Validate that the EAGF declaration of expenditure of October is closed by EC (in case of EAGF budget codes uploaded in the Annual Declaration) | The EAGF declaration of expenditure of October {{arg0}} is not “Closed” by EC |
ACA_XML_150 | Error | Validate that the EAFRD declaration of expenditure YYYYQ3 is Accepted by EC (in case of EAFRD budget codes uploaded in the Annual Declaration) | The EAFRD declaration of expenditure {{arg0}} is not ‘Accepted’ by EC |
Difference Explanation in XML (Document type =ACA.DIEX) | |||
Code | Severity | Description | Error Message |
ACA_XML_200 | Error | Validate the Budget codes in Difference Explanation | The Budget code “{{arg0}}” is not valid. It should be related to a Budget code provided in the Annual Declaration. It should also be defined in the relevant section of the XML file <differencesEAGF> or <differencesEAFRD> |
ACA_XML_210 | Error | Validate that the Difference explanation code (expCode) is valid for the related Budget code | Difference Explanation code (expCode) “{{arg0}}” is not valid for Budget code “{{arg1}}” |
ACA_XML_220 | Error | Validate that the Difference amounts is explained for each Budget code | for Budget code “{{arg1}}” the Difference amount is not explained (Discrepancy after Reconciliation (column 8) should be equal to 0 EUR) |
Debtor Ledger in XML (Annex V) (Document type = ACA.DL) | |||
Code | Severity | Description | Error Message |
ACA_XML_310 | Error | Validate that amounts for ‘Balance 15 October N-1’; ‘Total new cases’; ‘Total interest’ are >= 0 | Amounts for ‘Balance 15 October N-1’ or ‘Total new cases’ or ‘Total interest’ are not all >= 0 |
ACA_XML_320 | Error | Validate that amounts for ‘Total recoveries’ and ‘Total irrecoverable’ are <=0 | Amounts for ‘Total recoveries’ or ‘Total irrecoverable’ are not <=0 |
Advances EAGF in XML (Annex 4(a)(i)) (Document type = ACA.ADV1) | |||
Code | Severity | Description | Error Message |
ACA_XML_400 | Error | Validate Budget codes in Advances EAGF Details: The list of valid Budget codes inside CAP plan should start by 08 02 02: The list of valid Budget codes outside CAP plan: 08020302 - Promotion of agricultural products — Simple programmes under shared management 08020305 - Olive oil 08020306 - Fruit and vegetables 08029901 - Completion of previous measures under the European Agricultural For WINE, the MS have to provide the budget code related to WINE sub-measures (=sub-sector): The list of valid Budget codes for Wine are: 08 02 03 07 0000 014 Promotion - measures within the Union - advances - R.1308/13, Art.45(1)(a) 08 02 03 07 0000 016 Promotion - third countries - advances - R.1308/13, Art.45(1)(b) 08 02 03 07 0000 018 Restructuring and conversion of vineyards - advances - R.1308/13, Art.46 08 02 03 07 0000 024 Investment - advances - R.1308/13, Art.50 08 02 03 07 0000 026 By product distillation - advances - R.1308/13, Art.52 08 02 03 07 0000 032 Crisis distillation - advances - R.1308/13, Art.219(1); R.2020/592, Art.3; R.2020/1275; R.2021/95 08 02 03 07 0000 034 Aid for crisis storage of wine - advances - R.1308/13, Art.219(1); R.2020/592, Art.4; R.2020/1275; R.2021/95 | The Budget code “{{arg0}}” is not valid. It should be related to a sector inside CAP Strategic plan (8 or 10 digits for other sectors) present in the CAP Strategic Plan nomenclature for this Financial year. Or it should be related to a sector/sub-sector outside CAP plan (8 digits or 15 digits) present in the EAGF outside CAP Strategic Plan nomenclature for this Financial year. It should also be also defined in the relevant section of the XML file <advanceInsideCSP> or <advanceOutsideCSP> |
Advances EAGF Wine >5M in XML (Annex 4(a)(i)) (Document type = ACA.ADVWINE) | |||
Code | Severity | Description | Error Message |
ACA_XML_450 | Error | Validate Budget codes in Advances EAGF Wine above 5 Million Details: The list of Valid Budget codes for Wine are: 08 02 03 07 0000 014 Promotion - measures within the Union - advances - R.1308/13, Art.45(1)(a) 08 02 03 07 0000 016 Promotion - third countries - advances - R.1308/13, Art.45(1)(b) 08 02 03 07 0000 018 Restructuring and conversion of vineyards - advances - R.1308/13, Art.46 08 02 03 07 0000 024 Investment - advances - R.1308/13, Art.50 08 02 03 07 0000 026 By product distillation - advances - R.1308/13, Art.52 08 02 03 07 0000 032 Crisis distillation - advances - R.1308/13, Art.219(1); R.2020/592, Art.3; R.2020/1275; R.2021/95 08 02 03 07 0000 034 Aid for crisis storage of wine - advances - R.1308/13, Art.219(1); R.2020/592, Art.4; R.2020/1275; R.2021/95 | The Budget code “{{arg0}}” is not valid. It should be related to a WINE sub-sector (15 digits sub-items that start by 08 02 03 07) presents in the EAGF outside CAP Strategic Plan nomenclature for this Financial year. |
ACA_XML_460 | Error | Validate that Budget codes in Advances EAGF Wine above 5 Million are also reported in Advances EAGF | The Budget code “{{arg0}}” is not reported in ‘Advances EAGF’ |
Advances EAFRD 2023-2027 in XML (Annex 4(d)) (Document type = ACA.ANDE) | |||
Code | Severity | Description | Error Message |
ACA_XML_500 | Error | Validate Budget codes in Advances EAFRD 2023-2027 | The Budget code “{{arg0}}” is not valid. It should be related to an EAFRD Type of Intervention (12 digits) defined in the EAFRD inside CAP Strategic Plan nomenclature for this Financial Year |
ACA_XML_510 | Error | Validate that Advances EAFRD 2023-2027 are not declared for articles 75(INSTAL), 76(RISK) and 78(KNOW) | For Budget Code {{0}}, Advances EAFRD 2023-2027 cannot be declared for articles 75(INSTAL), 76(RISK) and 78(KNOW) |
ACA_XML_520 | Error | Validate that the CCI (if reported) for Advances EAFRD related to the previous programming 2014-2022 period matches the pattern 2014CC06RDTTXXX | In Advances EAFRD, CCI {{0}} related to the previous programming 2014-2022 is not valid, it should match the pattern 2014CC06RDTTXXX |
ACA_XML_530 | Error | Validate that Advances EAFRD related to the previous programming 2014-2022 period, for a given budget code, are either reported by CCI or either globally for all regions but not both | In Advances EAFRD related to the previous programming 2014-2022, for budget code {{0}}, Advances should either be reported by CCI or either globally for all regions but not both |
Advances EAFRD 2023-2027 above 5 million in XML (Annex 4(d)(i)) (Document type = ACA.ADV2B) | |||
Code | Severity | Description | Error Message |
ACA_XML_620 | Error | Validate that the CCI (if reported) for Advances EAFRD above 5 million related to the previous programming 2014-2022 period matches the pattern 2014CC06RDTTXXX | In Advances EAFRD above 5 million, CCI {{0}} related to the previous programming 2014-2022 is not valid, it should match the pattern 2014CC06RDTTXXX |
ACA_XML_630 | Error | Validate that Advances EAFRD above 5 million related to the previous programming 2014-2022 period, are either reported by CCI or either globally for all regions but not both | Advances EAFRD above 5 million, related to the previous programming 2014-2022 should either be reported by CCI or either globally for all regions but not both |
ACA_XML_640 | Error | Validate in Advances EAFRD above 5 million related to the previous programming 2014-2022 period, that the CCI is unique (if reported by CCI) | In Advances EAFRD above 5 million related to the previous programming 2014-2022 period, CCI {{0}} is not unique |
Financial Instruments in XML (Annex 5(d)) (Document type = ACA.FIN) | |||
Code | Severity | Description | Error Message |
ACA_XML_700 | Error | Validate Budget codes in Financial Instrument | The Budget code “{{arg0}}” is not valid. It should be related to an EAFRD Type of Intervention (12 digits) defined in the EAFRD inside CAP Strategic Plan nomenclature for this Financial Year |
ACA_XML_710 | Error | Validate that Financial Instruments – EAFRD Contribution are not declared for articles 70(ENVCLIM), 71(ANC) and 72(ASD) | For Budget Code {{0}}, Financial Instruments – EAFRD Contribution cannot be declared for articles 70(ENVCLIM), 71(ANC) and 72(ASD) |
ACA_XML_720 | Error | Validate in Financial Instruments – EAFRD Contribution, that for each Type of Intervention reported, at least one Intervention/PUA is financed by Financial Instruments in the linked CSP | Type of Intervention {{0}}, is not financed by Financial Instrument in the linked CSP |
Financial Instruments – Public Expenditure in XML (Document type = ACA.PUB) | |||
Code | Severity | Description | Error Message |
ACA_XML_800 | Error | Validate that combination Budget code and Funding agreement code is unique | In the table Financial Instruments, the combination of Budget code “{{arg0}}” and Funding agreement code “{{arg0}}” is not unique |
ACA_XML_810 | Error | Validate Funding Agreement (if not available in the Annual Accounts of the Coordinating Body, Funding Agreements should be retrieved from the Q3 DoE) | Funding Agreement code “{{arg0}}” is not valid |
ACA_XML_850 Duplicate with the one below | Error | Validate that Financial Instruments – Public Expenditure are not declared for articles 70(ENVCLIM), 71(ANC) and 72(ASD) | For Budget Code {{0}}, Financial Instruments – Public Expenditure cannot be declared for articles 70(ENVCLIM), 71(ANC) and 72(ASD) |
ACA_XML_840 | Error | Validate that Budget codes reported in Financial Instruments – Public Expenditure are financed by Financial Instrument in the linked CSP | For Budget Code {{0}}, Financial Instruments – Public Expenditure is not financed by Financial Instrument in the linked CSP |
Financial Instruments – Funding Agreement in XML (for FY 2024 onwards) (Document type = ACA.FA) | |||
Code | Severity | Description | Error Message |
ACA_XML_900 | Error | Validate that the Funding Agreement code is unique | The Funding Agreement code “{{arg0}}” is not unique |
Annex II (Irregularities) in XML (Document type = ACA.14DLANX2) | |||
Code | Severity | Description | Error Message |
ACA_XML_000 | Error | if(( NOT is_empty($e)), ( NOT matches($e, '[0-9]+[.|,]?[0-9]*E[+][0-9]*')), true) | %e% cannot be accepted. - Additional Info: Number in scientific notation is not allowed. |
ACA_XML_000 | Error | if(( NOT is_empty($h)), ( NOT matches($h, '[0-9]+[.|,]?[0-9]*E[+][0-9]*')), true) | %H% cannot be accepted. - Additional Info: Number in scientific notation is not allowed |
ACA_XML_000 | Error | ( NOT is_empty($b) ) | The obligatory field b (%b%) is not filled in. See GL No 5 |
ACA_XML_000 | Error | if(( NOT is_empty($b)), in_list($b, 'IRREG_B'), true) | Value specified is not a valid code for b(%B%). Valid codes for this field are in GL No 5 |
ACA_XML_000 | Error | ( NOT is_empty($c) ) | The obligatory field C (%C%) is not filled in. See GL No 5 |
ACA_XML_000 | Error | ( NOT is_empty($d) ) | The obligatory field d (%d%) is not filled in. See GL No 5 |
ACA_XML_000 | Error | ( NOT is_empty($e) ) | The obligatory field e (%e%) is not filled in. See GL No 5 |
ACA_XML_000 | Error | if(( NOT is_empty($g) and $AA = 'O'), in_list($g, 'IRREG_G'), true) | value %G% is not a valid code for g (Y/N). See GL No 5 |
ACA_XML_000 | Error | ( NOT is_empty($h) ) | The obligatory field h (%h%) is not filled in. See GL No 5 - item 2.11 |
ACA_XML_000 | Error | ( NOT is_empty($k) ) | The obligatory field k (%k%) is not filled in. See GL No 5 |
ACA_XML_000 | Error | if(( NOT is_empty($k)), in_list($k, 'IRREG_K'), true) | value %K% is not a valid code for k. See GL No 5 item 2.16 |
ACA_XML_000 | Error | if(( NOT is_empty($l)),$l>=0,true) | The amount to be recovered %l% must be positive |
ACA_XML_000 | Error | if(( NOT is_empty($n)),$n<= 0, true) | The value %N% of field N should be negative. See GL No 5 |
ACA_XML_000 | Error | if(( NOT is_empty($o)), $o<=0, true) | The value %O% for field O should be negative. See GL No 5 |
ACA_XML_000 | Error | ( NOT is_empty($s) ) | A value for field s is mandatory. See GL No 5 |
ACA_XML_000 | Error | if(( NOT is_empty($s)), $s<=0, true) | %S% is not a correct value for field S. See GL No 5 |
ACA_XML_000 | Error | ( NOT is_empty($u) ) | A value for u is requested. See GL No 5 |
ACA_XML_000 | Error | (not is_empty($AA)) | The obligatory field AA (%AA%) is not filled in. See GL No 5 |
ACA_XML_000 | Error | if(( NOT is_empty($AA)), if(( NOT in_list($AA, 'IRREG_AA')), ( NOT in_list(upper($AA), 'IRREG_AA')), true), true) | The value in field AA (%AA%) is not a correct code. Please note that values have to be in UPPERCASE |
ACA_XML_000 | Error | if(( NOT is_empty($BB)),$BB>=0, true) | The value specified (%BB%) is not valid for BB. See GL No 5 |
ACA_XML_000 | Error | if(( NOT is_empty($AA)), in_list($AA, 'IRREG_AA'), true) | The value in field AA (%AA%) is not a correct code |
ACA_XML_000 | Error | if(not is_empty($q),in_list($q,'IRREG_Q'),true) | The value %q% specified in column Q is not valid - see GL No 5. |
ACA_XML_000 | Error | if(( NOT is_empty($L1)),$L1>=0,true) | The value in L1 %L1% should be positive. See GL No 5 |
ACA_XML_000 | Error | if(( NOT is_empty($L2)),$L2>=0,true) | The value in L2 %L2% should be positive. See GL No 5 |
ACA_XML_000 | Error | if(( NOT is_empty($Y1) and $C > 2015),$Y1>=0,true) | The value of Y1 (%Y1%) cannot be negative. See GL No 5 item 2.19 |
ACA_XML_000 | Error | if(( NOT is_empty($Y2) and $C > 2015),$Y2>=0,true) | The value of Y2 (%Y2%) cannot be negative. See GL No 5 item 2.19 |
ACA_XML_000 | Error | if(( NOT is_empty($o1)),$o1<=0,true) | The value %O1% for field O1 should be negative. See GL No 5 |
ACA_XML_000 | Error | if(( NOT is_empty($o2)),$o2<=0,true) | The value %O2% for field O2 should be negative. See GL No 5 |
ACA_XML_000 | Error | if((NOT is_empty($z)),$z>=0,true) | The interest of the financial year must be positive |
ACA_XML_000 | Error | if(( NOT is_empty($s1)), $s1<=0, true) | %S1% is not a correct value for field S1. See GL No 5 |
ACA_XML_000 | Error | if(( NOT is_empty($s2)), $s2<=0, true) | %S2% is not a correct value for field S2. See GL No 5 |
ACA_XML_000 | Error | if($b='4',$i in ('N','Y'),true) | The value in field i (%I%) is not correct for the indicated Fund (%B%). See GL No5 |
ACA_XML_000 | Error | if($AA = 'N', is_empty($G),true) | For 'new' cases, a value for G is not requested - see GL No 5 |
ACA_XML_000 | Error | if(not is_empty($f),length($f)<=250,true) | The length of field f exceeds the maximum length of 250 characters |
ACA_XML_10000 | Error | Validate Paying Agency code | Paying Agency code “{{arg0}}” is not valid. |
ACA_XML_10001 | Error | Validate Currency code | Currency code {{arg0}} it is not a valid one. |
ACA_XML_10003 | Error | Validate Financial Year | Financial year “{{arg0}}” is not valid. |
ACA_XML_10201 | Error | Validate that in Annex II, element J >=1963 and J<=2014 | The value {{arg0}} is unlikely for J. See GL No 5 for more information |
ACA_XML_10202 | Error | Validate that in Annex II, element J is not null when AA = O | J cannot be null when AA = O. See GL No 5 for more information |
ACA_XML_10205 | Error | Validate that in Annex II, element L is not null when AA = O | L cannot be null when AA = O. See GL No 5 for more information |
ACA_XML_10207 | Error | Validate that in Annex II, element M is not null when AA = O | M cannot be null when AA = O. See GL No 5 for more information |
ACA_XML_10208 | Error | Validate that in Annex II, element N is not null when AA = O | N cannot be null when AA = O. See GL No 5 for more information |
ACA_XML_10211 | Error | Validate that in Annex II, element O is not null when AA = O | O cannot be null when AA = O. See GL No 5 for more information |
ACA_XML_10212 | Error | Validate that in Annex II, element P is not null when AA = O and O!=0 | A value is requested for column P because ´O´ <> 0. See GL No 5 |
ACA_XML_10214 | Error | Validate that in Annex II, element R is not null for AA=O | A value for R is mandatory |
ACA_XML_10215 | Error | Validate that in Annex II, element S is not null for AA=O | A value for S is mandatory |
ACA_XML_10222 | Error | Validate that in Annex II, element T is not null AA=O | For 'old' cases, a value for T is mandatory. See GL No 5 |
ACA_XML_10223 | Error | Validate that in Annex II, element T = (L) + (M) + (N) + (O) when AA=O | The value of T ({{arg0}}) does not correspond to the total as defined in GL No 5 |
ACA_XML_10225 | Error | Validate that in Annex II, element U >=0 and <=T when AA=O | The value specified ({{arg0}}) is not valid for U. See GL No 5 |
ACA_XML_10522 | Error | Validate that in Annex II, element BB is not null for AA=N | A value for BB is requested. See GL No 5 |
ACA_XML_10524 | Error | Validate that in Annex II, element T1 is not null when AA=N | A value for T1 is requested. See GL No 5 |
ACA_XML_10525 | Error | Validate that in Annex II, element T2 is not null when AA=N | A value for T2 is requested. See GL No 5 |
ACA_XML_105250 | Error | Validate that in Annex II, element V1 is not null when c>=2016 | The obligatory field V1 is not filled in - See GL No 5 |
ACA_XML_10526 | Error | Validate that in Annex II, element T1 is caculated correctly when x between FY and FY-1 | The value specified for T1 ({{arg0}}) is not valid. See GL No 5 Additional info: L1+O1+R1+S1=T1 |
ACA_XML_105260 | Warning | Validate that in Annex II, element V1 is between 1973 and C | The value in field V1 ({{arg0}}) is unlikely |
ACA_XML_10527 | Error | Validate that in Annex II, element T1 is caculated correctly when x between FY and FY-1 | The value specified for T1 ({{arg0}}) is not valid. See GL No 5 Additional info: Y1+O1+R1+S1=T1 |
ACA_XML_10528 | Error | Validate that in Annex II, element T2 is calculated correctly when x between FY and FY-1 | The value specified ({{arg0}}) for T2 is not valid. See GL No 5 |
ACA_XML_10529 | Error | Validate that in Annex II, element T2 is caculated correctly when x before FY-1 | The value specified {{arg0}} for T2 is not valid. See GL No 5 |
ACA_XML_10542 | Error | Validate that in Annex II, element P is not null and B in (3,5,6) then p=c | The value {{arg0}} of column P should be equal to the financial year C = {{arg1}} |
ACA_XML_105420 | Error | Validate that in Annex II, element V2 is not null when C>=2016 | A value in field V2 must be supplied as of FY2016 |
ACA_XML_10543 | Error | Validate that in Annex II, element P is not null when O1 + O2 !=0 | A value is requested for column p because ('O1' + 'O2') != 0. See GL No 5 |
ACA_XML_10544 | Error | Validate that in Annex II, element Q is not null when O != 0 and AA=O | A reason for Q must be indicated - see GL No 5 |
ACA_XML_10545 | Error | Validate that in Annex II, element Q is not null when O1 + O2 != 0 and AA=N | A reason for Q must be indicated - see GL No 5 |
ACA_XML_10546 | Error | Validate that in Annex II, element W is not null | For new cases, a date must be given for W. See GL No 5 |
ACA_XML_10547 | Error | Validate that in Annex II, element X is not null when AA=N | For new cases, a date must be given for X |
ACA_XML_10548 | Error | Validate that in Annex II, element L1 is not null for AA=N | A value for L1 is mandatory |
ACA_XML_10550 | Error | Validate that in Annex II, element L2 is not null for AA=N | A value for L2 is mandatory |
ACA_XML_10552 | Error | Validate that in Annex II, element Y1 is not null when AA=N | A value for Y1 is mandatory. See GL No 5 |
ACA_XML_10555 | Error | Validate that in Annex II, element Y2 is not null when AA=N | A value for Y2 is mandatory. See GL No 5 |
ACA_XML_10558 | Error | Validate that in Annex II, element O1 is not null for AA=N | A value for O1 is mandatory |
ACA_XML_10560 | Error | Validate that in Annex II, element O2 is not null for AA=N | A value for O2 is mandatory |
ACA_XML_10562 | Error | Validate that in Annex II, element Z is not null | A value for field Z is mandatory |
ACA_XML_10564 | Error | Validate that in Annex II, element G must be equal to ´Y´ if AA = N | For new cases, value {{arg0}} for G must equal Y. See GL No 5 |
ACA_XML_105640 | Error | Validate that in Annex II, element R1 is not null for AA=N | A value for R1 is mandatory |
ACA_XML_10565 | Error | Validate that in Annex II, element U >=0 and <=T1+T2 when AA=N | The value specified ({{arg0}}) is not valid for U. See GL No 5 |
ACA_XML_105650 | Error | Validate that in Annex II, element R2 is not null for AA=N | A value for R2 is mandatory |
ACA_XML_10566 | Error | Validate that in Annex II, element S1 is not null for AA=N | A value for S1 is mandatory |
ACA_XML_10568 | Error | Validate that in Annex II, element S2 is not null for AA=N | A value for S2 is mandatory |
ACA_XML_10570 | Error | Validate that in Annex II, element T = (T1) + (T2) when AA=N | The value of T ({{arg0}}) does not correspond to the total as defined in GL No 5 |
ACA_XML_10642 | Error | Validate that in Annex II, element G must be given if AA = O | For 'old' (AA = O) cases, a value must be given for G - see GL No 5. |
ACA_XML_10662 | Error | Validate that in Annex II, element I must be given if B in (4,5) | For the indicated Fund (B={{arg0}}), a value must be given in I. See GL No 5 |
ACA_XML_10664 | Error | Validate that in Annex II, element I = Y if B = 5 | The value in field I ({{arg0}}) is not correct for the indicated Fund (B={{arg1}}). TRDI has been closed |
ACA_XML_10665 | Error | Validate that in Annex II, element I is empty if B in (3,6) | For the indicated Fund (B={{arg0}}), no value is requested in I - see GL No 5 |
ACA_XML_10682 | Error | Validate that in Annex II, element P is not null and B=4 then P>=2007 and P<=C | The value ({{arg0}}) of column p should should be between 2007 and current financial year C ({{arg1}}) |
ACA_XML_10923 | Error | Validate that in Annex II, element Q is null when O = 0 and AA=O | There is no irrecoverable amount in O, therefore no reason should be indicated in field Q - see GL No 5 |
ACA_XML_10924 | Error | Validate that in Annex II, element Q is null when O1 + O2 = 0 and AA=N | There is no irrecoverable amount indicated in O1 or O2, therefore no reason should be indicated in field Q - see GL No 5 |
ACA_XML_10925 | Error | Validate that in Annex II, element P is null when O=0 and AA=N | There is no irrecoverable amount indicated in O; therefore field P should remain empty - see GL No 5 |
ACA_XML_10926 | Error | Validate that in Annex II, element P is null when O1 +O2 == 0 and AA=N | There is no irrecoverable amount indicated in O1 or O2; therefore field P should remain empty - see GL No 5 |
ACA_XML_10982 | Error | Validate that in Annex II, element V1 <= C | The value in field V1 ({{arg0}}) cannot be higher than the current financial year |
ACA_XML_11022 | Warning | Validate that in Annex II, element E, Q5 is only expected for debt cases originating from EAFRD 2007-2013 | The value in column ´E´ ({{arg0}}) is unlikely. Q5 is only expected for debt cases originating from EAFRD 2007-2013 |
ACA_XML_11882 | Error | Validate that in Annex II, element V2 is correct for B=5 | The value in field V2 ({{arg0}}) is not a correct code for fund B={{arg1}} |
ACA_XML_11883 | Warning | Validate that in Annex II, element V2 is correct for V1<=2003 | The value in field V2 ({{arg0}}) is not a correct code. Debts related to expenditure till FY2003 (V1 = {{arg1}}) should be identified with 'BXX' |
ACA_XML_11884 | Error | Validate that in Annex II, element V2 is correct for B=4 | The value in field V2 ({{arg0}}) is not a correct code. |
ACA_XML_11885 | Error | Validate that in Annex II, element V2 is correct for B=3, v1>=2007 and v1<=2020 | The value in field V2 ({{arg0}}) is not a correct code considering the value in V1 ({{arg1}}) |
ACA_XML_11886 | Error | Validate that in Annex II, element V2 is correct for B=6, and v1<=2020 | The value in field V2 ({{arg0}}) is not a correct code considering the value in V1 ({{arg1}}) |
ACA_XML_11887 | Error | Validate that in Annex II, element V2 is correct for B=3, and v1>=2021 | The value in field V2 ({{arg0}}) is not a correct code considering the value in V1 ({{arg1}}) |
ACA_XML_11888 | Error | Validate that in Annex II, element V2 is correct for B=6, and v1>=2021 | The value in field V2 ({{arg0}}) is not a correct code considering the value in V1 ({{arg1}}) |
ACA_XML_11903 | Error | Validate that in Annex II, element V2 is correct for B=3, and v1>=2004,v1<2007 | The value in field V2 ({{arg0}}) is not a correct code considering the value in V1 ({{arg1}}) |
ACA_XML_11904 | Error | Validate that in Annex II, element V2 is correct for B=3, and v1>=2004,v1<2007 | The value in field V2 ({{arg0}}) is not a correct code considering the value in V1 ({{arg1}}) |
ACA_XML_15300 | Error | Validate that in Annex II, element X is valid | The value specified ({{arg0}}) for X is not a valid date. See GL No 5 |
Annex II - total in XML (Document type = ACA.14DLANX2TOT) | |||
Code | Severity | Description | Error Message |
ACA_XML_000 | Error | ( NOT is_empty($b) ) | The obligatory field B is not filled in. See GL No 5 |
ACA_XML_000 | Error | if(( NOT is_empty($b)), in_list($b, 'IRREG_B'), true) | The value (%B%) is not valid for B. Valid codes for this field are in GL No 5 |
ACA_XML_000 | Error | if(NOT is_empty($Bal_I),$Bal_I>=0, true) | The value %Bal_I% for field Bal_I should be positive. See GL No 5 |
ACA_XML_000 | Error | ( NOT is_empty($BAL_P) ) | A value for Bal_P is requested. See GL No 5 |
ACA_XML_000 | Error | if(NOT is_empty($Bal_P),$Bal_P>=0, true) | The value in Bal_P %Bal_P% should be positive. See GL No 5 |
ACA_XML_000 | Error | ( NOT is_empty($c) ) | The obligatory field C is not filled in. See GL No 5 |
ACA_XML_000 | Error | if(( NOT is_empty($newc_I)),$newc_I>=0,true) | The value in newc_I ( %newc_I%) should be positive.See GL No 5 |
ACA_XML_000 | Error | if(( NOT is_empty($newc_p)),$newc_p>=0,true) | The value in NewC_P (%NewC_P%) should be positive. |
ACA_XML_000 | Error | ( NOT is_empty($O1) ) | A value for field O1 is mandatory. See GL No 5 |
ACA_XML_000 | Error | if(( NOT is_empty($O1)),$O1<=0,true) | The value in O1 (%O1%) should be negative. See GL No 5 |
ACA_XML_000 | Error | if(( NOT is_empty($O2)),$O2<=0,true) | The value in O2 (%O2%) should be negative. See GL No 5 |
ACA_XML_000 | Error | ( NOT is_empty($R1) ) | A value for field R1 is mandatory. See GL No 5 |
ACA_XML_000 | Error | ( NOT is_empty($S1) ) | A value for field S1 is mandatory. See GL No 5 |
ACA_XML_000 | Error | if(( NOT is_empty($S1)),$S1<=0,true) | The value in S1 (%S1%) should be negative. See GL No 5 |
ACA_XML_000 | Error | if(( NOT is_empty($S2)),$S2<=0,true) | The value in S2 (%S2%) should be negative. See GL No 5 |
ACA_XML_000 | Error | ( NOT is_empty($T1) ) | A value for field T1 is mandatory. See GL No 5 |
ACA_XML_000 | Error | if(( NOT is_empty($Z)),$Z>=0,true) | The value in Z (%Z%) should be positive. See GL No 5 |
ACA_XML_10000 | Error | Validate Paying Agency code | Paying Agency code “{{arg0}}” is not valid. |
ACA_XML_10001 | Error | Validate Currency code | Currency code {{arg0}} it is not a valid one. |
ACA_XML_10003 | Error | Validate Financial Year | Financial year “{{arg0}}” is not valid. |
ACA_XML_11622 | Error | Validate that in Annex II Total if AA = ´O´ then Bal_I must be empty | Bal_I must be empty when AA = ´O´ |
ACA_XML_11623 | Error | Validate that in Annex II Total if AA = ´N´ then Bal_I must not be null or empty | Bal_I cannot be empty when AA = ´N´ |
ACA_XML_11624 | Error | Validate that in Annex II Total if AA = ´N´ then NewC_P must not be null or empty | NewC_P cannot be empty when AA = ´N´ |
ACA_XML_11625 | Error | Validate that in Annex II Total if AA = ´O´ then NewC_P must empty | NewC_P must be empty when AA = ´O´ |
ACA_XML_11626 | Error | Validate that in Annex II Total if AA = ´O´ then NewC_I must be empty | NewC_I must be empty when AA = ´O´ |
ACA_XML_11627 | Error | Validate that in Annex II Total if AA = ´N´ then NewC_I must not be null or empty | NewC_I cannot be empty when AA = ´N´ |
ACA_XML_11629 | Error | Validate that in Annex II Total if AA = ´N´ then R2 must not be null or empty | R2 cannot be empty when AA = ´N´ |
ACA_XML_11629 | Error | Validate that in Annex II Total if AA = ´O´ then R2 must be empty | R2 must be empty when AA = ´O´ |
ACA_XML_11630 | Error | Validate that in Annex II Total if AA = ´N´ then Z must not be null or empty | Z cannot be empty when AA = ´N´ |
ACA_XML_11631 | Error | Validate that in Annex II Total if AA = ´O´ then Z must be empty | Z must be empty when AA = ´O´ |
ACA_XML_11634 | Error | Validate that in Annex II Total if AA = ´N´ then S2 must not be null or empty | S2 cannot be empty when AA = ´N´ |
ACA_XML_11635 | Error | Validate that in Annex II Total if AA = ´O´ then S2 must be empty | S2 must be empty when AA = ´O´ |
ACA_XML_11638 | Error | Validate that in Annex II Total if AA = ´N´ then O2 must not be null or empty | O2 cannot be empty when AA = ´N´ |
ACA_XML_11639 | Error | Validate that in Annex II Total if AA = ´O´ then O2 must be empty | O2 must be empty when AA = ´O´ |
ACA_XML_11641 | Error | Validate that in Annex II Total if AA = ´N´ then T2 must not be null or empty | T2 cannot be empty when AA = ´N´ |
ACA_XML_116410 | Error | Validate that in Annex II Total if AA = ´O´ then T2 must be empty | T2 must be empty when AA = ´O´ |
ACA_XML_11642 | Error | Validate that in Annex II Total that (T1) = (Bal_P) + (R1) + (S1) + (O1 when AA = O | T1 ({{arg0}}) must be equal to Bal_P + R1 + S1 + O1 ({{arg1}}) when AA = O |
ACA_XML_11643 | Error | Validate that in Annex II Total that (T1) = (NewC_P) + (R1) + (S1) + (O1) when AA = N | T1 ({{arg0}}) must be equal to Bal_P + NewC_P + R1 + S1 + O1 ({{arg1}}) when AA = N |
ACA_XML_11644 | Error | Validate that in Annex II Total (T2) = (Bal_I) + (NewC_I) + (R2) + (Z)+ (S2) + (O2) when AA = N | T2 ({{arg0}}) must be equal to Bal_I + NewC_I + R2 + Z+ S2 + O2 ({{arg1}}) when AA = N |
Annex III in XML (Document type = ACA.14DLANX3) | |||
Code | Severity | Description | Error Message |
ACA_XML_000 | Error | ( NOT is_empty($A) ) | The obligatory field a (%A%) is not filled in. See GL No 5 |
ACA_XML_000 | Error | ( NOT is_empty($B) ) | The obligatory field B (%B%) is not filled in. See GL No 5 |
ACA_XML_000 | Error | if(( NOT is_empty($B)), in_list($B, 'IRREG_B'), true) | Value entered for B (%B%) is not valid. Valid codes for this field are in GL No 5 |
ACA_XML_000 | Error | ( NOT is_empty($C) ) | The obligatory field C (%C%) is not filled in. See GL No 5 |
ACA_XML_000 | Error | ( NOT is_empty($D_III) ) | The obligatory field D_III is not filled in. See GL No 5 |
ACA_XML_000 | Warning | if(( NOT is_empty($D_III)), $D_III>=0, true) | The value in D_III (%D_III%) should be positive. Please verify your data before final submission. A negative amount must be explained by the Paying Agency/Coordinating Body and confirmed by the Certification Body, via email to AGRI-FINANCIAL-AUDIT@ec.europa.eu |
ACA_XML_000 | Error | ( NOT is_empty($E_III) ) | A value for field E_III is mandatory. See GL No 5 |
ACA_XML_000 | Error | if((NOT is_empty($E_III)),$E_III>=0,true) | %E_III% is not a correct value for field E_III (should be positive). See GL No 5 |
ACA_XML_000 | Error | ( NOT is_empty($F_III) ) | A value for field F_III is mandatory. See GL No 5 |
ACA_XML_000 | Warning | if(( NOT is_empty($F_III)), $F_III<=0, true) | The value in F_III (%F_III%) should be negative. Please verify your data before final submission. A positive amount must be explained by the Paying Agency/Coordinating Body and confirmed by the Certification Body, via email to AGRI-FINANCIAL-AUDIT@ec.europa.eu |
ACA_XML_000 | Error | (NOT is_empty($G_III)) | A value for field G_III is mandatory. See GL No 5 |
ACA_XML_000 | Error | ( NOT is_empty($H_III) ) | A value for field H_III is mandatory. See GL No 5 |
ACA_XML_000 | Warning | if(( NOT is_empty($H_III)), $H_III>=0, true) | The value in H_III (%H_III%) should be positive. Please verify your data before final submission. A negative amount must be explained by the Paying Agency/Coordinating Body and confirmed by the Certification Body, via email to AGRI-FINANCIAL-AUDIT@ec.europa.eu |
ACA_XML_000 | Error | ( NOT is_empty($I_III) ) | The obligatory field I_III is not filled in. See GL No 5 |
ACA_XML_000 | Error | if(( NOT is_empty($I_III)), in_list($I_III, 'IRREG_I_III'), true) | The value %I_III% is not valid for field I_III. See GL No 5 |
ACA_XML_000 | Error | ( NOT is_empty($A) ) | The obligatory field a (%A%) is not filled in. See GL No 5 |
ACA_XML_000 | Error | ( NOT is_empty($B) ) | The obligatory field B (%B%) is not filled in. See GL No 5 |
ACA_XML_000 | Error | if(( NOT is_empty($B)), in_list($B, 'IRREG_B'), true) | Value entered for B (%B%) is not valid. Valid codes for this field are in GL No 5 |
ACA_XML_000 | Error | ( NOT is_empty($C) ) | The obligatory field C (%C%) is not filled in. See GL No 5 |
ACA_XML_10000 | Error | Validate Paying Agency code | Paying Agency code “{{arg0}}” is not valid. |
ACA_XML_10001 | Error | Validate Currency code | Currency code {{arg0}} it is not a valid one. |
ACA_XML_10003 | Error | Validate Financial Year | Financial year “{{arg0}}” is not valid. |
ACA_XML_11588 | Error | Validate that in Annex III the value of H_III corresponds to the total as defined H_III = D_III + E_III + F_III + G_III | The value in H_III ({{arg0}}) it is not equal to the total D_III + E_III + F_III + G_III ({{arg1}}) |
Detailed table on recoveries related to previous programming periods in XML (Document type = ACA.14DLREC) | |||
Code | Severity | Description | Error Message |
ACA_XML_000 | Error | not is_empty($A) | The obligatory field A is not filled in. See GL No 5 |
ACA_XML_000 | Error | (not is_empty($AA)) | The obligatory field AA is not filled in. See GL No 5 |
ACA_XML_000 | Error | if(( NOT is_empty($AA)), if(( NOT in_list($AA, 'IRREG_AA')), ( NOT in_list(upper($AA), 'IRREG_AA')), true), true) | The value in field AA (%AA%) is not a correct code. Please note that values have to be in UPPERCASE |
ACA_XML_000 | Error | if(( NOT is_empty($AA)), in_list($AA, 'IRREG_AA'), true) | The value in field AA (%AA%) is not a correct code |
ACA_XML_000 | Error | ( NOT is_empty($B) ) | The obligatory field B is not filled in. See GL No 5 |
ACA_XML_000 | Error | if(( NOT is_empty($b)), in_list($b, 'IRREG_B'), true) | The value %B% is not valid for B. Valid codes for this field are in GL No 5 |
ACA_XML_000 | Error | ( NOT is_empty($B_21) ) | A value for field B_21 is mandatory. See GL No 5 |
ACA_XML_000 | Error | ( NOT is_empty($c) ) | The obligatory field C (%C%) is not filled in. See GL No 5 |
ACA_XML_000 | Error | not is_empty($C_21) | A value for field C_21 is mandatory. See GL No 5 |
ACA_XML_000 | Error | if(( NOT is_empty($C_21)), $C_21>=0, true) | %C_21% is not a correct value for field C_21 (should be positive). See GL No 5 |
ACA_XML_000 | Error | ( NOT is_empty($D_21) ) | A value for field D_21 is mandatory. See GL No 5 |
ACA_XML_000 | Error | if(( NOT is_empty($D_21)),$D_21=$S+$B_21-$C_21, true) | The value of D_21 (%D_21%) does not correspond to the total as defined in GL No 5 |
ACA_XML_000 | Error | ( NOT is_empty($s) ) | A value for field S is mandatory. See GL No 5 |
ACA_XML_000 | Error | if(( NOT is_empty($s)), $s>=0, true) | %S% is not a correct value for field S (should be positive). See GL No 5 |
ACA_XML_10000 | Error | Validate Paying Agency code | Paying Agency code “{{arg0}}” is not valid. |
ACA_XML_10001 | Error | Validate Currency code | Currency code {{arg0}} it is not a valid one. |
ACA_XML_10003 | Error | Validate Financial Year | Financial year “{{arg0}}” is not valid. |
ACA_XML_11557 | Error | Validate that in detailed table on recoveries the value of D_21 corresponds to the total as defined D_21 = S + B_21 - C_21 | The value in D_21 ({{arg0}}) it is not equal to the total S + B_21 - C_21 ({{arg1}}) |
Consult an uploaded XML document
Note | For each XML file displayed on the screen, the number of Errors (E) and Warnings (W) that occurred during the execution of the XML business rules validation will be displayed. |
Click on the arrow to consult the details of the uploaded document:

The file details now appear:

Different actions are possible based on the File Status (OK or ERROR):
(1) View the file.
(2) View the list of Errors and Warnings detected in the file.
In case of Warnings only, the File Status will be OK.
(3) View the file with the Errors and Warnings on the corresponding lines.
(4) Delete the file. This feature is useful if a file is used for testing purposes or to delete a file with errors.
Observations
Note | This section is used to provide any relevant information to the Annual Accounts. It can be used as a type of 'chat' between the Member State and Commission. All Users who have Read permission on the Annual Accounts will be able to read all Observations in the conversation. All Users who have Update permission on the Annual Accounts will be able to send an observation and participate in the conversation. All observations are kept against the specific version of the Annual Accounts. 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.
Annual Accounts
Note | The Annual Accounts section has to be edited and signed once all data have been inserted through the XML files |
Click on the Edit button to select the information:

The Edit details pop-up window appears:

Select the following:
(1) Tick the box(es) for the desired option(s).
(2) Click on Save to save the information and sign the Annual Accounts.
Remark | To sign the Annual Accounts section, the User must have the role of MS Paying Agency with Update rights (MSPAu). |
Click on the SIGN ANNUAL ACCOUNTS button to sign the Annual Accounts:

Click on OK to confirm the signing of the Annual Accounts. For completing this action, the User will be redirected to the EU Login signature page:

Remark | When the form is updated or when a document (XML or non-XML) is uploaded or deleted, the Annual Accounts signature is revoked and the User will have to sign again. |
Annual Declaration
Data are populated from the XML file(s) upload:

Remark | New: For Financial Year >= 2025, the Explanation code for the discrepency on Technical Assistance (which is automatically calculated by the system) will be also set automatically to ‘Rounding Error’ (B02) |
Debtor Ledger
Data are populated from the XML file upload:

Public Storage
Note | The Public Storage document type can be either uploaded here or from the General>Documents section. |
Click on the Add button to add a Public Storage document type:

The Add document pop-up window appears:

Follow instructions on how to upload and send documents here.
Accounting/Financial Instrument
Advances EAGF
Advances EAGF within CAP Strategic Plan
Note | Confirmation of advances paid during Financial Year YYYY or previous Financial Years and still to be cleared and unused as at 15/10/YYYY - market measures (within CAP Strategic Plan). |
Data are populated from the XML file upload:

Advances EAGF outside CAP Strategic Plan
Note | Confirmation of advances paid during Financial Year YYYY or previous Financial Years and still to be cleared and unused as at 15/10/YYYY - market measures (outside CAP Strategic Plan). |
Data are populated from the XML file upload:

Advances EAGF – Wine above 5 Million - Outside CAP Strategic Plan
Note | Confirmation of advances paid during Financial Year YYYY or previous Financial Years onwards and still to be cleared and unused as at 15/10/YYYY - WINE measures projects above EUR 5 million. |
Data are populated from the XML file upload:

Advances EAFRD
Advances EAFRD 2023-2027
Data are populated from the XML file upload:

Advances EAFRD 2023-2027 above 5 millions
Data are populated from the XML file upload:

Financial Instruments
EAFRD Contribution
Data are populated from the XML file upload:

Remark | ColumnTotal cumulated fund capital declared by the Paying Agency to the European Commission in the quarterly Declarations since 01/01/2023 (Total public including EAFRD and National) doesn’t apply anymore for Financial Year >=2024 For Financial Year >= 2025 columns numbering has been adapted accordingly. The footnotes have been adapted as well. |
Public Expenditure (Starting FY 2024 onwards)
Data are populated from the XML file upload:

Funding Agreement (Starting FY 2024 onwards)
Data retrieved automatically from EAFRD DoE but can be updated from the XML file upload:

Remark | The funding Agreement information should be provided per CAP Plan/CCI number. For Belgium, it should be available in both Annual Accounts (Flanders and Wallonia). However, in case there is more than one Paying Agency in the respective MS, the ‘Funding Agreement’ will be available only in the Accounts of the Paying Agency, performing the functions of Coordinating Body as specified below: GERMANY DE01 SPAIN ES18 FRANCE FR19 ITALY IT01 ROMANIA RO01 The Funding Agreement information will be retrieved automatically from EAFRD DoE, but MS can upload an XML file in Annual Accounts to update them. |
Management Declaration(s)
Management Declaration – Paying Agency
Remark | New: For Financial Year >= 2025, It will be possible for the Member States to submit an Annual Accounts version to the European Commission (EC) without including the Management Declaration of the Paying Agency. A separate Annual Accounts version must be created and submitted later to include the Management Declaration of the Paying Agency. This separate version should be submitted before the original deadline or, if applicable, before the extended deadline for Member States (MS) that have been granted an extension. In order to not include Management Declaration of the Paying Agency, the following box should be unticked. |

Click on the Edit button to enter the information:

The Edit details pop-up window appears:

Enter or select the following:
(1) Enter the name for Director of the Paying Agency.
(2) Enter the Name of the Paying Agency.
(3) Tick the box(es) for the desired option(s).
If the option ‘reservations’ or ‘no reservations with comments’ is checked, the User has to insert the relevant information in the field “comments”.
(4) Click on Save to save the information and sign the Management Declaration.
Remark | To sign the Management Declaration Paying Agency, the User must have the role of MS Paying Agency with Update rights (MSPAu). |
Click on the Sign manage declaration paying agency section button to sign the Management Declaration:

The Management Declaration of the PA should be signed with the credentials of the PA Director.
Click on OK to confirm the signing of the Management Declaration. For completing this action, the User will be redirected to the EU Login signature page:

Remark | When the form is updated, the Management Declaration Paying Agency signature is revoked and the User will have to sign again. |
Management Declaration – Coordination Body
Note | For Financial Year <= 2024, the encoding of the Management Declaration - Coordination Body will have to be executed only by Member States with Coordinating Body and in the Annual Accounts created for the following Paying Agencies: BE02 DE01 ES18 FR19 IT01 RO01 New: For Financial Year >=2025, Member States with a Coordinating Body must also create a separate 'Annual Accounts and Management Declaration(s)' version. This separate version should be used to submit the Management Declaration of the Coordinating Body to the European Commission. |
Click on the Edit button to enter the information:

The Edit details pop-up window appears:

Enter or select the following:
(1) Enter the Name of Director of Coordinating Body.
(2) Enter the Name of the Coordinating Body.
(3) Select the Paying Agency(ies) code(s).
(4) Tick the box(es) for the desired option(s).
If the option ‘reservations’ or ‘no reservations with comments’ is checked, the User has to insert comments.
(5) Click on Save to save the information and sign the Management Declaration.
Remark | To sign the Management Declaration Coordinating Body, the User must have the role of MS Coordination Body with Update rights (MSCBu). |
Click on the Sign manage declaration coordinating body section button to sign the Management Declaration:

The Management Declaration of the CoB should be signed with the credentials of the Director of the Coordinating Body.
Click on OK to confirm the signing of the Management Declaration. For completing this action, the User will be redirected to the EU Login signature page:

Remark | When the form is updated, the Management Declaration Coordinating Body signature is revoked and the User will have to sign again. |
Annexed Documents
Click on the Add button to add Management Declaration annexed documents (they can also be uploaded from the section General > Documents). These annexed documents should be uploaded before the signature of the Management Declaration(s) to avoid the signature to be revoked and to avoid doing the signature action again 
The Add document pop-up window appears:

Follow instructions on how to upload and send documents here.
Validate the Annual Accounts
Remark | The Annual Accounts can be validated at any time, when the current version is in status Open and resides at the User’s Node. To validate the Annual Accounts, the User must have the role of MS Paying Agency or MS Coordination Body with Update or Send rights (MSPAu/s or MSCBu/s). |
Click on the Validate button to validate the Annual Accounts:

Remark | An Error will block you from sending the Annual Accounts. The error(s) should be resolved and the Annual Accounts must be revalidated. Note that a Warning does not block you from sending the Annual Accounts, but highlits issues to be considered, and if applicable – resolved. |
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. |
004 | Error | Validate that all integral documents have at least one attachment with a length > 0. |
005 | Error | Validate that no XML documents are in status ERROR |
006 | Error | Validate that at least one budget code has been declared for EAFRD in the Annual Declaration in the first Annual Account version (YYYY.0) of each Financial Year |
007 | Error | Validate that at least one confirmation option (article 32(1)(i) of Implementing Regulation (EU) 2022/128) is ticked |
008 | Warning | Validate that ’assigned revenues’ confirmation option (article 32(1)(i) of Implementing Regulation (EU) 2022/128) is ticked if EAGF expenditure have been declared |
009 | Warning | Validate that ’details of each movement of intervention storage’ confirmation option (article 32(1)(i) of Implementing Regulation (EU) 2022/128) is ticked. if the public storage has been declared |
010 | Warning | Validate the Annual Accounts chapter is signed (Warning in lower node) |
011 | Error | Validate that the Difference amounts is explained for each Budget code. (this rule doesn’t apply to UK) |
012 | Error | Validate that Budget codes in ‘Advances EAGF Wine above 5 Million outside CAP Plan’ are also reported in ‘Advances EAGF outside CAP Plan’ and that the ‘Closing balance of EAGF advances still to be cleared’ in ‘Advances EAGF Wine above 5 Million outside CAP Plan’ are <= than the ‘Closing balance of EAGF advances still to be cleared’ in 'EAGF Advances Outside CAP plan' |
014 | Error | Validate that Uncleared Advances EAFRD 2023-2027 above 5 million are lower or equal than the sum of Uncleared Advances EAFRD 2023-2027 |
015 | Error | Validate when first working version, that the deadline date for submission of the Annual Accounts has not been passed. (Warning – this rule is reexecuted during send Action) |
016 | Error | Validate, for each Type of Intervention declared in the Financial Instrument – EAFRD Contribution, that there is at least one Budget Code related to this type declared in Financial Instruments – Public Expenditure |
017 | Error | Validate for each Type of Intervention, that the sum of Total Cumulative declared in column (5) of the Financial Instruments – Public Expenditure is higher or equal than the Total Cumulative declared in column (4) of the Financial Instrument – EAFRD Contribution, for this Type |
018 | Error | Validate that the Type of intervention related to the Budget Codes declared in Financial Instruments – Public Expenditure is also declared in the Financial Instrument – EAFRD Contribution |
020 | Error | Validate the Annual Accounts chapter is signed (Error in highest node. this rule should be also executed during ‘Send to EC’ action) |
030 | Error | Validate that all mandatory information related to the Management Declaration of the Paying Agency have been filled |
035 | Error | Validate that all mandatory information related to the Management Declaration of the Coordinating Body have been filled, if applicable |
040 | Warning | Validate that the Management Declaration of the Paying Agency is signed (Warning in lower node) |
050 | Error | Validate that the Management Declaration of the Paying Agency is signed (Error in highest node. this rule should be also executed during ‘Send to EC’ action) |
060 | Warning | Validate that the Management Declaration of the Coordinating Body is signed (Warning in lower node), if applicable |
070 | Error | Validate that the Management Declaration of the Coordinating Body is signed (Error in highest node. this rule should be also executed during ‘Send to EC’ action), if applicable |
An example of a validation window:

You can check the list of validation results at any time throughout the Annual Accounts:

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 Annual Accounts becomes Validated.
Prepare the Annual Accounts for send to EC
Remark | The Prepare for Send can occur when a User on the highest MS Node wants to indicate that the Annual Accounts version can be prepared for sending to the Commission, once the Validation Errors have been removed and the status is Validated or Sent. To prepare the send of the Annual Accounts, the User must have the role of MS Paying Agency or MS Coordination Body with Update or Send rights (MSPAu/s or MSCBu/s). |
Click on the Prepare for send to EC button to prepare to send the Annual Accounts to the Commission:

The system will ask you to confirm the send action:

Click on Confirm to confirm.
The status of the Annual Accounts is set to Preparing for send to EC.
Remark | When on the highest MS node, a ‘Snapshot’ document will be available in the Documents section so that the sender can first verify what will be sent to the Commission. |
Send the Annual Accounts
Remark | In order to send to EC the first version YYYY.0 of an Annual Accounts for a given financial year, the Declaration period should be open. Users cannot create/send this first version after the end of the Declaration period (= Submission deadline), MS will have to send an extension letter to EC (from a different SFC2021 menu because the letter could be also related to APR and CBR), and EC will have to extend this Declaration period for this MS only (for the relevant documents). In case this first version is returned by EC for revision, User can submit a new version even after the end of the Declaration period (= submission deadline = 15/02/YYYY+1) The Annual Accounts can only be sent once the Validation Errors have been removed and the status is Ready To Send or Sent. The "4 eyes principle" must be respected. Therefore, the User sending must be different from the User who last validated. To send the Annual Accounts version, the User must have the role of MS Paying Agency or MS Coordination Body with Update and Send rights (MSPAu/s or MSCBu/s). If a MS has a Coordinating Body, only Users with the MSCB role can perform the send action. If a MS doesn’t have a Coordinating Body, only Users with the MSPA role can perform the send action. |
Click on the Send button to send the Annual Accounts to the Commission or to the upper Node:

The system will ask you to confirm the send action:

Click on Confirm to confirm. For completing this action, the User will be redirected to the EU Login signature page to sign the submission of the Annual Accounts
On success, the Annual Accounts version has been sent to the Commission or to the 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 sent to the Commission:
|
Request for Revised Annual Accounts by MS
Remark | The Annual Accounts 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 Revision requested by MS. This action can be used when a User wants to request a revision for the Annual Accounts version sent by the Member State/Region because it is incomplete or incorrect. To request a revised Annual Accounts version, the User must have the role of MS Paying Agency or MS Coordination Body with Update rights (MSPAu/MSCBu). |
Follow the steps to request for revised Annual Accounts by MS:

Select the following:
(1) Select the icon with 3 vertical dots.
(2) Click on the Request revision 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 Programme will be changed to status Revision requested by MS and the sender is notified of the action and its reason.
Delete the Annual Accounts
Remark | The Annual Accounts can only be deleted when:
To delete the Annual Accounts, the User must have the role of MS Paying Agency or MS Coordination Body with Update rights (MSPAu/MSCBu). The delete is a physical delete and cannot be recovered! |
Follow the steps to remove the Annual Accounts from the system:

Select the following:
(1) Select the icon with 3 vertical dots.
(2) Click on the Delete button to remove the Annual Accounts 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 Annual Accounts.
Cancel the Annual Accounts
Remark | The Annual Accounts can only be cancelled when an Annual Accounts version with documents was sent to the Commission and without any previous work version in status Revision requested by EC. The notification utility will be called to notify the Commission of the cancel of the version. The Annual Accounts version must currently reside on the User's Node and its status is Open, Validated, Ready to send or Revision requested by MS and contains a sent Document and has no previous working version of the same major version in status Revision requested by EC. To cancel the Annual Accounts, the User must have the role of MS Paying Agency or MS Coordination Body with Update rights (MSPAu/MSCBu). |
Follow the steps to cancel the Annual Accounts from the system:

Select the following:
(1) Select the icon with 3 vertical dots.
(2) Click on the Cancel button to cancel the Annual Accounts 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 Annual Accounts.
On success, the status of the Annual Accounts will be changed to Cancelled.
Create a New Version of the Annual Accounts
Remark | A new version of the Annual Accounts can only be created when the last version is in status Revision requested by EC, Sent (to EC). To create a new version of the Annual Accounts, the User must have the role of MS Paying Agency or MS Coordination Body with Update rights (MSPAu/MSCBu). New: For Financial Year >= 2025, Member States (MS) can proactively create a new version of their Annual Account and Management Declaration(s), even if the European Commission (EC) has not requested a revision. This new version should include any information or sections not yet sent in previous versions. The new version must be submitted before the original deadline or, if applicable, before the extended deadline for MS that have been granted an extension. |
Click on the Create button to create a new version of the Annual Accounts:

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 Annual Accounts.
On success, a new version of the Annual Accounts 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.
|
|
|