Netherlands Tax Identification Number
Detects Netherlands 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: nine-digit numbers are common across many domains. Dutch tax-specific keywords like 'BSN' or 'burgerservicenummer' are required for accurate detection.
- Detection quality
- Verified
- Jurisdictions
- nl, 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{9}\bCorroborative evidence keywords
BSN, burgerservicenummer, tax identification, belastingnummer, sofinummer, TIN, tax identification number, tax number, tax return, IRD, NIF, tax ID, inland revenue, taxpayer identification, αριθμός φορολογικού μητρώου, ΑΦΜ, φορολογικός, Abgabenkontonummer, adóazonosító, adószám (+32 more)
Proximity: 300 characters
Should match
123456789— Nine-digit Dutch BSN/tax number987654321— Dutch burgerservicenummer112233445— Netherlands tax identification number
Should not match
12345678— Eight digits, too short for Dutch TIN1234567890— Ten digits, exceeds Dutch TIN 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.