Zoho Expense and SAP Concur Integration: Unified Travel and Expense Management

Organisations running SAP Concur for travel and expense management often reach a point where licensing costs outpace the value delivered, particularly at the mid-market level where Concur’s enterprise feature set goes partially unused. Zoho Expense offers a cost-effective alternative with strong automation, but switching platforms overnight is rarely practical. A Zoho Expense SAP Concur integration built on middleware like Make or Zapier lets you run both systems in parallel, sync expense data bidirectionally, and plan a controlled migration without disrupting active approval workflows or reimbursement cycles.

This guide walks through the full technical setup: comparing both platforms, configuring a middleware bridge, mapping expense policies, aligning approval chains, handling receipt OCR differences, and building a transition plan that keeps finance teams productive throughout the move.

SAP Concur vs Zoho Expense: Feature and Cost Comparison

Before building any integration, you need a clear picture of what each platform does well and where the gaps are. SAP Concur excels at enterprise travel booking, corporate card reconciliation, and compliance enforcement for organisations with 1,000+ employees. Zoho Expense targets the same expense management workflows but with simpler configuration, lower per-user pricing, and tighter integration with the broader Zoho financial ecosystem.

The cost difference is significant for mid-market companies. A 300-person organisation processing 500 expense reports per month might pay $4,000-12,500 monthly on Concur versus $1,500 on Zoho Expense Premium. That annual saving of $30,000-132,000 funds the middleware setup and migration effort several times over. For companies already using Zoho One, Expense is included in the suite, making the cost differential even larger.

Middleware Bridge Architecture with Make

The Zoho Expense SAP Concur integration runs through a middleware layer that connects both APIs. Make (formerly Integromat) is the recommended platform for this bridge because it supports both Concur’s OAuth 2.0 authentication and Zoho’s token-based API access with pre-built modules.

Authentication Setup

