Skip to content
Human resources ⇄ ERP

Hibob to QAD ERP integration — real-time, two-way sync

Keep Hibob and QAD ERP 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 Hibob and QAD ERP

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

Hibob 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. QAD 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 Items, Customers, Suppliers, Sales orders in QAD ERP with Time off, Lifecycle, Documents, Named lists in Hibob 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 QAD 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 items, customers, and orders between QAD and a CRM so sales teams work outside ERP screens.
  • 02 Replicate inventory and work-order data into a warehouse for supply chain analytics across plants.
  • 03 Two-way sync People (employee) profiles and Work records with a Postgres database so internal apps and directories read profiles in SQL while HR corrections flow back into Bob.
  • 04 Auto-provision or deprovision accounts in an IdP, ticketing tool, or app database when Bob Lifecycle events fire employee joined or terminated.

Common sync patterns

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

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

New hires ready to transact in QAD ERP

A new person set up in Hibob becomes an employee record in QAD ERP 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 QAD ERP roll up to the same structure Hibob maintains.

What you can sync between Hibob and QAD ERP

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.

Hibob objects QAD ERP objects How this pairing syncs
Lifecycle Hire, termination, and leave status changes at /people/{id}/lifecycle; read-only and the source of lifecycle webhook events. Inventory balances Stock levels by site and location, synced for multi-plant visibility Lifecycle is specific to Hibob and Inventory balances to QAD ERP — each maps to any object or custom field on the other side.
Documents Employee documents accessed under the Docs API; gated behind the Documents permission granted per service user. General ledger transactions Financial postings exported for consolidated reporting Documents is specific to Hibob and General ledger transactions to QAD ERP — each maps to any object or custom field on the other side.
Named lists Dropdown option lists such as departments and sites used to resolve field values when mapping People records during sync. Items Item master records shared with CRM, e-commerce, and planning systems Named lists is specific to Hibob and Items to QAD ERP — each maps to any object or custom field on the other side.
People (Employees) Core employee records with out-of-the-box and custom fields; read via POST /people/search, created and updated through the /people endpoints. Customers Account records kept consistent with the sales team's CRM People (Employees) is specific to Hibob and Customers to QAD ERP — each maps to any object or custom field on the other side.
Employment Historical table of job terms, contract, and working pattern under /people/{id}/employment; full CRUD, entries keyed by effectiveDate. Suppliers Vendor master data aligned with procurement and AP automation tools Employment is specific to Hibob and Suppliers to QAD ERP — each maps to any object or custom field on the other side.
Work Reporting line, department, site, and title under /people/{id}/work; drives the org chart and is synced two-way to directories. Sales orders Demand records written in from EDI or e-commerce and read out for status Work is specific to Hibob and Sales orders to QAD ERP — each maps to any object or custom field on the other side.

How changes propagate between Hibob and QAD ERP

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.

Hibob QAD ERP Sub-second propagation

DetectionHibob notifies Stacksync of record changes through webhook events. Webhooks fire for employee created/updated/deleted, table-entry created/updated, time off, and lifecycle events.

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

QAD ERP Hibob Interval-based propagation

DetectionStacksync polls QAD ERP for changes on an incremental schedule, reading only records changed since the previous pass. Polling on the API surface.

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

Rate-limit considerations

  • Hibob: Rate limits are enforced per service user; violations return HTTP 429 with X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset response headers. The docs list POST /people/search at 50 requests per minute, and bulk /people/search is preferred over per-record reads.
  • QAD ERP: Subject to instance capacity and the platform's API limits.
What ships with Hibob ⇄ QAD ERP

Connect Hibob and QAD ERP for flexible, real-time data sync.

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Hibob and QAD ERP.

How the Hibob and QAD ERP connectors work

Hibob

Integration surface
REST API (the Bob API)
Authentication
Service User credentials over HTTP Basic auth (Base64-encoded serviceUserId:serviceUserToken); permissions granted per data category (People, Payroll, Documents) in Bob admin
Change detection
Webhooks fire for employee created/updated/deleted, table-entry created/updated, time off, and lifecycle events; the employee.updated payload flags which fields changed and Bob recommends an API call for the full record. There is no CDC stream, and deleting a table entry fires no webhook (Bob has no table-entry deletion event).
Capabilities
read · write · webhooks
Rate limits
Rate limits are enforced per service user; violations return HTTP 429 with X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset response headers. The docs list POST /people/search at 50 requests per minute, and bulk /people/search is preferred over per-record reads.
Hibob setup guide

QAD ERP

Integration surface
REST APIs plus the QXtend XML integration framework
Authentication
instance credentials; specifics depend on the deployment and version
Change detection
polling on the API surface; document-based event exchange available through QXtend in supported configurations
Capabilities
read · write
Rate limits
subject to instance capacity and the platform's API limits
How it works

How to connect Hibob to QAD ERP — 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 Hibob and QAD ERP 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
    Hibob connected
    QAD ERP connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Hibob and QAD ERP 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 · Hibob ⇄ QAD ERP
    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
    Hibob QAD ERP
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Hibob and QAD ERP 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.

Learn more about security
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:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 505 integrations available for Hibob and QAD ERP.

Popular · 7 of 505
All Hibob integrations All QAD ERP integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

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

Book a demo Tour the platform on your own