A status machine that enforces your process, not a checklist you hope people follow
Arvexi's reconciliation workflow is a strict state machine: OPEN, IN_PROGRESS, PENDING_REVIEW, APPROVED. Plus AUTO_RECONCILED and EXCEPTION for edge cases. Separation of duties is enforced at the API level: the preparer cannot approve their own work. Period locking prevents changes after close. Every transition is logged. Your compliance team gets a process they can defend in an audit.
The problem
Your reconciliation 'workflow' is a shared spreadsheet with color-coded cells
Someone marks a cell green to mean 'done.' Someone else marks it yellow to mean 'in review.' Nobody is quite sure who reviewed what, whether the reviewer was different from the preparer, or when the status changed. Your auditors ask for evidence of separation of duties, and your team scrambles to reconstruct a timeline from email threads and spreadsheet timestamps.
Workflow controls
Six statuses. Enforced transitions. Complete audit trail.
Status machine
OPEN, IN_PROGRESS, PENDING_REVIEW, APPROVED, AUTO_RECONCILED, and EXCEPTION. Each transition is validated. You can't submit for review without completing required fields. Rejection routes back to the preparer with mandatory comments.
Separation of duties
Enforced at the API level, not the UI. The preparer who submits cannot be the reviewer who approves. Checked on every status transition. Logged in the audit trail with user ID and timestamp. SOX-compliant by design, not by policy.
Period locking
Once a period is locked, no reconciliations can be modified. No items added, no statuses changed, no work papers edited. Enforcement is at the database level. The lock is irreversible without administrator override, and the override itself is logged.
Role-based assignment
The right accounts assigned to the right people | automatically
Define account ownership rules: which preparer owns which accounts or account groups, and which reviewer covers which preparers. When a new period opens, Arvexi generates assignments automatically from these rules. Reassignment is tracked with full audit trail. Load balancing distributes accounts evenly when a preparer is over-assigned. New hires inherit their predecessor's account assignments with one action.
Bulk actions
Submit 200 reconciliations for review in one click
Supervisors can bulk assign, bulk submit, and bulk approve across multiple reconciliations. Select by account group, preparer, status, or confidence score. Every individual reconciliation within the batch is validated against workflow rules. Separation of duties is checked per account, not per batch. Failed validations are reported individually without blocking the rest of the batch.
Audit trail
Every action, every user, every timestamp | forever
Every status transition, every reconciling item, every tick mark, every comment, every assignment change, and every period lock action is recorded with the user who performed it, the timestamp, and the context. Your auditors can reconstruct the complete history of any reconciliation from claim through approval. Point-in-time queries show the state of any account at any moment during the close. No screenshots needed. Part of Account Reconciliation. Designed for controllers.
When our auditors asked for SOX evidence, we just gave them access to the audit trail. Every status change, every reviewer assignment, every approval. All timestamped and enforced by the system. The audit went from two weeks of evidence gathering to three days.
VP of Internal Audit
VP of Internal Audit at Multi-Facility Healthcare System
FAQ
Ready for a reconciliation workflow your auditors will trust?
See how enforced separation of duties, period locking, and complete audit trails make SOX compliance a byproduct of doing the work. Not a separate project.
Book a demo