Recover: money leaking between the order and the bank

Recover looks through your orders, shipments, invoices, payments, credits and vendor bills for money that's slipping away, and says what it would take to get each one back. It works from your own books: every figure is one you can click through to, and nothing is estimated.

What it finds

• Shipped, not invoiced. Goods left three or more days ago and no sent invoice bills them: no invoice yet, a draft never sent, or an invoice voided after they shipped.
• Work not billed (agencies). Billable items ready for a week or more and not on an invoice.
• Paid short. A customer paid part of an invoice, a week has gone by with nothing more, it's past due, and no more than a quarter is left.
• Discount taken late. They paid less the early-payment discount after its window closed, or a discount was credited after it.
• Vendor price up. A vendor charged 3% or more per item than on their last bill for the same product.
• Billed past the PO (agencies). Bills against a purchase order add up to more than it, past your tolerance.
• Under the price list, or below cost. Over the last 90 days, a line sold for less than the customer's list price, or for less than the goods cost. That money is already given up on the invoice: Recover shows it so the price gets fixed.

Getting it back

1. 1

   Open the leak

   Each one shows the figures from your books it was found from, with links to the invoice, bill or order.

   Recover
2. 2

   Take the step

   Bill the order, send the draft invoice, or check the price: the button goes to where it's done. For a customer who paid short or a vendor who charged more, Ask for it drafts the email.

3. 3

   Read the email, then send it

   With AI on, Claude writes it from the figures, and from what the customer wrote to you about it if they did. Every amount and document it mentions is checked against your books first; a draft that strays is replaced by one written by rule, and you're told why. Change anything, then Send. It goes in test mode while your delivery is in test.

Setting one aside

Some leaks are on purpose: a price you agreed, a deduction you accept, a vendor's new price. Set aside says why. Choose don't flag this again and Recover lets that kind go for that customer or vendor (or just that product) from now on. That's how it learns what your business lets go. The rules are listed on the page, where Flag again undoes one.

What counts as recovered

Only money that was billed, collected or corrected after Recover flagged it: the invoice sent, the rest of the payment received, the vendor's bill corrected. A leak that ends another way (credited, written off, voided) isn't counted. If a leak comes back, it's on the list again and what was counted for it is taken back.

Replay your last 90 days

Replay your last 90 days (at the top of Recover) plays back the last quarter as if thruflow had been running: thirteen weeks, each lighting up with what it would have caught that week and the reminders it would have sent. With QuickBooks connected it reads straight from there, so you can see it the day you connect, before anything is in thruflow. Otherwise it reads thruflow's own records.

• What it catches: short payments, discounts taken late, a vendor charging more for the same item, a bill keyed in twice (the same vendor invoice number, or the same amount within ten days), and an estimate accepted and never invoiced. In thruflow's own records, Recover's open leaks are in it too.
• Reminders: on Autopilot's schedule (Settings → Autopilot), stopping once an invoice is paid. Paid late counts invoices paid after their due date.
• Still there to recover is what's still open today; what was settled since is shown, marked as settled.
• Who to chase today: what's overdue now, the largest first, with how late each customer usually pays.

Each event opens the document it's about, in QuickBooks or in thruflow. A replay only reads: nothing is changed anywhere, and no AI is used.