Microsoft Dynamics NAV and SAP Concur integration

What moves between them

Expense reports, invoices, and purchase requests approved in SAP Concur flow into Microsoft Dynamics NAV as general ledger entries, payable invoices, and purchase orders, synchronized on a daily or weekly schedule depending on your approval workflow. Vendors and cost dimensions are synced bidirectionally to keep both systems current. Approved expenses and invoices in Concur post into NAV's general ledger allocated to the correct GL account and vendor, while new vendors created in NAV are provisioned in Concur if provisioning is enabled. The integration is read-only for historical GL entries in NAV and purchase requests in Concur, so corrections or cancellations are recorded as offsetting entries rather than deletions.

How ml-connector handles it

ml-connector stores both OAuth credential sets encrypted and uses the geolocation from Concur's token response to route all Concur API calls to the correct datacenter endpoint rather than hardcoding a single base URL. It refreshes both the NAV and Concur bearer tokens before they expire and handles 401 responses by retrying with a fresh token. Before posting an expense report or invoice from Concur into NAV, ml-connector validates that the associated vendor exists in NAV and maps the cost center and employee department from Concur to matching NAV dimensions. It monitors Concur's 5-subscription limit per app and coalesces related topics where possible. NAV's 3-day webhook subscriptions are renewed automatically, and if a subscription is deleted due to a non-2xx response, ml-connector resubscribes. For purchase requests and orders, the integration respects Concur's constraint that Purchase Requests v4 are POST and GET only, so modifications go through a separate flow. Every record carries a full audit trail, and if a downstream Concur API call fails, ml-connector queues the document for replay once the issue is resolved.

A real-world example

A mid-sized professional services firm runs Microsoft Dynamics NAV for accounting and operations and uses SAP Concur for travel and expense management across its staff. Before the integration, the operations team exported approved expense reports from Concur every week, manually looked up the matching vendors in NAV, and keyed the amounts into the GL as payable invoices, a process that created frequent mismatches between the two systems and delayed month-end close. With Microsoft Dynamics NAV and SAP Concur connected, approved expense reports and invoices flow into NAV automatically, matched to the correct vendors and GL accounts, and the operations team no longer re-enters data. Month-end close now starts with all expense and invoice accounts pre-populated and reconciled.

What you can do

• •Post approved SAP Concur expense reports and invoices into Microsoft Dynamics NAV general ledger entries and purchase invoices on a schedule matched to your approval workflow.
• •Validate vendors in SAP Concur against vendors in NAV before posting, preventing expenses from landing on non-existent or inactive vendors.
• •Map cost centers and employee departments from SAP Concur to dimensions in Microsoft Dynamics NAV so expenses allocate to the correct GL account.
• •Handle OAuth 2.0 for both systems, with automatic token refresh and geolocation routing for Concur's multi-datacenter infrastructure.
• •Manage Concur webhook subscriptions within the 5-per-app limit, renew expiring NAV subscriptions automatically, and track a full audit trail for every expense and invoice record.

Questions

What records flow from SAP Concur into Microsoft Dynamics NAV?

Approved expense reports, invoices (payment requests), and purchase requests flow from Concur into NAV as general ledger entries, payable invoices, and purchase orders respectively. Vendors and cost dimensions are synced in both directions. The integration respects Concur's read-only constraint on historical expense reports, so corrections are recorded as offsetting entries in NAV rather than deletions.

How does the integration handle geolocation routing for SAP Concur?

ml-connector extracts the datacenter geolocation from Concur's OAuth token response and uses it to route all subsequent API calls to the correct base URL (us.api.concursolutions.com, emea.api.concursolutions.com, or cn.api.concursolutions.com). This ensures compliance with Concur's multi-datacenter architecture without hardcoding a single endpoint.

What happens if a vendor in SAP Concur does not exist in Microsoft Dynamics NAV?

ml-connector validates the vendor before posting the expense report or invoice and holds the record in a pending state if the vendor is not found in NAV. The integration sends an alert and waits for the vendor to be created in NAV or the mapping to be resolved manually before retrying the post to the general ledger.