Example report
1. Leak Check result · DEMO
A synthetic business might receive a High process-risk checklist. This is a process-risk assessment, not proof that CAVOA found missing revenue. Try the real zero-data checklist.
2. Receivables Health · DEMO
0/100 · 1 of 1 supplied rows flagged by two CSV checks. receivables-health-v1.
100 × (accepted rows − distinct rows flagged by the two invoice rules) / accepted rows, rounded to the nearest whole number. Each row has equal weight; amounts are not combined. Paid and void rows are included. This is a snapshot of the supplied file, not your whole business. A score of 100 means no rows matched these two rules; it does not prove there is no missing revenue.
Payment: Not measured · Billing: Not measured · Subscription: Not measured · Recovery Readiness: Not measured.
Your Revenue Leak Report.
1 synthetic invoice checked · Fixed example date: February 1, 2026
DEMO balance matching the overdue rule
DEMO estimate, subject to review
No payment evidence. No recovered dollars.
Overdue invoiceInvoice DEMO-001 · Source row 2$125.50 · DEMO
This synthetic invoice is unpaid and at least 14 days past its due date.
Invoice: DEMO-001 · CSV row 2
Status: open · Balance: $125.50 USD
Due: 2026-01-01 · Scan date: 2026-02-01
Rule: invoice.overdue_unpaid · Version 1
Confidence means confidence in the rule match, not the chance of collection.
Potentially recoverable uses the full outstanding balance for this rule. It does not predict payment. A credit, dispute or recent payment may change the next step.
EXAMPLE ONLY · NOTHING SENT3. Action Center · SYNTHETIC SAMPLE
Needs review: compare DEMO-001 with your original records. Check for a credit, dispute or later payment. This static preview cannot approve, send or recover anything. The live Action Center lets you inspect evidence, approve manual review and export. Recovery remains separately gated.
4. Continuous Revenue Watch · gated concept
Future connected scans could show new issues and source-observed changes. Monitoring is not active here. No schedule is created.
Find → Verify → Recover → Prove
Recovery timeline: what would happen next?
- Find
The scan flags a source record. This is the only completed step in this example.
- Verify
A person checks the balance. A public-beta manual review approval sends nothing and does not authorize future automatic actions.
- Recover · gated pilot
Any permitted pilot action needs separate, specific authorization. Live sending is disabled.
- Observe payment · gated pilot
The commissioned source must supply payment evidence linked to the invoice and authorized action.
- Prove · not verified in this sample
The ledger applies attribution and duplicate checks, keeps its audit trail, and handles reversals separately. An approval or scan alone never proves recovery. This example has no verified recovery.
This is a preview of the evidence model, not a promise of enabled automation. Read the boundaries.
Start free scan