Skip to main content
Version: Current

Classifications

Overview

The NetSuite Classifications integration synchronizes cost center and classification data from NetSuite to Zudello, enabling accurate expense allocation and departmental financial tracking.

Integration Details:

  • Direction: NetSuite → Zudello (📥 Inbound)
  • Sync Type: Incremental
  • Sync Frequency: Every 6 hours
  • API Used: SuiteQL
Key Benefits
  • Accurate cost center tracking across systems
  • Supports multi-level classification hierarchies
  • Enables departmental expense analysis
  • Maintains classification relationships

Field Mappings

NetSuite FieldZudello FieldDescriptionData Type
nameClassificationNameClassification identifierString
classnumberClassificationCodeUnique classification codeString
isinactiveStatustrue = INACTIVE, false = ACTIVEString
parentParentClassificationParent classification for hierarchyRelation
subsidiarySubsidiaryAssociated subsidiaryRelation
includechildrenIncludeChildrenConsolidation indicatorBoolean
descriptionDescriptionClassification descriptionString

API Configuration

SuiteQL Query Structure

The integration uses SuiteQL to query classification data with support for hierarchical structures and incremental synchronization.

Authentication

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

Sync Configuration

Incremental Sync Logic

The integration efficiently syncs only modified classifications:

  • Initial sync captures entire classification structure
  • Subsequent syncs retrieve records where lastmodifieddate > last sync timestamp
  • Maintains parent-child relationships during incremental updates
  • Preserves classification hierarchy integrity

Data Transformation

  • Status Conversion: NetSuite boolean isinactive (T/F) → Zudello string status (INACTIVE/ACTIVE)
  • Hierarchy Processing: Ensures parent classifications sync before children
  • Subsidiary Mapping: Links classifications to appropriate entities

Processing Logic

  1. Hierarchy Retrieval: Query classifications with parent relationships
  2. Order Processing: Process parent classifications before children
  3. Status Transformation: Convert NetSuite boolean to string status
  4. Validation: Ensure classification codes are unique
  5. Subsidiary Association: Map classifications to correct subsidiaries
  6. Consolidation Rules: Apply include/exclude children logic

Troubleshooting

IssuePossible CauseSolution
Missing classificationsPermission restrictionsVerify Classifications view permissions
Hierarchy errorsParent not syncedRun full sync to rebuild hierarchy
Subsidiary mismatchMulti-subsidiary setupCheck subsidiary access permissions
Duplicate codesClassification renamingReview classification code uniqueness
Sync gapsTimezone differencesVerify timestamp handling