Summary

  • Pause reminders for one customer when there’s a reason the next reminder would be wrong: a dispute is open, a payment date has been agreed, a payment plan is running, or someone at your business is already talking to them.
  • Don’t pause because a customer has gone quiet or because they’re a big account. Silence is when chasing matters most, and a big account needs its own sequence, with the account manager copied in.
  • Every pause needs a reason, an owner and a restart date. Without all three, a paused customer turns into a debt nobody is chasing.
  • Xero and Microsoft Dynamics 365 Business Central can both stop reminders for one customer or invoice, but neither restarts them. Xero’s switch stays off until someone turns it back on, and Business Central’s On Hold field records no reason or review date.
  • Trove is credit control software that pauses chasing when a payment date is logged and restarts it if the money doesn’t arrive. You can set one date across several of a customer’s invoices at once, with a note saying why.

When to pause chasing for one customer

Pause when the next automated reminder would contradict something your business has already agreed or is still working out. There are four good reasons, and each one has its own restart point.

  • A dispute or query is open. The customer has told you something is wrong with an invoice: a short delivery, a price, a missing PO. Another reminder for that invoice reads as if nobody listened.
  • A payment date has been agreed. The customer has said when they’ll pay, and the date is reasonable. Chasing before it passes is noise.
  • A payment plan is running. The customer is paying in instalments. Chase the instalments, not the original balance.
  • Someone at your business is already talking to them. An account manager is in the middle of a conversation with the customer, about this invoice or about a renewal, and has asked finance to hold off for a few days.

There are two bad reasons, and they come up just as often.

  • The customer has gone quiet. No reply to three reminders is a reason to change the approach, by phoning or bringing in the account manager, not to stop. Here’s when to hand an overdue account to the account manager.
  • They’re a big account and nobody wants to upset them. Give them a gentler sequence, a different sender or an account manager in copy, using different reminders for different customers. Switching their reminders off just means the biggest balance on the ledger has nobody chasing it.

Most pauses start outside finance. The account manager agrees a date on a call, or the buyer mentions a query in a meeting. The account manager owns that conversation, so their job is to tell finance what was agreed. Finance owns the ledger, so finance logs the pause, the reason and the date chasing starts again.

Pause by customer or by invoice

Pause the smallest thing that fixes the problem. A query on one invoice shouldn’t stop reminders on the customer’s other overdue invoices, so most pauses belong on the invoice, not the customer.

Situation Pause the customer or the invoice Restart when
A query or dispute on one invoice The invoice. Keep chasing the rest The query is resolved, or on a review date 5 working days out, whichever comes first
A payment date agreed for specific invoices The invoices the date covers The day after the agreed date, if the payment hasn't arrived
A payment plan agreed The original invoice. Chase each instalment instead The day after an instalment is missed
An account manager in a live conversation with the customer The customer, for a set number of days The date the account manager agreed with finance, usually 5 working days at most
The customer has gone into administration The customer. Automated reminders stop for good Never. Chasing moves to the claim with the administrator

The last row is the one case where reminders should stop and stay stopped. Here’s what to do when a customer goes into administration.

How to pause one customer’s reminders in Xero

Xero lets you turn invoice reminders off for one customer or for specific invoices, according to Xero Central’s guide to turning invoice reminders on or off.

To turn them off for one customer:

  1. In the Contacts menu, select Customers.
  2. Click the customer’s name to open their contact record.
  3. Click the menu icon, then select Turn off invoice reminders.

To turn them off for specific invoices, go to Sales > Invoices, select the Awaiting Payment tab, tick the invoices, click More and select Turn reminders off. You can also open a single invoice, click the menu icon and select Turn invoice reminders off. Only those invoices stop. Reminders have to be on for the customer before you can change them on an invoice.

What the switch doesn’t do is remember why it’s off. It’s either on or off. There’s no field for a reason or a restart date, so the customer stays switched off until someone remembers to turn reminders back on. With several people chasing, that’s often nobody.

Here’s how to stop two people chasing the same customer twice.

If you pause in Xero, add a calendar reminder for the restart date and a note on the contact saying why.

Our full guide to Xero invoice reminders covers turning them off for the whole organisation and checking what sends when you turn them back on.

How to put a customer or invoice on hold in Business Central

In Microsoft Dynamics 365 Business Central, you pause reminders on a customer ledger entry by filling in its On Hold field. Microsoft’s guide to collecting outstanding balances says three things follow:

  • an entry marked On Hold won’t prompt the creation of a reminder
  • if a reminder is created because of another overdue entry, the on-hold entry is still included on it
  • no interest is calculated on lines with on-hold entries

The second point is the one that catches people out. A customer you’ve paused on one invoice can still get a reminder that lists it, because a different invoice went overdue. When you use Suggest Reminder Lines, leave Include Entries On Hold unticked, and check the reminder before you issue it.

