What happened to division 62, computer programming and consultancy?

Division 62, computer programming, consultancy and related activities, was restructured in NACE Rev. 2.1 so that each former class became a group containing a single class. Paragraphs 168 to 170 of the manual state the changes. The restructuring is a change in the shape of the hierarchy, not a change in the legal effect of a code, and it does not determine a code for a specific reader.

How did computer programming change?

Paragraph 168 states that class 62.01, computer programming activities, was transformed into group 62.1, computer programming activities, containing a single class 62.10, computer programming activities. The activity content is carried under a new number at a new level. The old class number 62.01 does not appear in the Rev. 2.1 structure. The new class number 62.10 sits inside the new group 62.1, and the group contains no other class. A reader who searches the Rev. 2.1 structure for 62.01 will not find it, and a reader who reads 62.10 without stating the version may confuse it with an old numbering pattern. The version must be stated.

The transformation matters for correspondence reading. A one to one correspondence at class level, where one Rev. 2 class corresponds exactly to one Rev. 2.1 class, is one of the four correspondence types in paragraph 207. Whether the programming change is recorded as one to one, or as part of a wider many to many pattern, is a question for the correspondence table, because paragraph 173 states that cybersecurity activities were integrated into the new classes in this division, which means the content of the new classes is not identical to the content of the old classes alone. This guide does not assert a correspondence type for the division. The table must be read.

How did consultancy and other services change?

Paragraph 169 states that classes 62.02, computer consultancy activities, and 62.03, computer facilities management activities, were merged into one new group 62.2, computer consultancy and computer facilities management activities, which contains a single class 62.20 of the same title. Two former classes therefore become one group with one class. The merger joins two activities that the old structure kept apart, under a combined title that names both. The explanatory note for the class states what the combined class includes and excludes, and the note is the authority for the content of the merged class, not the two old titles added together.

Paragraph 170 states the third change. Class 62.09, other information technology and computer service activities, was transformed into a new group 62.9, other information technology and computer service activities, which contains a single class 62.90 of the same title. The residual character of the old class is preserved in the new group title: other activities, not elsewhere classified in the division, sit here. The residual character does not make the class a general container for any computing work. The note for the class states its inclusions and exclusions, and work that belongs in groups 62.1 or 62.2, or in division 63, is excluded by the note.

How is the division laid out now?

| Group | Class | Former position, as stated in paragraphs 168 to 170 |

|---|---|---|

| 62.1 | 62.10 | Former class 62.01, transformed into a group |

| 62.2 | 62.20 | Former classes 62.02 and 62.03, merged |

| 62.9 | 62.90 | Former class 62.09, transformed into a group |

The table follows paragraphs 168 to 170. Each group contains a single class, and the group and class titles match. The table states the former position only as the manual summary states it. It does not state the correspondence type for any class, because the manual summary does not state it, and the cybersecurity integration in paragraph 173 means the content boundaries must be checked in the notes and the table before any correspondence claim is made.

What does the split not decide?

The split changes the structure of the classification. A code legal effect is unchanged by this, because beyond statistical use a code has no legal effect. Eurostat and the EUR-Lex summary both confine the legislation to statistical purposes. When a dataset shows an old Section J code, the first two questions are which version of the classification the dataset uses and what the correspondence table records about the move. The letter alone answers neither question, and this guide answers neither for a specific unit.

Where is a moved code confirmed?

Confirmation here means three checks in order. First, the section 4 summary in the manual for the structural change. Second, the explanatory notes for the categories at each end of the move. Third, the institute or register for the entry held for a specific unit. This guide gives the first check and points to the other two.

Read division 62 as three single class groups, check the notes for the merged and residual classes, and confirm the entry with the institute or register that holds it.