Purpose-built ETL platform for SAP Concur to Oracle Fusion migration — Expense, Travel and Invoice. REST API v3/v4 extractors, OAuth2 governance, receipt-image archive, corporate-card feed cutover. 40–60% faster than consultant-led programmes.
Most Concur to Fusion projects don't slip in the API extract. They slip in receipt-image volume, audit-rule inventory, Cognos report rebuild and corporate-card feed cutover.
SAP Concur, acquired by SAP in 2014, has been the dominant cloud T&E platform for over a decade. Customers carry a long tail of customization: hundreds of Custom Fields driving cost-center and project allocations, dozens of Audit Rules enforcing per-diem caps and policy exceptions, intricate Workflow definitions for multi-level approval, Cognos reports that finance has come to depend on for VAT recovery and policy reporting. Consultant-led migrations spend the first three months just cataloguing what exists.
Syntra ETL inverts the sequence. Pre-built Concur extractors against REST API v3/v4 with proper OAuth2 flows mean week-one extraction. A discovery engine that crawls the Custom Field catalog, Audit Service rule registry, Workflow definitions, Cognos report library and Policy Configuration produces a complete customization inventory in days. The concur to oracle fusion migration conversation that traditionally consumes a quarter now happens in week two with hard evidence on the table.
Whether you are moving Concur Expense alone, full Expense + Travel + Invoice, or running a hybrid where Concur Travel stays for online booking and only Expense data flows to Fusion, the same engine handles the workflow — with the same reconciliation rigor and the same audit trail evidence pack.
And how the Syntra ETL platform addresses each one — before they consume your timeline.
Receipt images are the single largest data volume in any Concur migration. Syntra ETL pulls them through the Receipts API in parallel, preserves the Concur receipt-image-id, and routes to Fusion attachments or to long-term cloud archive with IRS Pub 463 substantiation intact.
Concur Audit Service rules don't translate 1:1 to Fusion. Discovery crawls every Audit Rule, classifies by business purpose, and produces a Fusion-equivalent recommendation: native Audit Rule, AMX flow, or BI Publisher exception report. 30–50% typically retired.
T-feeds from Amex/Visa/Mastercard need re-cutover at the provider level. Syntra coordinates feed cutoff with the card provider, configures Fusion's corporate-card setup, and runs parallel reconciliation so no transaction is lost or double-counted.
Concur Reporting has been Cognos-based since the 2014 SAP acquisition; Cognos reports don't carry over. Inventory, classification, Fusion OTBI/BI Publisher rebuild plan. 40–60% retired during the cleanup.
Concur REST API v3/v4 requires OAuth2 with scoped client credentials. Syntra ETL ships a vetted OAuth client pattern with token rotation, scope minimization and SOC 2 audit logging — no admin shortcuts.
EU/UK VAT recovery depends on receipt-image substantiation for 6 years. The migration preserves the receipt→expense→report→GL chain so VAT recovery filings continue uninterrupted on the Fusion side.
A repeatable, governed workflow built for Concur's particular complexity. Typical full-scope timeline: 8–12 weeks.
Discovery engine catalogs every Custom Field, Audit Rule, Workflow definition, Cognos report and Policy Configuration in the Concur tenant via REST API v3/v4. Output: complete customization inventory, receipt-image volume estimate, corporate-card feed inventory, sized assessment with risk register.
Cost-center and expense-type crosswalks, custom-field to Fusion DFF routing, audit-rule retire/replace decisions, AMX workflow design, corporate-card program mapping. Reviewed and signed off by finance, T&E ops and compliance leads.
Concur REST extractors pull expense reports, entries, allocations, receipts (image + OCR), itineraries, corporate-card transactions, audit history. Output staged as Parquet plus original images, partitioned by fiscal year and business unit with hash-signed manifests.
Crosswalks applied, custom fields collapsed to DFFs, FBDI Expense Report payloads generated, receipt attachments linked, validated against Fusion 26x Expense templates. Errors surfaced locally with row-level diagnostics.
FBDI ZIPs submitted to Fusion ESS, monitored to completion, reconciled at row, sum and hash level. In parallel, critical OTBI and BI Publisher reports rebuilt and validated against Cognos equivalents. Corporate-card feed re-cutover coordinated with provider.
1–2 expense-month cycles in parallel (Concur + Fusion), deltas captured and replayed, reconciled to the cent, sign-off pack issued. Concur tenant moves to read-only archive mode; new expense reports flow to Fusion only.
No more bespoke REST clients or OAuth scaffolding. Just configure scope, run, reconcile.
Report headers, entries, itemizations, allocations, attendees, approvals — pulled via Expense API v3/v4. Full ChartField-style allocation context preserved for Fusion Expenses load.
Receipt images (JPG/PNG/PDF) via Receipts API, plus OCR-extracted metadata. Multi-TB archives streamed in parallel, hash-signed, indexed by Concur receipt-id for IRS Pub 463 substantiation.
Itineraries, air/hotel/car/rail segments, online booking tool history, unused tickets, agency-fee bookings via Travel API. Preserved as analytical archive even when Travel stays on Concur.
Corporate-card transactions from Amex, Visa, Mastercard T-feeds, plus regional issuers. Card-program, BIN range and MCC context preserved for Fusion corporate-card configuration.
AP invoice headers, line items, vendor master, payment requests, three-way match history from Invoice API. Routed to Fusion Payables FBDI for full AP modernization.
Audit Service rules, Workflow definitions, Policy Configurations, Custom Fields exported via Admin APIs — feeds the discovery-classification-rebuild loop without manual screenshots.
A typical Concur to Oracle Fusion migration covering Expense, Travel and basic Invoice scope, with 7+ years of expense reports and multi-TB of receipt images, runs 8–12 weeks with Syntra ETL versus 6–9 months on consultant-led projects. Single-module work (Concur Expense → Fusion Expenses only) completes in 5–7 weeks. The acceleration comes from pre-built Concur extractors that already speak REST API v3/v4 with proper OAuth2 flows, governed crosswalks between Concur Custom Fields and Fusion Expense DFFs, and corporate-card feed cutover playbooks for Amex, Visa and Mastercard T-feeds. Customers in regulated sectors carrying receipt-image archives needed for IRS Pub 463 substantiation routinely add 1–2 weeks for the parallel image-archive cutover.
Concur was acquired by SAP in 2014 for $8.3B and remains the dominant cloud T&E platform, but most Oracle ERP/Fusion customers find the per-user pricing punishing once travel volumes recover, and the SAP-leaning integration roadmap deprioritises Oracle ERP fit. Migrating Concur to Fusion Expenses consolidates T&E onto the same platform handling AP, GL and procurement, kills a six-figure annual subscription, removes a duplicated supplier/cost-center master, and lets you retire the Concur Travel online booking tool in favor of Fusion-integrated travel partners. Fusion Expenses now matches Concur on policy enforcement, audit rules, receipt OCR, mobile capture and corporate-card matching — and adds embedded AI for anomaly detection that Concur charges extra for.
Syntra ETL supports the full Concur footprint. Concur Expense: expense reports (header + entries + allocations + approvals), receipts (images plus OCR metadata), itemizations, attendees, mileage, cash advances, corporate-card transactions from Amex/Visa/Mastercard T-feeds, audit rule history and policy assignments. Concur Travel: itineraries, segments (air, hotel, car, rail), online booking tool history, unused tickets, agency-fee bookings. Concur Invoice: AP invoice headers, line items, vendor master, payment requests and three-way match history. All extracted through REST API v3/v4 with OAuth2 and routed either to Fusion Expenses/Payables via FBDI or to a long-term Concur archive for IRS Pub 463 substantiation.
Receipt images are the largest data volume in any Concur migration — multi-TB archives are routine and we have seen single tenants exceeding 40 TB across a 10-year retention window. The Receipts API streams the original receipt image (JPG/PNG/PDF) plus the OCR'd metadata. Syntra ETL pulls images in parallel, preserves the Concur receipt-image-id as a cross-reference, attaches each image to the corresponding Fusion Expense report attachment slot (if loading to Fusion) or stores them in cloud object storage with the immutable receipt-id index (if archiving). IRS Pub 463 requires the receipt to be retrievable for 7 years; both target paths satisfy that with signed, timestamped evidence of every read access.
Audit rules and workflows don't translate 1:1 — Concur's Audit Service uses a proprietary rule language and the Workflow engine is Concur-specific. What Syntra ETL does is inventory every active Concur Audit Rule (Concur Audit Service catalog), every Workflow definition, and every Policy configuration in the source tenant, classify each by business purpose (mileage limit, per-diem cap, alcohol policy, executive approval threshold, etc.), and produce a Fusion-equivalent recommendation: native Fusion Expense Audit Rule, Fusion Approvals Management (AMX) flow, or BI Publisher exception report. Customers commonly find 30–50% of Concur audit rules are redundant under Fusion's native policy engine and can be retired. The rest get re-implemented in Fusion-native tooling during the migration.
Since SAP acquired Concur in 2014, Concur Reporting has been Cognos-based — and Cognos reports don't carry over to Fusion. The Syntra ETL assessment inventories every Concur Cognos report in production use, classifies by business value (spend-by-category, top-spending-employees, policy-violation heatmaps, VAT-recovery reports, corporate-card reconciliation) and proposes Fusion replacements: OTBI dashboards for ad-hoc T&E analytics, BI Publisher for pixel-perfect operational reports like VAT recovery and 1099 substantiation, and Smart View for Excel-tethered analysis. Approximately 40–60% of legacy Cognos reports are duplicates or low-value and get retired. Critical reports are rebuilt in Fusion OTBI during the migration so go-live includes the reporting layer, not just the data.
Corporate-card feeds (Amex, Visa, Mastercard, plus regional issuers) need re-cutover at the provider level — Fusion can't ingest the same feed Concur is consuming until the feed is re-cut. Syntra ETL coordinates the cutover: confirms feed cutoff date with card provider, ensures last full Concur file is processed and reconciled before cutover, configures Fusion's corporate-card configuration with matching card-program, BIN ranges, merchant category codes and posting-account rules, and runs a parallel reconciliation period where late-posting transactions are caught manually. The whole feed cutover playbook takes 2–4 weeks for a typical Amex GBT global program and is sequenced so no transaction is lost or double-counted.
No. Syntra ETL's Concur extractors run as a read-only OAuth2 client with scoped access to the Expense, Travel, Invoice and Receipts APIs. Extracts are throttled to respect Concur's REST API rate limits (typically 25 requests/sec per tenant), and the largest extracts (receipt images for a decade of history) are scheduled to run during off-peak windows. No changes are required to the Concur tenant configuration, no Concur admin downtime is needed, and live expense reporting continues uninterrupted. The cutover itself is a defined moment — Concur switched to read-only, new expense reports filed in Fusion — typically scheduled for a Friday close-out so the week-end gives breathing room.
Book a 30-minute discovery call. We'll walk through your Concur modules, custom field design, audit-rule profile, receipt-image volume and corporate-card programs — and give you a concrete timeline and budget before the call ends.