Lesson 6 of 7 · 7 min

Overdue reminders on day 7 and day 14, and tracking money owed

Send overdue reminders on day 7 and day 14 with a workflow, and track money owed.

Read the lesson

Goal: Chase overdue invoices on day 7 and day 14 with a workflow. Read the open money in Invoices each week.

You need: Core or above for the workflow. Screens: Payments → Invoices, Workflows.

Why this matters

Some customers will not pay on the spot. A landlord wants a bill. A property manager pays on 30-day terms. A homeowner forgets. Without a reminder, these invoices sit for weeks.

Chasing them by hand is slow and awkward. The office does it when it has time, which is never. The owner hates making "where is my money" calls. So money they have earned stays out.

A workflow does the chasing on a fixed schedule, in a polite voice, for every invoice. The office only steps in when the reminders fail.

ServiceAgent has no built-in invoice reminder setting. Invoices → Invoice settings holds only Invoice appearance and Payment account. The reminders come from a workflow template: "Invoice Overdue Collection Nudge".

The idea: the due date drives everything

The template starts when an invoice becomes overdue. So the due date decides when the chasing begins. Get the due date wrong, and the workflow chases the wrong people.

Customer typeAgreed termsDue date to set
Homeowner, small jobPay on completionJob day
Homeowner, large jobBalance on completionJob day
Property managerNet 3030 days after the invoice
Builder or contractorAs agreed in writingThe agreed date
Fig 1

Which due date to set

  1. Create the invoice
  2. Did the customer agree other terms in writing?YesSet the agreed date, such as invoice date + 30 daysNoDue on the job day
  3. The overdue workflow waits for that date
  4. Reminders start only if the customer is really late
The due date decides when the chasing starts. Match it to the terms the customer agreed.

Then the reminders run on a schedule after the due date:

  • Day 7 overdue: a friendly text with the link. "Just a reminder, your invoice for [job] is open."
  • Day 14 overdue: a firmer text or email. Name the amount and offer a call.
  • After day 14: a task for a person. A call settles most of what texts do not.
Fig 2

An invoice from due date to a call

  1. Due dateInvoice is open; no message yet
  2. 7 days overdueFriendly text with the payment link
  3. 14 days overdueFirmer text or email: amount named, call offered
  4. After day 14Task for a named person to call
Two polite reminders, then a person. A call settles most of what texts do not.

Tone matters

Reminders protect the relationship as well as the cash. Most late payers simply forgot. Write for them, not for the rare bad payer.

  • Day 7: assume they forgot. "Hi Tom, a quick reminder that invoice 1042 for your AC repair is open. You can pay here: [link]."
  • Day 14: be clear and offer help. "Hi Tom, invoice 1042 for $640 is now 14 days overdue. Reply or call us if there is a problem with it."
  • The call: a person asks one question. "Is anything stopping you from paying this?" Often the answer is a problem with the job. Fix that first.
Fig 3Example numbers

Day 7 and day 14 reminders

  1. note7 days overdue
  2. Polar Air Services · 9:00 amHi Tom, a quick reminder that invoice 1042 for your AC repair is open. You can pay here: link
  3. note14 days overdue
  4. Polar Air Services · 9:00 amHi Tom, invoice 1042 for $640 is now 14 days overdue. Reply or call us if there is a problem with it.
  5. Customer · 12:47 pmThe AC is short-cycling again. I was waiting for someone to come back.
  6. noteThe office books a return visit first
Day 7 assumes the customer forgot. Day 14 names the amount and invites a reply. The reply often shows a job problem.

Never threaten in a text. Late fees, collections agencies and legal steps are the owner's decisions. They follow their written policy and their advisor's advice, not a template.

Reading the Invoices tab each week

Spend 10 minutes each Monday on the open invoices. Write down three numbers:

  1. The count of open invoices.
  2. The total dollars still open.
  3. The oldest open invoice and its age.

Compare them with last week. If the total rises while jobs stay flat, links are not going out on the job day. Check Lesson 5 with the crews. Put the three numbers in your monthly report notes.

