Open finance skill
Month-end close preview
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.
Inputs
- ✓Close month
- ✓Reconciliation status
- ✓Schedules and exceptions
Outputs
- ✓Ready items
- ✓Close blockers
- ✓Unknown evidence
Checks performed
- ✓Source freshness
- ✓Reconciliation coverage
- ✓Reviewer sign-off
Guided synthetic example
See the check from input to decision
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.
Start with the source records
About 15% of work| Close area | Status | Evidence |
|---|---|---|
| Bank reconciliations | Blocked | 1 account open |
| Accrual schedules | Unknown | Support missing |
| AR subledger | Ready | Tied |
| Reviewer sign-off | Blocked | Pending |
Run the deterministic check
About 20% of workRequire fresh evidence for every applicable close control and preserve ready, blocked, unknown, and not-applicable separately.
Surface the flagged result
About 10% of workNeeds review
July is not close-ready because a bank account is unreconciled, accrual evidence is missing, and sign-off is pending.
Use recorded finance judgment to analyze possible reasons
About 25% of workAt 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.
Make the final human judgment
About 20% of workA Level finance professional validates the source evidence, challenges the AI-assisted analysis, and decides which explanation is supported.
Make the operating decision
About 10% of workResolve the named blockers and obtain controller sign-off before declaring the period closed.
Use this system
Start with the example, then inspect the structure
- Download the invented input and expected output.
- Replace one field at a time with a safe test value.
- Compare the result with the expected structure.
- Have a finance professional review every exception before acting.
MCP preview
run_synthetic_example {"slug":"month-end-close-preview"}Human review is part of the system
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.