1. 5 NSI data to EGR
ESTP Training on EGR
22-23 May 2019

2. NSI data to EGR on LEU and REL
NSIs deliver to EGR:
Data on resident legal units - LEU file
Relationships of the delivered legal units - REL file
Enterprises of the delivered legal units - ENT file
Links of enterprises and legal units - LEL file
Date of delivery: November T+1
Yearly update - once per year
File transfer via EDAMIS
Automatic EDIT validation of the files and manual upload to the EGR at Eurostat

3. Legal units to EGR (1)
LEU file to EGR with resident legal units which are members of MNEs:
Inward perspective: resident legal units belonging to foreign multinational groups
Outward perspective: resident legal units belonging to multinational groups with GDC in the country
NSIs can deliver both type of data
Only resident legal units should be sent to EGR

4. Legal units to EGR IS (2) CSV format One record = one legal unit
Pos.
Field 1
LEU_FRAME_RYEAR 20
LEU_LFORM 2
LEU_LEID 21
LEU_TYPE 3
LEU_NSA_ID 22
LEU_STA_CODE 4
LEU_LEI 23
LEU_SPE_CODE 5
LEU_NAT_ID 24
LEU_SPE_CODE_CONF_I 6
LEU_NAT_ID_NIS_CODE 25
LEU_DATE_INC 7
LEU_NAT_ID_2 26
LEU_DATE_LIQ 8
LEU_NAT_ID_2_NIS_CODE 27
LEU_NACE_CODE 9
LEU_PRV_NAT_ID 28
LEU_NACE_CODE_CONF_I 10
LEU_PRV_NAT_ID_NIS_ CODE 29
LEU_PERS_EMPL 11
LEU_NAME 30
LEU_PERS_EMPL_CONF_I 12
LEU_ADDRESS 31
LEU_FOREIGN_OWNED_I 13
LEU_CITY_NAME 32
LEU_FOREIGN_OWNER_I 14
LEU_POSTAL_CODE 33
LEU_NGH_LEID 15
LEU_COUNTRY_CODE 34
LEU_UCI_IND 16
LEU_COUNTRY_TEL_CODE 35
LEU_EORI_ID 17
LEU_TEL_NUMBER 36
LEU_GGH_IND 18
LEU_ 37
LEU_STATE_NAME 19
LEU_WEB
CSV format
One record = one legal unit
37 variables

5. Legal units to EGR (3) Several compulsory fields, e.g.:
LEU_FRAME_RYEAR
LEU_LEID, LEU_NSA_ID
LEU_NAT_ID, LEU_NAT_ID_NIS_CODE
LEU_NAME
Also compulsory:
LEU_ADDRESS, LEU_CITY_NAME
In case of missing data for address and city an X should be added to these fields

6. Legal units to EGR (4) Name and address details Accepted characters
Latin characters, transformation needed for Greek and Cyrillic names
Characters of the English alphabet, transformation needed for specific characters (e.g. ä, ö, ß, á)
Legal forms abbreviated in company names
Accepted characters
a b c d e f g h i j k l m n o p q r s t u v w x y z 
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z   
space – - + ( ) . # _ = < > / \

7. Legal units to EGR (5) LEU_FOREIGN_OWNED_I LEU_FOREIGN_OWNER_I
Indicator whether the LEU is (directly or via its parent) foreign owned (Y/N). Foreign owned means that the unit is belonging to a foreign multinational group according to the NSA!
LEU_FOREIGN_OWNER_I
Indicator whether the LEU has foreign subsidiaries (Y/N). Y if a LEU does have foreign subsidiaries (with a control relationship). Only the direct control relationships to be reported!
Interpretation is different from LEU_FOREIGN_ OWNED_I!

8. Legal units to EGR (6) LEU_NGH_LEID LEU_UCI_IND
LEID number of the national group head. Should be filled if this information is available. If the unit is a national group head, the LEU_NGH_LEID= the LEID number of the unit.
LEU_UCI_IND
Indicator whether the legal unit is GDC in a group or not (Y/N). This should be filled according to the available information. It will not define automatically the GDC of an EGR group but will give information to the EGR that the LEU is considered as GDC by the NSA.

