Official Journal of the European Union

COMMISSION REGULATION (EC) No 1042/2007

of 21 August 2007

laying down form and content of the accounting information to be submitted to the Commission for the purpose of the clearance of the accounts of the EAGF and EAFRD as well as for monitoring and forecasting purposes

THE COMMISSION OF THE EUROPEAN COMMUNITIES,

Having regard to the Treaty establishing the European Community,

Having regard to Council Regulation (EC) No 1290/2005 of 21 June 2005 on the financing of the common agricultural policy (1), and in particular Article 42 thereof,

Whereas:

Article 8(1) of Commission Regulation (EC) No 885/2006 of 21 June 2006 laying down detailed rules for the application of Council Regulation (EC) No 1290/2006 as regards the accreditation of paying agencies and other bodies and the clearance of the accounts of the EAGF and of the EAFRD (2) provides that the form and content of the accounting information referred to in Article 7(1)(c) of that Regulation and the way it is to be forwarded to the Commission are to be established.

The form and content of the accounting information to be submitted to the Commission for the purpose of the clearance of the accounts of the European Agricultural Guarantee Fund (EAGF) and of the European Agricultural Fund for Rural Development (EAFRD) as well as for monitoring and forecasting purposes are presently laid down in Commission Regulation (EC) No 1481/2006 (3) .

The Annexes to Regulation (EC) No 1481/2006 cannot be used for their intended purposes in the financial year 2008. Regulation (EC) No 1481/2006 should therefore be repealed and replaced by a new regulation setting out the form and content of the accounting information for that financial year.

The measures provided for in this Regulation are in accordance with the opinion of the Agricultural Funds Committee,

HAS ADOPTED THIS REGULATION:

Article 1

The form and content of the accounting information referred to in Article 7(1)(c) of Regulation (EC) No 885/2006 and the way it is to be forwarded to the Commission shall be as set out in Annexes I (X-table), II (Technical specifications for the transfer of computer files to the EAGF and EAFRD), III (Aide-mémoire) and IV (Structure of EAFRD budget codes [F109]) to this Regulation.

Article 2

Regulation (EC) No 1481/2006 is repealed with effect from 16 October 2007.

Article 3

This Regulation shall enter into force on the seventh day following that of its publication in the Official Journal of the European Union.

It shall apply from 16 October 2007.

This Regulation shall be binding in its entirety and directly applicable in all Member States.

(1) OJ L 209, 11.8.2005, p. 1. Regulation as last amended by Regulation (EC) No 378/2007 (OJ L 95, 5.4.2007, p. 1).

(2) OJ L 171, 23.6.2006, p. 90.

(3) OJ L 276, 7.10.2006, p. 3.

(3) See Article 6(b) and (c) of Regulation (EC) No 885/2006.

Note: You should first read the preliminary remark concerning ‘quantities’ in Chapter 5 of Annex III.

(1) STATEL/STADIUM will be replaced by eDamis once the new version of the STADIUM client has been released. Furthermore, the underlying software WinCheckCSV will be upgraded to a new version.

If the coordinating body notices that false data were transmitted or a problem occurred with the data transfer, the Commission has to be informed immediately. All files, which contain incorrect information, are to be indicated. Therefore, the Commission has to be asked to delete these files. Thereafter, in order to avoid an overlapping of computer records or data files, the coordinating body must send the corrected computer files to replace entirely the previous incorrect information.

The coordinating body must send the computer files completely and only once.

The explanatory note shall have the look and feel of an ordinary letter. In particular the identity of the sender or the identity of the paying agency and the name or administrative unit of the addressee shall be clearly marked.

In the case where there are codes used for fields, for which Annex III does not enforce standard codes, in order to explain all these used codes. The STADIUM client includes a specific consignment type for this kind of tabular transfer i.e. ‘CODE-LIST’.

In the case where there are differences between the annual declaration and the sum of the records in the computer files (Σ F106), in order to explain them by budget sub-item. The STADIUM client includes a specific consignment type for this transfer i.e. ‘EXPLANATORY-NOTE’.

In the following cases only, the coordinating body of the Member State must transfer an explanatory note for each paying agency through STATEL/STADIUM:

Annual declaration files shall be sent through STATEL/STADIUM with consignment type ‘ANNUAL_DECLARATION’.

Files satisfying the rules will look like the following (example for financial year 2007):

The files should have the characteristics as described under 2.4. Each line should contain the following fields (in this order):

The coordinating body of the Member State must send either one annual declaration file for all paying agencies or separate annual declaration files for each paying agency. An annual declaration file should contain the total amounts by paying agency together with the budget and currency codes, for both EAGF and EAFRD measures (3) .

The computer program for checking the format of computer files before sending them to the Commission (‘WinCheckCsv’) is included in the data transfer program (‘STADIUM client’). The paying agencies are invited to download the check program from CIRCA separately for offline validation purposes.

Data files with the characteristics as described under 2.4 shall be sent with consignment type ‘X-TABLE-DATA’ (see ‘STADIUM client’).

(other data rows with the fields in the same order).

BE01;215452;+0.50;EUR;20030615;050201011000002 (Please note +0.50 and not +.50)

Files satisfying these rules will look like the following (example for financial year 2004):

All fields: no spaces at the beginning or end of a field.

Quotation marks (‘’) are not allowed at the beginning or at the end of the records. The semicolon field separator ‘;’ must not be used in data in text format.

