Still using NetSuite Payment Automation with HSBC? Plan the supported payment transition

Who should check?

Accounts using NetSuite Payment Automation linked to HSBC Online Accounts, checks, ACH or virtual-card payments, especially finance teams with open HSBC balances, pending payments, vendor bank details or multiple OneWorld subsidiaries. Other NetSuite payment methods and organizations not using this specific HSBC-integrated SuiteApp are not automatically affected.

Published milestones

1. March 4, 2026 — legacy HSBC enrollment cutoffOracle permits continued legacy use only for customers who applied by this date; it says new and pending HSBC online-account applications are not processed.
2. November 5, 2026 — Ebenstead research and publicationEbenstead documented the existing Oracle guidance on this date. The original Oracle Help Center pages have no independently established publication date.
3. Before December 31, 2026 — tested transitionInventory outstanding payments and records, configure IPA in an authorized environment, verify vendor bank data and payment approval controls, and test a payment run.
4. December 31, 2026 — targeted support endOracle says HSBC Payment Automation support is targeted to end. This is a support milestone, not automatic proof that the installed SuiteApp is removed or no longer executes.
5. After finance-approved transition and HSBC offboardingSettle balances and pending payments, archive statements by subsidiary, and only then consider optional uninstall. HSBC account closure prevents additional legacy payments.

Check your Oracle account notice before scheduling an update.

A practical response

• Have the AP and treasury owners identify every HSBC Payment Automation account, subsidiary, pending payment, open check, card balance and statement-retention obligation. Confirm the exact installed SuiteApp and vendor notice.
• Agree an authorized replacement payment workflow and install/configure Intelligent Payment Automation for one controlled payment type. Verify each vendor’s migrated primary bank details and any custom-form Payment Instruments fields; perform a permitted test payment and confirm its processing status.
• Create a cutover list for new versus in-flight payments, bank balances, card settlement, outstanding checks, approval roles and reconciliation. Move new payments only after the replacement test passes and finance approves.
• Download and preserve required HSBC statements, invoices and audit trails for all affected subsidiaries; offboard accounts with HSBC in the approved sequence and only then consider optional SuiteApp uninstall.

What we’ll review

Confirm which payment SuiteApp is installed and its version, HSBC online/card accounts and subsidiaries, open ACH/check/virtual-card activity and pending settlements, vendor bank record setup, payment approvals, bank owner and audit retention requirements. Check whether Payment Instruments appears on custom vendor forms, the authorized replacement payment process, and whether a tested transition can be completed before the targeted support end.

Follow this topic via RSS