Start by creating API credentials on both sides. In SAP Concur, register a new app in the SAP Concur Web Services Admin panel to obtain a client ID and secret. Configure the OAuth 2.0 flow using the geolocation-specific token endpoint (e.g., https://us.api.concursolutions.com/oauth2/v0/token for US instances). On the Zoho side, register a server-to-server application in the Zoho API Console at api-console.zoho.com, requesting scopes for ZohoExpense.fullaccess.all.

In Make, create two connections: one HTTP module authenticated with Concur’s OAuth 2.0 Bearer token, and one Zoho Expense module using the native Zoho integration. Test both connections by pulling a sample expense report from each system before building the sync scenario.

Core Sync Scenario

The primary Make scenario handles bidirectional expense report synchronisation:

1. Trigger: Watch for new or updated expense reports in Concur using the Reports v3 API endpoint (/api/v3.0/expense/reports) with a polling interval of 15 minutes
2. Transform: Map Concur expense categories to Zoho Expense categories using a lookup table (a Make data store works well for this)
3. Create/Update: Push the mapped report into Zoho Expense via the Create Expense Report API, including line items, project codes, and receipt attachments
4. Status sync: When approval status changes in either system, a separate scenario updates the corresponding record

For receipt images, download the attachment from Concur’s Image API (/api/v3.0/expense/receiptimages), temporarily store it in Make’s buffer, and upload it to the Zoho Expense report using the Attach Receipt endpoint. This preserves the audit trail across both platforms.

Expense Policy Mapping Between Platforms

Concur and Zoho Expense handle expense policies differently. Concur uses audit rules with exception levels (warning, hard stop, notification) tied to expense types and spending limits. Zoho Expense uses policy groups with per-category spending limits, mileage rates, and per-diem configurations.

Create a mapping document that covers every active Concur audit rule and its Zoho Expense equivalent:

• Spending limits: Concur’s per-expense-type limits translate directly to Zoho Expense’s category-level caps. Export your Concur audit rules and recreate them as Zoho Expense policy rules
• Mileage rates: Concur stores mileage rates per vehicle type and region. Zoho Expense supports the same structure under Settings > Mileage, with distance-based rates per vehicle category
• Per diem rules: Concur’s travel allowance configuration maps to Zoho Expense’s per-diem module, though Zoho uses a simpler flat-rate approach compared to Concur’s GSA/HMRC rate lookups
• Receipt requirements: Both platforms enforce receipt attachment rules above configurable thresholds. Match your Concur threshold (commonly $25 or $75) in Zoho Expense’s policy settings
• Custom fields: Export Concur’s custom field definitions and recreate them as Zoho Expense custom fields under Settings > Preferences. Map field IDs in your Make lookup table for accurate data transfer

Run a policy audit by submitting 20-30 test expense reports through both systems with intentional violations. Compare the flags raised by each platform. Any discrepancies indicate mapping gaps that need correction before going live.

Approval Chain Configuration

Approval workflows are where migrations most frequently break down. Concur supports complex approval chains with conditional routing based on expense amount, department, project, and cost centre. Zoho Expense provides multi-level approvals with conditional rules, though the configuration interface differs significantly.

Mapping Concur Approval Steps to Zoho Expense

Export your Concur approval workflow definitions. For each step, document the approver assignment rule (manager hierarchy, specific approver, cost-centre owner), the condition that triggers the step (amount threshold, expense type), and any delegation or backup approver settings.

In Zoho Expense, navigate to Settings > Approvals to build the equivalent chain. Zoho supports up to five approval levels with conditions based on amount, category, department, and custom field values. For organisations using Zoho Flow, you can extend approval logic beyond Zoho Expense’s native capabilities by triggering custom workflows on report submission.

Handling Edge Cases

Three common scenarios require special attention during approval chain migration:

1. Proxy approvers: Concur’s delegation feature lets managers assign temporary approvers during leave. In Zoho Expense, configure this under Settings > Approvals > Delegation. The middleware should sync delegation assignments if both systems run in parallel
2. Split approvals: Reports containing mixed expense types (e.g., client entertainment above $500 needing VP approval plus standard travel expenses) may route differently. Test these cases explicitly in Zoho Expense
3. Auto-approval rules: If Concur auto-approves reports below a threshold, replicate this in Zoho Expense using the auto-approval setting in the policy configuration

Receipt OCR Comparison and Reconciliation

Both platforms offer receipt scanning with OCR, but their extraction accuracy and field mapping differ. SAP Concur uses its own AI-powered receipt parser that extracts merchant name, date, amount, currency, and tax. Zoho Expense’s auto-scan feature extracts similar fields and can also pull line-item detail from structured receipts.

When running both systems in parallel, you need a reconciliation process to verify that OCR data matches across platforms. Build a Make scenario that:

1. Pulls expense line items from both Concur and Zoho Expense for the same reporting period
2. Matches records by employee ID, date, and amount (within a tolerance of $0.50 to account for rounding differences)
3. Flags mismatches in a Google Sheet or Zoho Sheet for manual review
4. Reports match rates weekly to the finance team

During initial parallel running, expect match rates of 92-96%. The most common discrepancies come from currency conversion timing differences, tax extraction variations, and category mapping errors. A 98%+ match rate after two weeks of tuning indicates readiness for Concur decommission planning. For companies tracking expenses at the project level, ensure your middleware maps Concur project codes to the equivalent structure in Zoho Books project accounting.

Transition Planning and Cutover Strategy

Moving from Concur to Zoho Expense is not a single-day event. A phased approach over 8-12 weeks reduces risk and gives finance teams time to adapt.

Phase 1: Parallel Running (Weeks 1-4)

Run both systems simultaneously with the middleware bridge syncing all data. Employees continue submitting expenses in Concur as usual. The bridge replicates every report in Zoho Expense automatically. Finance teams review reports in both systems and flag discrepancies. This phase validates data accuracy and builds confidence in the new platform.

Phase 2: Pilot Group (Weeks 5-8)

Select 20-50 employees from a single department to submit expenses exclusively in Zoho Expense. The middleware still syncs their reports back to Concur for audit trail continuity. Collect feedback on the Zoho Expense mobile app, approval speed, and any workflow gaps. Address configuration issues before expanding the pilot. Connect the accounts payable automation workflow so reimbursements process through Zoho’s payment pipeline.

Phase 3: Full Cutover (Weeks 9-12)

Migrate all remaining employees to Zoho Expense. Maintain the Concur read-only access for 90 days to satisfy audit and compliance requirements. Export all historical Concur data (reports, receipts, approval logs) to a structured archive. Decommission Concur API credentials and cancel the subscription at the next renewal window.

Throughout all phases, keep the middleware bridge active. It serves as both the sync mechanism and the safety net. If any critical issue surfaces in Zoho Expense, you can reroute expense submission back to Concur within hours by adjusting the bridge configuration.

Testing and Validation Checklist

Before declaring the integration production-ready, work through each validation point:

• Data integrity: Compare 100 expense reports side-by-side across both platforms. Every field, including custom fields, project codes, and tax amounts, must match
• Approval flow: Submit test reports that trigger every approval branch in your workflow. Verify that approvers receive notifications and can act within Zoho Expense’s interface
• Receipt handling: Upload 50 receipts (mix of paper scans, phone photos, and digital receipts) through both OCR engines. Compare extraction accuracy
• Corporate card reconciliation: Process a full month of card transactions through Zoho Expense. Confirm auto-matching rates and unmatched transaction handling
• Reporting parity: Generate your standard monthly expense reports from both platforms. Compare totals by category, department, and project
• Error handling: Simulate API failures in the middleware (disconnect one credential temporarily). Verify that the bridge queues failed transactions and retries them when connectivity restores
• Mobile experience: Have five employees test the complete expense submission flow on Zoho Expense’s mobile app, from receipt capture to report submission

Document results in a test summary shared with finance leadership. Green-light the next migration phase only when all validation points pass. For organisations managing broader financial integrations, this testing approach mirrors the methodology used in Zoho CRM integration projects where data accuracy between systems is the primary success metric.

For a full overview of all available options, explore our complete guide to Zoho integrations.

The path from SAP Concur to Zoho Expense does not require a hard cutover or months of downtime. With a properly configured middleware bridge on Make, expense data flows between both platforms while your team transitions at a controlled pace. Start with the policy mapping exercise, build the core sync scenario, run parallel for four weeks, and expand from there. The middleware stays active as your safety net until the final Concur decommission, giving finance leadership the confidence to approve each phase.