How to Automate Accounts Receivable in Sage Intacct (2026 Guide)

To automate accounts receivable in Sage Intacct you switch on three native layers, then close the gap with an agent. First turn on dunning and define your dunning levels by days overdue and dollar range. Second, add the Collections module if you want collection cases owned and tracked rather than chased ad hoc. Third, enable electronic payments so cash comes in cleanly. Intacct will then generate and send the notices. What it still will not do is call a customer, escalate a stubborn invoice, or split a lump-sum ACH batch across nine invoices, and that is where an AI AR agent on top finishes the job.

Does Sage Intacct automate accounts receivable on its own?

Sage Intacct automates more of accounts receivable than most ledgers, but not the collecting. Natively it delivers invoices, runs recurring billing, tracks aging in real time on configurable dashboards, and generates dunning notices on a schedule you define. That covers invoicing and the first layer of follow-up genuinely well. What it does not do is work the aging report the way a collector would: it will not phone a customer, will not notice that an account has ignored three notices and needs a different approach, will not capture a promise-to-pay and follow up when it slips, and will not reliably match a payment that arrives without clean remittance data.

That boundary is the whole story of Intacct AR. The easy invoices, the ones a customer simply forgot, clear on the first or second notice. The invoices that damage your cash position are the ones that read the notice and do nothing, and those need follow-up Intacct cannot run by itself. So the right sequence is to configure everything Intacct offers, then add what it structurally does not include.

How to set up dunning notices in Sage Intacct

Dunning is off by default. Turning it on and configuring it properly takes an afternoon, and it is the highest-value hour of AR configuration in Intacct. The steps look like this:

• Turn dunning on. Enable dunning notices in your Accounts Receivable configuration. Nothing generates until this is switched on.
• Define your dunning levels. Each level is a combination of a days-overdue range and an amount range. A customer 31 to 60 days late owing $1,000 to $5,000 can receive a different letter than one sitting at 90 days, so the tone escalates with the age and the exposure.
• Set a message-filtering threshold. Specify a minimum balance so a $12 rounding remainder on an otherwise-settled invoice never triggers a dunning letter. This one setting prevents most of the awkward customer emails that make finance teams switch dunning back off.
• Schedule the run times. Pick when notices execute rather than firing them manually. Consistency is what makes dunning work; a sequence that runs when someone remembers is not a sequence.
• Choose email or print. Intacct can email notices or print them for physical mailing, which still matters for a minority of large accounts that route paper through AP.

If you are writing the notice copy itself, the escalation logic matters more than the wording. Our guide to the modern dunning process covers how soft and hard dunning stages should differ and when each should fire.

What the Sage Intacct Collections module adds

Collections is an add-on rather than part of core AR, and it solves a different problem from dunning. Dunning generates the letters. Collections turns overdue accounts into managed cases: each one gets a named owner, a queue of next actions, and a recorded history of activity, so the work is assigned and visible instead of living in one person's inbox.

That is a real improvement if your problem is coordination, and it is worth the money for a team of three or more collectors who currently step on each other. It is not an improvement if your problem is capacity. Collections organizes who chases what. A human still does every actual chase, and the module does not add a channel that Intacct did not already have.

Where Sage Intacct AR automation stops

Here is the honest boundary between what Intacct handles, what the Collections module adds, and what still lands on a person:

The 2026 R1 release narrowed one of these gaps. Intacct added Customer Payment Services powered by Fortis, which takes electronic payments and reconciles those specific transactions automatically. That helps for cash arriving through that channel. It does not help with the lockbox check, or the wire that covers nine invoices with a remittance advice sitting in somebody's email. Matching that kind of payment is its own discipline, and our guide to the cash application process walks through how it should work.

How to fully automate accounts receivable in Sage Intacct

To automate the rest, connect an AI accounts receivable agent on top of Intacct. It reads your open invoices, customer records and entity structure through the Intacct connection, then runs the collecting you would otherwise assign to people. Every overdue invoice is chased across email, then SMS, then a live AI phone call, escalating on its own as the invoice moves through the aging buckets rather than waiting for a collector to reach it. When money lands, the agent applies it to the right invoices, splits lump-sum deposits across what they actually cover, and writes the applied payments back into Intacct so the ledger stays current.

Because it sits on top of the ledger, there is no migration, no parallel run and no re-implementation. Intacct stays your system of record and you keep invoicing exactly as you do now. The mechanics of the connection, including how it handles a multi-entity Intacct structure so a shared customer does not get three uncoordinated reminders in one morning, are covered on our page for Sage Intacct accounts receivable automation. If you run Sage 300, Sage 100 or Sage 50 instead, the same approach is described for accounts receivable software for Sage. Teams that only want tighter messaging without the calls should look at automated payment reminders first.

Rolling this out well is a sequencing problem more than a software problem. Our step-by-step plan for automating accounts receivable covers what to automate first, what to keep human, and how to avoid switching everything on at once.

Why Intacct invoices sit unpaid in construction and distribution

Sage Intacct has deep roots in construction, distribution and nonprofits, and in those industries a large share of aged invoices are not collection problems at all. They are documentation problems. The invoice is disputed, the purchase order number is missing, the lien waiver has not been returned, or the customer will not release payment until current compliance paperwork is on file. In construction and field services especially, a general contractor holding payment because your certificate of insurance tracking has lapsed is a completely different fix from a customer who is slow to pay, and no amount of dunning will move it.

This is worth separating before you judge your automation. Run your aging report and split it in two: invoices nobody has chased, and invoices blocked on something. Automation fixes the first pile immediately and permanently. The second pile needs the blocker cleared, and the useful thing an agent does there is surface the reason early instead of letting the invoice quietly age for 60 days. If your DSO is dominated by the second pile, start with the practical levers for reducing DSO rather than a new tool.

Does Sage Intacct send automatic payment reminders?

Yes. Sage Intacct sends automated dunning notices once you enable dunning and define your dunning levels, and you can schedule the runs, filter out trivial balances and send by email or print. That covers the reminder layer of accounts receivable properly, which is more than most mid-market ledgers manage. For the rest of the job, the escalation to SMS and phone, the promise-to-pay tracking, and hands-off cash application on messy payments, an AI AR agent on top of Intacct turns partial automation into a receivables desk that runs itself while Intacct stays the source of truth.