Skip to main content

Retention Monitoring

CoralLedger Comply enforces per-business data retention policies through scheduled enforcement runs. The default retention period is 7 years, as required by Value Added Tax Act, 2014, s. 26. Operators can review retention schedules, preview upcoming enforcement actions, and investigate detected violations before data is affected.

Accessing Retention Monitoring

Navigate to Platform Ops > Data Operations > Retention. This feature requires PlatformAdmin access.

Default Retention Policy

All businesses are subject to the platform-wide default:

SettingValueBasis
Minimum retention period7 yearsValue Added Tax Act, 2014, s. 26
Applies toTransactions, VAT returns, audit records, uploaded files
EnforcementScheduled; runs on a scheduled basis

Records that are within their retention window cannot be permanently deleted, regardless of operator action or approved deletion requests.

Per-Business Retention Policies

Operators can configure a custom retention policy for each business:

  1. Navigate to Platform Ops > Data Operations > Retention > Policies
  2. Select the business
  3. Adjust the retention period (minimum 7 years; longer periods are permitted)
  4. Click Save Policy
info

Custom policies can only extend the retention period beyond the 7-year minimum. Reducing a business's retention period below 7 years is not permitted.

Policy Summary

The Policy Summary table lists all businesses with their configured retention settings:

ColumnDescription
BusinessBusiness name
PolicyCustom or Default
Retention PeriodConfigured retention window
Records in WindowCount of records currently within retention
Upcoming PurgesRecords scheduled for purge in the next 90 days
ViolationsCount of active policy violations

Enforcement Preview

Before retention enforcement runs, operators can preview which records are scheduled to be purged:

  1. Navigate to Platform Ops > Data Operations > Retention > Preview
  2. Select the business (or view all)
  3. Set the preview window (e.g., next 30, 60, or 90 days)
  4. Click Run Preview

The preview shows:

  • Record Type — Transaction, return, file, etc.
  • Record ID — Unique identifier
  • Created Date — When the record was created
  • Retention Expiry — When the record is eligible for purge
  • Legal Hold — Whether a legal hold is blocking purge
tip

Use enforcement preview before each scheduled purge run to ensure no unexpectedly critical records are about to be removed.

Violation Detection

The system continuously monitors for retention policy violations — records that should have been retained but were prematurely deleted, or records past their retention window that have not yet been purged.

Viewing Violations

Navigate to Platform Ops > Data Operations > Retention > Violations to see:

ColumnDescription
Violation IDUnique identifier
BusinessAffected business
Record TypeType of affected record
Record IDAffected record identifier
Violation TypePremature deletion or retention overrun
Detected OnWhen the violation was flagged
SeverityLow, Medium, or High

Resolving Violations

  1. Review the violation details to understand the cause
  2. For premature deletion violations, check the Audit Trail for the deletion event
  3. Mark the violation as reviewed once investigated
  4. If data recovery is required, contact support

Enforcement Run

When the enforcement schedule triggers (or an operator manually initiates a run):

  1. Records past their retention window are identified
  2. Records under a legal hold are skipped
  3. Records within an active deletion grace period are skipped
  4. Eligible records are permanently purged
  5. A summary report is written to the Audit Trail

To manually trigger an enforcement run:

  1. Navigate to Platform Ops > Data Operations > Retention > Enforce
  2. Select the scope (single business or all)
  3. Review the enforcement preview
  4. Click Run Enforcement
warning

Enforcement purges are permanent and cannot be undone. Always run and review an enforcement preview first.

Best Practices

  1. Review the enforcement preview monthly — Avoid unexpected purges of important records
  2. Set longer retention for high-risk businesses — Businesses under audit or with litigation should have extended periods
  3. Resolve violations promptly — Unresolved violations may indicate a compliance gap
  4. Coordinate with legal holds — Ensure that any records subject to litigation are held before enforcement runs
  5. Export before purge — Use Business Data Export to archive records before they are purged if needed

By Statute References

Next Steps