The final gate before you close the books
Arvexi Entity Certification provides formal sign-off for every entity in your hierarchy before the period can be locked. A 5-stage lifecycle, NOT_STARTED through LOCKED, with prerequisite enforcement that blocks certification until all tasks, journals, and reconciliations are complete. Multi-level review chains ensure the right people approve at every level. Material changes after certification trigger automatic decertification.
The problem
Informal sign-off processes don't survive an audit
An email from the entity controller saying 'we're good to close.' A Slack message confirming the numbers look right. A checkbox in a shared spreadsheet. Informal sign-off has no prerequisite enforcement, no review chain, no decertification when something changes after the fact. When the auditor asks 'who certified this entity and when,' you're searching through email threads.
Certification engine
Five stages, enforced prerequisites, multi-level review
5-stage lifecycle
NOT_STARTED, IN_PROGRESS, PENDING_REVIEW, CERTIFIED, LOCKED. Each transition is enforced. You cannot skip stages or certify without meeting prerequisites. Every state change is recorded with the user, timestamp, and any comments. The lifecycle is auditable end to end.
Prerequisite enforcement
Certification is blocked until all prerequisites are met: all close tasks complete, all journals posted and approved, all reconciliations signed off, consolidation calc status OK. This is not a warning. It is a hard block. No exceptions, no overrides without explicit executive escalation.
Multi-level review chain
Configure one, two, or three levels of approval per entity. Entity controller, regional controller, corporate controller. Each signs off in sequence. Separation of duties is enforced: preparers cannot certify their own entities. The review chain is configurable per entity or entity group.
Governance and integrity
Certified means certified. Until it doesn't
Entity certification isn't a one-way door. When material changes happen after sign-off, Arvexi automatically revokes the certification and requires the entity to go through the full review chain again. This ensures the certified state always reflects the actual data.
Lock enforcement
Once certified and locked, no modifications are possible
When an entity reaches LOCKED status, all mutations are blocked at the API level. Not just the UI. No journal entries can be posted, no reconciliations can be modified, no trial balance data can be imported. The lock is enforced across every operation in the system. This is the foundation of period integrity.
Automatic decertification
Material changes revoke certification automatically
If a journal entry is corrected, a reconciliation is re-opened, or new trial balance data is imported after an entity has been certified, Arvexi automatically revokes the certification. The entity returns to IN_PROGRESS status with a recorded reason for decertification. The full review chain must be completed again before re-certification. Part of Financial Close.
The certification workflow gave us something we never had. Formal, auditable evidence that every entity was reviewed and signed off before period lock. Our external auditors noticed immediately.
Controller
Controller at Private Equity Portfolio Company
FAQ
See entity certification in action.
5-stage lifecycle, prerequisite enforcement, automatic decertification. Book a demo to see the final gate before period lock.
Book a demo