Budget code (field F109) required format without spaces: ‘999999999999999’ (where ‘9’ stands for any figure between 0 and 9).

Date field: ‘YYYYMMDD’ (year in four digits, month in two digits, day in two digits).

No spaces between digits. No spaces or other signs between thousands.

Fixed number of decimals (the details are set out in the Annex III hereto).

The symbol (‘+’ or ‘–’) appears on the far left, followed immediately by the figures. For positive numbers, the ‘+’ sign is optional.

BE, DK, DE, ES, FR, IE, IT, LU, NL, AT, PT, FI, SE and GB

The file is in ASCII coding according to following table. Other codes (such as EBCDIC, TAR, ZIP, etc.) are not accepted:

Records vary in length. Each record ends with a code ‘CR LF’ or ‘Carriage Return — Line Feed’ (in hexadecimal: ‘0D 0A’). The header row never ends on a ‘;’. Data rows only end on a ‘;’ if the last field is empty.

The fields are separated by a semicolon (‘;’). The header row and data rows shall all contain the same number of semicolons. In the data rows, empty fields appear as a double semicolon (‘;’) within the record, or as a single semicolon (‘;’) at the end of the record.

The following records in the file are data (data rows), in the order indicated by the first record describing the file structure.

The first record in the file (header row) contains the file description. The field names comprise an ‘F’ followed by the field number used in Annex I (the ‘X-table’). Only field names existing in this Annex are allowed.

The computer files must have the following characteristics:

All information for the same category of payments or receipts must be contained in the same computer file. Separate files relating to the same payments (e.g. for traders or inspections, or for basic and measure data) are not allowed.

The records must have a flat file structure. If fields have more than one value, separate records containing all data fields are required. Make sure that no double counting occurs. (2) .

The Member State must create a computer record for each individual component of the EAGF/EAFRD payments and receipts. These components are the individual items of which the payment (receipt) to (from) the beneficiary consists.

The coordinating body of the Member State must transfer the computer files and the relating documentation to the Commission through STATEL/STADIUM (1) . The Commission will only support one installation of STATEL/STADIUM per Member State. The latest STADIUM client and more information on the use of STATEL/STADIUM shall be downloaded from the Circa website of the agricultural funds.

These technical specifications apply in respect of the financial year 2007, which commenced on 16 October 2006.

Technical specifications for the transfer of computer files to the EAGF and EAFRD from 16 October 2007

ANNEX III

‘AIDE-MÉMOIRE’

Financial year 2008

CONTENTS

1. DATA RELATING TO PAYMENTS:

F100: name of paying agency

F101: reference number of payment

F102: reference number of previous payment

F103: type of payment

F105: payment with sanction

F105B: Cross-Compliance: reduction or exclusion from payments pursuant to Article 6 of Council Regulation (EC) No 1782/2003

F106: amount in Euro

F106A: public expenditure in Euro

F106B: private sector contribution in Euro

F107: currency unit

F108: date of payment

F109: budget code

F110: marketing year or period

2. DATA RELATING TO BENEFICIARY (APPLICANT):

F200: identification code

F201: name

F202A: applicant's address (street and number)

F202B: applicant's address (international post code)

F202C: applicant's address (municipality or city)

F205: holding in less-favoured region (where this affects the rate of aid)

F207: region and sub-region

F211: delivery reference quantity

F212: direct sales reference quantity

F213: reference fat content

F214: purchaser of milk

F217: date of entry private storage

F218: end date of private storage

F220: identification code of the intermediate organisation

F221: name of the intermediate organisation

F222B: organisation's address (international post code)

F222C: organisation's address (municipality or city)

3. DATA RELATING TO DECLARATION/APPLICATION:

F300: number of declaration/application

F300B: date of application

F301: number of contract/project (where applicable)

F304: authorising office

F305: number of certificate/licence

F306: date of issue of the certificate/licence

F307: office holding supporting documents

4. DATA RELATING TO SECURITY:

F402: amount of processing security (others than tender securities) in euro

5. DATA RELATING TO PRODUCTS:

F500: product code/rural development sub-measure code

F502: quantity paid (number of animals, hectares, etc.)

F503: quantity covered by payment application lodged (quantity claimed)

F508A: area covered by payment application lodged

F508B: area covered by payment made

F509A: area wrongly declared

F510: Community regulation and article number

F511: EAGF rate of aid (euro) per unit of measurement

F515: gross deliveries

F517: actual fat content

F518: adjusted deliveries

F519: direct sales

F519B: deliveries after administrative corrections (if any)

F519C: direct sales after administrative corrections (if any)

F520: quantities delivered over or under quotas

F521: direct sales over or under quotas

F522: additional levy due

F523: interest due for late payment

F531: total alcoholic strength by volume

F532: natural alcoholic strength by volume

F533: wine growing zone

6. DATA RELATING TO INSPECTIONS:

F600: on-farm inspection or remote sensing

F601: date of inspection

F602: application reduced

F602B: recalculation of additional levy payable

F603: reason for reduction

F604: Council Regulation (EEC) No 386/90 (on-the-spot checks)

F604B: Council Regulation (EEC) No 386/90 (substitution checks)

7. DATA RELATING TO PAYMENT ENTITLEMENTS:

F700: amount of payment entitlement in euro

F701: amount not paid in euro

F702: area covered by payment made

A) Payment entitlements based on areas (normal entitlements)

F703: unit value of payment entitlement in euro

F703A: area covered by payment application lodged

F703B: area determined

