close
Jump to content

Wikidata:Property proposal/Polish Taxpayer Identification Number

From Wikidata

Polish Taxpayer Identification Number

[edit]

Originally proposed at Wikidata:Property proposal/Organization

Descriptionan identifier for an entity paying taxes in Poland
RepresentsNIP (Q48840369)
Data typeExternal identifier
Allowed values\d{10}
Example 1Warsaw (Q270) → 5252248481
Example 2AGH University of Science and Technology (Q414245) → 6750001923
Example 3Association of Polish Minecraft Wiki (Q133944039) → 6423258855
Sourcehttps://isap.sejm.gov.pl/isap.nsf/DocDetails.xsp?id=WDU20250000237
See alsoEU VAT number (P3608), Belarus Tax Identification Number (P9782)
Wikidata projectWikiProject Poland (Q7160149), WikiProject Organizations (Q21830563)

Motivation

[edit]

The Polish Taxpayer Identification Number (in short, the NIP) requires creating a new property. Other Polish company numbers already have their own properties, namely the REGON ID (P11440) and the KRS number (P12228), but the NIP remained missing. Similarly, a separate property for entities from Belarus is already available as the Belarus Tax Identification Number (P9782). It should be noted that the NIP is currently loosely used as the EU VAT number (P3608), which is incorrect. The EU VAT number (P3608) is not the same as the Polish NIP. While a NIP can be a EU VAT number (P3608), preceded by phrase "PL", but this is not a rule. Often, a NIP exists, but the corresponding EU VAT number (P3608) does not. For example, in the Association of Polish Minecraft Wiki (Q133944039), due to a lack of valid options, the NIP was entered as the EU VAT number (P3608), even though this entity does not have the EU VAT number (P3608). Therefore, creating a new property for the Polish NIP is fully justified. Best regards, BartoszKonkol (talk) 06:30, 16 July 2025 (UTC)[reply]

Discussion

[edit]
  • BERJAYA Comment One thing to notice that the allowed values should be 10 or 11 digits (\d{10,11}), as per the Official Journal of the European Union C 481/15. Second thing is whether we should allow hyphens, as they are sometimes part of the official documentation with Tax Offices (Urząd Skarbowy), but they function the same without them, so I'm not too stingy about this Holek (talk) 11:49, 18 July 2025 (UTC)[reply]
    @Holek: Hi! The PESEL number is 11 digits long and is used in Poland to identify individuals. Individuals who do not run businesses use a PESEL as their tax identifier, but it is not the same as a NIP. Regarding the dash, it used to be used to grouping of digits. This is now being phased out, but formally, dashes have never been an integral part of the NIP. Best regards! BartoszKonkol (talk) 17:48, 18 July 2025 (UTC)[reply]
    @BartoszKonkol: Aah, right! They didn't specify that the 11-digit number was PESEL, hence my confusion! Sorry for that, thanks for reminding me of that! Holek (talk) 09:55, 22 July 2025 (UTC)[reply]
  • BERJAYA Comment Shouldn’t this be an external identifier? —Tacsipacsi (talk) 16:33, 26 July 2025 (UTC)[reply]
    @Tacsipacsi: Hi! It is possible, but there would not be a corresponding formatter URL (P1630) for this property, so I was not sure if it was actually a data type pointing to an external identifier. Regards, BartoszKonkol (talk) 19:43, 26 July 2025 (UTC)[reply]
    @BartoszKonkol: Are you sure there is no formatter URL, nor is it likely to become one available in the future?
    Wikidata:External identifiers indeed states that the formatter URL is required, but as far as I know, this isn’t technically true – the software can handle external identifiers without formatter URLs, by simply not turning the values into links –, nor is it by convention absolutely mandatory, so even if there is no URL, I think it’s fine to create it as an external ID.
    I also understand if you don’t want it; but in that case, it should be a string, not a monolingual text, for two reasons:
    • It has no linguistic content, so it makes no sense to say that the ID of Warsaw is 5252248481 in Polish (or in English or in any other language) – monolingual text is exactly about storing the language next to the actual value.
    • Should we later decide that we do want it to be an external identifier, a string-valued property can be simply converted by a developer, while a monolingual text-valued property would have to be deprecated, moved to a new property via a bot and finally the old property deleted. (This difference is because both string and external ID have the value type string, while monolingual text has the value type monolingualtext, and the value type is what affects the storage in items, the data type only affects its display.)
    P.S. It’s enough to ping someone either with {{Reply to}} or in the summary. Because you did both, I got two mention notifications. Which is not a big problem, but unnecessary. —Tacsipacsi (talk) 20:28, 26 July 2025 (UTC)[reply]
    @Tacsipacsi: Hi! First, I thank you for the extensive explanations and I apologize for only replying now. Regarding formatter URL (P1630), it is unlikely to be available in the future. The situation is similar with REGON ID (P11440), although from what I have just checked, it already has its data type set to an external identifier and since it is a good reference point, such a type should indeed be appropriate for this property. Regarding the type as a monolingual text, I understood it the other way around, as if it were meant to denote a language-independent value. So I definitely misunderstood that. Thank you for pointing that out. Thanks also for the information about the mention; I did not know it worked that way and the pings were duplicated. Sorry for the confusion. Best regards! BartoszKonkol (talk) 03:12, 31 July 2025 (UTC)[reply]
  • BERJAYA Comment @ArthurPSmith: Could you please create this property? Thanks in advance! ~ BartoszKonkol (talk) 20:39, 8 August 2025 (UTC)[reply]
  • @BartoszKonkol, Holek, Tacsipacsi: ✓ Done ArthurPSmith (talk) 02:07, 22 August 2025 (UTC)[reply]
Retrieved from "https://www.wikidata.org/w/index.php?title=Wikidata:Property_proposal/Polish_Taxpayer_Identification_Number&oldid=2395280964"