Skip to content
ERP ⇄ Human resources

NetSuite to Smartrecruiters integration — real-time, two-way sync

Keep NetSuite and Smartrecruiters in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect NetSuite and Smartrecruiters

Sync the workers, org structure, and cost centers that NetSuite and Smartrecruiters share in real time, so the people Smartrecruiters manages stay current in the system that runs finance and operations.

Smartrecruiters is the system of record for people: who was hired, which department and location they sit in, who they report to, and how they are paid. NetSuite runs finance and operations, and much of what it does depends on that same information, from booking labor cost to approving an expense report to staffing a project. Where the two are bridged by re-keying or an overnight file, each side spends the day out of step, with new hires missing from the systems they need and leavers still active where they should not be.

Stacksync syncs Term, Subsidiary, All custom objects, Nexus in NetSuite with Users, Approvals, Candidates, Applications in Smartrecruiters field by field, in real time, and in both directions. You decide which system owns which fields, so the people side stays authoritative for worker data while NetSuite keeps its own accounting and operational detail, and every change made in one is reflected in the other within seconds instead of at the next batch run.

Common use cases

  • 01 Mirror journal entries and transaction lines into a warehouse for financial reporting without CSV exports.
  • 02 Sync customers, sales orders, and invoices to an operational Postgres database so teams query ERP data without writing SuiteScript.
  • 03 Export Interviews and Offers to a data warehouse to analyze interviewer load, offer-acceptance rates, and hiring outcomes.
  • 04 Subscribe to the Webhooks API to react to new applications and status changes in near real time across downstream systems.

Common sync patterns

One org structure

Departments, cost centers, and locations that both systems reference stay in agreement, so labor cost, approvals, and reporting in NetSuite roll up to the same structure Smartrecruiters maintains.

Reporting lines drive approvals

Manager and reporting-hierarchy changes in Smartrecruiters keep expense and purchase approval chains in NetSuite pointed at the right people.

Where Smartrecruiters runs payroll: labor cost in the books

Pay and compensation data from Smartrecruiters posts into NetSuite as labor cost, so finance sees workforce spend without re-entering it by hand.

What you can sync between NetSuite and Smartrecruiters

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

NetSuite objects Smartrecruiters objects How this pairing syncs
Subsidiary Synced with incremental and full sync per the Stacksync docs. Approvals Approval requests for jobs and offers; requests can be created, retrieved as pending, commented on, and approved or rejected via the Approvals API. Subsidiary is specific to NetSuite and Approvals to Smartrecruiters — each maps to any object or custom field on the other side.
All custom objects Synced with incremental and full sync per the Stacksync docs. Candidates Person records with contact details, tags, attachments, custom properties, and consent; created, updated, and searched via the Candidates API, often populated from sourcing or enrichment pipelines. All custom objects is specific to NetSuite and Candidates to Smartrecruiters — each maps to any object or custom field on the other side.
Nexus Synced with incremental and full sync per the Stacksync docs. Applications Links a Candidate to a Job and carries the current hiring status and source; created and advanced through statuses (screening, interview, offer, hired, rejected) via the Application API. Nexus is specific to NetSuite and Applications to Smartrecruiters — each maps to any object or custom field on the other side.
Tax Type Synced with incremental and full sync per the Stacksync docs. Jobs Requisitions (positions) with openings, departments, locations, and hiring team; created, patched, and read out for requisition and time-to-fill reporting via the Jobs API. Tax Type is specific to NetSuite and Jobs to Smartrecruiters — each maps to any object or custom field on the other side.
Sales Tax Item Synced with incremental and full sync per the Stacksync docs. Job Postings Job ads and publications pushed to the career site and job boards; created and managed via the job publication endpoints (rate-limited to 2 requests/sec). Sales Tax Item is specific to NetSuite and Job Postings to Smartrecruiters — each maps to any object or custom field on the other side.
Billing Schedule Customer Subsidiary Relationship Synced with incremental and full sync per the Stacksync docs. Interviews Interview types, timeslots, templates, and scheduled interviews with interviewers and times; created, updated, and read for scheduling and interviewer-load analytics. Billing Schedule Customer Subsidiary Relationship is specific to NetSuite and Interviews to Smartrecruiters — each maps to any object or custom field on the other side.

