Payment Automation SuiteApp: Multi-Subsidiary Vendor Sync with BILL

What changed

The Payment Automation SuiteApp (BILL integration) adds multi-subsidiary vendor management for NetSuite OneWorld accounts. Instead of a single vendor profile in BILL, the SuiteApp now provisions a separate vendor profile per subsidiary. This keeps payment details (bank accounts, addresses) scoped to each subsidiary independently.

Sync behavior

• Primary subsidiary — changes to a vendor's address or bank information propagate to BILL immediately (real-time).
• Non-primary subsidiaries — changes are queued and applied during a daily batch sync at 5:00 PM Pacific (UTC−8). Payments against those subsidiaries are held until the sync completes.

Monitoring & manual override

• Sync status is visible at Payment Automation > Payment Dashboard > View. Select a subsidiary under the Enabled subtab, click View in the Actions column, then navigate to Payments and Vendors > Vendors in the left panel.
• A manual sync option is available from the Vendors dashboard if payments must be processed before the 5 PM window. Oracle references the help topic Manually Syncing Vendors with BILL for step-by-step instructions.

Technical details the source does not clarify

The release note is light on implementation specifics. The following points are not documented and should be verified in your environment or with Oracle support:

• Whether the per-subsidiary vendor profiles are represented as new records in NetSuite or only on the BILL side.
• Whether the daily sync is a scheduled script (Map/Reduce or Scheduled) bundled in the SuiteApp, and if its timing is configurable.
• How the payment hold is enforced — whether it sets a vendor status, a custom field, or blocks at the BILL API level.
• Impact on existing SuiteScript customizations that create or modify vendor records (e.g., N/record operations on record.Type.VENDOR) and whether subsidiary-assignment triggers additional sync events.
• Whether RESTlet or SuiteTalk integrations that update vendor bank/address fields trigger the same real-time vs. delayed sync behavior.

What to do

1. OneWorld + BILL users — confirm the Payment Automation SuiteApp bundle is updated to the version that includes this feature. Check Customization > SuiteBundler > Search & Install Bundles > List.
2. Review existing vendor scripts — if you have User Event or Workflow scripts on the Vendor record that modify address or bank fields, test whether those changes are picked up by the daily sync or require a manual trigger.
3. Adjust payment timing — if you run automated payment batches (via scheduled script or BILL's own scheduler) for non-primary subsidiaries, account for the 5 PM PT sync window. Payments submitted before the sync completes will be held.
4. Monitor the dashboard — incorporate the Subsidiary Dashboard sync-status check into your AP close procedures, especially during the first few cycles after enabling the feature.
5. Manual sync for urgency — familiarize your AP team with the manual sync option from the Vendors dashboard so time-sensitive payments are not blocked by the batch schedule.