Guided synthetic example
See the check from input to decision
An invoice is marked closed even though its recorded payments do not cover the invoice total.
How review effort might be shared
An illustrative allocation is 15% collecting records, 20% applying checks, 10% flagging results, 25% investigating reasons, 20% finance review and 10% choosing an action. These percentages were not measured across engagements. Actual effort varies with data quality, complexity and the issue found.
1Start with the source records
| Invoice | Status | Invoice total | Payments | Remaining |
|---|
| INV-901 | Closed | $12,000 | $9,500 | $2,500 |
| INV-902 | Paid | $4,800 | $4,800 | $0 |
2Apply the documented check
Recompute invoice total minus recorded payments, then compare that preliminary balance with workflow status. Credits, write-offs and payment-to-deposit continuity require separate evidence absent from this table.
3Surface the flagged result
Needs review
INV-901 is marked closed with $2,500 remaining before any unrecorded credits or write-offs; the supplied records do not explain the difference.
4Use recorded finance judgment to analyze possible reasons
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.
5Make the final human judgment
In a Level engagement, a Level finance professional validates the source evidence, challenges the AI-assisted analysis, and decides which explanation is supported.
Was a credit or write-off authorized?
Is a payment missing from the source?
Which system controls the final status?
6Make the operating decision
Trace payment, credit, and write-off evidence before correcting the receivable or documenting the resolution.