NetSuite 2026.2 Release Notes: Finance & Accounting

This is the first installment of our NetSuite 2026.2 Release Notes Series, where we break down the release by role — so you only read what actually applies to your work.

If you handle the close, the reconciliation, or the payment run, 2026.2 is a heavier release for you than it is for most other roles. Bank reconciliation in particular has been substantially rebuilt.

A note on sourcing. This breakdown is based on Oracle's Release Preview release notes for 2026.2, which every page marks as subject to change. Details can shift before the notes reach general availability. We are reading the same document you can request access to, and we will update this post if Oracle revises it.

---

Bank reconciliation got the biggest rework in years

Seven separate enhancements land in banking, and together they change the shape of the workflow rather than just polishing it.

Match Suggestions is now its own subtab

The Review subtab on the Match Bank Data page is replaced by a Match Suggestions subtab. Instead of only showing matches NetSuite already made automatically, it now surfaces likely matches for you to review before you reconcile, each with a suggested action:

• Match Transaction — accept a system suggestion outright.
• Review Match Options — pick from several plausible matches.
• Apply Payment — create and apply a payment for an eligible invoice or payable.
• Review Payment Options — choose among several candidate invoices or payables.
• Create (transaction type) — create and reconcile from an auto-create rule.

Payment suggestions now cover payables, not just receivables

This is the change most worth knowing. Previously, suggesting a payment against an open item only worked on the accounts receivable side, through the Automated Cash Application page. In 2026.2 you can review, create, apply, and reconcile against both open invoices and open payables, directly from Match Bank Data.

The constraints matter, because they decide whether this helps your team or not:

• One-to-one matches only, for the full outstanding amount. Partial payments are not supported, and neither is one payment covering multiple invoices or payables.
• The invoice or payable must be open, posting, and in the same subsidiary and currency as the bank account.
• Two accounting preferences control it — Generate Match Suggestions for Accounts Receivable and Generate Match Suggestions for Accounts Payable. Both are enabled by default, so this will appear in your account whether or not you planned for it.

Automated Cash Application still exists. If it creates a match for a transaction that also had an apply-payment suggestion, NetSuite drops the suggestion.

Matching and submitting became one step

Manual matches and cleared transactions are now submitted for reconciliation automatically. The separate submission step is gone, and the buttons say so: Match and Submit replaces Match, Clear and Submit replaces Clear. Submitted transactions show up on the Review subtab of Reconcile Account Statement.

If your team documented the old two-step process, that documentation is now wrong.

A real audit trail

System notes now track reconciliation lifecycle events on the related GL transactions — when a transaction was cleared, submitted, unmatched, reconciled, or unreconciled, and who did it. Reconciliation Status and Date Reconciled are available in transaction searches and in specific accounting reports.

Alongside that, the reconciliation pages now show Matched By and Submitted By columns, so you can tell a system-generated match from a human one and filter by either. The same applies to exclusions — the Excluded tab identifies who or what excluded a transaction.

For anyone who has had to reconstruct who touched a reconciliation three months after the fact, this is the quiet win of the release.

Interface changes you will notice on day one

• To Be Matched is renamed Transactions to Match; Excluded becomes Excluded Transactions.
• Action buttons now appear above and below the transaction list, so you stop scrolling to the bottom to click Exclude.
• Filter chips for date, type, and cash flow type on Match Bank Data; and on Reconcile Account Statement, chips for bank date, match type, cash flow type, matched by, and submitted by.
• The Review tab now carries bank and GL detail together — bank date, bank details, match type, amount, name, GL transaction info — so you can validate before reconciling instead of after.
• New banners on the Format Profile and Upload File pages warn that imported bank memo fields may contain sensitive data such as account numbers, card numbers, and addresses.

---

Payment Runs: a real AP workflow

2026.2 introduces Payment Runs, an accounts payable workflow for preparing, reviewing, approving, and processing multiple payables from a single transaction record.

You pick a payment account — which sets the subsidiary and currency context — then add eligible vendor bills, vendor credits, journal entries, expense reports, and bill payments. Save the selection, review it, submit when ready. NetSuite processes it through the Bulk Processing Framework and groups the resulting vendor payments consistently with existing Pay Bills behavior.

The part that makes this more than a UI convenience: a payment run is a real NetSuite transaction. It supports permissions, approvals, custom fields, custom segments, numbering, searches, REST, SuiteScript, and CSV. That means your existing approval matrix and reporting can wrap around it, instead of AP living in a process nobody can audit.

The stated benefit is reducing duplicate payment selection and showing related payment activity on source transactions — which is the failure mode most AP teams actually have.