F703C: area not found

B) Set-aside entitlement

F704: unit value of payment entitlement in euro

F704A: area covered by payment application lodged

F704B: area determined

F704C: area not found

C) Grassland entitlements

F705: unit value of payment entitlement in euro

F705A: area covered by payment application lodged

F705B: area determined

F705C: area not found

D) Other entitlements like national reserve

F706: unit value of payment entitlement in euro

F706A: area covered by payment application lodged

F706B: area determined

F706C: area not found

E) Payment entitlements subject to special conditions

F707: unit value of payment entitlement in euro

F707A: number of livestock units (LU) in the reference period

F707B: number of livestock units (LU) declared

F707C: number of livestock units (LU) determined

8. ADDITIONAL DATA RELATING TO EXPORT REFUNDS:

F800: net weight/quantity

F800B: unit of measurement for field F800

F801: application number (export refunds: SAD)

F802: customs office of placing under customs supervision

F802B: customs office of exit

F804: export refund code

F805: code for destination

F808: date of advance fixing

F809: last day of validity (advance fixing)

F812: reference of the invitation to tender if applicable (advance fixing)

F814: day of acceptance of payment declaration (COM-7)

F816: date of acceptance of export declaration

F816B: date of export from the EU territory

9. (NOT USED)

General remark: significance of the X, A and D codes used in Annex I:

All the information marked ‘X’ or ‘A’ is obligatory.

‘X’ = data element already included in the previous version of this Regulation. ‘A’ = data element to be added compared to the previous version of this Regulation. ‘D’ = data element to be deleted compared to the previous version of this Regulation.

Where a data request makes no sense under particular circumstances or is not applicable for the Member States concerned, then put NULL value, which shall be represented by two consecutive semicolons (;;) in the CSV format data file.

1. DATA RELATING TO PAYMENTS:

Preliminary remark: In this section, the term ‘payment’ refers to both the EAGF and EAFRD payments and the receipts.

F100: name of paying agency

Required format: to be expressed by a code (see the code list F100 kept up-to-date on CAP-ED):

https://webgate.ec.europa.eu/agriportal

F101: reference number of payment

The reference number identifying the payment clearly in the paying agency's accounts. Removals relating to food aid shall not be considered as sales of intervention products. In this particular case field F101 can be ignored.

F102: reference number of previous payment

The reference number identifying the payment clearly in the paying agency's accounts, for instance as an advance or an amount recovered.

F103: type of payment

Required format: to be expressed by a one-character code corresponding to the following code list:

Code Significance 0 Food Aid 1 Advance or partial payment 2 Final payment (first and single payment; or settlement of the balance after advance payment; or normal export refund payment) 3 Recovery/reimbursement (following a sanction)/correction 4 Receipt of amounts (not preceded by an advance or final payment) 5 Pre-financing payment export refund 6 No financial transaction

F105: payment with sanction

Required format: yes = ‘Y’; no = ‘N’.

F105B: Cross-Compliance: reduction or exclusion from payments pursuant to Article 6 of Council Regulation (EC) No 1782/2003

The field F105B must be used to indicate the amount reduced or excluded on the basis of Article 6 of Council Regulation (EC) No 1782/2003 (1). This (negative) amount (in euro) resulting from cross-compliance shall be indicated for each budget post under direct aids. It concerns the 100 % reduction to the farmer i.e. without the 25 % retention provided for in Article 9 of Council Regulation (EC) No 1782/2003.

Required format: +99 … 99.99 or –99 … 99.99, where 9 stands for any number from 0 to 9 inclusive.

F106: amount in euro

Amount of each individual item of payment in Euro.

The amounts in field F106 relate to the EAGF and EAFRD expenditure only. National expenditure shall not appear under this heading.

For EAGF, the sum of these amounts (F106) by budget code (F109) shall in principle correspond with the amounts declared in table 104.

Required format: +99 … 99.99 or –99 … 99.99, where 9 stands for a digit from 0 to 9.

F106A: public expenditure in euro

Amount of any public contribution to the financing of operations whose origin is the budget of the State, of regional and local authorities, of the European Communities and any similar expenditure.

The sum of these amounts (F106A) by budget code (F109) shall in principle correspond with the certified public expenditure declared in the EAFRD table.

Required format: +99 … 99.99 or –99 … 99.99, where 9 stands for a digit from 0 to 9.

F106B: private sector contribution in euro

Amount of private sector expenditure in euro when such a contribution is foreseen for the measure.

Required format: +99 … 99.99 or –99 … 99.99, where 9 stands for a digit from 0 to 9.

F107: currency unit

Required format: EUR

F108: date of payment

The date determining the month of declaration to the EAGF/EAFRD.

Required format:‘YYYYMMDD’ (year in four digits, month in two digits, day in two digits).

F109: budget code

For EAGF, the full code of the Activity Based Budgeting structure must be given, including the title, chapter, Article, item and sub-item.

For EAFRD budget line 05040501, the budget sub-items must be given according to Annex IV.

Required ABB-format without spaces:‘999999999999999’, where 9 stands for a digit from 0 to 9. Missing positions shall be filled with zeroes (e.g. 05020901160 becomes 050209011600000).

F110: marketing year or period

For intervention products the Commission needs to know the marketing year to which the product corresponds or the quota period it is to be set off against.

2. DATA RELATING TO BENEFICIARY (APPLICANT):

