Dynamics 365 Finance AR automation: what collections process automation does, and where it stops

It is easy to run Dynamics 365 Finance AR automation with only part of it switched on: aging snapshots get built, collection letters go out, and the rest of collections happens in Outlook and a spreadsheet. Before you buy an accounts receivable tool, it is worth knowing exactly what the ERP you already pay for will automate, and where it hands the work back to a person. This guide covers both, using Microsoft’s own documentation.

One naming note first. Dynamics 365 Finance belongs to Microsoft’s finance and operations apps, which is why so many people call it F&O. Everything below applies to accounts receivable in Dynamics 365 Finance. Business Central, Microsoft’s ERP for smaller businesses, works differently.

What Dynamics 365 Finance automates in accounts receivable

Collections in Dynamics 365 Finance is organised around a central Collections page. Customers are grouped into collections pools, each pool can belong to a collections agent, and balances come from aging snapshots. The snapshots matter more than they sound: the collections list pages show nothing until one has been created, so a stale snapshot means collectors work from yesterday’s numbers. Write-offs, NSF payments and waiving interest or fees each take one step from the same page.

On top of that sit three layers of automation, each switched on separately.

Collections process automation

This is the real engine. You define a collections strategy for each customer pool, and each step in it is one of three action types: an email from a template, an activity such as a phone call assigned to a collector, or a collection letter. Steps are timed a number of days before or after the due date of the leading invoice, which is the customer’s oldest open one.

Collections coordinator workspace and Copilot

The Collections coordinator workspace puts a customer’s aged balances, last payment and open invoices on one page and lists the customers with the highest and oldest balances. With the Copilot app installed in Dataverse, the Collections coordinator summary adds an AI-generated summary of overdue invoices, payment history and remaining credit, and drafts a reminder email for the collector to edit and send.

Customer payment predictions

Part of Finance insights, customer payment predictions estimate the probability that each open invoice is paid on time, late or very late, and flag any invoice with less than a 50% chance of arriving on time. Collections process automation can use those predictions to create collection activities for the invoices most at risk.

How collections process automation works

Setup happens in two places: the Collections process automation tab under Accounts receivable parameters, and the collections process setup under Credit and collections. A few behaviours decide whether it fits how your team collects.

• One strategy per pool. Each customer pool is assigned to one process hierarchy, and a rank decides which wins when a customer sits in more than one pool.
• Timed to the oldest invoice. Steps key off the leading invoice, not every invoice. A pre-dunning step is the exception: it fires for every invoice as it approaches its due date, and only one step per hierarchy can be pre-dunning.
• Quiet days and thresholds. Quiet days stop a customer being contacted too often, and you can exclude customers whose balance, or invoices whose amount, falls below a set value.
• Once a day, as of today. According to Microsoft’s FAQ, a run always uses the current date and does not run again the same day once it has succeeded.
• Letters per customer. Automation creates collection letters per customer, and it works alongside the collection letter sequence rather than replacing it.
• Simulation first. A process simulation previews the actions a run would create, which is the safest way to test a new strategy.

Two parameters are worth setting deliberately: posting collection letters automatically, and creating activities for automated steps so every action taken on an account shows up in its history.

Where native Dynamics 365 Finance AR automation stops

Everything above is rule-based outreach plus tools for the people who do the rest. The gaps are in what happens after a message goes out.

• Replies come back to a person. When a customer answers a reminder with a question, a remittance or a complaint, a collector reads it.
• Promises to pay and disputes are manual. The automation sends the next step on schedule; recording a promise, deciding to pause, or working a dispute is a collector’s job.
• Activities are reminders for your team. A phone-call activity puts a call on a collector’s list; someone still has to make it.
• Copilot drafts, people send. The summary and the reminder draft save reading time; the collector still edits and sends.
• The oldest invoice sets the pace. A customer with one old invoice and ten current ones is handled on the old invoice’s timeline, apart from pre-dunning.

The native tools are good at outreach. The conversation after it is the part they leave to people, and for most collectors that is where the working day goes.

When native tools are enough, and when to add an AR platform

Native collections process automation is usually enough when most customers pay once reminded, disputes are rare, and one or two collectors comfortably cover the ledger. The signs you have outgrown it show up in the numbers: collections headcount rising in step with invoice volume, DSO stuck even though every reminder goes out on time, disputed invoices aging because nobody reached them, and working capital tied up in invoices that customers had already said they would pay.

That is the point where teams look at an autonomous AR platform, one that reads replies, follows up on promises, takes payment inside the message and applies the cash back to Dynamics, rather than another layer of reminders. Finero is one; how it connects is covered on the Dynamics 365 integration page, and what it automates end to end on the collections automation page.

What to ask any AR vendor about Dynamics 365 Finance

• Is the integration two-way, or does it only read from Dynamics?
• Where does applied cash post, and does it land against the invoice it settles?
• How does it handle several legal entities?
• Does it support Dynamics 365 Finance, Business Central, or both?
• What happens to a payment it cannot match?
• Does it replace collections process automation, or run alongside it?

If you are comparing the larger suites, the Versapay vs HighRadius comparison covers two vendors that list Dynamics integrations, and the AR software guide scores nine tools on the same criteria.

FAQ