Period governance that can't be bypassed
Arvexi Period Management enforces a 5-stage lifecycle for every financial period: FUTURE, OPEN, IN_CLOSE, CLOSED, and LOCKED. Entity-level locking allows phased close processes. API-level enforcement means no mutations are possible on locked periods. Regardless of user role. AI verification checks all prerequisites before a period can be locked. Every state transition is fully audited.
The problem
Periods without enforcement are periods without integrity
The period is 'closed' but someone posts a journal entry anyway. The CFO asks for an adjustment after the books are finalized. A data import runs against last month because nobody changed the default period. Without system-level enforcement, 'closed' is a suggestion, not a state. Period integrity requires governance that can't be worked around.
Period lifecycle
Five stages from future to locked, enforced at every level
5-stage lifecycle
FUTURE: defined but not active. OPEN: accepting transactions and data. IN_CLOSE: close process underway with limited mutations. CLOSED: all entities certified, no changes. LOCKED: permanently sealed. Each transition has clear rules and is tracked in the audit trail.
Entity-level locking
Lock individual entities within a period independently. Entity A can be LOCKED while Entity B is still IN_CLOSE. This supports phased close processes where different subsidiaries operate on different timelines. The period transitions to CLOSED only when all entities are certified and locked.
API-level enforcement
Every mutation endpoint checks period and entity status before executing. Journal entries, reconciliation changes, data imports, and trial balance modifications are all blocked on locked periods. This enforcement is in the data layer. Not the UI. It cannot be bypassed by any user, role, or integration.
Intelligence and auditability
AI verifies readiness, the audit trail proves compliance
Locking a period is a consequential action. Arvexi uses AI to verify that every prerequisite is met before allowing the lock, and records every state change in an immutable audit trail that external auditors can review directly.
AI verification before locking
Every prerequisite checked before the period can be sealed
Before a period transitions to LOCKED, AI verification scans for: uncompleted close tasks, unposted journals, unapproved reconciliations, consolidation issues (IMPACTED or NO_DATA entities), unresolved IC disputes, and unsigned certifications. Any issue blocks the lock and presents a prioritized remediation list. No silent failures, no locked periods with incomplete work.
Complete audit trail
Every state change recorded, every decision traceable
Period opens, entity locks, failed lock attempts (with blocking reasons), administrative overrides, and final period sealing. Every event is logged with the user, timestamp, before/after state, and comments. The audit trail is immutable. External auditors can review period governance directly in the system without requesting exports or screenshots. See also Entity Certification. Part of Financial Close.
Period locking used to be a gentleman's agreement. Someone would always post a journal after we said the books were closed. Now the system enforces it at the API level. No exceptions.
VP of Accounting
VP of Accounting at Multi-Facility Healthcare System
FAQ
See period governance in action.
5-stage lifecycle, entity-level locking, API enforcement, AI verification. Book a demo to see periods that can't be bypassed.
Book a demo