Migrating Vendor Bank Data to Payment Instruments for Intelligent Payment Automation (BILL)

What Changed

NetSuite's Intelligent Payment Automation SuiteApp (powered by BILL) introduces a migration path for organizations currently using Electronic Bank Payments or Payment Automation with HSBC. On install, the SuiteApp automatically migrates U.S.-addressed vendor bank accounts into the Payment Instrument record type, which becomes the canonical store for bank details and remittance information going forward.

Migration Behavior

• Only the vendor's U.S. primary bank is migrated — secondary banks and non-U.S. banks are excluded.
• If both Electronic Bank Payments and Payment Automation with HSBC are in use, HSBC data takes priority.
• Existing Payment Instrument records are not overwritten. The migration is additive only.
• After migration completes, NetSuite sends an email with results (success confirmation or failure details). Review this email for records that need manual attention.
• Once a BILL payment account is created, vendor records with open AP balances automatically sync to BILL along with their Payment Instrument banking details.

Where to Verify Migrated Data

• Electronic Bank Payments users: Vendor record > Bank Payment Details subtab (pre-migration source).
• Payment Automation with HSBC users: Vendor record > SuiteBanking subtab (pre-migration source).
• Post-migration (all users): Vendor record (view mode) > Financials subtab > Payment Instruments subtab > click Edit next to the payment instrument. Requires Administrator role.

Manual Migration Script

If the automated migration fails or does not complete, you can manually trigger it by deploying the bundled MapReduce script:

• Script Name: NSNPA - Bank Account Migration MR
• Deployment Script ID: customdeploy_nsnpa_mr_bankacct_migration

Deploy this via the standard Script Deployment Record workflow (Customization > Scripting > Script Deployments).

Non-U.S. Vendors

BILL payment options apply to U.S. vendors only. Non-U.S. vendor payments should continue through Electronic Bank Payments — that SuiteApp is not deprecated by this migration.

Role and Permission Impact

Intelligent Payment Automation ships with its own roles for payment managers and clerks. If you use custom roles, you will need to manually add the Intelligent Payment Automation permissions to those roles. The bundled roles are not automatically merged into existing custom role configurations.

What to Do

1. Audit your vendor bank data before installing. Confirm which vendors have U.S. primary bank records set on the Bank Payment Details or SuiteBanking subtab. Only those records will migrate.
2. Install the Intelligent Payment Automation SuiteApp and monitor the migration email for failures or partial completions.
3. If migration fails, redeploy customdeploy_nsnpa_mr_bankacct_migration manually from the Script Deployment Record.
4. Verify Payment Instrument records on vendor records (Financials > Payment Instruments) to confirm bank details migrated correctly.
5. Update custom roles with Intelligent Payment Automation permissions — the SuiteApp's bundled roles do not replace or augment existing custom roles automatically.
6. For vendors with non-U.S. banks or secondary U.S. banks, manually create Payment Instrument records as needed — the migration only handles U.S. primary banks.
7. Continue routing non-U.S. vendor payments through Electronic Bank Payments.

Gaps in the Documentation

Oracle's source does not specify which NetSuite release introduced this migration path, nor does it name the specific permissions required for custom roles. The exact record fields on the Payment Instrument record are not enumerated. Before rolling this out, verify permission requirements in a sandbox and confirm Payment Instrument field mappings against your existing bank data.