How to Automatically Alert Slack When a QuickBooks Online Invoice Becomes Overdue Using Make.com

Introduction

If you are still finding overdue invoices by opening QuickBooks Online and scanning the ageing report, you already know how easy it is to miss a follow-up. By the time someone notices an invoice has slipped past due, the client has usually had at least one extra week to delay payment.

That means slower cash collection, more awkward reminders, and a finance team that spends too much time chasing data instead of acting on it. A QuickBooks Online to Slack automation changes that by surfacing overdue invoices the moment they need attention, with enough context for your team to act immediately.

By the end of this guide, you will know how to build a QuickBooks Online overdue invoice alert in Make.com, add a small amount of filtering so you only notify on real exceptions, and optionally log the alert to Google Sheets for tracking.

What You'll Need

• A QuickBooks Online account with access to invoices and reports
• A Slack workspace with permission to post into the finance or collections channel
• A Make.com account
• A Google Sheets file if you want a simple audit log of overdue alerts
• Access to QuickBooks Online connection credentials in Make.com
• Slack app permissions in Make.com for posting messages
• Ideally, a Make.com paid plan if you expect a high volume of scheduled checks or multiple scenarios

How It Works

Here is the logic in plain English: Make.com runs on a schedule, asks QuickBooks Online for open invoices, checks which ones are past due, filters out anything already handled, then posts a Slack alert for each overdue invoice. If you add Google Sheets, it also writes a row for every alert so you have a lightweight collections log.

This is a polling workflow rather than a true webhook trigger. That matters because overdue status is usually something you check on a schedule, not something QuickBooks pushes instantly. For finance operations, a scheduled scan is usually the right fit.

Step-by-Step Setup

1. Define what counts as overdue in your workflow

Before you build the scenario, decide what you actually want to alert on.

Common options:

• Invoice due date is before today and balance due is greater than zero
• Invoice is overdue by 1 day or more
• Invoice is overdue by 7 days or more for escalation
• Only invoices above a set value, such as £500 or $1,000

Be specific here. If you alert on every past-due invoice with no threshold, you will end up with a noisy Slack channel and a lot of ignored messages.

2. Create a scheduled scenario in Make.com

In Make.com, create a new Scenario and add a scheduler as the first module.

Set it to run every morning, or every few hours if your finance team works a more active collections process. For most businesses, a once-daily check at the start of the day is enough.

If you need same-day follow-up for high-value customers, you can run a second scenario in the afternoon with a different filter.

3. Add the QuickBooks Online module to fetch open invoices

Add the QuickBooks Online module that lists invoices or searches invoice records. The exact module name can vary slightly depending on your Make.com connector version, but you want the action that returns invoice records from QuickBooks Online.

Configure it to pull invoices that are still open or unpaid.

If the module supports server-side filtering, use it to narrow the dataset before Make.com does the rest of the work. At minimum, pull:

• Invoice ID
• Invoice number
• Customer name
• Due date
• Balance due
• Currency
• Status
• Invoice link if available

The more you can filter at source, the less unnecessary processing you will do later.

4. Filter for overdue invoices only

Add a filter after the invoice retrieval step.

Your filter should allow invoices through only when:

• Balance due is greater than 0
• Due date is less than today
• Status is still open or unpaid

If your QuickBooks data returns dates as strings, make sure Make.com is comparing them as actual dates, not text. That is a common mistake and it causes invoices to slip through or get ignored.

If you want a seven-day grace period, adjust the date comparison accordingly. Many finance teams prefer to alert internally on day 1 but wait until day 7 before sending a second reminder to the account owner.

5. Add a de-duplication check so you do not alert twice

This is the part most teams miss.

If your scenario runs every day, the same overdue invoice will keep matching the filter unless you store a record of what has already been notified. The cleanest lightweight option is Google Sheets.

Add a Google Sheets step that looks up the invoice ID in a tracking sheet before sending the Slack message.

