Planning and Budgeting Sync SuiteApp: SuiteQL support, auto-prefixed allowlists, and account mapping fixes

This page consolidates release notes for the Planning and Budgeting Sync SuiteApp across versions 25.1 through 26.1.3. Below is a technically oriented breakdown of what changed and what you need to act on.

Version 26.1.3 (May 26, 2026) — Bug fix

Fixes a defect in account metadata hierarchies deeper than two levels. When account type mapping was enabled, child accounts were incorrectly assigned to the wrong parent. If you use multi-level account hierarchies with account type mapping, verify your hierarchy output after upgrading.

Version 26.1.2 (March 3, 2026) — Account type mapping enhancement

A new Source Account Number field is available on the account type mapping configuration. You can now map NetSuite accounts to Planning and Budgeting account members using a combination of account type and account number, rather than account type alone. This provides finer-grained control when your chart of accounts contains multiple accounts of the same type that must map to distinct P&B members.

Version 26.1.1 (February 10, 2026) — Installation fix

Resolves an installation failure for version 26.1.0 on accounts hosted outside the United States. No functional changes.

Version 26.1 (January 20, 2026) — Major release

Inbound connection verification

A new checkbox, Use Entered URL to Verify Inbound Connections, lets you validate that the correct Planning and Budgeting application is connecting to NetSuite. This is set during the connection setup (step 4 of Setting Up the Connection to Planning and Budgeting).

Automatic allowlist prefixing

Previously you had to manually register the customsearch_nspb_ prefix (for saved searches) and custdataset_nspb_ prefix (for datasets) in the NetSuite EPM Connector allowlist. The SuiteApp now injects these prefixes automatically when default saved searches and datasets are created. If you maintain a custom allowlist, confirm that no duplicate entries conflict after upgrade.

SuitePeople saved searches migrated

The saved searches formerly bundled in the separate NSPB-SuitePeople Sync SuiteApp are now included directly as NSPB SuitePeople - Saved Searches. You can use these to load SuitePeople data and metadata into Planning and Budgeting without a separate SuiteApp install.

SuitePeople payroll data by category

You can now view NetSuite SuitePeople payroll data loaded into Planning and Budgeting grouped and summed by workforce categories.

Terminology and UI changes

• Data Load Rule jobs are renamed to Data Integration jobs.
• Relative period options in Data Integration, Group, and Pipeline jobs are renamed: This Month → This Period, Last Month → Last Period. A new option Period Before Last is added.
• The account metadata hierarchy setup page has been redesigned.

If you have scripts, workflows, or documentation referencing the old terminology ("Data Load Rule", "This Month", "Last Month"), update them accordingly. Note: Oracle's notes do not clarify whether any script IDs or internal identifiers changed — only the UI labels are confirmed renamed. Verify in your environment whether any customrecord_ or customscript_ IDs were affected.

Version 25.1 (August 26, 2025) — Major release

SuiteQL query support

You can now write SuiteQL queries to load transaction data and metadata from NetSuite into Planning and Budgeting. This is a significant addition — it gives you the full power of N/query-style syntax to define exactly which data crosses the integration boundary, rather than relying solely on saved searches or datasets.

Pipeline jobs

Pipeline jobs can be scheduled and run directly from NetSuite. For Planning and Budgeting Financials, the old default batch jobs have been replaced by pipeline jobs. Action required: download the updated integration artifacts ZIP from NetSuite and re-upload it into your Planning and Budgeting Financials instance.

Plug-in Code Generator

A new code generator produces custom plug-in scripts for importing budget data from Planning and Budgeting back into NetSuite. This scaffolds the SuiteScript plug-in implementation rather than requiring you to write it from scratch.

Role permission auto-population

During SuiteApp installation, the NSEPM Implementer and NSPB Integration roles are now auto-populated with required permissions based on the features enabled in the target account. Manual permission assignment is no longer needed for fresh installs.

OneWorld no longer required for SuiteSuccess searches

The SuiteSuccess Standard and Premium saved searches now work on accounts without the OneWorld feature enabled.

What to do

1. If you use multi-level account hierarchies with account type mapping: upgrade to 26.1.3 and verify that child accounts map to the correct parents.
2. If you maintain a custom EPM Connector allowlist: after upgrading to 26.1, check for duplicate prefix entries (customsearch_nspb_, custdataset_nspb_) now that the SuiteApp registers them automatically.
3. If you use Planning and Budgeting Financials: download the updated integration artifacts ZIP and re-upload it. The old batch jobs have been replaced by pipeline jobs as of 25.1.
4. If you reference "Data Load Rule" in scripts, scheduled tasks, or docs: update references to "Data Integration". Confirm whether any internal script or record IDs changed — Oracle's notes only confirm the UI label rename.
5. If you previously installed NSPB-SuitePeople Sync separately: the saved searches are now bundled in the main SuiteApp. Evaluate whether you can remove the standalone SuiteApp to reduce bundle clutter.
6. If you run a non-US account and are still on 26.1.0: upgrade to at least 26.1.1 to resolve the installation defect.