How a 30-person agency took accounts payable from a shared inbox to two hours a week
AI bill coding by client project, duplicate detection and amount-based approval routing replaced a spreadsheet, a Slack thread and a month-end reconciliation scramble.
Vendor bills processed / month
310
Time on AP / week
2 hrs
Duplicate bills caught (first quarter)
7
Before HelloBooks
Contractor invoices and media bills landed in a shared inbox. The operations lead copied each one into a spreadsheet, guessed the client project it belonged to, and asked for approval in a Slack thread. Bills over budget were spotted at month end, if at all. The controller spent the first week of every month matching payments to bills so client margins could be reported.
After HelloBooks
Vendors and contractors send bills to a HelloBooks forwarding address. The AI reads each line, codes it to the client project and expense account, and holds anything that looks like a re-sent invoice. Bills under a threshold route to the account lead; larger ones go to a founder. Payments are matched back to the bank feed automatically, so client margin reports are current every morning.
The agency runs paid media and content for around forty clients, which means a long tail of freelance contractors, media platforms, software subscriptions and production vendors — roughly three hundred bills a month, nearly all of them tied to a specific client engagement. The old process was not broken so much as slow and fragile. Each bill had to be read, assigned to a client project so the margin on that engagement could be tracked, and approved by someone who knew whether the spend was inside the retainer. That knowledge lived in people's heads, and the spreadsheet that recorded it was updated when someone had time. HelloBooks changed the shape of the work rather than just speeding it up. Bills forwarded to the inbox address are read line by line; the AI proposes the expense account and the client project for each line, with a confidence score, and the first few weeks of corrections taught it the vendor-to-client mapping the operations lead had been carrying around. A contractor who works across three clients now arrives split across three projects without anyone typing. Duplicate detection turned out to matter more than expected. Contractors re-send invoices when they are not paid on the day they hoped, often with a new invoice number and the same amount and reference. Seven of those were held in the first quarter before they reached the approval queue. Approvals now route on the amount and the client: routine bills go to the account lead, anything above the threshold goes to a founder, and both approve from email or the mobile app. Paid bills are matched to the bank feed as they clear, so the controller's month-end matching week has become a review of a short exception list.
“The AI learned which contractor belongs to which client faster than our last two hires did. Approvals happen on phones now, and month end is a list, not a week.”
Illustrative scenario — composite example, not a named customer
Integrations used
- Plaid
Start your own HelloBooks story
Free plan with invoices within 200 transactions, bills & quotes. No credit card required. No time limit.
Get started free