Skip to content
ERP ⇄ Human resources

Epicor ERP to Smartrecruiters integration — real-time, two-way sync

Keep Epicor ERP 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 Epicor ERP and Smartrecruiters

Sync the workers, org structure, and cost centers that Epicor ERP 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. Epicor ERP 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 Suppliers, Parts, Sales orders, Purchase orders in Epicor ERP with Jobs, Job Postings, Interviews, Offers 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 Epicor ERP 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 Sync Epicor customers and AR invoices into a CRM so sales sees order history and credit status without ERP logins.
  • 02 Push won opportunities from the CRM into Epicor as sales orders and sync order status back.
  • 03 Stream Jobs and Job Postings into a reporting database for requisition, funnel, and time-to-fill dashboards.
  • 04 Export Interviews and Offers to a data warehouse to analyze interviewer load, offer-acceptance rates, and hiring outcomes.

Common sync patterns

Where Smartrecruiters runs payroll: labor cost in the books

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

Where Smartrecruiters is the worker system of record: one employee master

When a worker is hired, moved, or offboarded in Smartrecruiters, the matching employee record in Epicor ERP is created, updated, or deactivated, so the business system reflects the workforce as it actually is.

New hires ready to transact in Epicor ERP

A new person set up in Smartrecruiters becomes an employee record in Epicor ERP in time to submit expenses, enter time, or approve a purchase, without waiting on manual setup.

What you can sync between Epicor ERP 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.

Epicor ERP objects Smartrecruiters objects How this pairing syncs
Jobs Production jobs whose status feeds shop-floor dashboards and delivery-date updates. 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. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Customers Master records synced with CRM accounts so sales and the ERP agree on ownership and credit status. 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). Customers is specific to Epicor ERP and Job Postings to Smartrecruiters — each maps to any object or custom field on the other side.
Suppliers Vendor masters kept aligned with procurement and AP automation tools. Interviews Interview types, timeslots, templates, and scheduled interviews with interviewers and times; created, updated, and read for scheduling and interviewer-load analytics. Suppliers is specific to Epicor ERP and Interviews to Smartrecruiters — each maps to any object or custom field on the other side.
Parts Item masters that anchor inventory, BOM, and order line syncs. Offers Offer records tied to an Application with status, custom offer fields, and offer documents; readable and writable, commonly synced to an HRIS on hire (documents endpoint limited to 2 requests/sec). Parts is specific to Epicor ERP and Offers to Smartrecruiters — each maps to any object or custom field on the other side.
Sales orders Created from won CRM opportunities; status and line changes sync back out. Users Company users (recruiters, hiring managers) with roles, access groups, and activation state; read and written via the User Management API. Sales orders is specific to Epicor ERP and Users to Smartrecruiters — each maps to any object or custom field on the other side.
Purchase orders Synced with procurement systems and matched against receipts. Approvals Approval requests for jobs and offers; requests can be created, retrieved as pending, commented on, and approved or rejected via the Approvals API. Purchase orders is specific to Epicor ERP and Approvals to Smartrecruiters — each maps to any object or custom field on the other side.

How changes propagate between Epicor ERP 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.

Epicor ERP Smartrecruiters Interval-based propagation

DetectionStacksync polls Epicor ERP for changes on an incremental schedule, reading only records changed since the previous pass. Polling on change-date fields.

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

Smartrecruiters Epicor ERP 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 Epicor ERP through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Epicor ERP: Subject to the platform's API rate limits and per-tenant throttling on Kinetic cloud deployments.
  • 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 Epicor ERP ⇄ Smartrecruiters

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Epicor ERP 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 Epicor ERP or Smartrecruiters record.

Observability

Monitoring

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

Trading partners

EDI

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

How the Epicor ERP and Smartrecruiters connectors work

Epicor ERP

Integration surface
REST API (OData) over Epicor business objects, plus BAQ (Business Activity Query) endpoints
Authentication
API key combined with basic or token authentication, depending on version and deployment
Change detection
Polling on change-date fields; outbound calls can be wired through BPM directives, but there is no standard webhook subscription surface
Capabilities
read · write
Rate limits
Subject to the platform's API rate limits and per-tenant throttling on Kinetic cloud deployments

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 Epicor ERP 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 Epicor ERP 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
    Epicor ERP connected
    Smartrecruiters connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Epicor ERP 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 · Epicor ERP ⇄ 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
    Epicor ERP Smartrecruiters
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Epicor ERP 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 510 integrations available for Epicor ERP and Smartrecruiters.

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

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