Two-way sync
Changes in Dynamics 365 F&O or Lever instantly reflect in both systems. No stale data, no manual imports.
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.
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.
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.
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.
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.
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. |
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.
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.
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.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Dynamics 365 F&O–Lever connection.
Changes in Dynamics 365 F&O or Lever instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Dynamics 365 F&O or Lever data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Dynamics 365 F&O or Lever record.
Track your Dynamics 365 F&O ⇄ Lever sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Dynamics 365 F&O and Lever.
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.
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.
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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Dynamics 365 F&O and Lever: authenticate both systems, choose the objects to sync (such as Dynamics 365 F&O's Released Products and Sales Orders), 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 Dynamics 365 F&O and Lever connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Dynamics 365 F&O–Lever integration in-house.
Yes — Stacksync ships production-grade connectors for both Dynamics 365 F&O and Lever. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on Dynamics 365 F&O: Change data capture via the Dynamics 365 Change Tracking feature, enabled per entity; falls back to periodic full-sync where change tracking is unavailable. On Lever: 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. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Dynamics 365 F&O side: Vendor Invoices, General Journal Entries, On-hand Inventory, Customers, plus custom fields where Dynamics 365 F&O exposes them. On the Lever side: Notes and Contacts, Opportunities, Postings, Requisitions. 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.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 414 integrations available for Dynamics 365 F&O and Lever.