Preliminary remark: The fields F200, F201, F202A, F202B and F202C must be used to identify the beneficiary of a payment i.e. the final beneficiary. The fields F220, F221, F222B and F222C must additionally be used if a payment is made to the beneficiary through an intermediate organisation. If the intermediate organisation is also the final beneficiary the same data have to be filled in the fields F220, F221, F222B and F222C as indicated in the fields F200, F201, F202A, F202B and F202C.

The field F207 is only related to the field F200.

F200: identification code

The individual unique identifier allocated to each applicant at Member State level.

F201: name

The applicant's last name and first name, or the business name.

F202A: applicant's address (street and number)

F202B: applicant's address (international post code)

F202C: applicant's address (municipality or city)

F205: holding in less-favoured region (where this affects the rate of aid)

In the case of support in a less-favoured area, this must be indicated here.

Required format: yes = ‘Y’; no = ‘N’.

F207: region and sub-region

Region and sub-region code (NUTS 3) is defined by the main activities of the holding of the beneficiary to which the payment is assigned.

The code ‘Extra Region’ (MSZZZ) should only be indicated in cases e.g. where no NUTS 3 code exists.

Required format: NUTS 3 code as specified in the code list F207 on CAP-ED:

https://webgate.ec.europa.eu/agriportal

F211: delivery reference quantity

This relates to the milk quota scheme.

Required format: +99 … 99.999 or –99 … 99.999, where 9 stands for a digit from 0 to 9.

F212: direct sales reference quantity

This relates to the milk quota scheme.

Required format: +99 … 99.999 or –99 … 99.999, where 9 stands for a digit from 0 to 9.

F213: reference fat content

This relates to the milk quota scheme.

Required format: 9 … 9.99, where 9 stands for a digit from 0 to 9.

F214: purchaser of milk

In accordance with Article 5(e) of Council Regulation (EC) No 1788/2003 (2). This relates to the milk quota scheme.

F217: date of entry private storage

Required format:‘YYYYMMDD’ (year in four digits, month in two digits, day in two digits).

F218: end date of private storage

Required format:‘YYYYMMDD’ (year in four digits, month in two digits, day in two digits).

F220: identification code of the intermediate organisation

The individual unique identifier allocated to intermediate organisations at Member State level.

The payment is made to the beneficiary via the intermediate organisation i.e. via each intermediate institution or directly to this organisation.

F221: name of the intermediate organisation

The organisation's name.

F222B: organisation's address (international post code)

F222C: organisation's address (municipality or city)

3. DATA RELATING TO DECLARATION/APPLICATION:

F300: number of declaration/application

This must enable the declaration/application to be traced through the Member States' files.

F300B: date of application

The date of receipt of the application by the paying agency (including any divisional or regional offices thereof).

Required format:‘YYYYMMDD’ (year in four digits, month in two digits, day in two digits).

F301: number of contract/project (where applicable)

For EAFRD measures and programmes, a unique identification number must be allocated to each project.

F304: authorising office

This is the office responsible for administrative control and authorisation, e.g. the region. The more decentralised the management of the scheme is, the more important this information becomes.

F305: number of certificate/licence

F306: date of issue of the certificate/licence

Required format:‘YYYYMMDD’ (year in four digits, month in two digits, day in two digits).

F307: office holding supporting documents

Only where this is not the same as that specified in field F304.

4. DATA RELATING TO SECURITY:

F402: amount of processing security (others than tender securities) in Euro

Required format: +99 … 99.99 or –99 … 99.99, where 9 stands for a digit from 0 to 9.

5. DATA RELATING TO PRODUCTS:

Preliminary remark concerning quantities: as a basic rule, quantities, areas and numbers of animals must only be shown once. In the case of an advance payment followed by a balance payment, the quantity must be shown in the record of the advance payment. This is also true for cases where the advance payment and balance payment are booked on different budget sub-posts (advances and balance). Adjustments to quantities, areas and numbers of animals must be shown in the records covering the balance or subsequent payments. In the case of sums recovered, if the amount applied for is reduced because of incorrect quantities, areas or numbers of animals, the adjustments to the quantities must be indicated by a minus sign.

F500: product code/rural development sub-measure code

The Member States must draw up their own lists of codes, to be detailed in the explanatory note to the payment file(s).

In the case of rural development expenditure in the new Member States (budget post 050404000000) a one-character or two-character code corresponding to the following list must be expressed:

Code Significance A Investment in farms B Start-up assistance for young farmers C Training D Early retirement E Less-favoured areas and areas with environmental restrictions F Agri-environment and animal welfare G Improving the processing and marketing of agricultural products H Afforestation of agricultural land I Other forestry measures J Land improvement K Reparcelling L Setting up farm relief and farm management services, setting-up consulting services in farms and agricultural vulgarisation M Marketing of quality agricultural products N Basic services for the rural economy and population O Renovation and development of villages and protection and conservation of the rural heritage P Diversifying agricultural activities and activities close to agriculture to provide multiple activities or alternative sources of income Q Managing agricultural water resources R Developing and improving infrastructure connected with the development of agriculture S Encouraging tourist and craft activities T Protecting the environment in connection with agriculture, forestry and landscape management and improving animal welfare U Restoring agricultural production potential damaged by natural disasters and introducing appropriate prevention instruments V Financial engineering X Respect of standards Y Recourse of consulting services regarding respect of standards Z Voluntary participation of farmers in food quality systems AA Measures of producer groups in the area of food quality AB Semi-subsistence farms in the restructuring process AC Producer groups AD Technical assistance AE Complements to direct payments AF Complements to State aid in Malta AG Full-time farmers in Malta SA Financing of Sapard projects

