Skip to content
ERP ⇄ Human resources

Microsoft Dynamics NAV to Paylocity integration — real-time, two-way sync

Keep Microsoft Dynamics NAV 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 Microsoft Dynamics NAV and Paylocity

Sync the workers, org structure, and cost centers that Microsoft Dynamics NAV 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. Microsoft Dynamics NAV 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 & Invoices, Purchase Orders, G/L Entries, Item Ledger Entries in Microsoft Dynamics NAV with Deductions (Pay Setup), Earnings (Pay Setup), Local and State Taxes, Direct Deposit 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 Microsoft Dynamics NAV 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 G/L and ledger entries into a warehouse for consolidated finance reporting.
  • 02 Keep inventory availability current in storefronts and customer portals.
  • 03 Push hired candidates from an ATS into Paylocity via the Onboarding endpoint, then read Onboarding Status to confirm the record before the first payroll run.
  • 04 Upsert recurring Deductions and Earnings on employee records when benefits or 401(k) elections change in a benefits admin system, without re-keying payroll setup.

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 Microsoft Dynamics NAV roll up to the same structure Paylocity maintains.

Reporting lines drive approvals

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

Where Paylocity runs payroll: labor cost in the books

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

What you can sync between Microsoft Dynamics NAV 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.

Microsoft Dynamics NAV objects Paylocity objects How this pairing syncs
Items Item cards and availability mirrored to ecommerce and planning systems. 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. Items is specific to Microsoft Dynamics NAV and Direct Deposit to Paylocity — each maps to any object or custom field on the other side.
Sales Orders & Invoices Sales documents created from external orders and read back for posting status. 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. Sales Orders & Invoices is specific to Microsoft Dynamics NAV and Pay Statements to Paylocity — each maps to any object or custom field on the other side.
Purchase Orders Purchasing documents reconciled with receiving and vendor systems. Company Codes Read-only reference codes and descriptions (cost centers, departments, positions) used to validate field mappings on employee writes. Purchase Orders is specific to Microsoft Dynamics NAV and Company Codes to Paylocity — each maps to any object or custom field on the other side.
G/L Entries Posted ledger entries replicated to warehouses for finance reporting. Custom Fields Read-only company-specific custom fields returned by category, used to enrich the employee record downstream. G/L Entries is specific to Microsoft Dynamics NAV and Custom Fields to Paylocity — each maps to any object or custom field on the other side.
Item Ledger Entries Inventory movement history read for stock and costing analytics. 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. Item Ledger Entries is specific to Microsoft Dynamics NAV and Employees to Paylocity — each maps to any object or custom field on the other side.
Dimensions Analytical codes carried on documents and entries for reporting splits. 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. Dimensions is specific to Microsoft Dynamics NAV and Onboarding to Paylocity — each maps to any object or custom field on the other side.

How changes propagate between Microsoft Dynamics NAV 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.

Microsoft Dynamics NAV Paylocity Sub-second propagation

DetectionChanges in Microsoft Dynamics NAV are captured at the source via change data capture — no polling loop against its API. Polling on modified/timestamp fields, or SQL Server change tracking/CDC on on-premises databases.

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

Paylocity Microsoft Dynamics NAV 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 applied to Microsoft Dynamics NAV as a row-level write, with types converted between the two schemas.

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 Microsoft Dynamics NAV ⇄ Paylocity

Connect Microsoft Dynamics NAV and Paylocity for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Microsoft Dynamics NAV–Paylocity connection.

Real-time

Two-way sync

Changes in Microsoft Dynamics NAV or Paylocity instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Microsoft Dynamics NAV 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 Microsoft Dynamics NAV or Paylocity record.

Observability

Monitoring

Track your Microsoft Dynamics NAV ⇄ Paylocity sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Microsoft Dynamics NAV and Paylocity.

How the Microsoft Dynamics NAV and Paylocity connectors work

Microsoft Dynamics NAV

Integration surface
SOAP and OData web services published from NAV pages and codeunits; direct SQL Server access on-premises
Authentication
Windows authentication or NavUserPassword credentials
Change detection
Polling on modified/timestamp fields, or SQL Server change tracking/CDC on on-premises databases; no native webhooks
Capabilities
read · write · CDC

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 Microsoft Dynamics NAV 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 Microsoft Dynamics NAV 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
    Microsoft Dynamics NAV connected
    Paylocity connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Microsoft Dynamics NAV 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 · Microsoft Dynamics NAV ⇄ 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
    Microsoft Dynamics NAV Paylocity
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Microsoft Dynamics NAV 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.

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 504 integrations available for Microsoft Dynamics NAV and Paylocity.

Popular · 6 of 504
All Microsoft Dynamics NAV integrations All Paylocity 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