---

Two new CFO reports, with AI summaries

2026.2 adds a Labor Costs Report and a Labor Costs and Revenue Insights Report. Both let you analyze labor cost by period, subsidiary, department, location, or other segments, and both can generate AI summaries of the underlying data.

Before you use them, configure which payroll components are included — the numbers are only as useful as that mapping. They can be embedded in CFO dashboards.

---

Tax on term discounts, finally automated

If you take early-payment discounts on vendor bills, you have been adjusting the discount amount in NetSuite and calculating the related tax adjustment by hand. In 2026.2 that becomes automatic: NetSuite generates bill credits for the discount and its associated tax, as term discount adjustment bill credit transactions.

Three setup steps gate it:

1. Enable the Create Adjustment Transactions for Term Discounts accounting preference.
2. Enable Include Tax When Calculating Term Discount at the nexus level, if you want tax adjusted alongside the discount.
3. Grant edit-level permission on the Tax Details tab, plus permission to create bill credits, to any role that records vendor payments with term discounts.

One caveat worth flagging to your team: system-generated adjustment transactions cannot be edited or deleted. That is deliberate, for record accuracy, but it means a misconfigured preference produces records you cannot clean up afterward. Test this one in Release Preview before you enable it in production.

---

Smaller changes that still touch your day

• Excel exports are now .xlsx. Lists, saved searches, and reports export in the modern format instead of legacy .xls. If you have downstream scripts or macros keyed to the old extension, check them.
• Bill Capture preferences were cleaned up. Blank selections have been removed: a blank Save Tax As maps to No tax, a blank Save Shipping Cost As maps to No shipping cost. New options separate net from gross on Expense Line Total and Item Line Total, and some incompatible gross/net combinations are now blocked outright. Review yours at Setup > Accounting > Bill Capture Preferences — a value you never set explicitly now means something explicit.
• Order fulfillment can start from sales order lists, without opening each order or running a separate bulk process.

---

One change from another section that will reach your reports

Filed under Accounting but genuinely a platform change: SuiteQL queries and Analytics datasets built on generic transactions now default to sorting by Transaction.tranDate instead of Transaction.tranDisplayName. Oracle made the change to prevent performance problems.

Anything that specifies a sort order is unaffected. Anything that relied on the old implicit ordering — a saved dataset feeding a report, a workbook someone built two years ago — will come back in a different sequence. If order matters, state it explicitly. Our developers and IT architects breakdown covers the technical side.

---

SuiteApp updates for finance

• Fixed Assets Management 26.2 adds two FAM Diagnostics processes — Check Duplicate DHRs and Check Stale DHRs — to find depreciation history records without journal entries that distort depreciation. Duplicates typically appear when prior forecast DHRs were not cleared before new ones generated; stale ones when forecast DHRs generated but the related Asset Value records did not update. You can review selections and download a CSV before deletion. Asset Reset also now processes cleanup in smaller batches, which should stop the timeouts large asset histories used to hit.
• Brazil Deferred Revenue Recognition is now available as a shared, managed SuiteApp, for companies on Advanced Revenue Management (Essentials) that must account for revenue from tax amounts included in item prices.
• European Union Electronic Invoicing 1.7.0 adds outbound transmission for Poland via KSeF, covering invoices and credit memos.
• Universal Mapping Assistant 1.1.0 adds units-of-measure mapping on the PEPPOL UN/ECE standard and tax code mapping against country tax codes.
• Southeast Asia Localization now supports Philippines invoicing in SuiteTax accounts, including EoPT invoice templates and BIR-required document details.

---

What we would test first

If you only get one Release Preview cycle, spend it here:

1. The reconciliation workflow end to end, with the payment suggestion preferences on — because they are on by default and they change AP behavior, not just AR.
2. Term discount tax adjustments, because the resulting records cannot be edited or deleted.
3. Any saved dataset or workbook whose output order matters, because of the SuiteQL sort change.

Your account's upgrade date is in the New Release portlet on your dashboard. The rest of the series — developers, system administrators, operations, and sales and pricing — is indexed on our complete NetSuite 2026.2 breakdown, which also lists every change by feature area. For the wider 2026 cycle, see the NetSuite 2026 release notes hub.

Frequently asked questions

What clients ask before signing

What changed in NetSuite bank reconciliation in 2026.2?expand_more

What are Payment Runs in NetSuite 2026.2?expand_more

Do I need to enable the new bank reconciliation payment suggestions?expand_more

Can I edit the term discount tax adjustments NetSuite creates?expand_more