Invoice chasing automation with Smokeball for law firms
Invoice chasing automation for Smokeball users: reminders drafted from billing records, approved by staff, with pause rules and a clear log.
Updated 2026-05-18
Invoice chasing automation with Smokeball
Law firms carry a particular version of the late-payment problem. A reminder about an unpaid fee note can touch a matter that is still open, a client who is already in correspondence, or a dispute that the responsible lawyer has not yet resolved. Smokeball keeps the matter as the central record, so a chasing workflow has a sensible place to read from. The build works from the billing side: it looks at invoices raised against each matter, notes their due dates and checks whether a payment or a query has been logged. Reminders are drafted from that information and held for a clerk or fee earner to approve, because a firm's relationship with a client is rarely routine. Trust account money and anything touching a regulated ledger stay outside the scope of this build. The gain is that follow-up no longer depends on someone remembering which matters were last chased.
How it works
Review how fee notes, due dates and payments are recorded on matters in Smokeball, and agree which fields the workflow may read.
Confirm with Smokeball which connection method your edition supports for reading billing data, since no public API is assumed here.
Set reminder intervals and pause rules, such as stopping when a payment is logged or a query is flagged on the matter.
Draft reminder wording for each stage, then have a clerk or fee earner approve each message before it is sent.
Route accounts needing a decision to a named person and review the daily list of open balances together with the matter file.
Frequently asked questions
- What should I back up in Smokeball first?
- Take a full copy of the data your firm relies on, including matters, contacts, billing records and the document store, following Smokeball's own guidance for your edition. Keep it somewhere separate from the live system and note the date it was made. With that copy in hand, you can trial the automation with a fallback ready, so every test run is relaxed. A good backup is also a handy snapshot of where your firm stood on the day you began.
- How does invoice chasing automation connect to Smokeball?
- The connection depends on what Smokeball makes available to your firm for your edition. The build reads invoice status, due dates and logged payments, then prepares reminders for a person to approve. If Smokeball offers no suitable interface, the data may need to pass through an accounting package or an export your firm already uses, and that route should be confirmed with Smokeball before work starts. Nothing is sent to a client until a staff member has approved it.
- Do I need a developer to connect invoice chasing automation to Smokeball?
- Some technical help is usually needed, since a reminder workflow must read billing data and write logs consistently. Whether that help must come from a developer depends on the connection route Smokeball supports for your edition and on the tools chosen for the build. A firm with a clear list of invoice fields and a named owner for approvals can keep the scope small. Ask for the connection route in writing, and keep reminder wording under your own team's control.
- How does invoice chasing automation stay in step with Smokeball?
- The workflow needs a check whenever the matter record changes shape, for example when a billing field is renamed, a payment is posted to a different matter or a new invoice template is introduced. Someone on the team should regularly review the reminder log and compare it with the billing record, so mismatches surface early. Any change to Smokeball itself should be tested on a copy before it reaches live matters. Keeping a short change note shows which rule caused each reminder.
- How do I know invoice chasing automation works with Smokeball?
- Test it on a small set of matters where the outcome is already known, such as an invoice that was paid, one that is still open and one that has a logged query. Check that each reminder shows the right amount, due date and matter reference, and that paused accounts receive nothing. A staff member should read every test message before any live send is allowed. Record the results, so the team can see what was checked and when it passed.
Related
read these nextUp a level
More with Smokeball
- Contract generation automation with Smokeball
- Document Q&A assistant for Smokeball legal matter files
- Email triage automation with Smokeball for law firm inboxes
- Timesheet automation with Smokeball for law firms
- AI adoption for Smokeball law firms
- AI strategy for Smokeball law firms: where AI could help in the matter file
- Custom development for Smokeball: bespoke tools for your matter workflow
- Product idea for Smokeball law firms: a scoped first version
- Workflow automation for Smokeball law firms
