Skip to content
ERP ⇄ Human resources

Dynamics 365 F&O to Lever integration — real-time, two-way sync

Keep Dynamics 365 F&O and Lever 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 Dynamics 365 F&O and Lever

Sync the workers, org structure, and cost centers that Dynamics 365 F&O 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. Dynamics 365 F&O 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 Vendor Invoices, General Journal Entries, On-hand Inventory, Customers in Dynamics 365 F&O with Notes and Contacts, Opportunities, Postings, Requisitions 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 Dynamics 365 F&O 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 Mirror GL journals and invoice lines into a warehouse for finance reporting without recurring DMF exports.
  • 02 Distribute product and price master data from F&O to downstream channels through a synced database.
  • 03 When an Opportunity is marked hired, write the candidate and its Offer into an HRIS or onboarding system to start employee provisioning.
  • 04 Consolidate Feedback, Interviews, and Notes into a warehouse for interviewer scorecard and time-to-fill reporting.

Common sync patterns

Where Lever runs payroll: labor cost in the books

Pay and compensation data from Lever posts into Dynamics 365 F&O as labor cost, so finance sees workforce spend without re-entering it by hand.

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

When a worker is hired, moved, or offboarded in Lever, the matching employee record in Dynamics 365 F&O is created, updated, or deactivated, so the business system reflects the workforce as it actually is.

New hires ready to transact in Dynamics 365 F&O

A new person set up in Lever becomes an employee record in Dynamics 365 F&O in time to submit expenses, enter time, or approve a purchase, without waiting on manual setup.

What you can sync between Dynamics 365 F&O and Lever

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.

Dynamics 365 F&O objects Lever objects How this pairing syncs
Released Products Sellable product master; read out to commerce channels and CRM catalogs. 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. Released Products is specific to Dynamics 365 F&O and Postings to Lever — each maps to any object or custom field on the other side.
Sales Orders Order transactions; written in from storefronts or CRM and tracked through fulfillment. 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. Sales Orders is specific to Dynamics 365 F&O and Requisitions to Lever — each maps to any object or custom field on the other side.
Purchase Orders Procurement transactions; extracted for spend and supply chain reporting. 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. Purchase Orders is specific to Dynamics 365 F&O and Offers to Lever — each maps to any object or custom field on the other side.
Customer Invoices AR billing documents; status synced back to CRM and customer success tools. Users Lever team members (recruiters, hiring managers) with configurable roles; can be created via POST /users, deactivated, and reactivated through the API. Customer Invoices is specific to Dynamics 365 F&O and Users to Lever — each maps to any object or custom field on the other side.
Vendor Invoices AP documents; synced with invoice automation systems. Stages Pipeline stage definitions that Opportunities move through; read to model funnel state and stage transitions in a database. Vendor Invoices is specific to Dynamics 365 F&O and Stages to Lever — each maps to any object or custom field on the other side.
General Journal Entries GL postings; read-only extracts for consolidated finance reporting. Feedback Interview feedback and scorecard forms attached to Opportunities; created via POST /opportunities/:id/feedback and consolidated into a warehouse for interviewer analytics. General Journal Entries is specific to Dynamics 365 F&O and Feedback to Lever — each maps to any object or custom field on the other side.

How changes propagate between Dynamics 365 F&O and Lever

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.

Dynamics 365 F&O Lever Sub-second propagation

DetectionDynamics 365 F&O pushes changes as they happen — webhook events backed by change data capture. Change data capture via the Dynamics 365 Change Tracking feature, enabled per entity.

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

Lever Dynamics 365 F&O 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 Dynamics 365 F&O through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Dynamics 365 F&O: OData requests are subject to platform throttling; high-volume loads belong in the Data Management Framework.
  • 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.
What ships with Dynamics 365 F&O ⇄ Lever

Connect Dynamics 365 F&O and Lever for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Dynamics 365 F&O–Lever connection.

Real-time

Two-way sync

Changes in Dynamics 365 F&O or Lever instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Dynamics 365 F&O or Lever 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 Dynamics 365 F&O or Lever record.

Observability

Monitoring

Track your Dynamics 365 F&O ⇄ Lever sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Dynamics 365 F&O and Lever.

How the Dynamics 365 F&O and Lever connectors work

Dynamics 365 F&O

Integration surface
OData REST endpoint over data entities, plus the Data Management Framework for batch
Authentication
OAuth via Microsoft sign-in: provide the D365 F&O environment URL, sign in with Microsoft credentials, and grant the Stacksync app consent (admin consent may be required — "Need admin approval for this app")
Change detection
Change data capture via the Dynamics 365 Change Tracking feature, enabled per entity; falls back to periodic full-sync where change tracking is unavailable
Capabilities
read · write · CDC · webhooks
Rate limits
OData requests are subject to platform throttling; high-volume loads belong in the Data Management Framework.
Dynamics 365 F&O setup guide

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
How it works

How to connect Dynamics 365 F&O to Lever — 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 Dynamics 365 F&O and Lever 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
    Dynamics 365 F&O connected
    Lever connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Dynamics 365 F&O and Lever 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 · Dynamics 365 F&O ⇄ Lever
    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
    Dynamics 365 F&O Lever
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Dynamics 365 F&O and Lever 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 414 integrations available for Dynamics 365 F&O and Lever.

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

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