How-to-Integrate-Dynamics-365-with-Concur-final

If you’re running Microsoft Dynamics 365 and SAP Concur side by side, you already know the pain.

Expense reports live in Concur. Financial records live in Dynamics. And someone — probably you or someone on your team — is manually moving data between them.

That’s a problem. The average cost of processing a single expense report manually is $58, and nearly 20% of expense reports contain errors (GBTA). Multiply that across your whole organization and you’re looking at thousands of dollars down the drain every month.

The good news? Integrating Dynamics 365 with Concur eliminates that bottleneck entirely. Automated sync means no more duplicate data entry, no more reconciliation headaches, and no more delayed reimbursements.

This guide breaks it all down — step by step, no fluff.

How to Integrate Dynamics 365 with Concur

There are three main ways to connect Dynamics 365 with SAP Concur. Which one is right for you depends on your Dynamics version (F&O, Business Central, or GP) and how much customization you need.

Understand What You’re Connecting

Before you touch a single setting, get clear on what data needs to flow between the two systems.

Typical integration touchpoints include:

• Expense reports from Concur → General Ledger or Accounts Payable in Dynamics
• Employee and vendor data syncing bidirectionally
• Cost center and dimension mapping
• Reimbursable vs. non-reimbursable transaction categorization
• Payment batch processing and closure

Fun stat: Businesses that automate expense management reduce processing time by 60% and cut costs by 35% (Expense Management Trends Report 2025). That alone makes this integration worth the setup time.

Option 1 — Use a Native Connector (Dynamics 365 F&O)

If you’re on Dynamics 365 Finance & Operations, Microsoft offers native integration support with Concur through the Concur Financial Integration Services.

Here’s how it works:

Step 1 — Enable the Concur Integration in D365 F&O

Navigate to your Accounts Payable module. Under Setup, look for the Concur integration parameters. You’ll need your Concur credentials — client ID, client secret, and the Concur endpoint URL — ready before you start.

Step 2 — Map Your Financial Dimensions

This is where most people get stuck. Every expense category in Concur needs to map to an account or dimension in Dynamics. Set up your chart of accounts mapping carefully — mismatches here are what cause reconciliation errors downstream.

Step 3 — Configure Data Flow Direction

Decide if you need one-way or bidirectional sync. One-way pushes expense reports from Concur into Dynamics. Bidirectional also lets Dynamics data (like cost centers and employee info) flow back into Concur — saving your finance team from double entry on both sides.

Step 4 — Run a Test Batch

Never go live blind. Process a small batch of test expense reports and verify the journal entries are posting correctly in Dynamics. Check the General Ledger and Accounts Payable for accuracy before turning on automated runs.

Step 5 — Schedule Automated Syncs

Once validated, set your integration to run on a schedule — daily, hourly, or triggered by batch status. Most teams run it daily overnight so everything is reconciled by morning.

Option 2 — Use a Third-Party Connector

If you’re on Dynamics 365 Business Central or need more flexibility, a pre-built connector is often the fastest path.

Popular options include:

• ExpenseConnect by Wipfli — Installable directly into your D365 F&O or Business Central environment. It leverages native web services to automate the pull from Concur without any manual file downloads. Supports reimbursable transactions, billable/non-billable categorization, and VAT identification.
  
  
• SmartConnect by eOne Solutions — A no-code integration platform that connects Concur Expense to Business Central. Great for teams who want full control over mapping without writing custom code.
  
  
• Expense Connect by Digital Architect Group (DAG) — Built specifically for D365 F&O and D365 Project Operations. Fully configurable, supports custom dimension mapping, and includes a monitoring workspace to catch errors before they hit your ledger.
  
  

Why this matters: Only 29% of workers currently have access to automated expense management software (Rho, 2024). The other 71% are still doing this manually. A connector closes that gap fast.

Implementation steps for connectors are generally:

1. Install the connector module into your Dynamics environment
2. Authenticate both your Concur and Dynamics credentials inside the connector dashboard
3. Map your expense types, GL accounts, employees, and dimensions
4. Set integration triggers (on-demand, scheduled, or API-driven)
5. Monitor the first few live runs via the connector’s error-handling workspace

Option 3 — Use Celigo or a Middleware iPaaS

For teams with complex multi-entity setups or custom workflows, a middleware integration platform like Celigo gives you granular control over every data flow.

Celigo offers a Concur Expense – Dynamics 365 Business Central quickstart template that pre-configures common flows including:

• Syncing Concur companies as Business Central customers
• Importing expense reports by payment batch
• Closing payment batches in Concur after they’ve posted in Dynamics

Steps:

1. Install the quickstart template from Celigo’s integration marketplace
2. Configure hard-coded field mappings (company names, payment batch filters)
3. Set dynamic mappings for journal lines based on your Business Central GL structure
4. Enable each flow individually — all flows are disabled by default after installation
5. Run or schedule each flow from the Flows dashboard

Pro tip: Always configure the filter for company record types in the search parameters before going live. This prevents mismatches if you’re running multiple legal entities.

Key Things to Get Right (So You Don’t Have to Redo This)

Getting the integration working is one thing. Getting it working well is another. A few things most guides skip over:

Dimension mapping is non-negotiable. If your expense types in Concur don’t match the account codes in Dynamics, journal entries will fail silently or post to the wrong GL. Do this mapping carefully before anything else.

Bidirectional sync saves time but needs governance. Letting Dynamics push employee and vendor data back to Concur means your records stay in sync automatically. But set clear rules for which system is the “source of truth” to avoid conflicts.

Error monitoring is your safety net. Every integration tool mentioned above includes some form of error-handling workspace or alerting. Use it. A failed batch that goes unnoticed for a week can create a reconciliation nightmare.

Automate your schedules but audit regularly. Gartner predicts that by 2025, 80% of organizations will use expense analytics tools to drive business value from their data. Automation gets you the data — but someone still needs to review it.

Conclusion

Integrating Dynamics 365 with Concur isn’t complicated once you know which path to take. The native D365 F&O connector works great for standard setups. Third-party tools like ExpenseConnect or SmartConnect are the right call for Business Central or when you want more flexibility. And for complex, multi-entity environments, middleware like Celigo gives you full control.

The bottom line? Manual expense management is costing your business time and money it doesn’t need to spend. A Forrester study found that companies automating expense workflows saved over 5,400 employee hours — and the average employee wastes 40 hours a year just on manual expense reports (Rydoo, 2024).

Set up the integration once. Let it run. Get your team’s time back.

Want more meetings booked without any of the manual work? At Salesso, we run done-for-you LinkedIn outbound and cold email campaigns — targeting your ideal prospects, crafting your campaigns, and scaling what works. Book a strategy meeting today →