Intelligent Payment Automation Now Supports Multi-Subsidiary (OneWorld)

What Changed

Intelligent Payment Automation — the SuiteApp that integrates NetSuite with BILL for automated vendor payments — now supports multiple subsidiaries in OneWorld accounts. Previously the integration was limited to a single subsidiary context. Key points:

• Each subsidiary with a valid U.S. address must create its own separate BILL account and go through the full three-step sign-up process independently.
• The Payment Automation dashboard (Payment Automation > Dashboard > Overview) now includes a subsidiary switcher in the left panel, scoped to subsidiaries the current user has access to.
• Only subsidiaries that have completed the BILL sign-up flow appear in the switcher.
• Vendors linked to multiple subsidiaries are now supported, meaning a single vendor record shared across subsidiaries can be used with the payment automation workflow in each subsidiary context.

Limitations & Gaps in the Source

Oracle's documentation does not specify:

• Whether any new records, custom fields, or sublists were added to support the per-subsidiary BILL account mapping. Inspect the SuiteApp bundle (Intelligent Payment Automation) post-update for new custom records or fields on the subsidiary record.
• Any SuiteScript or REST API surface changes. If you have custom scripts that interact with payment automation custom records or the BILL integration, verify they still function correctly in a multi-subsidiary context.
• Whether existing single-subsidiary BILL configurations are automatically migrated or require manual re-enrollment.

What to Do

1. Identify eligible subsidiaries — Review which of your OneWorld subsidiaries have valid U.S. addresses and need automated bill payments.
2. Complete BILL sign-up per subsidiary — Each subsidiary must independently go through:
   • Setting up IPA roles and permissions
   • Signing up with BILL within the SuiteApp
   • Configuring bank accounts
3. Configure vendor records — For vendors shared across subsidiaries, verify they are linked to all relevant subsidiaries and that payment automation settings are correct in each subsidiary context.
4. Assign subsidiary access to employees — Use the Assigning a Subsidiary to an Employee workflow to control which users can view and manage each subsidiary's payment automation dashboard.
5. Audit existing customizations — If you have SuiteScript customizations, saved searches, or workflows that reference payment automation records, test them in a multi-subsidiary sandbox to confirm they handle the subsidiary dimension correctly.
6. Review the updated SuiteApp bundle — After the update, check for new custom records, fields, or script deployments added by the bundle to understand the data model changes.