Skip to content
ERP ⇄ Human resources

Dynamics 365 Business Central to Paylocity integration — real-time, two-way sync

Keep Dynamics 365 Business Central and Paylocity 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 Business Central and Paylocity

Sync the workers, org structure, and cost centers that Dynamics 365 Business Central and Paylocity share in real time, so the people Paylocity manages stay current in the system that runs finance and operations.

Paylocity 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 Business Central 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 Sales Orders, Sales Invoices, Purchase Orders, General Ledger Entries in Dynamics 365 Business Central with Custom Fields, Employees, Onboarding, Deductions (Pay Setup) in Paylocity 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 Business Central 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 Replicate GL entries and dimensions into a SQL database for financial reporting without giving analysts ERP logins.
  • 02 Sync vendor and purchase order data with procurement or AP automation tools.
  • 03 Read Pay Statements and Direct Deposit allocations into a Postgres or warehouse database for labor-cost, GL, and headcount reporting in SQL.
  • 04 React to the Employee Change webhook to pull the updated Employee record and propagate title, location, or manager changes to downstream apps within minutes.

Common sync patterns

Reporting lines drive approvals

Manager and reporting-hierarchy changes in Paylocity keep expense and purchase approval chains in Dynamics 365 Business Central pointed at the right people.

Where Paylocity runs payroll: labor cost in the books

Pay and compensation data from Paylocity posts into Dynamics 365 Business Central as labor cost, so finance sees workforce spend without re-entering it by hand.

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

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

What you can sync between Dynamics 365 Business Central and Paylocity

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 Business Central objects Paylocity objects How this pairing syncs
Payments Customer and vendor payment records reconciled against invoices. Direct Deposit Read-only: Get All Direct Deposit and Get Employee Bank Accounts return main and additional allocations. Bank details cannot be written through the API. Payments is specific to Dynamics 365 Business Central and Direct Deposit to Paylocity — each maps to any object or custom field on the other side.
Customers Core master data synced with CRMs so sales and finance share one customer list. Pay Statements Read-only detailed payroll statement data — earnings, deductions, taxes, and direct deposit allocations by year, check date, or date range. Pulled for reporting, never written. Customers is specific to Dynamics 365 Business Central and Pay Statements to Paylocity — each maps to any object or custom field on the other side.
Vendors Supplier master data synced with procurement and AP automation tools. Company Codes Read-only reference codes and descriptions (cost centers, departments, positions) used to validate field mappings on employee writes. Vendors is specific to Dynamics 365 Business Central and Company Codes to Paylocity — each maps to any object or custom field on the other side.
Items Product and inventory records aligned with e-commerce and warehouse systems. Custom Fields Read-only company-specific custom fields returned by category, used to enrich the employee record downstream. Items is specific to Dynamics 365 Business Central and Custom Fields to Paylocity — each maps to any object or custom field on the other side.
Sales Orders Order headers and lines created from external channels and read back for fulfillment status. Employees Core HR record keyed by companyId + employeeId; two-way via Create New Employee (POST) and Update Employee (PATCH), plus Get Employee / Get All Employees for reads. Sales Orders is specific to Dynamics 365 Business Central and Employees to Paylocity — each maps to any object or custom field on the other side.
Sales Invoices Billing documents synced to CRMs and payment platforms. Onboarding Create Employee Onboarding pushes new-hire data into Paylocity's onboarding workflow; Get Onboarding Status reads back partner onboarding progress. Write-in for hires from an ATS. Sales Invoices is specific to Dynamics 365 Business Central and Onboarding to Paylocity — each maps to any object or custom field on the other side.

How changes propagate between Dynamics 365 Business Central and Paylocity

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 Business Central Paylocity Sub-second propagation

DetectionDynamics 365 Business Central notifies Stacksync of record changes through webhook events. API webhooks (change notifications on subscribed entities) plus polling on lastModifiedDateTime.

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

Paylocity Dynamics 365 Business Central Sub-second propagation

DetectionPaylocity notifies Stacksync of record changes through webhook events. Webhooks — Paylocity POSTs Employee New Hire, Employee Change, Termination, Payroll Processed, and Time Off Approval events to a callback URL.

DeliveryEach detected change is written to Dynamics 365 Business Central through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Paylocity: 25 requests per second (1,500 per minute); exceeding it returns HTTP 429. Every path is scoped to a Paylocity-assigned companyId (a company code, not a UUID).
What ships with Dynamics 365 Business Central ⇄ Paylocity

Connect Dynamics 365 Business Central and Paylocity for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Dynamics 365 Business Central–Paylocity connection.

Real-time

Two-way sync

Changes in Dynamics 365 Business Central or Paylocity instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Dynamics 365 Business Central or Paylocity 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 Business Central or Paylocity record.

Observability

Monitoring

Track your Dynamics 365 Business Central ⇄ Paylocity 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 Business Central and Paylocity.

How the Dynamics 365 Business Central and Paylocity connectors work

Dynamics 365 Business Central

Integration surface
REST API built on OData v4 (standard API v2.0), extensible with custom API pages in AL
Authentication
OAuth 2.0 via Microsoft Entra ID
Change detection
API webhooks (change notifications on subscribed entities) plus polling on lastModifiedDateTime
Capabilities
read · write · webhooks

Paylocity

Integration surface
REST API (v1 and v2), JSON payloads
Authentication
OAuth 2.0 client credentials via the Paylocity Identity Provider (/IdentityServer/connect/token) with the WebLinkAPI scope; access tokens expire after one hour and API access must be enabled by Paylocity for the company
Change detection
Webhooks — Paylocity POSTs Employee New Hire, Employee Change, Termination, Payroll Processed, and Time Off Approval events to a callback URL; payloads carry only companyId and employeeId, so the receiver calls the relevant API to fetch changed values. Scheduled polling is used for objects without webhooks.
Capabilities
read · write · webhooks
Rate limits
25 requests per second (1,500 per minute); exceeding it returns HTTP 429. Every path is scoped to a Paylocity-assigned companyId (a company code, not a UUID).
How it works

How to connect Dynamics 365 Business Central to Paylocity — 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 Business Central and Paylocity 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 Business Central connected
    Paylocity connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Dynamics 365 Business Central and Paylocity 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 Business Central ⇄ Paylocity
    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 Business Central Paylocity
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Dynamics 365 Business Central and Paylocity 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 509 integrations available for Dynamics 365 Business Central and Paylocity.

Popular · 8 of 509
Coworkers laughing in front of a laptop in a casual office setting

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