Build it in ServiceAgent

  1. Set due dates at the source. In Payments → Invoices → Create Invoice, fill Due Date to match the agreed terms. For net-30 accounts, set it 30 days out.
  2. Open the template. Go to Workflows → Templates. Find "Invoice Overdue Collection Nudge". Its description says it sends reminders when an invoice becomes overdue and creates a collections task with escalation.
  3. Set the days. The delays in the template are editable. Set the first reminder at 7 days and the second at 14 days after the invoice becomes overdue.
  4. Write the messages. Keep texts under 160 plain characters. Name the job and the amount. Stay polite in both.
  5. Add the person. The last step must be Create CRM Task with a named Owner. Give it a due date and Priority HIGH.
  6. Check for paid invoices. Before each send, the workflow must skip invoices that are now paid. Check if the template already does this. If not, test whether a Condition can read the invoice status in this account. If it cannot, flag it to ServiceAgent support before you publish.
  7. Test, then publish. Click Test to run the free simulation. Then click Publish. On Core, this counts as 1 of 10 active automations.
  8. Read the Invoices tab weekly. Open Payments → Invoices. Look at each open invoice, its due date and its status. Note the total still open.
Fig 4

The overdue workflow, ready to publish

Invoice Overdue Collection Nudge

Delay7 days, then 14 days after the invoice is overdue
ConditionSkip invoices that are paid (test this)
Send SMSDay 7 reminder with the link
Send EmailDay 14: amount named, call offered
Create CRM TaskNamed Owner, due date, Priority HIGH
Publish
Set the days, write two polite messages and end with a named person. Test before you publish.

Worked example: Polar Air Services

Polar Air Services (about 20 techs, Growth) services rental units for a property manager on net-30 terms. The office set their invoices to "due on receipt". So the overdue workflow chased them a few days after each visit. They complained.

The fix is not a softer message. The fix is the due date. The office now sets their invoices 30 days out. The workflow only starts if they are really late.

Fig 5

Polar Air's property manager, before and after

Due on receipt
  • Net-30 customer billed as due on receipt
  • Workflow chased them days after each visit
  • They complained
Due in 30 days
  • Invoices set 30 days out
  • Workflow starts only if they are really late
  • Reminders stay on for everyone else
The fix was the due date, not a softer message.

Now measure days to paid. In one week, Polar logs five paid invoices. These are example inputs. They were paid 0, 2, 9, 16 and 33 days after the job.

  • Total days: 0 + 2 + 9 + 16 + 33 = 60
  • Average days to paid: 60 ÷ 5 = 12 days
Fig 6Example numbers

Days to paid for five invoices

Invoice 10 days
Invoice 22 days
Invoice 39 days
Invoice 416 days
Invoice 533 days
Average: 60 ÷ 5 = 12 days. Pay-by-text pulls the short ones to 0; reminders pull in the long tail.

Track this number each month. Pay-by-text (Lesson 5) pulls the small numbers to 0. The reminders pull the long tail in. Both move the average down.

The credits are small. Each reminder text is 2 credits, and each run is 1 credit. Most invoices never reach a reminder at all.

Common mistakes

  • Wrong due dates. The workflow chases a net-30 customer on day 3. Fix: set due dates to the agreed terms.
  • Turning reminders off for everyone after one complaint. Fix: fix that account's due dates instead.
  • No person at the end. Fix: end with a task that has a named owner and a date.
  • Reminding customers who already paid. Fix: check that the workflow skips paid invoices before you publish.

Do this now

List each client customer with special terms, such as property managers. Write the due-date rule for each. Then open the template in your practice account and set the 7 and 14 day delays.

Practice the conversation

  1. Operator How much money is owed to you right now, over 30 days?
  2. Owner I couldn't tell you. Too much.
  3. Operator We will set a reminder on day 7 and day 14 after a bill is overdue. Then a task for your office to call.
  4. Owner I don't want to annoy my property managers.
  5. Operator We set their bills to your agreed terms. Net 30 means the reminders wait until day 30 has passed.
  6. Owner And the homeowners?
  7. Operator Most will pay by text on the day. The reminders catch the few who forget.
  8. Owner Who makes the call after that?
  9. Operator You pick one person. The task goes to them with a date.

Quick check

  1. A property manager pays on 30-day terms, but their invoices are due on receipt. The overdue workflow chases them days after each visit. What do you fix?
    • Rewrite the reminder to sound more polite
    • Turn off overdue reminders for every customer
    • Set this account's due dates to match the agreed terms
    • Send them only the last reminder
  2. Four invoices were paid 0, 4, 10 and 22 days after the job. What is the average days to paid?
    • 8 days
    • 9 days
    • 10 days
    • 12 days
  3. Where do overdue reminders come from in ServiceAgent?
    • A reminder setting in `Invoice settings`
    • The workflow template "Invoice Overdue Collection Nudge"
    • An automatic email from Stripe on day 7 and day 14
    • The voice agent's `Follow-up` tab

ServiceAgent UniversityLearn to run a service business on autopilot. Free courses, Blueprints and certification for Service Operators.

Learn

Get certified

Community