Premium payment histories

Detects references to premium payment histories in financial and compliance documents. Commonly found in international regulatory filings, transaction records, and audit documentation.

Type

regex

Engine

boost_regex

Confidence

medium

Confidence justification

identifier/document-structure anchored regex with constrained context replaces phrase-only detection. Added context gating and exclusion rules improve precision and reduce incidental matches.

Detection quality

Mixed

Jurisdictions

global

Regulations

GDPR

Data categories

financial

Scope

wide

Platform compatibility

Purview: Compatible, GCP DLP: Compatible, Macie: Compatible, Zscaler: Compatible, Palo Alto: Degraded, Netskope: Unsupported

Pattern

(?is)\b(?:premium\s+payment|insurance\s+premium|payment\s+history|premium\s+schedule|premium\s+due|policy\s+renewal|premium\s+arrears|instalment\s+payment|premium\s+notice|lapsed\s+policy|premium\s+collection|policyholder\s+payment)\b

Corroborative evidence keywords

premium payment histories, premium, payment, histories, credit, lending, insurance, financial, fiscal, monetary, accounting, treasury, audit, revenue, expenditure, budget, ledger, accounts payable, accounts receivable, balance sheet (+31 more)

Proximity: 300 characters

Should match

• premium payment — Primary topic phrase match
• insurance premium — Case-insensitive topic phrase match
• payment history — Alternative topic phrase match
• premium schedule — Additional topic phrase match

Should not match

• unrelated generic text without domain phrases — No relevant topic phrases present
• placeholder value 12345 — Random text should not match topic-specific regex
• credit premium — Generic word pair from old broad template should not match

Known false positives

• Financial terminology appearing in published reports, accounting textbooks, regulatory guidance, or template documents without actual transaction data. Mitigation: Require corroborative evidence keywords within the proximity window. Cross-reference with structured financial identifiers to confirm actual sensitive data.
• In English (as the primary international business language), standard business terminology overlapping with financial detection keywords in routine correspondence and documentation. Mitigation: Increase confidence threshold when scanning business correspondence. Layer with transaction-specific patterns for higher precision.

References

• https://handbook.apra.gov.au/standard/gps-230
• https://www.oaic.gov.au/privacy/your-privacy-rights/your-personal-information/what-is-personal-information