Skip to content
ERP ⇄ Accounting and finance

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

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

Keep Rillet and Microsoft Dynamics NAV agreeing on customers, invoices, and balances, whether they split the finance workload or one is replacing the other.

A dedicated finance tool and an ERP end up side by side for practical reasons: a subsidiary runs lighter software than headquarters, billing runs in a specialist system while the enterprise system holds the wider view, or the company is mid-migration and both are live. Whatever the split, the two systems describe overlapping customers and transactions, and that overlap drifts without a live connection.

Stacksync syncs Reimbursement, Custom Field, Account, Customer in Rillet with Item Ledger Entries, Dimensions, Companies, Customers in Microsoft Dynamics NAV in real time and in both directions. You decide which system wins on which field, and every change made in one is reflected in the other within seconds instead of at the next batch run.

Common use cases

  • Mirror journal entries and contract revenue data into a warehouse for board and ARR reporting.
  • Push billing events from a product or usage-metering system into Rillet for revenue recognition.
  • Keep inventory availability current in storefronts and customer portals.
  • Run parallel sync during a NAV-to-Business Central migration so both systems stay usable.

Migration without a hard cutover

When one system is replacing the other, run both in parallel with records matching until the switch is complete.

One customer and vendor master

Where both systems keep records of the same organizations, corrections made in either propagate to the other.

Subsidiary to headquarters

Where Rillet serves a business unit and Microsoft Dynamics NAV is the group system, transactions and customer records roll up continuously, so consolidation starts from live data.

What you can sync between Microsoft Dynamics NAV and Rillet

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 Rillet objects
Companies Per-company data partitions that scope every sync. Journal Entry Synced with incremental and full sync per the Stacksync docs.
Customers Customer cards synced with CRMs so sales sees ERP balances and terms. Invoice Payment Synced with incremental and full sync per the Stacksync docs.
Vendors Vendor cards aligned with procurement and AP tools. Charge Synced with incremental and full sync per the Stacksync docs.
Items Item cards and availability mirrored to ecommerce and planning systems. Reimbursement Synced with incremental and full sync per the Stacksync docs.
Sales Orders & Invoices Sales documents created from external orders and read back for posting status. Custom Field Synced with incremental and full sync per the Stacksync docs.
Purchase Orders Purchasing documents reconciled with receiving and vendor systems. Account Synced with incremental and full sync per the Stacksync docs.
What ships with Microsoft Dynamics NAV ⇄ Rillet

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

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

Real-time

Two-way sync

Changes in Microsoft Dynamics NAV or Rillet 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 Rillet 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 Rillet record.

Observability

Monitoring

Track your Microsoft Dynamics NAV ⇄ Rillet 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 Rillet.

How the Microsoft Dynamics NAV and Rillet 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

Rillet

Integration surface
REST API (OpenAPI-specified, with production and sandbox environments)
Authentication
API key generated in Rillet (Organization Setting -> API Access); uncheck Read Only for bidirectional sync, check Read Only for one-way sync
Change detection
Near real-time updates via change tracking; incremental sync per object, with delete detection (some objects checked every 1h or 4h)
Capabilities
read · write · CDC · webhooks
Rate limits
Subject to the platform's API rate limits.
Rillet setup guide
How it works

How to connect Microsoft Dynamics NAV to Rillet — 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 Rillet 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
    Rillet connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Microsoft Dynamics NAV and Rillet 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 ⇄ Rillet
    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 Rillet
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Microsoft Dynamics NAV and Rillet integration FAQ

SECURITY

Security teams love 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
CSA STAR
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 386 integrations available for Microsoft Dynamics NAV and Rillet.

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

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