On Hold works entry by entry, so pausing a whole customer means marking each open entry. Like Xero, it records nothing about why the entry is on hold or when to look at it again. For more on reminder terms and where Business Central’s chasing stops, see how to chase overdue invoices in Business Central.

Every pause needs a reason, an owner and a restart date

A pause with no restart date is the most common way an invoice ends up 90 days overdue with nobody chasing it. Each of the three parts does a different job.

  • The reason tells whoever opens the account next why it went quiet, so they don’t chase over an agreement or, worse, leave it paused after the reason has gone.
  • The owner is the person who checks on the restart date. Usually that’s the credit controller, even when the account manager made the agreement.
  • The restart date is when chasing starts again unless someone has a reason to extend it. It should be in the system, not in someone’s head.

Worked example: a date agreed by the account manager

Hannah is the credit controller at Example UK Ltd. Tim is the account manager for Example Retail Ltd, which owes £8,400 across two overdue invoices, EUK-5102 (£5,100) and EUK-5108 (£3,300). A third invoice, EUK-5131, isn’t due until 27 November.

Date What happens Chasing
Tue 3 Nov On a call about next year's prices, Example Retail Ltd's buyer tells Tim both invoices will be paid on Fri 20 Nov, once a delivery query on EUK-5108 is signed off. Tim messages Hannah with the date and the reason Due to send a chaser on both invoices on Thu 5 Nov
Tue 3 Nov Hannah adds a note in Trove with an expected payment date of 20 Nov and applies it to EUK-5102 and EUK-5108. The note says "Tim agreed with buyer on 3 Nov. Delivery query on EUK-5108 being signed off." Trove writes the date to both invoices in the accounting system Paused on EUK-5102 and EUK-5108. EUK-5131 keeps its normal reminders
Fri 20 Nov £5,100 arrives for EUK-5102. EUK-5108 isn't paid EUK-5102 is closed and its follow-up cancelled
Mon 23 Nov The follow-up on EUK-5108 sends, asking whether the delivery query has been signed off. Hannah sees it went out and tells Tim Chasing restarts on EUK-5108

Nobody had to remember to restart anything. The date was the restart rule, the note was the reason, and Hannah stayed the owner even though Tim made the agreement.

How Trove pauses and restarts chasing

Trove pauses chasing on an invoice when a payment date is logged against it, and books a follow-up in case the payment doesn’t land. If the invoice is paid first, the follow-up is cancelled.

There are three ways a date gets logged:

  1. From the customer’s reply. Trove’s AI Reply Agent reads replies to your chasers, picks out a promised date and suggests setting it as the expected payment date. You approve it, or switch that kind of action to auto-approve.
  2. From your accounting system. An expected payment date already set in Xero pauses chasing in Trove until it passes. Here’s more on using Xero’s expected payment date.
  3. From a note in Trove. Click Add note on the customer page, enter the date, and choose every invoice it applies to. Trove updates the expected payment date on each one, which is how you pause a customer’s invoices together.

For a payment plan, set the plan up in Trove with late payment policies and it chases only an instalment that’s missed, not the whole balance. Our guide to managing a payment plan you’ve agreed with a customer covers what to agree first.

To keep the reason and owner visible, use the Kanban board. Give the account an owner, move it into a column such as “in discussion”, “disputed” or “promised to pay”, and the notes stay with the account so whoever picks it up next sees what’s been agreed. On the Advanced plan, user roles and approvals let you limit who can send emails to customers, so a reminder from someone with limited access waits for an approver.

If the customer’s own reply is “your invoice is on hold”, that’s a different job: finding out why. Here’s how to handle holding replies.

FAQs

How do I stop reminders for a customer we’re already talking to?

Pause the invoices the conversation is about, with a restart date agreed with the person who’s talking to them. In Xero you can turn reminders off on the contact, but you’ll need a calendar reminder to turn them back on. In Trove, log the date agreed with the customer and chasing restarts on its own if they don’t pay.

Will chasing restart automatically after a pause?

Not in Xero or Business Central. Both stay paused until someone switches reminders back on or clears the On Hold field. In Trove, chasing restarts with a follow-up when a logged payment date passes without payment. Read more about how Trove’s AI Reply Agent works.

Can I pause one invoice and keep chasing the rest?

Yes, and that’s usually the right call. Xero lets you turn reminders off for one invoice, Business Central uses the On Hold field on the ledger entry, and Trove pauses only the invoices a payment date covers.

Should I pause reminders while an invoice is disputed?

Pause the disputed invoice and keep chasing the customer’s other overdue invoices. Set a review date, around 5 working days out, so the dispute doesn’t sit unresolved. For deductions and short payments from big retailers, see how to find, dispute and recover supermarket deductions.

How long should a pause last?

As long as the reason does, and no longer. An agreed payment date ends the pause on that date. A conversation an account manager is having should come with a date, usually within a week, after which chasing starts again unless they’ve agreed something new.

Trove runs a free 30-day trial. You can start a free trial here or book a demo if you’d like to see pausing and restarting on your own customers first.