How changes propagate between NetSuite and Smartrecruiters

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

NetSuite Smartrecruiters Interval-based propagation

DetectionStacksync polls NetSuite for changes on an incremental schedule, reading only records changed since the previous pass. Polling on lastModifiedDate via SuiteQL or saved searches.

DeliveryEach detected change is written to Smartrecruiters through its API, with automatic retries and rate-limit backoff.

Smartrecruiters NetSuite Sub-second propagation

DetectionSmartrecruiters notifies Stacksync of record changes through webhook events. Webhooks API — subscribe to events (new application, candidate updated, status changed) delivered with a signing secret and retrievable callback logs.

DeliveryEach detected change is written to NetSuite through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • NetSuite: API concurrency is governed per account; sync tools queue and throttle requests.
  • Smartrecruiters: Per API credential: most endpoints allow up to 10 requests/sec (job publication and offer documents 2/sec), plus a concurrency limiter of up to 8 simultaneous requests (GET /candidates capped at 1). Exceeding returns 429; responses carry X-RateLimit-Limit/Remaining and concurrent-limit headers.
What ships with NetSuite ⇄ Smartrecruiters

Connect NetSuite and Smartrecruiters for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every NetSuite–Smartrecruiters connection.

Real-time

Two-way sync

Changes in NetSuite or Smartrecruiters instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever NetSuite or Smartrecruiters data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single NetSuite or Smartrecruiters record.

Observability

Monitoring

Track your NetSuite ⇄ Smartrecruiters sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between NetSuite and Smartrecruiters.

How the NetSuite and Smartrecruiters connectors work

NetSuite

Integration surface
SuiteTalk REST and SOAP web services, plus SuiteQL queries
Authentication
Token-Based Authentication (TBA): enable REST Web Services (and SOAP Web Services) + Token-Based Authentication in NetSuite, create an integration record to get Consumer ID/Secret
Change detection
Polling on lastModifiedDate via SuiteQL or saved searches; no native webhooks without custom SuiteScript
Capabilities
read · write
Rate limits
API concurrency is governed per account; sync tools queue and throttle requests.
NetSuite setup guide

Smartrecruiters

Integration surface
SmartRecruiters REST APIs (SmartAPIs) on api.smartrecruiters.com — Candidates, Application, Jobs, Interviews, Offers, Users, Approvals, plus a Webhooks API for event subscriptions
Authentication
X-SmartToken API key header for a customer's own integration (grants full company access, no scopes or expiry), or OAuth 2.0 authorization-code flow for partner and Marketplace apps with user-scoped permissions
Change detection
Webhooks API — subscribe to events (new application, candidate updated, status changed) delivered with a signing secret and retrievable callback logs; otherwise poll list endpoints with updated-after-style filters. No log-based change data capture.
Capabilities
read · write · webhooks
Rate limits
Per API credential: most endpoints allow up to 10 requests/sec (job publication and offer documents 2/sec), plus a concurrency limiter of up to 8 simultaneous requests (GET /candidates capped at 1). Exceeding returns 429; responses carry X-RateLimit-Limit/Remaining and concurrent-limit headers.
Smartrecruiters setup guide
How it works

How to connect NetSuite to Smartrecruiters — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate NetSuite and Smartrecruiters with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    NetSuite connected
    Smartrecruiters connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the NetSuite and Smartrecruiters objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · NetSuite ⇄ Smartrecruiters
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    NetSuite Smartrecruiters
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

NetSuite and Smartrecruiters integration FAQ

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

Related integrations

Every pair below is a real-time, two-way sync. Search all 529 integrations available for NetSuite and Smartrecruiters.

Popular · 7 of 529
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.