In the case of the restructuring and conversion of vineyard (budget post 050209071650) measures codes must be expressed. These codes refer to the definitions of the measures defined by the competent authorities of the Member States in accordance with Article 13(2)(a) of Commission Regulation (EC) No 1227/2000 (3).

In the case of export refunds: F500 is only required if F804 contains ingredients for which export refund is fixed. Then in F500, the code of the goods (in principle the CN code declared in box 33 of the SAD; 8 digits) must be indicated for non-annex 1 goods, or the product code for the final processed agricultural products.

F502: quantity paid (number of animals, hectares, etc.)

See preliminary remarks in heading 5 (data relating to products).

For the wine sector, the products obtained after distillation shall be expressed by alcoholic strength.

For all other sectors, the quantity paid shall be expressed in the unit which is laid down in the Regulation as the basis for the premium payment.

Required format: +99 … 99.99 or –99 … 99.99, where 9 stands for a digit from 0 to 9. With a possibility to increase the number of decimals if significant. (max 6).

F503: quantity covered by payment application lodged (quantity claimed)

Required format: +99 … 99.99 or –99 … 99.99, where 9 stands for a digit from 0 to 9. With a possibility to increase the number of decimals if significant. (max 6).

F508A: area covered by payment application lodged

The area covered by the application.

See preliminary remark in heading 5 (data relating to products).

For budget post 050404000000 (Rural Development in the new Member States) this field is required only for the measures E, F and H.

Required format: +99 … 99.99 or –99 … 99.99, where 9 stands for a digit from 0 to 9.

F508B: area covered by payment made

The area on which the payment is made.

For budget post 050404000000 (Rural Development in the new Member States) this field is required only for the measures E, F and H.

Required format: +99 … 99.99 or –99 … 99.99, where 9 stands for a digit from 0 to 9.

F509A: area wrongly declared

The difference between the area declared and that found. Overstatement being the area declared exceeding the area found and reported with a positive figure. Understatement being the area found exceeding the area declared and reported with a negative figure.

Required format: +99 … 99.99 or –99 … 99.99, where 9 stands for a digit from 0 to 9.

F510: Community regulation and article number

In the case of intervention goods, the ad hoc instrument published in the Official Journal of the European Union is required.

F511: EAGF rate of aid (EUR) per unit of measurement

Only if there is a change during the marketing year or period.

Required format: 9 … 9.999999, where 9 stands for a digit from 0 to 9.

The use of six decimal places may seem odd but some regulations like Council Regulation (EC) No 660/1999 (4) fix the premium with up to five decimals even when using euro. To cover all possibilities the number of decimals has been raised to six.

F515: gross deliveries

‘Gross deliveries’ covers all quantities of milk and milk products delivered as defined in Article 5(f) of Council Regulation (EC) No 1788/2003, without any adjustment for the fat content.

Required format: +99 … 99.999 or –99 … 99.999, where 9 stands for a digit from 0 to 9. With a possibility to increase the number of decimals if significant. (max 6).

F517: actual fat content

As shown by the laboratory analysis findings, expressed as a percentage rather than in grams or kilograms.

Required format: 9 … 9.99, where 9 stands for a digit from 0 to 9. With a possibility to increase the number of decimals if significant. (max 6).

F518: adjusted deliveries

Quantities delivered, adjusted for the fat content in accordance with Article 10(1) of Commission Regulation (EC) No 595/2004 (5).

Required format: +99 … 99.999 or –99 … 99.999, where 9 stands for a digit from 0 to 9. With a possibility to increase the number of decimals if significant. (max 6).

F519: direct sales

Milk and milk equivalent as defined in Article 5(g) of Council Regulation (EC) No 1788/2003.

Required format: +99 … 99.999 or –99 … 99.999, where 9 stands for a digit from 0 to 9. With a possibility to increase the number of decimals if significant. (max 6).

F519B: deliveries after administrative corrections (if any)

Milk sector: ‘administrative corrections’ means adjustments made by the paying agency to the quantities declared by purchasers. Such changes must always be shown separately from the quantities declared by the purchasers. Corrections may be positive or negative. The net changes must be shown as compared with the situation before the correction. There is no provision for including flat-rate corrections here.

Corrections following on-the-spot checks, required under Article 21 of Commission Regulation (EC) No 595/2004, must be recorded in fields F600 to F603.

Required format: +99 … 99.999 or –99 … 99.999, where 9 stands for a digit from 0 to 9. With a possibility to increase the number of decimals if significant. (max 6).

F519C: direct sales after administrative corrections (if any)

For the definition of administrative corrections, see field F519B.

Required format: +99 … 99.999 or –99 … 99.999, where 9 stands for a digit from 0 to 9. With a possibility to increase the number of decimals if significant. (max 6).

F520: quantities delivered over or under quotas

Required format: +99 … 99.999 or –99 … 99.999, where 9 stands for a digit from 0 to 9.

F521: direct sales over or under quotas

Required format: +99 … 99.999 or –99 … 99.999, where 9 stands for a digit from 0 to 9. With a possibility to increase the number of decimals if significant. (max 6).

F522: additional levy due

For deliveries or direct sales (a distinction is to be made through the budget code (field F109)).

Required format: +99 … 99.99 or –99 … 99.99, where 9 stands for a digit from 0 to 9.

