Real-time
Two-way sync
Changes in Sage 100 or Smartrecruiters instantly reflect in both systems. No stale data, no manual imports.
ERP ⇄ Human resources
Sage 100 to Smartrecruiters integration — real-time, two-way sync
Keep Sage 100 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 Sage 100 and Smartrecruiters
Sync the workers, org structure, and cost centers that Sage 100 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. Sage 100 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 Journal Entries, Customers, Vendors, Inventory Items in Sage 100 with Job Postings, Interviews, Offers, Users 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 Sage 100 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 Replicate GL and sales history to a warehouse or Postgres database for reporting off the on-premise system.
- 02 Sync customers, invoices, and payment status into a CRM so sales sees AR standing without opening the ERP.
- 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
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 Sage 100 is created, updated, or deactivated, so the business system reflects the workforce as it actually is.
New hires ready to transact in Sage 100
A new person set up in Smartrecruiters becomes an employee record in Sage 100 in time to submit expenses, enter time, or approve a purchase, without waiting on manual setup.
One org structure
Departments, cost centers, and locations that both systems reference stay in agreement, so labor cost, approvals, and reporting in Sage 100 roll up to the same structure Smartrecruiters maintains.
What you can sync between Sage 100 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.
| Sage 100 objects | Smartrecruiters objects | How this pairing syncs | |
|---|---|---|---|
| Customers AR customer master records synced to CRMs for account and credit visibility. | 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. | Customers is specific to Sage 100 and Candidates to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Vendors AP vendor master records synced with procurement and payment tools. | 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. | Vendors is specific to Sage 100 and Applications to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Inventory Items Item master with pricing and quantities, synced to e-commerce catalogs. | 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. | Inventory Items is specific to Sage 100 and Jobs to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Sales Orders Order headers and lines, the usual write target for web and EDI orders. | 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 Orders is specific to Sage 100 and Job Postings to Smartrecruiters — each maps to any object or custom field on the other side. | |
| AR Invoices Billing documents synced outward for payment status and revenue reporting. | Interviews Interview types, timeslots, templates, and scheduled interviews with interviewers and times; created, updated, and read for scheduling and interviewer-load analytics. | AR Invoices is specific to Sage 100 and Interviews to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Purchase Orders Procurement documents read for spend and receiving workflows. | 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). | Purchase Orders is specific to Sage 100 and Offers to Smartrecruiters — each maps to any object or custom field on the other side. |
How changes propagate between Sage 100 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.
Sage 100 Smartrecruiters Interval-based propagation
DetectionStacksync polls Sage 100 for changes on an incremental schedule, reading only records changed since the previous pass. Scheduled polling.
DeliveryEach detected change is written to Smartrecruiters through its API, with automatic retries and rate-limit backoff.
Smartrecruiters Sage 100 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 applied to Sage 100 as a row-level write, with types converted between the two schemas.
Rate-limit considerations
- 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 Sage 100 ⇄ Smartrecruiters
Connect Sage 100 and Smartrecruiters for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Sage 100–Smartrecruiters connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Sage 100 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 Sage 100 or Smartrecruiters record.
Observability
Monitoring
Track your Sage 100 ⇄ Smartrecruiters sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Sage 100 and Smartrecruiters.
How the Sage 100 and Smartrecruiters connectors work
Sage 100
- Integration surface
- ODBC (ProvideX driver) for reads; Business Object Interface (BOI) or Sage-provided web services for writes
- Authentication
- Sage 100 company and user credentials; ODBC DSN credentials for direct reads
- Change detection
- Scheduled polling; no webhooks or change log on the integration surface
- Capabilities
- read · write
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.
How it works
How to connect Sage 100 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.
- 01
Connect your apps
Authenticate Sage 100 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.
Sage 100
connected
Smartrecruiters
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Sage 100 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.
objects · Sage 100 ⇄ SmartrecruitersCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Sage 100 SmartrecruitersCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Sage 100 and Smartrecruiters integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Sage 100 and Smartrecruiters: authenticate both systems, choose the objects to sync (such as Sage 100's Customers and Vendors), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
-
Common patterns for Sage 100 and Smartrecruiters: Where Smartrecruiters is the worker system of record: one employee master; New hires ready to transact in Sage 100; One org structure. When a worker is hired, moved, or offboarded in Smartrecruiters, the matching employee record in Sage 100 is created, updated, or deactivated, so the business system reflects the workforce as it actually is.
-
Sage 100: ODBC (ProvideX driver) for reads; Business Object Interface (BOI) or Sage-provided web services for writes. Authentication: Sage 100 company and user credentials; ODBC DSN credentials for direct reads. Smartrecruiters: 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. Stacksync manages authentication, retries, and rate limits on both sides.
-
Sage 100: Writes should go through the Business Object Interface rather than direct file access, so module validation and GL postings are enforced. Smartrecruiters: Every response returns rate-limit metadata via X-RateLimit-Limit/Remaining and X-RateLimit-Concurrent-Limit/Remaining headers. Stacksync's field mapping accounts for these differences between Sage 100 and Smartrecruiters without custom code.
-
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Sage 100 and Smartrecruiters records are not retained after a sync operation.
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 507 integrations available for Sage 100 and Smartrecruiters.
Popular · 7 of 507
-
Sage 100 ⇄ D2l Brightspace -
Sage 100 ⇄ Oracle Fusion Cloud HCM -
Sage 100 ⇄ Ukg Pro -
Sage 100 ⇄ Greenhouse -
Smartrecruiters ⇄ Fishbowl Manufacturing -
Smartrecruiters ⇄ Infor CloudSuite - Smartrecruiters ⇄ Infor LN
No integrations match .
