Dormancy

The implementation of a "dormancy" feature typically focuses on managing and automated fee processing for inactive entities. This is common in financial platforms, membership systems, and customer loyalty programs to maintain system hygiene and comply with unclaimed property regulations. Key Components of a Dormancy Feature

Define how settings at a higher level (like a division) flow down to sub-programs. dormancy

Automated alerts to users before their account enters a dormant state or incurs fees. The implementation of a "dormancy" feature typically focuses

: Establish a recurring schedule (e.g., daily at a specific timezone) to scan for accounts hitting these thresholds. Automated alerts to users before their account enters

Determine if dormancy rules apply to a specific program, division, or globally.

: Identify specific actions or processing codes that automatically return an account to "Active" status. Functional Requirements for Developers Feature Attribute Description Config Level

: Define a progression of states (e.g., Active → Inactive → Dormant → Unclaimed).