Business licensing applications

Identifies business and trade licence application records, including renewal and variation applications. Topic phrases are retained for discovery; enforcement requires at least two populated applicant, enterprise, premises, activity, or licence fields, and high confidence also requires a formal application, licence, or permit reference.

Type: regex
Engine: boost_regex
Confidence: medium
Confidence justification: Medium confidence requires two populated application fields rather than licensing terminology alone. High confidence adds a formal reference tied to the application, licence, or permit.
Detection quality: Topic false positive
Jurisdictions: global
Regulations: GDPR
Data categories: pii
Scope: wide
Risk rating: 5
Platform compatibility: Purview: Compatible, GCP DLP: Compatible, Macie: Compatible, Zscaler: Compatible, Palo Alto: Degraded, Netskope: Unsupported

Pattern

(?is)\b(?:business\s+licensing\s+applications?|(?:business|trade)\s+licen[cs]e\s+(?:applications?|renewal\s+applications?|variation\s+applications?)|applications?\s+for\s+(?:a\s+)?(?:business|trade)\s+licen[cs]e|business\s+permit\s+applications?)\b

Corroborative evidence keywords

legal business name, premises address, business activity, licence category, application number

Proximity: 240 characters

Should match

Business licence application — Low-tier probe - licensing-application topic without populated fields
Business licence application; Legal business name: River Street Cafe; Premises address: 10 Queen Street; Business activity: food service — Medium-tier probe - multiple populated application fields without a formal reference
Business licence application; Application ID: BL-2026-1048; Legal business name: River Street Cafe; Premises address: 10 Queen Street; Licence category: food premises — High-tier probe - populated application with a formal licensing reference

Should not match

Building and operating permit application: site plan, zoning approval, occupancy certificate, and construction inspection — Building-permit application belongs to the adjacent permit SIT
Export licence application for controlled goods; exporter name and destination country — Export-control licensing is not routine business licensing
Professional licence application: applicant name, profession, qualifications, and registration board — Individual professional licensing must not collide
The software license application tracks the license holder, entitlement, and renewal date. — Software entitlement workflow is not a government business-licence application
Training example: Business licence application; Application ID: BL-2026-1048; Legal business name: River Street Cafe; Premises address: 10 Queen Street — Explicit training content must not enforce even with realistic fields and an identifier

Known false positives

Licensing authority guidance and blank application forms can contain the title and all expected field labels without containing a submitted application. Mitigation: Keep title-only material at discovery and require multiple labels with populated values; reserve 85 for a formal application or licence reference.
Building, export, professional, and software licensing workflows share applicant, approval, holder, and renewal language. Mitigation: Restrict the primary to business or trade licence and business-permit applications rather than generic licence, permit, registration, or approval phrases.
Training fixtures can contain realistic business names, premises, categories, and application numbers. Mitigation: Reject explicit template, demo, tutorial, sample-data, and training-example framing from enforcing tiers.