Loading...
Asserts that no individual record in the table is older than the specified number of days without an update. Identifies records that may have been missed by incremental update pipelines or are stuck in a stale state.
Validates that the Customer Due Diligence (CDD) review date is not older than the risk-based refresh period. High-risk customers must be reviewed at least annually (365 days), medium-risk every 2 years (730 days), and low-risk every 3 years (1095 days). Stale CDD records indicate gaps in ongoing monitoring.
Asserts that the most recent value in a date/timestamp column is within the specified number of hours from the current time. Useful for verifying that new data is arriving as expected in date-partitioned or event-driven tables.
Validates that personal data records do not exceed their stated retention period from the collection date. Under CPRA, businesses must disclose retention periods and must not retain personal information longer than reasonably necessary for the disclosed purpose. Records past their retention limit must be flagged for deletion.
Validates that Suspicious Activity Reports (SARs) are filed within 30 calendar days of the initial detection of the suspicious activity. The filing_date minus detection_date must not exceed 30 days, per FinCEN regulatory requirements under 31 CFR 1020.320.
Validates that consumer data correction requests are resolved within the statutory SLA. Under CPRA, businesses must respond to correction requests within 45 calendar days of receipt, with a possible 45-day extension if reasonably necessary. This rule checks the gap between request_date and resolution_date.
Validates that the KYC review date is not stale based on the customer risk rating. High-risk customers must have KYC refreshed within 1 year, medium-risk within 2 years, and low-risk within 3 years. Stale KYC reviews expose the institution to regulatory risk and may indicate gaps in ongoing due diligence.
Asserts that the time difference between the source event timestamp and the load/ingestion timestamp is within the defined SLA. Detects pipeline lag, backpressure, or ingestion failures that cause data to arrive late.
Asserts that the latest partition or date value in a partitioned table is within the expected range of the current date. Ensures that daily, hourly, or other periodic data loads are completing on schedule.
Validates that claims are submitted within the timely filing limit from the date of service. Most payers require claims to be filed within 365 days (1 year) of the service date. Medicare requires filing within 12 months of the date of service, and many commercial payers have 90-180 day limits. Late filings result in claim denials.
Validates that Currency Transaction Reports (CTRs) are filed within 15 calendar days of the reportable cash transaction exceeding $10,000. Financial institutions must electronically file CTRs with FinCEN per 31 CFR 1010.306.
Asserts that a table has been updated within the specified number of hours. Uses the table's metadata (last modified timestamp) or a designated timestamp column to verify data is fresh and pipelines are running on schedule.
PCI-DSS 3.2.1 — cardholder data must not be retained longer than the documented business/legal need. Records older than the retention limit must be purged.
Golden records should be re-resolved within the refresh SLA after upstream source changes; stale masters drift from reality.
Reportable results must be transmitted to public health within the jurisdiction's mandated window (commonly 24 hours for urgent conditions) of the result being finalized. Late reports defeat outbreak response.
All source records up to the high-watermark must be present in target — guards incremental loads against gaps.
Case notifications must be transmitted to CDC within the cadence required for the condition (commonly within 7 days, sooner for urgent conditions).
CMS-9115 requires the Provider Directory API to be updated no later than 30 calendar days after the payer receives updated information.