F523: interest due for late payment

For deliveries or direct sales (to be distinguished by means of the budget code in field F109).

Required format: +99 … 99.99 or –99 … 99.99, where 9 stands for a digit from 0 to 9.

F531: total alcoholic strength by volume

Expressed in % vol/hl.

Required format: 99.99, where 9 stands for a digit from 0 to 9.

F532: natural alcoholic strength by volume

Expressed in % vol/hl.

Required format: 99.99, where 9 stands for a digit from 0 to 9.

F533: wine growing zone

Wine growing zone as defined in annex III to Council Regulation (EC) No 1493/1999 (6).

Required format: to be expressed by one of the following codes: A, B, CIA, CIB, CII, CIIIA, CIIIB.

6. DATA RELATING TO INSPECTIONS:

The Commission needs to know the number of inspections carried out and the number of cases where penalties have been applied as a result. Where the premium is withheld or recovered in full, zero payments must be indicated with the date of the decision in F108.

F600: on-farm inspection or remote sensing

The ‘on-the-spot checks’ mentioned here are those referred to in the relevant regulations (7) They include physical visits of the farm (code ‘F’ or code ‘C’) and/or checks by remote sensing (code ‘T’). Field F601 needs only be completed where an on-farm inspection or control on cross-compliance (‘F’, or ‘C’) is indicated in field F600. Fields F602 to F602B need only be completed where an on-the-spot check (‘F’, ‘C’, or ‘T’) is indicated in field F600. In the case of multiple visits concerning the same measure and the same producer only report once. Every record, be it the advance or balance payment or other, that can be related to a particular inspection, shall have the appropriate code (see below) in field F600.

Administrative checks, within the meaning of the above-mentioned regulations (see footnote below), shall not be mentioned in F600. They are not mentioned as such in any field. Nevertheless, the penalties imposed shall be given in F105, whether they originate from an administrative check or on-the-spot check.

Required format:‘N’= no inspection, ‘F’= on-farm inspection, ‘C’= controls on cross-compliance and ‘T’= inspection by remote sensing. In case of a combination of on-farm inspection and cross-compliance and/or inspection by remote sensing one of the corresponding codes ‘FT’, ‘CT’, ‘CF’ or ‘FTC’ must be shown.

F601: date of inspection

This field must be completed when an on-farm inspection or control on cross-compliance (‘F’ or ‘C’) is indicated in field F600. The date of inspection is not required for remote sensing checks.

Required format:‘YYYYMMDD’ (year in four digits, month in two digits, day in two digits).

F602: application reduced

If the application has been reduced as a result of an inspection, this must be indicated here. This field must be completed when an on-the-spot inspection is indicated in field F600.

Required format: yes = ‘Y’; no = ‘N’.

F602B: recalculation of additional levy payable

For instance, after on-the-spot inspections.

Required format: +99 … 99.99 or –99 … 99.99, where 9 stands for a digit from 0 to 9.

F603: reason for reduction

Where there is more than one reason indicate the one justifying the highest penalty. This field must be completed when the application has been reduced as a result of an on-the-spot inspection.

Required format: to be expressed by a code; the codes must be explained in the accompanying letter.

F604: Council Regulation (EEC) No 386/90 (8) (on-the-spot checks)

Required format yes = ‘Y’; no = ‘N’.

F604B: Council Regulation (EEC) No 386/90 (substitution checks)

Required format: yes = ‘Y’; no = ‘N’.

7. DATA RELATING TO PAYMENT ENTITLEMENTS:

Preliminary remark:

The Commission needs to know the corresponding amount (unit value) for each kind of entitlement as defined in Title III of Council Regulation (EC) No 1782/2003.

Furthermore, the Commission needs to know financial information on the amounts not paid following administrative or on-the-spot-checks (IACS controls).

F700: amount of payment entitlement in euro

Amount of payment entitlement in EURO i.e. the total amount to be paid in respect of the payment entitlements as defined in Title III of Council Regulation (EC) No 1782/2003 after performing the IACS controls.

Required format: +99 … 99.99 or –99 … 99.99, where 9 stands for a digit from 0 to 9.

F701: amount not paid in euro

If the amount (F700) has been reduced as a result of administrative or on-the-spot checks, then the amount not paid following administrative or on-the-spot checks must be indicated here.

Required format: +99 … 99.99 or –99 … 99.99, where 9 stands for a digit from 0 to 9.

F702: area covered by payment made

For payment entitlements based on areas: The area on which the payment is made.

Required format: +99 … 99.99 or –99 … 99.99, where 9 stands for a digit from 0 to 9.

If a payment is composed of more than one kind of entitlement then the requested information under section A) to E) has to be filled in as appropriate. If a section is not applicable, then put NULL value in that section.

Payment entitlements mentioned below are those referred to in Title III of Council Regulation (EC) No 1782/2003:

A) Payment entitlements based on areas (normal entitlements) F703: unit value of payment entitlement in euro The unit value of payment entitlement in euro as lodged in the claim. Required format: +99 … 99.99, where 9 stands for a digit from 0 to 9. F703A: area covered by payment application lodged The ‘activated’ area covered by the aid application: For payment entitlements based on areas, this is the area ‘activated’ i.e. maximum area subject to payment (see also Article 50(2) of Commission Regulation (EC) No 796/2004) (9). Required format: +99 … 99.99 or –99 … 99.99, where 9 stands for a digit from 0 to 9. F703B: area determined The area determined as a result of administrative or on-the-spot checks. Required format: +99 … 99.99 or –99 … 99.99, where 9 stands for a digit from 0 to 9. F703C: area not found The difference between the ‘activated’ area declared in the aid application and the one found as a result of administrative or on-the-spot checks. Overstatement being the area declared exceeding the area found and reported as a positive figure. Understatement being the area found exceeding the area declared and reported as a negative figure. Required format: +99 … 99.99 or –99 … 99.99, where 9 stands for a digit from 0 to 9.

