Poland: how is the current PKD position checked?

The current PKD position in Poland is checked with Statistics Poland, GUS, and with the registers that hold entries, because no timetable, code list, or register procedure for Poland was verified against a GUS page for this work. Secondary summaries, including law firm and consultancy summaries, describe a new Polish Classification of Activities called PKD 2025, with an in force date and a transition period, and with register names including CEIDG, the Central Registration and Information on Business, the National Court Register, KRS, and REGON, the National Official Register of National Economic Entities.

Those summaries were not verified against GUS, and this guide does not present their dates, counts, or procedures as the institute’s position. A guide that copied them would present secondary claims as primary facts. Instead, this guide describes how a reader checks the position directly: what GUS publishes, what the registers hold, and what questions to ask, with an explicit statement that no timetable was verified.

What should a reader check first?

A reader should check first whether GUS publishes a current classification page, a structure, explanatory notes, and a correspondence table, and what version and date that material states. The check should be made on the GUS website itself, not on a secondary summary. A reader should record the version stated on the GUS page, the date of the page, and the edition of any table found. A reader should then check whether the register that holds the entry, CEIDG for sole traders and KRS for companies, states a procedure for checking or updating an entry, and what that procedure says about the version to use. The two checks answer different questions: GUS answers what the classification is, and the register answers what entry is held and how it is updated. A reader who checks only one will have an incomplete position. No timetable was published on a GUS page checked on 28 October 2026, in the sense that no GUS timetable page was returned for this work, and no timetable is asserted in this guide.

Check	Asked of	What to record
Classification version and structure	GUS, on its own website	Version, date, edition of any table
Entry held for the unit	Register that holds it, CEIDG or KRS as applicable	Entry, version stated beside it, date copied
Movement between versions	Correspondence table published by GUS, if available	Row, direction read, edition stated
Procedure for updating an entry	Register that holds it	Procedure as stated by the register itself

The table above is a checking method, not a statement of Polish procedure. It names the registers as they appear in secondary summaries, for the purpose of telling a reader where to ask, and it does not assert that those summaries describe the registers correctly. The reader must confirm the register names and procedures with the registers themselves.

How is a Polish code read in a dataset?

A Polish code in a dataset is read with its version, its reference period, and its source stated, as with every national variant after a revision. A bare code is ambiguous, because the same digits can sit in different places under different versions, and different digits can describe the same activity after renumbering or restructuring. A dataset that mixes codes from two versions, without stating which code belongs to which version, cannot be compared across the change. A reader should ask the dataset publisher for the version, and should not guess it from the digits. A reader should also check the date on which the code was copied from the register, because an entry copied before a version change will show the old code, while the same unit shows the new code in the register after the change. The European correspondence table shows the movement at the shared levels. The GUS table, where published, shows the movement at the Polish levels, including any Polish fifth level detail. Neither table determines the entry for a specific unit.

What must not be copied from secondary summaries?

A reader must not copy a timetable, a code, a count, or a procedure from a secondary summary and present it as the institute’s position. Secondary summaries in this area state dates, transition periods, subclass counts, and register deadlines with confidence, and they disagree with each other in detail. The disagreement itself is a warning: where secondary sources disagree, the primary source must be checked, and where the primary source cannot be found, the position must be stated as unchecked. This guide follows that rule. It states no in force date, no transition end date, no subclass count, and no register deadline for Poland. It states the checking method, and it directs the reader to GUS and to the registers. A future update to this guide should add the timetable and the procedure only when they have been verified on a GUS or register page, with the page cited.

What does a PKD code not decide?

A PKD code, like every statistical classification code, does not decide any question about a specific business beyond its statistical description. It does not decide tax, social security, licensing, funding or collective agreement questions. The EUR-Lex summary states that the European legislation only applies to statistical purposes. Other bodies apply their own rules to the questions they decide. The entry for a specific unit is confirmed with GUS or the register that holds the record. This site holds no register and decides no entry. A reader who needs the current Polish position should check GUS and the register directly, and should treat any secondary date as unchecked until the institute or register confirms it.

No Polish timetable was verified against GUS for this guide, the check runs through GUS for the classification and through the register for the entry, and no secondary date, count or procedure is presented as the institute’s position.