Real-time
Two-way sync
Changes in Sage 300 or Smartrecruiters instantly reflect in both systems. No stale data, no manual imports.
ERP ⇄ Human resources
Sage 300 to Smartrecruiters integration — real-time, two-way sync
Keep Sage 300 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 300 and Smartrecruiters
Sync the workers, org structure, and cost centers that Sage 300 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 300 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 AP Vendors, GL Accounts, Journal Batches, Order Entry Orders in Sage 300 with Interviews, Offers, Users, Approvals 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 300 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 AR customers, invoices, and balances into a CRM for multi-currency account visibility.
- 02 Write web and EDI orders into Order Entry and return order status to the source channel.
- 03 Two-way sync Candidates and Applications with Postgres so recruiting-ops apps read and update hiring status, tags, and custom fields in SQL while recruiters keep working in SmartRecruiters.
- 04 Write enriched or sourced Candidates from external sourcing tools into SmartRecruiters and keep contact fields refreshed as data changes.
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 300 is created, updated, or deactivated, so the business system reflects the workforce as it actually is.
New hires ready to transact in Sage 300
A new person set up in Smartrecruiters becomes an employee record in Sage 300 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 300 roll up to the same structure Smartrecruiters maintains.
What you can sync between Sage 300 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 300 objects | Smartrecruiters objects | How this pairing syncs | |
|---|---|---|---|
| Purchase Orders Procurement documents read for spend visibility and receiving. | Users Company users (recruiters, hiring managers) with roles, access groups, and activation state; read and written via the User Management API. | Purchase Orders is specific to Sage 300 and Users to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Inventory Items Item master with costing and quantities, synced to storefronts and WMS. | Approvals Approval requests for jobs and offers; requests can be created, retrieved as pending, commented on, and approved or rejected via the Approvals API. | Inventory Items is specific to Sage 300 and Approvals to Smartrecruiters — each maps to any object or custom field on the other side. | |
| AR Invoices and Receipts Billing and payment records replicated for cash and revenue reporting. | 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. | AR Invoices and Receipts is specific to Sage 300 and Candidates to Smartrecruiters — each maps to any object or custom field on the other side. | |
| AR Customers Receivables customer master synced to CRMs and billing 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. | AR Customers is specific to Sage 300 and Applications to Smartrecruiters — each maps to any object or custom field on the other side. | |
| AP Vendors Payables vendor master synced with procurement and payment systems. | 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. | AP Vendors is specific to Sage 300 and Jobs to Smartrecruiters — each maps to any object or custom field on the other side. | |
| GL Accounts Chart of accounts read for transaction mapping across integrations. | 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). | GL Accounts is specific to Sage 300 and Job Postings to Smartrecruiters — each maps to any object or custom field on the other side. |
How changes propagate between Sage 300 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 300 Smartrecruiters Interval-based propagation
DetectionStacksync polls Sage 300 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 300 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 300 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 300 ⇄ Smartrecruiters
Connect Sage 300 and Smartrecruiters for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Sage 300–Smartrecruiters connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Sage 300 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 300 or Smartrecruiters record.
Observability
Monitoring
Track your Sage 300 ⇄ 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 300 and Smartrecruiters.
How the Sage 300 and Smartrecruiters connectors work
Sage 300
- Integration surface
- Sage 300 Web API (REST) on newer releases; .NET/COM SDK and direct SQL Server access on-prem
- Authentication
- Sage 300 user credentials (Basic auth on the Web API); database credentials for direct SQL reads
- Change detection
- Scheduled polling; batch-oriented modules with no webhook 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 300 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 300 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 300
connected
Smartrecruiters
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Sage 300 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 300 ⇄ 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 300 SmartrecruitersCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Sage 300 and Smartrecruiters integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Sage 300 and Smartrecruiters: authenticate both systems, choose the objects to sync (such as Sage 300's Purchase Orders and Inventory Items), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Sage 300 and Smartrecruiters connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Sage 300–Smartrecruiters integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Sage 300 and Smartrecruiters. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Sage 300: Scheduled polling; batch-oriented modules with no webhook surface. On Smartrecruiters: 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. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Sage 300 side: AP Vendors, GL Accounts, Journal Batches, Order Entry Orders, plus custom fields where Sage 300 exposes them. On the Smartrecruiters side: Interviews, Offers, Users, Approvals. Stacksync auto-detects both schemas and converts types between the two systems.
-
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.
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 509 integrations available for Sage 300 and Smartrecruiters.
Popular · 8 of 509
-
Sage 300 ⇄ Jobvite -
Sage 300 ⇄ Lever -
Sage 300 ⇄ Namely -
Sage 300 ⇄ Paylocity -
Smartrecruiters ⇄ SAP S/4HANA -
Smartrecruiters ⇄ Odoo -
Smartrecruiters ⇄ Blue Yonder WMS -
Smartrecruiters ⇄ Brightpearl
No integrations match .
