Send thirty chase emails on the second, not the eleventh

What does the chasing pass look like?

Overdue invoices grouped by customer, each with number, amount, days late, and a drafted email in your own mail account that names them. Grouped by customer rather than by invoice, because a customer with four overdue invoices should get one email listing four.

You approve most, rewrite the two going to your largest account, and delete the one where you know a payment is already in flight. That last decision is why sending stays with you.

Can it prepare a reconciliation?

A companion reads bank transactions and the invoice and bill records, lines up what it can, and reports what it cannot match by amount, date and counterparty. What comes back is a shortlist of unmatched items with the evidence.

Closing a period and deciding what a discrepancy means are professional judgments that stay with you and your accountant. The evidence arrives assembled.

The invoice comes from three places that are not the ledger

The signed order is in email, the terms are in a document, the customer record is in a CRM, and somebody is supposed to notice all three and type an invoice. That gap is where revenue leaks.

A companion works your signed-in browser sessions as well as the Zoho Books connection, so the draft invoice arrives with line items, contact and reference filled from the upstream sources. Related: how to automate invoice chasing with ai.

The rest of the Zoho suite, one connection at a time

Several Zoho products appear separately in the connectable catalog, each with its own approval. A companion holding a Books invoice next to a Desk ticket means two connections rather than one.

Products you have not connected are still workable in the browser session you are signed into, which is how most cross-product reading happens. The wider finance pattern is ai for finance teams.

Frequently asked questions