Close management
In developmentFinancial close management with clear approvals
A dependable close starts with a ledger that protects reported months. Finovra's period locks, approvals and audit trail are built into the core engine. The checklist and reconciliation tools that sit on top are in development, and this page says which is which.
Where month-end close goes wrong
Late changes
An entry lands in a month that has already been reported, and the numbers you sent no longer match the books.
Unreviewed adjustments
Accruals and reclasses are posted by the same person who prepared them, with no second look.
Missing evidence
At review time nobody can say who changed what, when, or why a period was reopened.
Built into the ledger today
Core engine builtPeriod locks
Lock a month once it is reported. Postings into it fail until someone with permission reopens it and records a reason.
Second-person approval
Draft entries wait in an approval queue. The preparer cannot approve their own entry, and a rejection needs a note.
Reversals, not edits
Late corrections go in as reversing entries linked to the original, so the closed month's history stays as reported.
Audit trail
Locks, reopenings, approvals and rejections are recorded with the person and time, in a log that cannot be edited.
Period locks, self-approval checks, immutability and the audit log are enforced by the database as well as the application, so a script, import or AI agent cannot get around them. They run in our development environment; customer accounts are not open yet.
In development
In developmentClose checklist
Tasks per period with owners, due dates and attached evidence.
Reconciliation status
Each balance sheet account shown as reconciled, in progress or not started, tied to bank and subledger reconciliations.
Accrual proposals
AI agents drafting recurring accruals from prior periods, each sent to the approval queue with its sources.
Close dashboard
One view of open tasks, unapproved entries and unreconciled accounts for the month.
Where AI fits in the close
AI agents in Finovra are limited to preparing work. The API refuses to let agent accounts post, approve, reverse or lock periods, and the database separately rejects any entry posted by an agent. Anything an agent drafts during close goes to the same approval queue as a person's draft.
The agents themselves are in development. We won't quote close-time savings until customers have closed real months on Finovra. See how the platform is designed on the AI-native ERP page.
Walk through a close on sample books
We'll lock a period, approve and reject entries, and show the audit trail on a demo workspace.
Last reviewed against the product on .