MILabs
Integrations

Invoice chasing automation for MYOB: reminders and follow-up

Automated overdue invoice reminders for MYOB, with logged contacts, pause rules and your team kept in charge of escalations.

Updated 2026-08-01

Invoice chasing automation with MYOB

Chasing unpaid invoices is repetitive work in MYOB. Someone exports the overdue list, copies names and amounts into emails, and tries to remember who was contacted last. An invoice chasing automation takes over the routine part. It reads open invoices from your MYOB data, prepares reminders with the right invoice number and amount, and records each contact against the customer. For bookkeepers managing several client files, that shared log often matters as much as the emails themselves. Your team still decides the tone for difficult accounts, when a balance goes to escalation, and whether an invoice is in dispute. Payments stay recorded in MYOB by your team, so the automation supports the ledger without taking over its entries. The build starts with a sample of your overdue invoices and the rules your team already follows when chasing a customer.

How it works

  1. Export open invoices from MYOB with customer, invoice number, amount and due date, so each reminder starts from a clean list.

  2. Map each overdue invoice to the reminder stage your team has agreed, starting with a first notice once the due date has passed.

  3. Draft each reminder from a template, filling in the customer name, invoice number and amount, and hold it for review before sending.

  4. Send approved reminders from your team's mailbox, and where a connector such as Zapier links MYOB to email, confirm which MYOB actions it supports first.

  5. Pause each sequence when a payment is recorded in MYOB or a dispute is flagged, and send a daily summary of accounts that need a person.

good questions, straight answers

Frequently asked questions

Is an invoice chasing automation safe with MYOB data?
The automation reads only the invoice fields it needs, such as customer, number, amount and due date, and what it can reach is set by the permissions you grant in MYOB. Confirm which products an API key or connector can access before connecting anything, and keep exported copies within your privacy policy. Reviewing reminders before they go out keeps the tone right for each customer.
What happens if MYOB changes?
If MYOB changes a field name, report layout or access rule, the workflow may read the wrong column or stop receiving data, so the build should include a check that flags missing or unexpected fields. Review the vendor's release information when it applies to invoices or access, and retest the reminder step after any change. Because the ledger remains the record, a broken workflow should stop sending reminders rather than alter entries.
Who owns an invoice chasing automation built around MYOB?
Your business owns the workflow, the templates, the reminder logs and the MYOB data it touches, and the build agreement should say so in writing. The tools that connect the pieces, such as Zapier or Make, each have their own account and terms, so someone on your team should hold those accounts. Your MYOB subscription remains with you. Ownership of the workflow design should pass to whoever maintains it after handover, with documentation covering each step.
How does an invoice chasing automation hand work to a person in MYOB?
The workflow does not post payments or change balances, so a person picks up each account at the point a decision is needed. A daily summary lists customers who have passed the final reminder, disputed an invoice or replied with a question. The person opens the customer record in MYOB, checks the payment position, and decides on a call, a payment plan or escalation. Their note goes back into the reply log so the next reminder is paused.
Can an invoice chasing automation work with MYOB data exports?
Yes. A workflow can start from a regular export of open invoices rather than a live connection, which suits teams that prefer to keep MYOB access narrow. The trade-off is timing: an export is a snapshot, so a payment recorded after the file was made will not stop a reminder until the next export is loaded. Schedule exports to match your reminder checks, and make the pause rule look for payments in each new file before anything is sent.
let's make something happen

Custom development: how we can help

Choose how you want to work on this with MILabs. Both options start with an enquiry.

Discovery is free, no obligation from the first chat.

Let us build it for you

We build it and look after it.

Build it yourself, we'll help

You build it with our direction, teaching and a weekly check-in.