NetSuite 2026.2 Finance Updates: Payment Runs and the Redesigned Match Bank Data Page

NetSuite 2026.2 includes two updates that directly change how finance teams process payments and reconcile bank transactions. Neither requires configuration changes to start using, but both change the interface your team works in every day.

This post covers what changed, what the new workflows look like, and what to communicate to your team before they encounter the changes on their own.

Managing a NetSuite finance function and want to make sure your team is prepared for 2026.2? SuitePacific works with NetSuite customers through release updates, including walkthroughs of new finance features in Sandbox before they go live in Production. Contact us.

Payment Runs: batch AP processing in one workflow

What it is

Payment Runs is a new feature in 2026.2 that allows finance teams to batch multiple payable documents together and process them through a single review, approval, and payment run.

Before Payment Runs, processing vendor payments required handling each document type separately. Vendor bills went through one process, credits through another, and journal entries and expense reports each had their own workflow. For finance teams processing high volumes of payables, this meant significant repetition across payment cycles.

With Payment Runs, the following document types can be included in a single batch:

• Vendor bills
• Vendor credits
• Journal entries
• Expense reports

What the workflow looks like

A Payment Run groups the selected documents into one unit. The finance team reviews the batch together, approves it as a group, and processes the payment run as a single operation rather than working through each document individually.

This consolidation is most valuable for organizations with regular AP cycles: weekly or bi-weekly vendor payment runs where the same set of document types needs to be processed together. Instead of running separate processes for bills, credits, and expense reports, a single Payment Run handles the full cycle.

What to communicate to your team

Finance team members who process AP payments will see Payment Runs as a new option in their workflow. Teams that have an established rhythm for processing payables should be briefed on the new batch approach so they understand how it relates to existing processes.

Match Bank Data: new Match Suggestions interface

What changed

The Match Bank Data page received a redesigned interface in 2026.2. The Review subtab that was previously used to work through unmatched bank transactions has been replaced by a Match Suggestions interface.

The new interface presents each bank transaction alongside matching suggestions, with five actions available per transaction. This replaces the previous Review subtab workflow where transactions were reviewed and matched from a tab-based layout.

What this means for bank reconciliation

The core task has not changed: finance teams are still matching imported bank transactions to existing NetSuite records or creating new records for unmatched transactions. What changed is the interface for doing that work.

The Match Suggestions approach surfaces potential matches alongside the transaction being reviewed, rather than requiring the user to navigate to a separate tab to find matches. The five available actions per transaction give users more options in a single view without switching between screens.

What to communicate to your team

Team members responsible for bank reconciliation will notice the change when they open the Match Bank Data page. The new layout is different enough that a brief walkthrough before the team encounters it in Production is worth doing. Your Sandbox account already has the 2026.2 update; the Match Suggestions interface is available there now.

Testing both features in Sandbox

Both Payment Runs and the Match Bank Data redesign are available in Sandbox now. Before your team encounters them in Production:

• Walk through a Payment Run in Sandbox using representative vendor bills, credits, and expense reports
• Open the Match Bank Data page and work through the Match Suggestions interface with test bank transactions
• Identify any process documentation or team training that needs to be updated to reflect the new workflows

The underlying accounting does not change with either feature. The changes are in the workflow and interface, which means the risk is team members being unfamiliar with the new screens rather than any accounting outcome being different.

How SuitePacific can help

Preparing finance teams for interface changes requires more than communicating that something looks different. If your team needs a Sandbox walkthrough of Payment Runs or the Match Bank Data redesign before 2026.2 reaches your Production environment, contact SuitePacific. We work with NetSuite finance teams through release updates and can help your team build familiarity with new workflows before they go live.