Compliance Overview
The Compliance module manages regulatory obligations across your practice using a template-driven model. Instead of tracking deadlines manually, AtlasOS combines entity service flags, compliance templates, public holidays, workflow stages, and calendar visibility to keep work moving.
How Compliance Works
Compliance work is built from a few live building blocks:
- compliance templates define what should be generated
- service flags determine which obligations apply to an entity
- obligations store the actual dated compliance work
- workflow step templates can spawn linked task work
- calendar layers surface obligations, consolidated deadlines, year-ends, holidays, and tasks together
Current obligation model
The current obligation records include fields such as:
- obligation type
- deadline type
- regulatory body
- period
- due date
- effective due date
- filing status
- workflow stage
- assigned user
- priority
- consolidated vs entity-scoped status
- notes and tracking references
Workflow stages
The current workflow-stage model is:
- pending
- preparation
- internal_review
- client_approval
- filing
- payment_pending
- closed
Filing status and prioritization
Obligations can also carry filing status and auto-priority metadata. The live APIs support filtering and sorting by:
- entity
- regulatory body
- deadline type
- filing status
- workflow stage
- date range
- assigned user
- consolidated only vs entity-only
- due date, priority, entity, or obligation-type ordering
Template-driven generation
The current compliance engine supports both practice-specific and system templates, filtered by jurisdiction.
Generation currently considers:
- jurisdiction
- regulatory body
- service flag
- entity type filter
- annual and biannual month rules
- last-business-day logic
- year-end-relative due date rules
- public holidays when calculating effective due dates
- duplicate protection for already-created obligations
Workflow task spawning
For supported obligation types, AtlasOS can also generate linked workflow tasks from workflow step templates so operational work is created alongside the obligation record.
Deadline escalation and notifications
The live system escalates obligation and linked-task priority based on time to deadline and overdue state, and it supports notification creation for approaching and overdue work.