NSPB Account Type Mapping Now Supports Account-Number-Level Overrides

NetSuite's Planning and Budgeting Sync now exposes a custom record type — NSPB | Account Type Mapping — that gives admins explicit control over how NetSuite account types translate to Planning and Budgeting account types. Previously, this mapping followed implicit logic based solely on account type. The new record lets you override at the individual account-number level.

Note: Oracle's documentation does not specify which release introduced this feature. Verify availability in your environment before relying on it.

What changed

• A new custom record type NSPB | Account Type Mapping is available at Customization > Lists, Records, & Fields > Record Types.
• Each mapping record has three key fields: Source Account Type (picklist of NetSuite account types), Target Account Type (free-text name of the P&B account type), and Source Account Number (optional, for account-level overrides).
• When a Source Account Number is set, it takes priority over the Source Account Type mapping. If no account number is defined, the legacy account-type-based logic applies.
• Setting a unique account number lets you fan out a single NetSuite account type to multiple P&B account types.
• Mapping records feed into generated saved searches consumed by the sync. Duplicate account numbers within the same NetSuite account type are silently dropped — only the first record appears in the saved search results.

Ordering and priority rules

Record ordering is critical and easy to get wrong:

1. Do not add an account number to an existing mapping record. Always create a new record with the account number.
2. The account-number record must appear after the generic (empty account number) record for the same Source Account Type.
3. A generic record for the Source Account Type must exist first, even if you only intend to map a specific account number.
4. Each account number may only appear once per Source Account Type. A second record with the same account number is treated as a duplicate and excluded from the saved search.

What to do

1. Navigate to Customization > Lists, Records, & Fields > Record Types and locate NSPB | Account Type Mapping.
2. Click List to review any existing mappings before creating new ones.
3. To add a type-level mapping, click New Record, select the Source Account Type, enter the Target Account Type, and leave Source Account Number blank.
4. To add an account-number override, create a second record for the same Source Account Type, populate the Source Account Number (found at Lists > Accounting > Accounts), and set a different Target Account Type. Ensure this record is ordered after the generic record.
5. Verify your mappings by checking the generated saved search results — confirm no duplicates were silently dropped.
6. If you use SuiteScript or integrations that read NSPB metadata saved searches downstream, test that the new mapping records surface correctly and that your code handles the additional granularity.