LogoLogo
Agentnoon.com
  • Agentnoon Help Center
  • Changelog
  • FAQs
  • Agentnoon Help Center
  • Quick Start
    • Video Guides
  • Data Import
    • Data Requirements
    • Attributes Overview
    • Calculated Agentnoon Attributes
    • Data Error Checklist
    • Data Import
    • Partial Data Upload
    • Formulas
  • Access Control
    • Access Groups
    • Advanced Access Controls
    • User Invitations
  • Settings
    • General
    • Fields
    • Compensation Cards
    • Field Duplication
  • Org Chart
    • Org Chart Navigation
  • Hub
    • Chart Navigation
    • Packs
    • Chart Library
  • Forecast
    • Forecast Navigation
  • Scenarios
    • Scenario Creation
    • Single Position Interactions
    • Bulk Position Interactions
    • Advanced Position Interactions
    • Change Tracker
    • Before and After Analysis
    • Scenario Change Log
    • Scenario Comparisons
    • Scenario Refresh
    • Project Creation
    • Talent Selection
    • User Collaboration
    • Undo Actions
    • Scenario Management
    • Scenario Tags
    • Scenario Symbols
  • Approvals
    • Approvals
  • Activity Analysis
    • Activity Analysis
  • Best Practice Guides
    • Best Practices for Salary Data
Powered by GitBook

© 2025 Agentnoon Inc. All rights reserved.

On this page
  • 1. Upload Each Component Separately
  • 2. Use Consistent Field Naming
  • 3. Support for Multiple Currencies
  • 4. Normalize Units Across Fields
  • 5. Avoid Free Text in Numeric Fields
  • 6. Validate Totals Before Upload
  • 7. Secure Sensitive Information

Was this helpful?

  1. Best Practice Guides

Best Practices for Salary Data

To ensure accurate compensation modeling, analytics, and reporting

1. Upload Each Component Separately

Break down salary data into its individual components:

  • Base Salary

  • Bonus

  • Benefits

  • Allowances

  • Other Compensation

This allows Agentnoon to calculate total compensation and run cost modeling with flexibility.

2. Use Consistent Field Naming

Ensure the field names used in the imported salary files exactly match the naming in your:

  • Rate Cards

Example: If your salary upload uses Base_Salary, your rate card should not use BasePay—they must be the same.

3. Support for Multiple Currencies

If your data spans multiple currencies:

  • Include a Currency column (e.g., USD, EUR, NGN)

  • Include a Salary_Amount_Local field

(Optional) Add a Salary_Amount_USD field if conversion is pre-applied Agentnoon supports in-platform currency conversion, but clarity at upload helps validate totals.

4. Normalize Units Across Fields

Ensure all monetary values are uploaded in the same unit (e.g., annual, monthly). Use a Frequency field to denote if values are:

  • Annual

  • Monthly

  • Hourly

This enables fair comparisons and accurate forecasting.

5. Avoid Free Text in Numeric Fields

Do not enter salary data as text with symbols (e.g., "$50,000"). Use numeric values only (e.g., 50000) with separate fields for currency or frequency.

6. Validate Totals Before Upload

Sum each salary record to ensure: Total Compensation = Base + Bonus + Benefits + Allowances + Other This prevents mismatches in dashboards or when filtering for salary bands.

7. Secure Sensitive Information

Ensure salary files are access-controlled and uploaded by authorized users only.

PreviousActivity Analysis

Last updated 1 day ago

Was this helpful?