Skip to content
Accounting and finance ⇄ ERP

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

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

Keep Bill 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 Invoices, Customers, Payments, Chart of Accounts in Bill with Sales Orders & Invoices, Purchase Orders, G/L Entries, Item Ledger Entries 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

  • 01 Sync Customers and Invoices from BILL AR into a CRM or ERP so sales and finance see billing and payment status on the account.
  • 02 Write Vendors created during ERP onboarding into BILL so new payees are ready to pay without manual re-entry.
  • 03 Sync customers, items, and orders between NAV and a CRM in both directions.
  • 04 Push ecommerce orders into NAV sales orders through published page services.

Common sync patterns

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

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.

Bill objects Microsoft Dynamics NAV objects How this pairing syncs
Vendors Payee master records; synced two-way with vendor/supplier tables in an ERP or accounting system so new payees don't have to be re-keyed. Vendors Vendor cards aligned with procurement and AP tools. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Customers AR customer master records; mapped to customer/account records in a CRM or ERP so finance and sales share one view. Customers Customer cards synced with CRMs so sales sees ERP balances and terms. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. Custom fields on either side are included in the mapping.
Chart of Accounts GL accounts used to code bills and invoices; typically mastered in the accounting system and written into BILL for consistent coding. Sales Orders & Invoices Sales documents created from external orders and read back for posting status. Chart of Accounts is specific to Bill and Sales Orders & Invoices to Microsoft Dynamics NAV — each maps to any object or custom field on the other side.
Bank Accounts Funding and deposit accounts; read to reconcile payments and posted transactions against the ledger. Purchase Orders Purchasing documents reconciled with receiving and vendor systems. Bank Accounts is specific to Bill and Purchase Orders to Microsoft Dynamics NAV — each maps to any object or custom field on the other side.
Vendor Credits and Credit Memos AP and AR adjustments applied against bills and invoices; synced so balances stay accurate on both sides. G/L Entries Posted ledger entries replicated to warehouses for finance reporting. Vendor Credits and Credit Memos is specific to Bill and G/L Entries to Microsoft Dynamics NAV — each maps to any object or custom field on the other side.
Bills Accounts-payable amounts owed to vendors, with bill line items; read and created via /v3/bills and pulled incrementally by filtering on createdTime/updatedTime. Item Ledger Entries Inventory movement history read for stock and costing analytics. Bills is specific to Bill and Item Ledger Entries to Microsoft Dynamics NAV — each maps to any object or custom field on the other side.

How changes propagate between Bill and Microsoft Dynamics NAV

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.

Bill Microsoft Dynamics NAV Sub-second propagation

DetectionBill notifies Stacksync of record changes through webhook events. Webhook event subscriptions (POST /v3/subscriptions) for bills, vendors, payments, invoices, and bank accounts, with polling on.

DeliveryEach detected change is applied to Microsoft Dynamics NAV as a row-level write, with types converted between the two schemas.

Microsoft Dynamics NAV Bill 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 Bill through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Bill: 20,000 requests per developer key per hour; login (POST /v3/login) capped at 200/hour; maximum 3 concurrent requests per developer key per organization. Spend & Expense API is a separate token at 60 calls/token/minute.
What ships with Bill ⇄ Microsoft Dynamics NAV

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Bill and Microsoft Dynamics NAV connectors work

Bill

Integration surface
REST/JSON (BILL v3 Connect API)
Authentication
Session-based: POST /v3/login with username, password, organizationId, and a developer key (devKey) returns a sessionId that is passed with the devKey as headers on every subsequent call; OAuth is available for partner/embedded apps
Change detection
Webhook event subscriptions (POST /v3/subscriptions) for bills, vendors, payments, invoices, and bank accounts, with polling on createdTime/updatedTime list filters as the fallback
Capabilities
read · write · webhooks
Rate limits
20,000 requests per developer key per hour; login (POST /v3/login) capped at 200/hour; maximum 3 concurrent requests per developer key per organization. Spend & Expense API is a separate token at 60 calls/token/minute.

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

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

    Choose tables

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

Bill and Microsoft Dynamics NAV 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
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:

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

Popular · 8 of 498
All Bill integrations All Microsoft Dynamics NAV 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