New Payments Experience (NetSuite)

Bank's New Payments Experience is a modern, reimagined approach to bill payments and expense reimbursements in NetSuite. Built from the ground up for speed and collaboration, the new experience brings powerful features like partial payments, cross-page bulk selection, and flexible payment runs capabilities that transform how your AP team works.

This upgrade removes the friction of managing two separate bundles to make payments, creating a seamless experience where all vendor and employee payment information lives in one place. Say goodbye to switching between the Bank Plugin and Entity Bank Details, everything you need is now unified under the Payment Methods page.

This guide helps administrators upgrade once your organization is invited to the New Payments Experience and explains what changes for all users.

Currently, you need to install two separate bundles to manage payments: the Bank Plugin (for payment processing) and the Entity Bank Details bundle (for storing vendor and employee bank accounts). Managing payment information means switching between these two bundles.

With the new experience, all bank account management is built directly into the Bank Plugin's Payment Methods page. You only need the Bank Plugin, no more managing a separate Entity Bank Details bundle. Everything you need to manage and process payments is in one place under Accounts Payable (New).

Pay any amount less than the full bill balance. This is useful when you want to pay in installments or match available cash flow. The remaining balance stays on the bill for future payments. For example, if a bill is for $10,000, you can pay $3,000 now and the remaining $7,000 later.

Pages load faster with smoother navigation. The new experience reads data from a high-performance database instead of querying NetSuite directly every time. You'll notice less waiting for bills and expense reports to load, and navigating between pages feels more responsive.

Select bills across multiple pages without losing your selections. Currently, if you select bills on page 1 and navigate to page 2, your selections on page 1 are cleared. With the new experience, you can select bills across the entire list (page 1, page 2, page 3, etc.), then pay them all in one batch. This saves time when processing large payment runs.

Multiple team members can work on payments simultaneously without blocking each other. Currently, all users are locked out when someone else is initiating the payments. With the new experience, your entire AP team can work together, selecting and processing payments at the same time. This improves efficiency for teams processing high payment volumes.

Process payments across multiple currencies in a single payment run by selecting a different source account for each currency. Currently, you can only select one source account per payment run. This means if you need to pay bills in CAD, USD, and EUR, you have to run three separate payment processes. Each currency requires its own payment run. With the new experience, select bills in any currency all at once, then choose which source account to pay from for each currency during the same payment run.

Choose exactly which bank account to use for each vendor or employee when you set up their payment method. In the current experience, you select "ACH" as the payment method and then separately mark a bank account as Primary in Entity Bank Details. This causes less visibility, is cumbersome while making payments, and is prone to error. However, with the new experience, you set up "ACH + Bank Account A" or "ACH + Bank Account B" directly for each vendor in the Payment Methods page. This full detail shows up when you pay bills, so you always know exactly which account the payment will come from.

Set up multi-level approval workflows for payee's payment information changes with up to 3 tiers of up to 5 approvers in each tier. Define who can approve when someone adds, updates, or deletes a payee's payment information (bank account, address, and email). Email notifications are automatically sent to approvers when changes need approval. This gives you more control and helps with compliance for your payee management processes.

Before starting the upgrade, ensure the following requirements are met:

The New Payments Experience is available to invited clients only. This is a controlled rollout to ensure a smooth transition for all clients.

How to check if you're invited:

To request access:

Only NetSuite administrators can perform the upgrade. If you are not an administrator, contact your NetSuite admin to start the upgrade process. Non-admins will see an informational message in the upgrade popup but cannot proceed with the upgrade.

The new experience requires REST Web Services to be enabled in NetSuite.

To enable:

Only upgrade Production after confirming everything works in Sandbox.

The upgrade brings your approved bank accounts from Entity Bank Details (EBD) to the new experience. This is a one-time migration and only migrates approved records.

Before upgrading:

Any unapproved bank accounts will NOT migrate and will not be available in the Payment Methods page after upgrade.

This video walks you through the complete upgrade process and gives you a sneak peek into the new Payments experience.

After the upgrade completes successfully, there are two important setup tasks for administrators:

All non-administrator users in your NetSuite account won't have access to the new Accounts Payable (New) pages by default. You need to grant permissions to the following Suitelet scripts for your AP team to allow them to use the New Experience.

Required Suitelet Scripts:

How to grant access:

To get access to the Payment Approvals page, please have your ERP Administrator navigate to the role to Customization → Scripting → Script Deployment. Use the following filters:

Edit the above listed scripts and, under the Audience tab, add roles that require access to Payment Approvals.

If your organization requires approval workflows for changes to vendor or employee payment information, you can set up multi-level approval rules with up to 3 tiers of up to 5 approvers in each tier.

What gets approved:

Who can approve: