Open finance skill
What is ready, blocked, or still unknown before the books can close?
Preview reconciliation, schedule, exception, freshness, and sign-off status without posting entries or declaring the period closed.
Guided synthetic example
Most July close work is complete, but one reconciliation and one accrual schedule remain unresolved.
This is the operating model we use at Level. The percentages are estimated shares of the work in a typical review. Actual effort varies with data quality, complexity, and the issue found.
| Close area | Status | Evidence |
|---|---|---|
| Bank reconciliations | Blocked | 1 account open |
| Accrual schedules | Unknown | Support missing |
| AR subledger | Ready | Tied |
| Reviewer sign-off | Blocked | Pending |
Require fresh evidence for every applicable close control and preserve ready, blocked, unknown, and not-applicable separately.
Needs review
July is not close-ready because a bank account is unreconciled, accrual evidence is missing, and sign-off is pending.
At Level, we record the review logic, known explanations, and questions our finance professionals use in this situation. AI applies that documented human judgment to organize the most plausible reasons, without pretending it knows which reason is true.
Possible reasons to investigate
The remaining items may be small, but close readiness depends on control completion, not just estimated dollar impact.
A Level finance professional validates the source evidence, challenges the AI-assisted analysis, and decides which explanation is supported.
Resolve the named blockers and obtain controller sign-off before declaring the period closed.
Financial Systems Field Tests
These are repeatable Level Operating Rule tests using invented records only. They identify a control boundary and a refusal condition. They do not establish vendor behavior or replace review of your actual configuration.
FST-012 · LOR-016 · LOR-067 · LOR-071
Test: Separate an AI-proposed explanation from the source evidence, reviewer decision, and approved action.
Expected: The proposal remains unapproved without supporting evidence and review.
Refuse when: AI as sole authority, Missing provenance.
FST-014 · LOR-034 · LOR-055 · LOR-072
Test: Compare the verified target state with the analytical mirror fingerprint and refresh state.
Expected: A stale mirror remains unknown, not current reporting.
Refuse when: Failed read, Mismatched fingerprint.
Use this system
MCP preview
run_synthetic_example {"slug":"month-end-close-preview"}This check organizes evidence and surfaces exceptions. A person with finance domain expertise still needs to interpret the result, validate the source records, and discuss the operating decision.
Open source does not mean open client data. We publish reusable finance tools, checks, templates, and playbooks. Client records, workpapers, credentials, communications, and private configurations remain confidential.
Use it yourself, or bring us the messy part
Tell us where the records stop making sense. We will reply with the first check to run, the records it needs, and the decision that still needs human finance judgment.
Install the free skills yourself