How does the integration handle real-time bill updates from Ramp?

ml-connector listens to Ramp webhooks for bill events (created, updated, paid, archived) and processes them in real-time, verifying each webhook with HMAC-SHA256 to confirm it came from Ramp. When a bill is marked paid, ml-connector immediately creates a purchase invoice in NAV with GL journal entries mapped to the correct cost centers and GL accounts. If a bill is updated after posting, ml-connector adjusts the corresponding NAV journal entries.

What happens if Microsoft Dynamics NAV and Ramp have conflicting vendor records?

ml-connector syncs vendor master data bidirectionally on a schedule, preferring Ramp as the source of truth for newly created vendors from procurement flows. If the same vendor exists in both systems with different names or addresses, ml-connector flags the conflict in the audit log and pauses that vendor sync until resolved manually. Existing vendors are updated in place without duplication.

How are GL accounts and cost centers mapped between the two systems?

Each bill line in Ramp carries accounting dimensions (cost center, GL account, department) that ml-connector uses to select the correct NAV GL account and dimension when creating journal entries. ml-connector polls NAV GL accounts on a schedule to ensure mappings stay current if your chart of accounts changes, and it maintains a mapping table so bills always post to valid NAV accounts.

Microsoft Dynamics NAVRamp

Microsoft Dynamics NAV and Ramp integration

Microsoft Dynamics NAV manages your general ledger, accounts payable, and GL dimensions. Ramp manages corporate spend across cards, bills, and reimbursements. Connecting the two keeps your finance records in agreement. Bills paid through Ramp post into NAV as purchase invoices and GL journal entries mapped to your cost centers and GL accounts, vendors are aligned in both directions, and month-end close starts with AP already reconciled.

How Microsoft Dynamics NAV works

Microsoft Dynamics NAV for Business Central online exposes vendors, purchase orders, purchase invoices, GL accounts, GL entries, dimensions, and journal templates through OData v4 REST, with a base URL containing your tenant ID and company ID. Authentication uses OAuth 2.0 client credentials through Microsoft Entra ID, or legacy basic auth with a web service access key. NAV publishes webhook events for most entities including vendors, purchase invoices, and GL entries with a 3-day subscription expiry, and subscriptions must be renewed before they expire; alternatively records can be polled via OData. GL accounts and GL entries are read-only once posted, so ml-connector cannot modify historical GL postings.

How Ramp works

Ramp exposes bills, vendors, purchase orders, GL accounts, and transactions through a REST API at https://api.ramp.com/developer/v1, authenticated with OAuth 2.0 client credentials with a 10-day token lifespan. Ramp pushes real-time webhook events for bills (created, updated, paid, archived), vendors (updated), transactions (cleared, synced), and other spend events, with HMAC-SHA256 signature verification. Vendors cannot be created directly through the API, and purchase orders are read-only; Ramp is primarily a source of spend transactions and bills that flow into downstream financial systems.

What moves between them

The main flow is from Ramp into Microsoft Dynamics NAV. Bills paid through Ramp are synced as purchase invoices into NAV, with each bill line creating a GL journal entry allocated to the correct cost center and GL account based on Ramp's accounting dimensions. Vendor master data syncs bidirectionally so NAV vendors stay aligned with Ramp vendor master, and Ramp receives GL account updates from NAV so bill GL mappings reflect the current chart of accounts. Ramp pushes bill and vendor updates in real-time via webhooks, and ml-connector also polls NAV for GL account changes on a schedule.

How ml-connector handles it

ml-connector stores credentials for both systems encrypted and uses OAuth 2.0 client credentials to obtain bearer tokens for Ramp, refreshing every 10 days before expiry, and Microsoft Entra ID bearer tokens for NAV. It listens to Ramp webhooks for bill and vendor events, verifying each webhook with HMAC-SHA256 signature to confirm authenticity, and processes bills immediately when they are paid or updated. On the NAV side, it polls GL accounts and vendor master data on a schedule to keep the two systems aligned, since NAV subscriptions expire after 3 days and must be renewed. Each bill from Ramp is mapped to a NAV purchase invoice with GL journal lines, pulling accounting dimensions from Ramp to select the correct NAV cost center and GL account. Vendor names, addresses, and contact info sync from Ramp into NAV so new vendors from procurement flows appear in finance. Every record carries an audit trail and can be replayed if NAV is temporarily unavailable.

A real-world example

A mid-sized services firm runs Microsoft Dynamics NAV for accounting and GL management, and uses Ramp for corporate cards, bill pay, and travel expenses across five regional offices. Before the integration, the finance team exported approved bills from Ramp each week and manually entered them into NAV as purchase invoices, allocating each line to the correct cost center and GL account. Month-end close required reconciling Ramp's paid bills against NAV's AP accounts and chasing mismatches caused by data-entry errors. With Ramp and NAV connected, paid bills flow into NAV in real-time as purchase invoices with correct GL postings, vendors are kept current, and AP is reconciled automatically at the end of the month.

What you can do

Sync Ramp bills into Microsoft Dynamics NAV as purchase invoices with GL journal entries, allocated to cost centers and GL accounts.
Align vendor master data bidirectionally between Ramp and NAV so procurement and finance systems have the same vendor records.
Listen to Ramp webhook events for real-time bill updates and vendor changes, verifying webhook authenticity with HMAC-SHA256.
Authenticate both systems with OAuth 2.0, managing Ramp client credentials tokens and Microsoft Entra ID bearer tokens with automatic renewal.
Poll NAV GL accounts on a schedule to keep accounting dimensions current, with a full audit trail and error replay on every record.

Questions

How does the integration handle real-time bill updates from Ramp?: ml-connector listens to Ramp webhooks for bill events (created, updated, paid, archived) and processes them in real-time, verifying each webhook with HMAC-SHA256 to confirm it came from Ramp. When a bill is marked paid, ml-connector immediately creates a purchase invoice in NAV with GL journal entries mapped to the correct cost centers and GL accounts. If a bill is updated after posting, ml-connector adjusts the corresponding NAV journal entries.
What happens if Microsoft Dynamics NAV and Ramp have conflicting vendor records?: ml-connector syncs vendor master data bidirectionally on a schedule, preferring Ramp as the source of truth for newly created vendors from procurement flows. If the same vendor exists in both systems with different names or addresses, ml-connector flags the conflict in the audit log and pauses that vendor sync until resolved manually. Existing vendors are updated in place without duplication.
How are GL accounts and cost centers mapped between the two systems?: Each bill line in Ramp carries accounting dimensions (cost center, GL account, department) that ml-connector uses to select the correct NAV GL account and dimension when creating journal entries. ml-connector polls NAV GL accounts on a schedule to ensure mappings stay current if your chart of accounts changes, and it maintains a mapping table so bills always post to valid NAV accounts.

Connect Microsoft Dynamics NAV and Ramp

Free to use. Add your credentials, ping your real systems, and see if we fit.

Get started