9. Legal units to EGR (7) LEU_GGH_IND
Indicator whether the legal unit is GGH in a group or not (Y/N). This should be filled according to the available information. It will not determine the unit as GGH in an EGR group but will give information to the EGR that the LEU is considered as GGH by the NSA.

10. Legal units to EGR (8) Example record in the LEU file
Pos.
Field 1
LEU_FRAME_RYEAR 20
LEU_LFORM 2
LEU_LEID 21
LEU_TYPE 3
LEU_NSA_ID 22
LEU_STA_CODE 4
LEU_LEI 23
LEU_SPE_CODE 5
LEU_NAT_ID 24
LEU_SPE_CODE_CONF_I 6
LEU_NAT_ID_NIS_CODE 25
LEU_DATE_INC 7
LEU_NAT_ID_2 26
LEU_DATE_LIQ 8
LEU_NAT_ID_2_NIS_CODE 27
LEU_NACE_CODE 9
LEU_PRV_NAT_ID 28
LEU_NACE_CODE_CONF_I 10
LEU_PRV_NAT_ID_NIS_ CODE 29
LEU_PERS_EMPL 11
LEU_NAME 30
LEU_PERS_EMPL_CONF_I 12
LEU_ADDRESS 31
LEU_FOREIGN_OWNED_I 13
LEU_CITY_NAME 32
LEU_FOREIGN_OWNER_I 14
LEU_POSTAL_CODE 33
LEU_NGH_LEID 15
LEU_COUNTRY_CODE 34
LEU_UCI_IND 16
LEU_COUNTRY_TEL_CODE 35
LEU_EORI_ID 17
LEU_TEL_NUMBER 36
LEU_GGH_IND 18
LEU_ 37
LEU_STATE_NAME 19
LEU_WEB
Example record in the LEU file
2015;AT c;
;;03962c;21013;
ATU ;22013;;;
PETER GMBH; PUCHSTR. 76; KITZBUHEL;8020;AT;;;;
23/07/1993;;4110;C;47;C;Y;
N;AT c;N;;N;

11. Relationships to EGR (1)
REL file to EGR with the relationships of the legal units of the LEU file
All legal units participating in relationships, (including the non-resident legal units) should be identified with LEID numbers
LEID numbers can be collected from the EGR IS after successful identification of foreign legal units

12. Relationships to EGR (2)
Relationships can be:
Relationships between two resident legal units,
Relationships between one resident and one foreign legal unit
…where the resident legal units are part of multinational enterprise groups
Control relationships (>50%) with preference
Minority relationships as above 10% can be also sent to EGR
Currently: focus on relationships between incorporated units

13. Relationships to EGR (3)
Pos.
Field 1
REL_FRAME_RYEAR 2
REL_LEU_LEID 3
REL_P_LEU_LEID 4
REL_STATUS_REL 5
REL_TYPE_OF_REL 6
REL_TYPE_OF_OWN 7
REL_PERCENT_CONTROL 8
REL_PERCENT_SHARES 9
REL_START_DATE 10
REL_END_DATE 11
REL_CONF_I
CSV format
One record = one relationship between two LEUs
REL expressed between two LEID numbers
11 variables

14. Relationships to EGR (4)
Pos.
Field 1
REL_FRAME_RYEAR 2
REL_LEU_LEID 3
REL_P_LEU_LEID 4
REL_STATUS_REL 5
REL_TYPE_OF_REL 6
REL_TYPE_OF_OWN 7
REL_PERCENT_CONTROL 8
REL_PERCENT_SHARES 9
REL_START_DATE 10
REL_END_DATE 11
REL_CONF_I
Example records
in the REL file:
2018;AT c;
AT f;A;C;D;
100;100;;;C
2018;AT f;
BE ;A;C;D;
51;51;;;C

15. Enterprises to EGR (1)
ENT file to EGR with the enterprises of the legal units of the LEU file
LEL file with links between enterprises and legal units
1-1, 1-n combinations are possible
Timing is the same as for LEU and REL files
EGR 2.0 concept is based on clear split of LEU and ENT
EGR 2.0 output (EGR FATS) is ENT oriented, enterprises and their links to legal units are needed!

