Poland Tax Identification Number
Detects Poland Tax Identification Number patterns. This pattern is based on a Microsoft Purview built-in sensitive information type. Due to the numeric format, corroborative evidence keywords are essential for reliable detection.
- Type
- regex
- Engine
- universal
- Confidence
- medium
- Confidence justification
- Medium confidence: the 3-3-2-2 digit grouping pattern with optional hyphens is somewhat distinctive but can match other formatted numbers. Keywords like 'NIP' improve accuracy.
- Detection quality
- Verified
- Jurisdictions
- pl, eu
- Regulations
- GDPR
- Data categories
- pii, financial, government-id
- Scope
- narrow
- Risk rating
- 7
- Platform compatibility
- Purview: Compatible, GCP DLP: Compatible, Macie: Compatible, Zscaler: Compatible, Palo Alto: Compatible, Netskope: Compatible
Pattern
\b\d{3}-?\d{3}-?\d{2}-?\d{2}\b
Corroborative evidence keywords
NIP, PESEL, numer identyfikacji podatkowej, tax identification, Urząd Skarbowy, TIN, tax identification number, tax number, tax return, IRD, NIF, tax ID, inland revenue, taxpayer identification, αριθμός φορολογικού μητρώου, ΑΦΜ, φορολογικός, Abgabenkontonummer, adóazonosító, adószám (+20 more)
Proximity: 300 characters
Should match
123-456-78-90— Polish NIP with hyphens1234567890— Polish NIP continuous digits987-654-32-10— Polish tax ID with separators
Should not match
123-456-78-9— Only 9 digits, too short for Polish NIP123-456-789-01— Wrong grouping for Polish NIP format
Known false positives
- Generic numeric sequences in non-tax contexts such as reference numbers or account identifiers Mitigation: Require corroborative evidence keywords within the proximity window to distinguish tax identifiers from general numeric data.
- Numbers from other identification schemes with similar digit patterns Mitigation: Layer with jurisdiction-specific detection to prioritise matches in tax-related documents and cross-reference with other identifier types.