NetSuite 2026.2 and Accounts Receivable: What SMBs Can Do to Improve Collections and Cash Flow

Last Modified: October 29th, 2026

3 min read

NetSuite 2026.2 gives finance teams better visibility into what has been paid, matched, and reconciled. That is useful. It is also only half of the cash flow story.

Knowing exactly where your receivables stand does not collect a single dollar. Someone still has to remind the customer, follow up on the overdue invoice, and escalate when the reminders go unanswered. This post covers how to pair the visibility you are gaining with a repeatable collections process, and why NetSuite accounts receivable automation is where most SMBs have the most room to improve.

What NetSuite 2026.2 changes for finance teams (and what it does not)

Let’s be precise here, because it is easy to overstate. The 2026.2 finance updates focus on banking and reconciliation. Bank reconciliation now records when a transaction is cleared, submitted, unmatched, reconciled, or unreconciled, and shows who matched and who submitted. A new Match Suggestions subtab brings likely matches into the workflow, and payment application suggestions now extend to both receivables and payables. On the AR side, teams can also record bank fees, convenience fees, and customer underpayments directly from customer payment or deposit transactions.

For controllers, that means a cleaner audit trail and less manual matching at close. For AR managers, it means payments get applied with fewer touchpoints.

What these updates are not is a collections engine. They improve how you see and record cash that has arrived. They do not decide who gets a reminder, when, or what happens when an invoice goes 45 days past due. Treat them as stronger groundwork, not a finished process.

The gap between visibility and collections

Here is the pattern we see in growing finance teams. The aging report is accurate. The reconciliation is tidy. And the follow-up still lives in someone’s inbox, a spreadsheet, or a sticky note on a monitor.

That works at 50 open invoices. It breaks at 500. The usual symptoms:

• Reminders go out when someone remembers, not on a schedule.
• Tone and timing vary by who happens to be chasing the invoice.
• Large overdue balances get the attention while small, aging ones quietly pile up.
• There is no clear trigger for escalation, so accounts sit until month end.
• Nobody can easily answer, “What did we send this customer, and when?”

Each of these costs you days sales outstanding (DSO), and DSO is cash flow.

Three habits that improve collections

1. Send reminders on a schedule, not on a memory.
   A friendly pre-due notice, a first overdue reminder, and a firmer second notice should go out at defined intervals for every customer, without anyone having to build the list by hand each week. Consistency does more for collections than any single clever email.
2. Make overdue follow-up systematic.
   Define what “overdue” triggers at 7, 15, 30, and 60 days. Decide who owns each stage. When the process is written down and automated, follow-up stops depending on whoever has the bandwidth that week.
3. Build escalation into the workflow.
   Reminders alone have a ceiling. Escalation is the step that gets a stalled invoice in front of the right person: an account manager, a controller, or a customer’s finance contact. It should be a defined step with a clear trigger, not a judgment call made under pressure at month end.

Where NetSuite accounts receivable automation fits

This is the part where visibility and action meet. With reconciliation and payment matching getting cleaner, your receivables data is more trustworthy as an input. Automation can then act on that data: sending the right reminder to the right contact at the right time, tracking what was sent, and routing overdue accounts through escalation steps you define.

That is the purpose of Excelym Dunning Solution. It works within NetSuite to support systematic collection reminders, overdue invoice follow-up, and escalation workflows, so your team spends its time on conversations that need a human, not on assembling the chase list.

To be clear, Excelym Dunning Solution is a separate layer from the 2026.2 release. The release improves the foundation. Dunning automation is what turns that foundation into a consistent collections process.

What to do next

If you are a CFO, controller, or AR manager planning around 2026.2, a short checklist helps:

• Review your current aging and identify where follow-up depends on manual effort.
• Document your reminder cadence and escalation thresholds, even if they are informal today.
• Confirm your upgrade window and check which reconciliation and payment matching preferences are enabled in your account.
• Decide which parts of collections you want automated and which should stay personal.

Better visibility is worth having. Pairing it with a collections process that runs on its own is what moves cash flow.

Ready to tighten up collections? Explore Excelym Dunning Solution.