B) Set-aside entitlement F704: unit value of payment entitlement in euro The unit value of payment entitlement in euro as lodged in the claim. Required format: +99 … 99.99, where 9 stands for a digit from 0 to 9. F704A: area covered by payment application lodged The ‘activated’ area covered by the aid application. Required format: +99 … 99.99 or –99 … 99.99, where 9 stands for a digit from 0 to 9. F704B: area determined The area determined as a result of administrative or on-the-spot checks. Required format: +99 … 99.99 or –99 … 99.99, where 9 stands for a digit from 0 to 9. F704C: area not found The difference between the ‘activated’ area declared in the aid application and the one found as a result of administrative or on-the-spot checks. Overstatement being the area declared exceeding the area found and reported as a positive figure. Understatement being the area found exceeding the area declared and reported as a negative figure. Required format: +99 … 99.99 or –99 … 99.99, where 9 stands for a digit from 0 to 9.

C) Grassland entitlements F705: unit value of payment entitlement in euro The unit value of payment entitlement in euro as lodged in the claim. Required format: +99 … 99.99, where 9 stands for a digit from 0 to 9. F705A: area covered by payment application lodged The ‘activated’ area covered by the aid application. Required format: +99 … 99.99 or –99 … 99.99, where 9 stands for a digit from 0 to 9. F705B: area determined The area determined as a result of administrative or on-the-spot checks. Required format: +99 … 99.99 or –99 … 99.99, where 9 stands for a digit from 0 to 9. F705C: area not found The difference between the ‘activated’ area declared in the aid application and the one found as a result of administrative or on-the-spot checks. Overstatement being the area declared exceeding the area found and reported as a positive figure. Understatement being the area found exceeding the area declared and reported as a negative figure. Required format: +99 … 99.99 or –99 … 99.99, where 9 stands for a digit from 0 to 9.

D) Other entitlements like national reserve F706: unit value of payment entitlement in Euro The unit value of payment entitlement in Euro as lodged in the claim. Required format: +99 … 99.99, where 9 stands for a digit from 0 to 9. F706A: area covered by payment application lodged The ‘activated’ area covered by the aid application. Required format: +99 … 99.99 or –99 … 99.99, where 9 stands for a digit from 0 to 9. F706B: area determined The area determined as a result of administrative or on-the-spot checks. Required format: +99 … 99.99 or –99 … 99.99, where 9 stands for a digit from 0 to 9. F706C: area not found The difference between the ‘activated’ area declared in the aid application and the one found as a result of administrative or on-the-spot checks. Overstatement being the area declared exceeding the area found and reported as a positive figure. Understatement being the area found exceeding the area declared and reported as a negative figure. Required format: +99 … 99.99 or –99 … 99.99, where 9 stands for a digit from 0 to 9.

E) Payment entitlements subject to special conditions F707: unit value of payment entitlement in euro The unit value of payment entitlement in euro as lodged in the claim. Required format: +99 … 99.99 or –99 … 99.99, where 9 stands for a digit from 0 to 9. F707A: number of livestock units (LU) in the reference period This number represents the agricultural activity exercised in the reference period expressed in LU according to Article 49(2) of Council Regulation (EC) No 1782/2003. Required format: +99 … 99.99 or –99 … 99.99, where 9 stands for a digit from 0 to 9. F707B: number of livestock units (LU) declared This field must indicate the exact number of LU declared for the calendar year concerned (Article 49(2) of Council Regulation (EC) No 1782/2003). Required format: +99 … 99.99 or –99 … 99.99, where 9 stands for a digit from 0 to 9. F707C: number of livestock units (LU) determined The number of LU determined as a result of administrative or on-the-spot checks, in order to check the compliance with Article 49(2) of Council Regulation (EC) No 1782/2003. Required format: +99 … 99.99 or –99 … 99.99, where 9 stands for a digit from 0 to 9.

8. ADDITIONAL DATA RELATING TO EXPORT REFUNDS:

F800: net weight/quantity

See preliminary remark in heading 5 (data relating to products).

The weight or the quantity shall be expressed in the unit of measurement

In the case of processed products (non-annex I goods or processed agricultural products): the quantity of the ingredient eligible for funding. If the code of the goods (F500) contains more than one ingredient eligible for funding (F804), then multiple records with corresponding amounts (F106) and quantities (F800) must be created.

Required format: +99 … 99.99 or –99 … 99.99, where 9 stands for a digit from 0 to 9. With a possibility to increase the number of decimals if significant. (max 6).

F800B: unit of measurement for field F800

Required format: to be expressed by a one-character code corresponding to the following table:

Code Meaning K Kilogram L Litre P Piece (item)

F801: application number (export refunds: SAD)

F802: customs office of placing under customs supervision

