Does Copilot Send Automatic Payment Reminders to Clients?

You sent the invoice through your client portal weeks ago. The work is delivered, the client was happy, and the invoice is still sitting there marked open. You keep telling yourself the software is handling it, because that was rather the point of paying for a portal in the first place.

It is a fair assumption, and it is half right. If you run on Copilot, the platform genuinely does chase unpaid invoices for you. But the reminders follow a fixed schedule you cannot change, they stop sooner than most people expect, and a few quiet settings can switch them off for a client without you noticing.

This post covers exactly what Copilot sends, when, which invoices are excluded, and what happens after the last automatic reminder goes out. It also clears up a naming change that trips up a lot of searches, because the tool you signed up for is not called Copilot anymore.

Which Copilot are you actually asking about?

This is worth two sentences up front, because the word has become badly overloaded. If you searched for automatic payment reminders in Copilot, you are almost certainly asking about one of these:

Copilot the client portal — the platform for professional service firms with messaging, files, contracts and billing in one branded workspace. This is the one this post covers.
Sage Copilot — an AI assistant inside Sage accounting that includes its own automated payment reminder rules.
Microsoft Copilot or GitHub Copilot — AI assistants with no invoicing function at all.

If you meant the client portal, there is one more thing to know: it changed its name to Assembly at the end of September 2025. The company rebranded specifically because “Copilot” had started appearing everywhere in the Microsoft and GitHub worlds. Same product, same accounts, same billing tools, new name and a new documentation site. So if you go looking for help articles about Copilot invoice reminders and find nothing, that is why. Search for Assembly instead.

The short answer: yes, and you do not have to turn them on

Copilot, now Assembly, sends automatic branded reminder emails for unpaid invoices, and unlike a lot of platforms it does not ship the feature switched off. Reminders are part of the standard client notification behaviour, which means new workspaces have them running from day one.

That puts the platform ahead of several competitors where the reminder setting is buried in a preferences screen nobody opens. The reminders carry your company branding and can be sent from a custom domain.

There is one nice touch worth calling out: the system will not email a client who is actively using your portal at that moment. It is a small thing, but it is the difference between a system that feels attentive and one that feels like it is pestering people.

The exact reminder schedule

According to Assembly's client notification documentation, manual invoices and subscriptions trigger reminders at four fixed points:

Due Soon — three days before the payment is due.
Due Today — on the due date itself.
Overdue — three days after the due date.
Overdue — seven days after the due date.

Two things stand out. The first is that the sequence starts before the invoice is late, which is the single most useful reminder in it. A note that lands three days early is not a chase at all; it is a courtesy, and it catches the large share of late payments that are simply forgotten rather than disputed.

The second is where the list ends. The final automatic email goes out seven days past due, and then the sequence is finished. There is no reminder at day fourteen, day thirty, or day sixty. The invoice stays open in your dashboard, the client stops hearing about it, and nothing further happens unless a human does something.

The day-seven cliff, and why it matters more than it sounds

Seven days past due feels like a reasonable place to stop if you picture the typical late invoice as being a few days behind. In practice, that is not the shape of the problem. The invoices that hurt are the ones that quietly cross the thirty-day mark while everyone assumes someone else is handling it.

A sequence that ends on day seven covers the easy cases beautifully and then hands the hard cases straight back to you, at exactly the moment they become uncomfortable to deal with. The client has ignored two reminders already, so the next message is no longer a gentle nudge; it is a conversation. And because the automation has gone quiet, nothing is prompting you to have it.

This is not unique to one platform. Most built-in sequences stop somewhere between seven and fourteen days past due, which is why some accounting tools leave you hanging in the exact window where following up matters most.

Which invoices get no reminders at all

There are three categories of invoice that the automatic sequence will never touch, and each one catches people out.

Auto-charge invoices and subscriptions. If a client is set up to be charged automatically, the reminder emails do not fire. The logic is sound, since there is nothing for the client to do. But it also means a failed card on a recurring subscription does not produce the four-step nudge sequence you might be expecting, so recurring revenue needs a different kind of monitoring than one-off work does.

Invoices created outside the platform. The QuickBooks Online integration is a one-way sync running from Assembly out to QuickBooks, as described in the payments app documentation. An invoice raised in Assembly appears in QuickBooks. An invoice raised in QuickBooks does not appear in Assembly, and therefore gets no portal reminders. If you bill from two places, half your invoices are silently unmonitored.

