Open finance skill
Revenue Leak Detective
Revenue leakage review
Where could completed work be missing from billing?
Compare synthetic completed-work and invoice records to find jobs that may be unbilled, underbilled, or awaiting review.
A complete finance workflow
The spreadsheet has the numbers. The missing context is usually in someone's head.
Teams usually compare completed work with invoices by hand, ask operations what happened, and reconstruct missing context across spreadsheets, email, and meetings.
- 1
Read completed-work and invoice records
- 2
Find completed jobs with no invoice or an unexplained amount difference
- 3
Draft the billing questions that operations and finance need to answer
- 4
Organize the evidence, explanation, owner, and next review step
- 5
Export resolved explanations into a review history that the finance team maintains
What a maintained review history makes easier to see
- ✓Which job types repeatedly miss billing
- ✓Where approval or handoff delays occur
- ✓Which customers require unusual billing treatment
- ✓Who owns each unresolved billing question
Inputs
- ✓Completed work
- ✓Invoice records
- ✓Job identifiers
Outputs
- ✓Unbilled candidates
- ✓Amount differences
- ✓Review queue
Checks performed
- ✓Completed job without invoice
- ✓Job-to-invoice amount gap
- ✓Missing job identifier
Guided synthetic example
See the check from input to decision
A completed service job has signed completion evidence but no matching invoice.
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| Job | Status | Completed | Quoted value | Invoice |
|---|---|---|---|---|
| JOB-1208 | Complete | Jul 19 | $6,400 | None |
| JOB-1211 | Complete | Jul 20 | $3,250 | INV-804 |
Run the deterministic check
About 20% of workFor each completed job, require a matching invoice identifier and compare job value with billed value.
Surface the flagged result
About 10% of workNeeds review
JOB-1208 may contain $6,400 of unbilled completed work.
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 missing invoice may indicate leakage, but warranty work, a bundled agreement, or delayed billing could explain it.
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 workConfirm the billing obligation and either issue the invoice or document why no invoice is required.
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":"revenue-leakage-review"}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.