The Member States must use the Transit Customs Office List (COL (10). This is the list of authorised customs offices for Community/common transit operations. It may be that due to its objective of ‘transit operations’ some of the customs offices might be missing although this will be the exception. In that case the Member State shall provide the name of the customs office in full.

Required format: The format of the COL code consists of two positions to denote the country followed by a six-character code that define the customs office. For instance ‘EE1000EE’.

F802B: customs office of exit

Indicate the customs office, which certifies that products covered by refund applications have left the customs territory of the Community. The Member States must use the Transit Customs Office List (COL). This is the list of authorised customs offices for Community/common transit operations. It may be that due to its objective of ‘transit operations’ some of the customs offices might be missing although this will be the exception. In that case the Member State shall provide the name of the customs office in full.

This information is vital for the auditors in connection with the application of Council Regulation (EEC) No 386/90 concerning substitution checks. The information is available in T5 or equivalent documents.

Required format: The format of the COL code consists of two positions to denote the country followed by a six-character code that define the customs office. For instance ‘NL146123’.

F804: export refund code

In the case of non-processed agricultural products: The 12 digit product code, for which export refund is fixed.

In cases of processed products (non-annex I goods or processed agricultural products): the CN code(s) of the ingredient(s) for which export refund is fixed. In this case, F500 must be completed with the code of the final product. See also the explanatory note to F800 for the procedure to follow where more than one ingredient of a processed product is eligible for refund.

F805: code for destination

Required format:‘XX’, where X stands for a letter between A and Z (codes of the nomenclature of countries and territories for the external trade statistics of the Community. See Commission Regulation (EC) No 2020/2001 (11) of 15 October 2001 and subsequent updates).

In view of harmonisation, the Member States shall also use the miscellaneous category (codes Q*) of the nomenclature of countries and territories for the external trade statistics. It is known that that nomenclature does not cover all special export refund cases but the Commission does not require that kind of detail. Member States shall therefore convert their special national codes to the broader categories of the nomenclature of countries and territories for the external trade statistics before sending their data to the Commission.

F808: date of advance fixing

If fixed in advance, the date on which the rate of refund was set.

Required format:‘YYYYMMDD’ (year in four digits, month in two digits, day in two digits).

F809: last day of validity (advance fixing)

Required format:‘YYYYMMDD’ (year in four digits, month in two digits, day in two digits).

F812: reference of the invitation to tender if applicable (advance fixing)

The procedure stipulated in Article 5 of Commission Regulation (EC) No 1501/95 (12) or similar procedure for other sectors. The Commission needs the reference of the invitation to tender.

F814: day of acceptance of payment declaration (COM-7)

For the beef sector: in the case of pre-financing, complete field F814 only (disregarding fields F816 and F816B); if pre-financing is not involved, complete fields F816 and F816B (disregarding field F814).

Required format:‘YYYYMMDD’ (year in four digits, month in two digits, day in two digits).

F816: date of acceptance of export declaration

Date within the meaning of Article 5 point 1 of Commission Regulation (EC) No 800/1999 (13).

Required format:‘YYYYMMDD’ (year in four digits, month in two digits, day in two digits).

F816B: date of export from the EU territory

Date of export as indicated on the export declaration or on the T5. See also Article 7 point 1 of Commission Regulation (EC) No 800/1999.

Required format:‘YYYYMMDD’ (year in four digits, month in two digits, day in two digits).

9. (NOT USED)

(1) OJ L 270, 21.10.2003, p. 1. Regulation as last amended by Council Regulation (EC) No 2013/2006 (OJ L 384, 19.12.2006, p. 13).

(2) OJ L 270, 21.10.2003, p. 123. Regulation as last amended by Council Regulation (EC) No 1406/2006 (OJ L 265, 26.9.2006, p. 8).

(3) OJ L 143, 16.6.2000, p. 1. Regulation as last amended by Regulation (EC) No 1216/2005 (OJ L 199, 29.7.2005, p. 32).

(4) OJ L 83, 27.3.1999, p. 10.

(5) OJ L 94, 31.3.2004, p. 22. Regulation as last amended by Commission Regulation (EC) No 1468/2006 (OJ L 274, 5.10.2006, p. 6).

(6) OJ L 179, 14.7.1999, p. 1. Regulation as last amended by Council Regulation (EC) No 1791/2006 (OJ L 363, 20.12.2006, p. 1).

(7) Article 69 of Commission Regulation (EC) No 817/2004 [rural development]

Article 25 of Council Regulation (EC) No 1782/2003 [direct support schemes]

Part II, Title III of Commission Regulation (EC) No 796/2004 [direct support schemes]

Article 8 of Commission Regulation (EEC) No 2159/89 [nuts]

Article 8 of Commission Regulation (EC) No 1621/1999 [dried grapes].

(8) OJ L 42, 16.2.1990, p. 6. Regulation as amended by Regulation (EC) No 163/94 (OJ L 24, 29.1.1994, p. 2).

(9) OJ L 141, 30.4.2004, p. 18. Regulation as last amended by Regulation (EC) No 972/2007 (OJ L 216, 21.8.2007, p. 3).

(10) http://europa.eu.int/comm/taxation_customs/dds/en/csrdhome.htm

(11) OJ L 273, 16.10.2001, p. 6.

(12) OJ L 147, 30.6.1995, p. 7. Regulation as last amended by Regulation (EC) No 1996/2006 (OJ L 398, 30.12.2006, p. 1).

(13) OJ L 102, 17.4.1999, p. 11. Regulation as last amended by Regulation (EC) No 1913/2006 (OJ L 365, 21.12.2006, p. 52).