Skip to content
Human resources ⇄ ERP

Lever to SAP S/4HANA integration — real-time, two-way sync

Keep Lever and SAP S/4HANA 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 Lever and SAP S/4HANA

Sync the workers, org structure, and cost centers that SAP S/4HANA and Lever share in real time, so the people Lever manages stay current in the system that runs finance and operations.

Lever 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. SAP S/4HANA 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 Deliveries, Journal Entries, Customer / Supplier Roles, Production Orders in SAP S/4HANA with Users, Stages, Feedback, Interviews in Lever 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 SAP S/4HANA 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 Surface invoice and payment status from S/4HANA inside the CRM so account teams see open balances.
  • 02 Replicate material master and pricing data to e-commerce and quoting tools.
  • 03 Consolidate Feedback, Interviews, and Notes into a warehouse for interviewer scorecard and time-to-fill reporting.
  • 04 Write enriched Sources, Tags, and Contact data back onto Opportunities from an outbound sourcing pipeline.

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 SAP S/4HANA roll up to the same structure Lever maintains.

Reporting lines drive approvals

Manager and reporting-hierarchy changes in Lever keep expense and purchase approval chains in SAP S/4HANA pointed at the right people.

Where Lever runs payroll: labor cost in the books

Pay and compensation data from Lever posts into SAP S/4HANA as labor cost, so finance sees workforce spend without re-entering it by hand.

What you can sync between Lever and SAP S/4HANA

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.

Lever objects SAP S/4HANA objects How this pairing syncs
Postings Job posting records with categories, apply URLs, workplace type, and requisition codes. Can be created via POST /postings and read into a warehouse for open-role reporting. Deliveries Outbound delivery status synced to customer-facing systems for order tracking. Postings is specific to Lever and Deliveries to SAP S/4HANA — each maps to any object or custom field on the other side.
Requisitions Headcount/requisition records with custom requisition fields, tied to Postings; read via GET /requisitions and synced to an HRIS to reconcile approved headcount against open roles. Journal Entries Financial postings read into warehouses and consolidation tools for reporting. Requisitions is specific to Lever and Journal Entries to SAP S/4HANA — each maps to any object or custom field on the other side.
Offers Offer records attached to an Opportunity with status and offer-form fields; exposed read-only through GET /opportunities/:id/offers, so they sync outbound to an HRIS or onboarding system when a candidate reaches the offer stage. Customer / Supplier Roles Role-specific views of Business Partners mapped to CRM account types. Offers is specific to Lever and Customer / Supplier Roles to SAP S/4HANA — each maps to any object or custom field on the other side.
Users Lever team members (recruiters, hiring managers) with configurable roles; can be created via POST /users, deactivated, and reactivated through the API. Production Orders Manufacturing order status surfaced in planning and operations tools. Users is specific to Lever and Production Orders to SAP S/4HANA — each maps to any object or custom field on the other side.
Stages Pipeline stage definitions that Opportunities move through; read to model funnel state and stage transitions in a database. Business Partners Unified customer and supplier master records, the anchor entity for CRM-to-ERP account syncs. Stages is specific to Lever and Business Partners to SAP S/4HANA — each maps to any object or custom field on the other side.
Feedback Interview feedback and scorecard forms attached to Opportunities; created via POST /opportunities/:id/feedback and consolidated into a warehouse for interviewer analytics. Sales Orders Order headers and line items synced to CRMs and fulfillment systems as they are created or amended. Feedback is specific to Lever and Sales Orders to SAP S/4HANA — each maps to any object or custom field on the other side.

How changes propagate between Lever and SAP S/4HANA

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.

Lever SAP S/4HANA Sub-second propagation

DetectionLever notifies Stacksync of record changes through webhook events. Webhooks for candidate and application lifecycle events (applicationCreated, candidateStageChange, candidateArchiveStateChange, candidateHired,.

DeliveryEach detected change is written to SAP S/4HANA through its API, with automatic retries and rate-limit backoff.

SAP S/4HANA Lever Interval-based propagation

DetectionStacksync polls SAP S/4HANA for changes on an incremental schedule, reading only records changed since the previous pass. Polling on change timestamps exposed by the OData services.

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

Rate-limit considerations

  • Lever: 10 requests/second per API key with a token-bucket burst to ~20/s; POSTs that create candidates/applications are throttled to roughly 2/second. Sustained overage returns 429 with Retry-After. List endpoints are cursor-paginated at up to 100 records per page.
  • SAP S/4HANA: Subject to the platform's API rate limits, which vary by edition and communication arrangement.
What ships with Lever ⇄ SAP S/4HANA

Connect Lever and SAP S/4HANA for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Lever–SAP S/4HANA connection.

Real-time

Two-way sync

Changes in Lever or SAP S/4HANA instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Lever or SAP S/4HANA 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 Lever or SAP S/4HANA record.

Observability

Monitoring

Track your Lever ⇄ SAP S/4HANA sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Lever and SAP S/4HANA.

How the Lever and SAP S/4HANA connectors work

Lever

Integration surface
REST Data API (api.lever.co/v1)
Authentication
API key over HTTP Basic auth (key as username, blank password) for internal integrations, or OAuth 2.0 with 1-hour access tokens for partner integrations (auth.lever.co)
Change detection
Webhooks for candidate and application lifecycle events (applicationCreated, candidateStageChange, candidateArchiveStateChange, candidateHired, interview created/updated/deleted), plus incremental polling via created_at and updated_at range filters on Opportunities
Capabilities
read · write · webhooks
Rate limits
10 requests/second per API key with a token-bucket burst to ~20/s; POSTs that create candidates/applications are throttled to roughly 2/second. Sustained overage returns 429 with Retry-After. List endpoints are cursor-paginated at up to 100 records per page.
Lever setup guide

SAP S/4HANA

Integration surface
OData REST APIs (v2/v4), with SOAP, BAPI/RFC, and IDoc interfaces on on-premise editions
Authentication
OAuth 2.0 with communication arrangements on cloud editions; basic auth or certificate-based on-premise
Change detection
Polling on change timestamps exposed by the OData services; business events can be emitted through SAP's event infrastructure on cloud editions
Capabilities
read · write
Rate limits
Subject to the platform's API rate limits, which vary by edition and communication arrangement
How it works

How to connect Lever to SAP S/4HANA — 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 Lever and SAP S/4HANA 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
    Lever connected
    SAP S/4HANA connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Lever and SAP S/4HANA 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 · Lever ⇄ SAP S/4HANA
    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
    Lever SAP S/4HANA
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Lever and SAP S/4HANA 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 509 integrations available for Lever and SAP S/4HANA.

Popular · 8 of 509
All Lever integrations All SAP S/4HANA 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