Your tracking sheet can include:

• Invoice ID
• Invoice number
• Customer name
• First alert date
• Last alert date
• Alert count
• Status

If the invoice ID already exists and you only want one alert, stop the scenario there. If you want escalation reminders, allow the scenario to continue when the alert count is below your threshold.

6. Post the overdue alert into Slack

Add the Slack module to post a message into a finance or collections channel.

Keep the message tight and useful. A good format is:

Overdue invoice detected

Customer: {{Customer name}}
Invoice: {{Invoice number}}
Amount due: {{Balance due}} {{Currency}}
Due date: {{Due date}}
Age: {{days overdue}} days
Open invoice: {{Invoice link}}

If you support multiple account managers, include the customer owner or internal account owner in the message so the right person can act without asking around.

7. Write the alert to Google Sheets

After the Slack step, add a Google Sheets row insertion module.

Map the same fields you used in the Slack alert, plus:

• Alert timestamp
• Scenario run ID if you want traceability
• Next follow-up date

This gives you a simple collections log without needing a separate finance tool. It is also helpful if you want to review patterns later, such as which customers repeatedly pay late.

8. Add a second branch for high-value invoices

Because this is an advanced workflow, it is worth splitting low-risk and high-risk invoices.

Use a router in Make.com so invoices above a certain amount, say £2,500 or $5,000, trigger a second Slack message into a senior finance or leadership channel. That message can be shorter, for example:

• Customer name
• Amount overdue
• Days overdue
• Owner

That way your team sees both the collections queue and the escalations without mixing them together.

9. Test with a known overdue invoice

Pick one invoice that is already overdue in QuickBooks Online and run the scenario manually.

Check these points:

• The invoice is returned by the QuickBooks step
• The date filter catches it correctly
• The duplicate check behaves as expected
• The Slack message is readable on mobile and desktop
• The Google Sheets row is written once

If the dates look wrong, inspect the date format coming from QuickBooks Online and compare it against the date handling in Make.com. Date parsing is usually the source of most failures in finance automations.

10. Turn it on and review the first week of runs

Once the test passes, activate the scenario and review the first week of output.

You are looking for three things:

• False positives, where invoices are flagged too early
• Missed invoices, usually caused by filters or date formatting
• Repeated notifications, which means your de-duplication logic needs tightening

This is a finance workflow, so it is worth spending time on the edge cases. A reliable collections alert is one your team trusts enough to act on without checking the source system every time.

Real-World Business Scenario

A B2B services company with 150 active clients can use this setup to cut manual receivables checks to near zero. Every morning, Make.com scans QuickBooks Online, flags any overdue invoices, posts them into a finance Slack channel, and logs them in Google Sheets for follow-up.

The outcome is simple: the team sees overdue accounts the same day they become actionable, account managers stop relying on memory, and leadership gets a clearer picture of cash collection risk. For a company with several recurring retainers and project invoices, that can shorten the average chase time by days, not hours.

Common Variations

Add an escalation after 7 days overdue

Use a second filter so invoices older than seven days post into a leadership or operations channel with a stronger follow-up message.

Send the alert to the account owner by email

If your team prefers inbox-based follow-up, add Gmail or Outlook after the Slack step and send the invoice details directly to the assigned account manager.

Split alerts by customer tier

Route enterprise invoices, agency retainers, and small one-off invoices into separate Slack channels so each team only sees the accounts they own.

Keeping receivables visible

You do not need a complicated finance system to stay on top of overdue invoices, you just need the right trigger at the right time. This QuickBooks Online to Slack workflow gives your team a practical way to spot late payments early, keep a record in Google Sheets, and stop invoices from getting lost in the weekly churn.

If you want this kind of workflow built properly across QuickBooks Online, Slack, Google Sheets, Make.com, or the rest of your operations stack, Olmec Dynamics builds these systems for real businesses.