A hundred and forty For Review lines, already categorized

What does the bank-feed pass look like?

A companion opens For Review and works the queue.

For each transaction it proposes a category and a vendor consistent with how you categorized that payee last month, with your history right there to check against. The twelve SaaS charges get their usual accounts. What it cannot place goes on a short list with its reading of why the line is odd.

Then you review: every line showing the transaction, the proposed account and the precedent behind it. Approve, correct the few that need it, and the queue that ate the 28th is a fifteen-minute pass. Your corrections set next month’s precedent.

Can it chase the invoices too?

Reading runs freely: the overdue list, who owes what and for how long, whether a payment landed since the last reminder. Reminder emails are drafted per customer with the invoice attached, staged behind approvals. The 60-day ladder is the collection playbook; the polite version is invoice chasing.

If your books live in Xero, that one is a native integration with a traced tool surface. Time-tracking data feeding your invoices has the same status through Harvest.

What stays with you and your accountant

Journal entries, payroll runs, tax filings, and anything that touches the chart of accounts structure. Those are judgments with legal and financial consequence, where the review cost equals the doing cost. Same logic as the money surfaces in Stripe.

A companion compresses the mechanical nine tenths of the queue into one reviewed batch and makes the tenth that deserves a human easier to see. Your accountant gets that tenth with better notes attached.

Frequently asked questions