Accounting Automations

How to build if-this-then-that rules that fire on accounting events like overdue invoices or received payments.

Automations handle the repetitive parts of bookkeeping so you don’t have to remember them.

How they work

Each automation has a trigger event and an action. When the event happens — an invoice is created or goes overdue, a payment is received, a transaction is imported, an estimate is accepted — the rule runs automatically.

Common uses

Send a reminder when an invoice becomes overdue.
Notify your team when a large payment arrives.
Categorize imported transactions.

You’re responsible for configuring rules and for the messages they send. Toggle any automation active or paused at any time.

Testing an automation safely

Before relying on a new rule, trigger it against a test invoice or a low-stakes record first, and confirm the resulting message or action is exactly what you intended — automations run without a manual review step once live.

Frequently asked questions

Can one event trigger more than one automation?

Yes — multiple rules can listen for the same trigger event, so a single overdue invoice could both notify your team and send a reminder to the customer.

Do automations count against any limit?

There’s no meaningful limit for typical use — most businesses run well within any practical cap on the number of active rules.

Can automations send SMS as well as email?

Where SMS is available for the recipient and they’ve provided the required consent, an automation can include SMS as one of the notification channels alongside email and in-app.