Running Manual Payment Reminders After the QuickBooks Desktop Sunset

Automated payment reminders in QuickBooks Desktop stop when the online service behind them is cut; here is what to save first and how to keep collecting.

Automated payment reminders look like a local feature, but only half of one is. The schedules and templates live in your company file; the entitlement check and, for one mail option, the delivery itself run on the vendor's servers. When a Desktop version loses its connected services, the reminders stop firing and nothing announces it. This page covers what breaks, what to capture beforehand, and a routine that keeps collections moving on Desktop.

The schedule sits in your file, the delivery does not

Releases of QuickBooks Desktop from 2020 onward can schedule reminder emails for open invoices. Two parts make that work. The schedule definitions, the attached templates, and the customer assignments are ordinary data inside your company file. The trigger runs inside the program, which validates connected services against the vendor's servers, and the QuickBooks Email delivery option hands your messages to the vendor's mail relay.

After a version is discontinued, the validation fails and the feature is switched off with the rest of the connected services. Your schedules survive as records. They simply never fire again, and no error appears. That is the dangerous part: the queue still looks scheduled, so staff assume somebody reminded the customer.

The feature was always fragile in this respect. Reminders fired only while the program was open, a company file was loaded, and the signed-in user could send email. Discontinuation does not create a new weakness; it makes the old one permanent.

Export these before the cutoff

Our engineers treat the weeks before a sunset as a collection window. Capture four things while the service still runs.

• The schedules. From the Customers menu, open Payment Reminders and then the schedules list. For each schedule, record the name, the active flag, the timing rules in days before or after the due date, the attached template, and any customer filter. There is no export button, so copy the settings by hand or screenshot them.
• The templates. Go to Edit, then Preferences, then Send Forms, and open the Company Preferences tab. Open each reminder template, copy the subject and body into a plain text document, and note which fields fill from the invoice. Templates keep working locally; the copy is insurance.
• The enrollment list. Print or screenshot the view that shows which customers receive reminders, along with their contact details and preferred send method.
• The baseline. Run the A/R Aging Summary and the Collections report, export both to Excel, and date the files. Your manual routine starts from these numbers.

Turn the automation off before it misleads someone

Once the cutoff passes, open each schedule and clear its active checkbox, then note the retirement in your written procedures. A dead queue that still looks live is worse than no queue.

Move the mail path at the same time. In the Send Forms preferences, set delivery to Outlook or to your own webmail account, then send a test message to yourself. Mail sent through your own account leaves your mail server directly and keeps working. Mail handed to the vendor's relay does not.

A weekly routine that replaces the schedule

Rebuild the old timing on paper first. Map the schedule rules you exported onto a calendar: a reminder a set number of days before the due date, then follow-ups at your chosen intervals after it. Consistency matters more than cleverness.

1. Fix one weekday and time for the run, and put it on the calendar of whoever owns collections.
2. Run the A/R Aging Summary and export it to Excel. Work the buckets in order, starting with invoices not yet due.
3. Open the Collections report for phone numbers, contact names, and per-invoice aging when a call is faster than an email.
4. Open each overdue invoice and email it with the saved reminder template, chosen from the template list in the send window. One invoice, one message.
5. Where a customer holds several open invoices, send one statement instead of many emails: Customers, then Create Statements, pick the form and date range, and email the batch.
6. Log every send. Add a dated note to the customer record and keep the weekly Excel file as the reminder log. The audit trail still records emailed invoices.

If the reminder window still opens on your build, use it for a manual batch when that is faster. Treat it as a convenience, not a dependency. Anything the vendor gates can be switched off remotely; reports, statements, and Send Forms run locally and cannot.

Review the routine monthly

Once a month, compare average days to pay and the count of overdue invoices against the baseline you exported. Tighten or relax the intervals on that evidence rather than on habit. For the wider housekeeping that keeps an unsupported Desktop install reliable, our QuickBooks Desktop help knowledge base covers backups, verification, and file maintenance. A healthy file keeps the weekly run short; a bloated one slows every screen you touch.