Skip to main content
Version: Current

Departments

Overview​

The NetSuite Departments integration synchronizes organizational department structure from NetSuite to Zudello, enabling accurate expense allocation and departmental reporting across systems.

Integration Details:

  • Direction: NetSuite → Zudello (📥 Inbound)
  • Sync Type: Incremental
  • Sync Frequency: Every 6 hours
  • API Used: SuiteQL
Key Benefits
  • Maintains organizational structure consistency
  • Supports hierarchical department relationships
  • Enables departmental cost tracking
  • Facilitates accurate expense allocation

Field Mappings​

NetSuite FieldZudello FieldDescriptionData Type
nameDepartmentNameDepartment nameString
isinactiveStatustrue = INACTIVE, false = ACTIVEString
parentParentDepartmentParent department for hierarchyRelation
includechildrenIncludeChildrenConsolidation indicatorBoolean
subsidiarySubsidiaryAssociated subsidiaryRelation
nohierarchyFlatStructureHierarchy participation flagBoolean

API Configuration​

SuiteQL Query Structure​

The integration queries department data with hierarchical relationships to maintain organizational structure integrity.

Authentication​

  • Method: Token-based Authentication (TBA)
  • Required Permissions:
    • Departments (View)
    • Lists → Employees (View)
    • Subsidiaries (View)

Sync Configuration​

Incremental Sync Logic​

The integration maintains efficient department synchronization:

  • Initial sync captures complete department hierarchy
  • Subsequent syncs retrieve departments where lastmodifieddate > last sync timestamp
  • Processes parent departments before child departments
  • Maintains hierarchy relationships during updates

Data Transformation​

  • Status Conversion: NetSuite boolean isinactive (T/F) → Zudello string status (INACTIVE/ACTIVE)
  • Hierarchy Validation: Ensures parent departments exist before processing children
  • Subsidiary Mapping: Associates departments with correct organizational entities

Processing Logic​

  1. Hierarchy Query: Retrieve departments with parent relationships
  2. Order Processing: Process parent departments before children
  3. Status Management: Update active/inactive department flags
  4. Validation: Ensure department names are unique within scope
  5. Subsidiary Linking: Associate departments with subsidiaries
  6. Consolidation Rules: Apply include/exclude children logic

Troubleshooting​

IssuePossible CauseSolution
Missing departmentsPermission restrictionsVerify Departments view permissions
Hierarchy breaksParent not syncedRun full sync to rebuild hierarchy
Subsidiary conflictsMulti-subsidiary accessCheck subsidiary permissions
Duplicate departmentsDepartment mergingReview department consolidation
Sync timing issuesLarge hierarchyOptimize processing order