16. Enterprises to EGR (2) Information on resident enterprises CSV format
Pos.
Field 1
ENT_NSA_ID 2
ENT_FRAME_RYEAR 3
ENT_COUNTRY_CODE 4
ENT_START_DATE 5
ENT_END_DATE 6
ENT_NAME 7
ENT_STA_CODE 8
ENT_INST_CODE 9
ENT_NACE_CODE 10
ENT_PERS_EMPL 11
ENT_TURNOV 12
ENT_TURNOV_CUR_CODE 13
ENT_REP_LEU_LEID 14
ENT_SIZE_CLASS
Information on resident enterprises
CSV format
One record = one enterprise
ENT identified by NSA ID number
14 variables

17. Enterprises to EGR (3) Example record in the ENT file:
Pos.
Field 1
ENT_NSA_ID 2
ENT_FRAME_RYEAR 3
ENT_COUNTRY_CODE 4
ENT_START_DATE 5
ENT_END_DATE 6
ENT_NAME 7
ENT_STA_CODE 8
ENT_INST_CODE 9
ENT_NACE_CODE 10
ENT_PERS_EMPL 11
ENT_TURNOV 12
ENT_TURNOV_CUR_CODE 13
ENT_REP_LEU_LEID 14
ENT_SIZE_CLASS
Example record in the ENT file:
R009X5422;2018;AT; 24/02/1992;;PETER GMBH; A;;1530; 5;160200;EUR; AT b;;

18. ENT-LEU links to EGR (1)
Pos.
Field 1
LNK_ENT_NSA_ID 2
LNK_LEU_LEID 3
LNK_FRAME_RYEAR 4
LNK_START_DATE 5
LNK_END_DATE
Relationships between enterprises and their legal units
CSV format
One record = one link
1-1, 1-n combinations possible
ENT identified by NSA ID number
LEU identified by LEID number

19. ENT-LEU links to EGR (2) Example record in the LEL file:
Pos.
Field 1
LNK_ENT_NSA_ID 2
LNK_LEU_LEID 3
LNK_FRAME_RYEAR 4
LNK_START_DATE 5
LNK_END_DATE
Example record in the LEL file:
R009X5428; AT c;2018; 24/02/1992;

20. Consistent LEU, REL, ENT, LEL data to EGR
LEU data
2018;AT c; ;;039678c;21013 ;ATU ;22013;;;PETER GMBH;…
REL data
2018;AT c;BE ;A;C; D;100;100;;;C
ENT data
R009X542;2015;AT;24/02/1992;;PETER GMBH;A;; 1530;5;160200;EUR;AT c;;
LEL data
R009X542; AT c;2018;24/02/1992;

21. Summary: NSI information to EGR
No data on the foreign parent or subsidiary!
LEU
BE21021
2 REL data
1 LEU data
LEU
AT21013
03967c
ENT
R009X542
3 ENT data
4 LEL data

22. Foreign-controlled legal units to EGR without relationships
From the 2016 cycle NSIs can send foreign controlled legal units without relationship data
Where parents were not identified
The legal units should be added to the LEU file
Variable LEU_FOREIGN_OWNED_I should be = Y
Later in the process, if no other relationship information will arrive to EGR, the system will create for them single unit "groups“ marked as foreign controlled (FC)
Country of GDC can be specified in the repair phase
The single unit "groups" will be part of EGR frames, if country of GDC is different

23. Validation of data files
EDAMIS delivers the LEU, REL, ENT and LEL files to a folder on the Eurostat secure area
EDIT is validating the files
If format is correct EDIT splits the files into two:
Valid records
Invalid records
Automatic error report is sent to NSIs in EDAMIS
Files with valid records will be loaded to EGR
Manually by the EGR team

24. EDIT validation rules for LEU
Compulsory fields should be filled, e.g.
LEU_NAME, LEU_ADDRESS
Check for values of code lists, e.g.
LEU_NACE_CODE values as in the code list
Check on dependent variables, e.g.
if LEU_NAT_ID_2 is not null then LEU_NAT_ID_2_NIS_CODE is not null
Check for characters in name and address fields
Validation of the format of the national ID
The formats should follow the agreed pattern

25. EDIT validation rules for REL
Compulsory fields should be filled, e.g.
REL_LEU_LEID, REL_P_LEU_LEID
Check for values of code lists, e.g.
REL_STATUS_REL, REL_CONF_I
Check on dependent variables, e.g.
if REL_STATUS_REL is A then REL_END_DATE should be null
REL_TYPE_OF_REL and REL_TYPE_OF_OWN variables only specific combinations are accepted
limitations on percentage values (REL_PERCENT_ CONTROL and REL_PERCENT_SHARES) to keep the consistency of data
THE MATRIX