Invoices to clients whose notifications are muted. Email can be switched off for one contact from the Contacts page, and there is a workspace-level toggle that suppresses client email for everybody. Neither is loud about what it is doing. If a client swears they never heard from you, the mute setting is the first place to look before you assume the email went to spam.

What to do about the gap after day seven

The honest answer is that you need a plan for days eight through thirty, and it should not depend on you remembering. Three approaches work, in rough order of effort:

Put a recurring review in your calendar. Fifteen minutes every Monday, open the invoices list, filter to anything more than ten days past due, and send one message per invoice. It is unglamorous and it works, provided you actually keep the appointment with yourself.

Escalate the channel rather than the tone. The fifth contact should usually not be a fifth email. Reply on the existing message thread in the portal, or pick up the phone. A different channel gets read, and it lets you stay warm instead of firm, which is almost always the faster route to payment anyway.

Add a follow-up layer that keeps going. If you would rather not run the calendar habit yourself, a dedicated reminder tool such as DueDrop sits alongside the portal you already use and continues the polite follow-ups past the point where the built-in sequence stops. Your invoicing, payments and client portal stay exactly where they are; only the chasing changes hands. That is the same principle behind automating follow-ups without switching accounting software.

Whichever you pick, the goal is the same: make day fourteen and day thirty somebody's job rather than a gap nobody owns.

A few practical settings to check this week

Confirm client email is enabled workspace-wide. Settings, then Client notifications. It is on by default for new workspaces, but it is worth confirming rather than assuming.
Check the setting for uninvited contacts. A client added to your CRM who has never accepted an invite sits outside the normal flow unless the second toggle is on. Turn it on so an invoice sent to a brand-new client actually reaches them.
Audit your muted contacts. Anyone muted in the past for a good reason may still be muted now for no reason at all.
Decide where invoices get raised. Pick one system and stick to it. Split billing is the most common cause of invoices that nobody is chasing.
Note your own day-seven date. Work out the calendar date on which the automation goes quiet, and treat it as the start of your manual window rather than the end of the process.

One last thing worth remembering: a late invoice is not always about the client. Larger clients often route everything through a procurement or approvals system, and an accounts payable portal can be the real bottleneck no matter how good your reminders are. If a particular client is consistently slow, ask what their internal process looks like before assuming the reminders are not landing.

Frequently Asked Questions

Does Copilot send automatic payment reminders by default?

Yes. Copilot, now called Assembly, sends automatic reminder emails for unpaid manual invoices and subscriptions without you enabling anything, and new workspaces have client email notifications switched on. The reminders are branded to your company and can be sent from your own domain.

How many payment reminders does Copilot send?

Four. One three days before the due date, one on the due date, one three days after, and one seven days after. The schedule is fixed, and there are no further automatic reminders after the seven-day email.

Can I change the reminder schedule or write my own reminder emails?

Not in the way you can in a dedicated reminder tool. The intervals are set by the platform, and the controls available to you are workspace-level on and off switches plus the ability to mute email for an individual contact. If you need custom timing or custom wording per client, you will need a separate layer for that.

Why did Copilot stop appearing in search results and help articles?

The company rebranded from Copilot to Assembly on 30 September 2025, largely because the word had become crowded by Microsoft and GitHub products. The documentation now lives under the Assembly name, so search for Assembly rather than Copilot when you are looking for help articles.

Do reminders go out for failed subscription payments?

No. Auto-charge payments and subscriptions do not generate the reminder sequence, because there is normally no action for the client to take. Recurring revenue needs its own monitoring, since a failed card will not trigger the same four emails a manual invoice would.

The takeaways

Copilot is now Assembly, and yes, it sends automatic payment reminders without you turning anything on.
The sequence is four emails: three days before due, on the due date, and three and seven days after.
Nothing is sent automatically after day seven, which is precisely when most genuinely late invoices are still outstanding.
Auto-charge subscriptions, invoices raised in QuickBooks, and muted contacts are all excluded from the sequence.
The schedule and wording are fixed, so plan for a manual or separate follow-up layer covering days eight to thirty.
Before blaming the reminders, check whether the client's own approvals process is what is actually holding up payment.