Open finance skill
Do invoice, payment, deposit, and balance records tell the same story?
Trace receivables from invoice through payment and deposit, including partially paid and closed-with-balance exceptions.
Guided synthetic example
An invoice is marked closed even though its recorded payments do not cover the invoice total.
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.
| Invoice | Status | Invoice total | Payments | Remaining |
|---|---|---|---|---|
| INV-901 | Closed | $12,000 | $9,500 | $2,500 |
| INV-902 | Posted | $4,800 | $4,800 | $0 |
Recompute the invoice balance from invoice and payment records, then compare money state with workflow status.
Needs review
INV-901 is closed with a computed $2,500 remaining balance.
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 difference could be a write-off, credit, missing payment, migration issue, or an incorrect status.
A Level finance professional validates the source evidence, challenges the AI-assisted analysis, and decides which explanation is supported.
Trace payment, credit, and write-off evidence before correcting the receivable or documenting the resolution.
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-003 · LOR-001 · LOR-021 · LOR-023
Test: Trace invoice, credit, payment, deposit, open balance, and workflow status at one cutoff.
Expected: A closed invoice with unsupported remaining balance is an exception.
Refuse when: Missing application evidence, Mixed cutoffs.
FST-004 · LOR-017 · LOR-023 · LOR-054
Test: Foot source and target open-item detail, aging, and control accounts at one documented cutoff.
Expected: Aggregate agreement without traceable open items remains unresolved.
Refuse when: Missing crosswalk, Unexplained control-account difference.
FST-013 · LOR-018 · LOR-053 · LOR-054
Test: Compare an import acceptance response with the target record and its financial consequence.
Expected: Accepted is not described as financially verified without read-back.
Refuse when: No target read-back, Unexpected posted result.
Use this system
MCP preview
run_synthetic_example {"slug":"ar-integrity-review"}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