26. The MATRIX
For type of relationship and type of ownership variables only specific combinations are accepted
5 combinations (out of 6 potential ones)
There are additional limitations for the % values

27. How to express relationships?
Majority with control (50%+)
Minority, no control (below 50%)
Through accounts (cumulative control / indirect)

28. How to express relationships?
Express relationships in simple way
Majority: LEID;P_LEID;C;D;99.00;99.00
Minority: LEID;P_LEID;N;D;15.00;15.00
Indirect: LEID;P_LEID;A;I;51.00;49.00
EGR will calculate indirect relationships, where needed
E.g. if the two 40-40% minority parents have the same owner, EGR will create the indirect link
Fill both percentage values, otherwise EDIT will impute 0.01 or (based on the matrix table)

29. EDIT validation rules for ENT
Compulsory fields should be filled, e.g.
ENT_NSA_ID is not null
ENT_COUNTRY_CODE is not null
ENT_NAME is not null
Check for acceptable characters for name
Check for values of code lists, e.g.
ENT_STA_CODE values as in the code list
ENT_NACE_CODE values as in the code list
ENT_TURNOV_CUR_CODE values as in the code list

30. EDIT validation rules for LEL
Compulsory fields should be filled, e.g.
LNK_ENT_NSA_ID, LNK_LEU_LEID
Checks for dates
Date format should be DD/MM/YYYY
LNK_START_DATE <= LNK _END_DATE
LNK_START_DATE <= LNK _FRAME_RYEAR
LNK_END_DATE between 01 JAN and 31 DEC of LNK_FRAME_RYEAR
Start and end dates are not compulsory!

31. EDIT error reports
Example of EDIT error report with invalid characters
LEU file
Rule 14 violated
Example of EDIT error report with invalid codes
REL file
Rule 4 and 5 violated 31

32. EDIT validation rules
The Guidelines on EGR wiki explain the critical points (e.g. the MATRIX)
The validation rules of EGR files can be found on the EGR wiki
EDIT files page
2 documents:
EGR IS files
EGR files

33. Most frequent errors of EGR CORE files (1)
Wrong file structure
Columns are missing, wrong order
Header row is missing
Field separator is comma instead of semi-colon
Special characters in the files
Comma, quotation mark in names, ö, ä, ü, à, etc.
Number values with decimal separator comma ","
Empty % numbers with double quotations ("")
Spaces in fields, e.g. " "

34. Most frequent errors of EGR CORE files (2)
Invalid date formats:
D/M/YYYY instead of DD/MM/YYYY
Invalid dates, e.g. 31 February
ENT_START_DATE after the frame reference year
Inconsistency between LEU, REL files (manual checks by EGR Team)
Inconsistency between LEU, ENT, LEL files (manual checks by EGR Team)

35. Most frequent errors of EGR CORE files (3)
Wrong file naming in EDAMIS
EGR_LEU_A_CC_2018_0001_V0001_DDMMYYYY_NSA.CSV
EGR_LEU_A_CC_2018_0001_V0001_DDMMYYYY_NSA.TXT
EGR_LEU_A_CC_2018_0001_V0001_DDMMYYYY-NSA.CSV
EGR_LEU_A_CC_2018_0001_V0001_YYYYMMDD_NSA.CSV
File naming in EDAMIS is defined by NSI user
Select the dataset: EGR_LEU_A
Select the year
Fill the free text comment : _NSA or _NSA_BR
Start and close request

36. Success factors for NSIs EGR CORE files
NSIs should update the NBRs based on validated data from the last final frame
Strong collaboration between NBRs and other relevant statistical domains on national level should be ensured
NSIs should develop strong validation rules on national level
NBRs should ensure business continuity
All contributors to the cycle should adhere to the calendar
Objective criteria for attributing Full/Partial authentic store and procedures for ensuring data coverage for EGR
Improvement of Group continuity algorithm

37. Guidelines, further reading
EGR wiki
Guidelines page
Guidelines 3 - LEU, REL, ENT and LEL data to EGR
EDAMIS & EDIT page
File naming
Validation rules

38. Notes