Skip to content
ERP ⇄ Accounting and finance

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

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

Keep Ramp 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 Vendors, Funds (Spend Controls), General Ledger Accounts, Transactions in Ramp with Vendors, Items, Sales Orders & Invoices, Purchase Orders 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 Mirror Bills and their approval and payment state into an AP or ERP system, marking each one ready-to-sync then synced to keep both ledgers reconciled.
  • 02 Read Reimbursements into a finance database for cross-entity expense reporting and reconciliation without manual CSV exports.
  • 03 Run parallel sync during a NAV-to-Business Central migration so both systems stay usable.
  • 04 Sync customers, items, and orders between NAV and a CRM in both directions.

Common sync patterns

Subsidiary to headquarters

Where Ramp 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.

Where Ramp handles billing: invoices land in Microsoft Dynamics NAV

Invoices and payment activity from the billing side post through to the enterprise system automatically.

Migration without a hard cutover

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

What you can sync between Microsoft Dynamics NAV and Ramp

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 Ramp objects How this pairing syncs
Vendors Vendor cards aligned with procurement and AP tools. Vendors Supplier records under the accounting namespace; uploaded and updated for AP matching and payments. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Sales Orders & Invoices Sales documents created from external orders and read back for posting status. Bills Accounts-payable bills; created, updated, approved, and paid, then posted ready-to-sync and synced to accounting. Sales Orders & Invoices is specific to Microsoft Dynamics NAV and Bills to Ramp — each maps to any object or custom field on the other side.
Purchase Orders Purchasing documents reconciled with receiving and vendor systems. Funds (Spend Controls) Spend controls governing card usage; read and created via the funds API to enforce budgets per user, department, or program. Purchase Orders is specific to Microsoft Dynamics NAV and Funds (Spend Controls) to Ramp — each maps to any object or custom field on the other side.
G/L Entries Posted ledger entries replicated to warehouses for finance reporting. General Ledger Accounts Chart-of-accounts entries uploaded from the ERP; accounting codings are posted back against transactions and bills. G/L Entries is specific to Microsoft Dynamics NAV and General Ledger Accounts to Ramp — each maps to any object or custom field on the other side.
Item Ledger Entries Inventory movement history read for stock and costing analytics. Transactions Card purchase records with merchant, amount, and state; read for spend/GL sync and written back via accounting codings and sync status. Item Ledger Entries is specific to Microsoft Dynamics NAV and Transactions to Ramp — each maps to any object or custom field on the other side.
Dimensions Analytical codes carried on documents and entries for reporting splits. Cards Physical and virtual card records; created and managed through the API to provision or suspend cardholder spend. Dimensions is specific to Microsoft Dynamics NAV and Cards to Ramp — each maps to any object or custom field on the other side.

How changes propagate between Microsoft Dynamics NAV and Ramp

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

Ramp Microsoft Dynamics NAV Sub-second propagation

DetectionRamp notifies Stacksync of record changes through webhook events. Signed webhooks (HMAC-SHA256 X-Ramp-Signature) for bill, transaction, reimbursement, vendor, and user events.

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

Rate-limit considerations

  • Ramp: 200 requests per 10-second rolling window per source IP; exceeding it returns 429 Too Many Requests, and requests running over 60 seconds return 504. Results use keyset pagination (follow the page.next URL / start cursor); higher limits can be requested from support.
What ships with Microsoft Dynamics NAV ⇄ Ramp

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

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

Real-time

Two-way sync

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

Observability

Monitoring

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

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

Ramp

Integration surface
REST API (Developer API v1)
Authentication
OAuth 2.0: exchange client_id/client_secret (HTTP Basic) at api.ramp.com/developer/v1/token for scoped bearer tokens; client_credentials grant for server-to-server and authorization_code for user-delegated access; scopes follow resource:permission (e.g. transactions:read, bills:write, accounting:write).
Change detection
Signed webhooks (HMAC-SHA256 X-Ramp-Signature) for bill, transaction, reimbursement, vendor, and user events; otherwise poll incrementally (synced_after on transactions, from_created_at on bills) with keyset pagination, or read the audit-logs/events feed.
Capabilities
read · write · webhooks
Rate limits
200 requests per 10-second rolling window per source IP; exceeding it returns 429 Too Many Requests, and requests running over 60 seconds return 504. Results use keyset pagination (follow the page.next URL / start cursor); higher limits can be requested from support.
Ramp setup guide
How it works

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

    Choose tables

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

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

Popular · 5 of 499
All Microsoft Dynamics NAV integrations All Ramp 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