Why recovered revenue needs payment proof, not optimistic dashboards

AI products love big numbers. Found revenue. Potential revenue. Recovered revenue. Saved revenue.

Those are not the same thing.

For a real business owner, the difference matters. For a serious buyer or auditor, it matters even more.

The four buckets

Found means Chatty found a source-backed opportunity. Example: an unpaid invoice or a dormant customer.

In play means an owner approved a move, a message was drafted, or a sequence is running.

Booked means the customer committed to a time or action, but payment is not proven yet.

Recovered means a payment, booking outcome, or owner-accepted attribution is backed by a receipt.

Stripe proof

For money, the cleanest proof is a provider-backed payment event:

• Stripe PaymentIntent or Checkout Session ID
• signed webhook
• same-tenant payment record
• ledger row with money_receipt=true
• dashboard number sourced from the receipt-backed ledger

If any one of those pieces is missing, the number should not be called recovered cash.

Manual payments are different

Cash and checks happen in real businesses. But owner-entered cash is a claim until it is reviewed or reconciled.

The safe state is pending_review.

That lets the owner record reality without letting local status pretend money was collected.

What great AI accounting feels like

The owner should see:

• what was found,
• what is in play,
• what was booked,
• what was paid,
• what failed,
• what proof exists,
• and what still needs a human.

That is the difference between a dashboard and a system of record.