2026.1 Banking SuiteApps: Payment Automation Sunset, On-Demand Bank Feeds, Cash 360 & IPA Updates

The 2026.1 banking notes bundle one major deprecation (HSBC/Payment Automation) and a set of incremental SuiteApp upgrades across Bank Feeds, Cash 360, and Intelligent Payment Automation (IPA). Most of the impact is admin-level configuration and SuiteApp version bumps, but the Payment Automation sunset is a hard deadline that needs project planning now.

Payment Automation SuiteApp - End of Support

HSBC and Oracle NetSuite are ending their partnership for the NetSuite Payment Automation Cloud Service. Concrete dates and effects:

• March 4, 2026 - last date HSBC online applications could be submitted/approved through the SuiteApp.
• 2026.1 - the SuiteBanking > HSBC Application > Apply navigation path is removed; no new HSBC online account applications can be submitted.
• December 31, 2026 - phased end of support; the Payment Automation SuiteApp will no longer be available.

Existing customers (including those approved by March 4, 2026) can continue to use the SuiteApp until EOS. Oracle's recommended replacement is Intelligent Payment Automation (IPA).

What to do

1. Inventory any saved searches, workflows, SuiteScripts, or scheduled jobs that reference Payment Automation records, custom records, or the HSBC application flow. They will break after EOS.
2. Open a migration project to IPA. Validate that your vendor base, subsidiary structure, and payment file formats are supported.
3. If you rely on integrations posting to Payment Automation endpoints, plan to repoint them at IPA before Q4 2026.
4. Review the official NetSuite Payment Automation Cloud Service End of Support Notice for the authoritative timeline.

Bank Feeds 26.1.0 - On-Demand AISP Imports

Previously the Bank Feeds SuiteApp pulled transactions from your Account Information Service Provider (AISP) once per day. Version 26.1.0 adds an on-demand refresh for connected accounts.

• Supported AISPs: MX Technologies, Yodlee, Salt Edge.
• A new Update Imported Bank Data button appears in view mode at the top of the Format Profile page for all preinstalled Bank Feeds format profiles.
• Clicking the button triggers an import of recent transactions for every connected account in that format profile.
• Limitation: not available for accounts that require multi-factor authentication (MFA).

Note: the release notes do not document a SuiteScript API, REST endpoint, or governance cost for triggering this refresh programmatically. If you need to automate it, verify on your sandbox whether the button maps to a callable Suitelet/RESTlet or whether it is UI-only.

Cash 360 1.4.0 - Sales Orders with Billing Schedules in Forecasts

Cash 360 SuiteApp 1.4.0 now includes sales orders that have standard billing schedules in cash forecasts, provided the Include Sales Orders box is checked on the Cash 360 Preferences page.

• A new Sales Orders with Billing Schedules row appears under inflows on the Cash Forecast table.
• Drill-down shows billing schedule, payment terms, forecast date, and amounts.
• Forecast date formula: Forecast date = Billing schedule bill date + Payment terms.
• Payment terms defined on the billing schedule override any payment terms set on the sales order header. This is a behavior change worth flagging to AR/finance.

Cash 360 1.3.5 - Map/Reduce Bug Fix

Cash 360 SuiteApp 1.3.5 fixes errors thrown by the Order Billing Lead Time map/reduce script for sales orders and purchase orders. If you have been seeing failed script executions tied to Cash 360 in the script execution log, upgrade and re-run.

Intelligent Payment Automation 2.0.0

IPA 2.0.0 ships several functional expansions. All UI lives under Payment Automation > Dashboard > Overview, with most new fields under Payment Processing > Payables.

Global customers with U.S. subsidiaries

IPA was previously restricted to U.S.-based companies paying U.S.-based vendors. It can now be installed in OneWorld accounts where at least one subsidiary is in the U.S. Re-evaluate eligibility if you previously ruled IPA out for this reason.

Class / Department / Location (CDL) on Payables

If CDL features are enabled in the account, the Payables page now exposes Class, Department, and Location fields. Review any custom GL impact, segment-based reporting, or saved searches over IPA records to make sure the new classification fields are populated as expected.

Multi-subsidiary vendor support (OneWorld + BILL)

• Vendors linked to multiple subsidiaries now create a unique vendor profile per subsidiary in BILL.
• Address and bank-info changes in NetSuite sync to BILL automatically daily at 5:00 PM Pacific (UTC-8).
• You can trigger a manual sync before the scheduled run.

If you have integrations or scripts that mutate vendor records, be aware that each NetSuite vendor may now correspond to N BILL profiles. Reconciliation logic that assumed a 1:1 mapping needs review.

Cleared check visibility

Payment records now expose Sent Date and Check Number for checks cleared via BILL, plus a View Check action that displays/downloads the cleared check image. Useful for AP audit workflows - consider surfacing these on custom payment forms.

Update vendor/bank details after sending payment

Previously, vendor and bank detail edits were blocked until a payment was fully processed. IPA 2.0.0 allows edits immediately after the payment is sent. Review approval workflows and any SuiteScript user-event triggers on the vendor record that assumed the old lockout window.

Vendor ID search in the Payee filter

For accounts using autogenerated vendor numbers, the Payee filter on the Payables page now matches against both Vendor ID and Vendor name. Previously only the Vendor ID was searchable in this filter.

What to do

1. Payment Automation customers: start an IPA migration plan immediately. Block calendar time before December 31, 2026.
2. Bank Feeds users: upgrade to 26.1.0 and confirm none of your critical accounts require MFA (those won't get on-demand refresh).
3. Cash 360 users: upgrade to at least 1.3.5 to clear the map/reduce errors; upgrade to 1.4.0 if you want billing-schedule SOs in the forecast, and warn finance about the payment-terms override rule.
4. IPA users: upgrade to 2.0.0, validate CDL field population on Payables, and audit any vendor-sync integrations for multi-subsidiary impact.
5. OneWorld customers not using IPA: reassess eligibility now that non-U.S. parents with U.S. subsidiaries are supported.
6. Verify on a sandbox whether any of the new UI controls (on-demand bank refresh, manual BILL sync, View Check) expose scriptable hooks - the release notes do not document SuiteScript modules, REST endpoints, or governance units for these features.