Account Type Mapping Now Supports Account-Number-Level Granularity in FCCS Sync

What changed

The Account Type Mapping configuration in NetSuite EPM > Close Management and Consolidation > Configuration Checklist now lets you optionally specify a Source Account Number alongside the Source Account Type. This enables one-to-many mappings — the same NetSuite account type can map to different FCCS target account types depending on the specific account number.

Matching priority

• If a mapping record includes a Source Account Number, it takes priority over any type-only mapping for the same account type.
• If no account number is defined on the mapping record, the existing logic based solely on account type is used.

Ordering and duplicate rules

• When adding account-number-level mappings alongside a type-level mapping, the type-level record (with an empty account number field) must come first. The account-number-specific record must be placed after it.
• Do not add account numbers to existing mapping records. Always create a separate record with the account number.
• Each account number may only appear once per NetSuite account type. A second record with the same account type and account number is treated as a duplicate; only the earlier record appears in the generated saved search result used for the FCCS metadata export.
• Account-number-specific records must target a different FCCS account type than the type-level record.

Note: Account numbers are found at Lists > Accounting > Accounts.

What to do

1. Navigate to NetSuite EPM > Close Management and Consolidation > Configuration Checklist.
2. Locate The Account Type Mapping is set for FCCS and click View.
3. To add a granular mapping, click Add Account Type Mapping. Select the Source Account Type, enter the specific account number in Source Account Number, and set the Target Account Type to the desired FCCS type.
4. Ensure record ordering is correct: the type-only record (no account number) must precede any account-number-specific records for the same source account type.
5. Verify the generated saved search results reflect the expected mappings — duplicate account-number entries are silently dropped.
6. After saving mappings, load Accounts metadata into FCCS following the Accounts Metadata in Close Management and Consolidation Sync guide to confirm the sync picks up the new mapping logic.

Caveats

• Oracle's documentation does not specify which release introduced account-number-level granularity. If you do not see the Source Account Number field in your configuration checklist, confirm your NetSuite version and verify that the EPM Close Management feature is enabled.
• The behavior around duplicate detection (silent drop from saved search results) is worth testing in Sandbox before relying on it in production consolidation runs.