Pre-built Concur data conversion for Expense, Travel and Invoice. REST API v3/v4 extractors with OAuth2, multi-TB receipt-image streaming, Custom Field to DFF crosswalks, FBDI Expense Report emitters, row-level reconciliation. Audit-ready evidence at every load.
The hard part isn't pulling JSON from a REST API. It's translating Concur's data model into Fusion's expense, payables and GL model without losing receipt-image substantiation or audit-rule context.
Concur, acquired by SAP in 2014, presents a cloud-native data model built around Expense Reports (header + entries + allocations + attendees + approvals), Receipts (image + OCR metadata), Itineraries, Cash Advances, Mileage logs and Corporate-Card transactions ingested as T-feeds from Amex, Visa and Mastercard. Oracle Fusion Expenses uses a different shape — Expense Reports tied to Workers, Expense Items, Distribution lines aligned to the COA, and Attachments stored against UCM document IDs.
Every concur data migration to Oracle Fusion has to bridge those gaps without breaking the audit chain that links a GL journal line back to its original receipt image. Custom REST clients and one-off transformation SQL can do it — but every domain becomes a multi-week negotiation between functional, technical and compliance teams. Syntra ETL replaces that with pre-built crosswalks refined across dozens of Concur conversions.
The same engine handles three deployment scenarios: full Concur replacement (Expense + Travel + Invoice → Fusion), Expense-only migration with Travel kept on Concur (common when the corporate travel team likes the Concur online booking tool), and the consolidation pattern where Concur Invoice migrates to Fusion Payables ahead of the Expense module.
The transformations Syntra ETL ships pre-built. No custom REST scaffolding, no multi-month bespoke conversion development.
Concur Custom Fields walked, classified by reporting materiality, and routed: required fields collapse to Fusion COA segments, optional fields route to Fusion Expense DFFs, analytical fields go to OTBI dimensions or archive.
Multi-TB receipt images streamed via Receipts API, hash-signed, bound to Fusion Expense attachments via FBDI attachment metadata. Receipt-id cross-reference preserved for IRS Pub 463 substantiation.
T-feed transactions from Amex/Visa/Mastercard matched to expense entries, card-program/BIN/MCC context preserved, Fusion corporate-card configuration auto-suggested from source mapping.
Concur multi-way allocations (per-line cost splits across cost-centers, projects, internal orders) converted to Fusion Expense Distribution lines with full traceability and audit log.
Concur Audit Service rule violations and approver overrides captured as evidence metadata in the Fusion expense report, preserving the original SOX-relevant approval context.
EU/UK VAT recovery substantiation maintained: receipt image, gross/net/tax breakdown and vendor VAT registration carried through to Fusion for HMRC and EU VAT Directive compliance.
A repeatable load order that respects Fusion Expenses' data dependencies. Skip a step and your expense report load fails on missing workers or expense templates.
Fusion enterprise structures, ledgers, BUs, COA segments, expense templates, expense categories, corporate-card programs configured. Loaded via FSM tasks — not user-facing data, but everything downstream depends on it.
Workers (HDL Worker.dat), expense templates (FBDI Expense Template), corporate-card programs and BIN ranges, vendor master from Concur Invoice (FBDI Supplier Import). Loaded in dependency order — workers before expense reports, cards before card transactions.
In-flight expense reports and pending approvals migrated via FBDI Expense Report Import. Approval state and approver chain preserved via AMX. Receipt images linked through FBDI attachment metadata.
Closed expense reports for the operational window (typically current FY + prior FY) loaded if Fusion is the target archive; older history routed to long-term Concur archive. Either way, queryable for audit during full IRS Pub 463 retention.
Coordinated with Amex/Visa/Mastercard feed providers: confirm cutoff date, process last Concur file, configure Fusion corporate-card setup, parallel reconciliation period for late-posting transactions.
Final delta replay, parallel-month reconciliation, sign-off pack (expense register, AP reimbursement aging, receipt-image attachment counts — Concur vs Fusion to the cent). Production cut to Fusion.
Every concur data migration load produces signed drill-downable reconciliation reports.
Source Concur expense report count vs Fusion-loaded report count per business unit per period. Entry counts and attachment counts reconciled separately. Variance threshold zero.
Reimbursable amount, total amount, tax amount and per-currency totals reconciled per period per business unit. Variance flags surface before any subsequent load is allowed.
Each expense report content-hashed at Concur source and re-hashed post-Fusion-load. Hash drift indicates transformation bug or corruption — surfaced with row-level diff.
Concur expense register per period vs Fusion Expense Register, drillable to entry line, distribution line and originating receipt image.
Corporate-card transactions ingested in Concur vs corresponding charges in Fusion corporate-card configuration. Unmatched transactions surfaced for manual review.
Receipt image counts and total bytes per period reconciled between Concur source and target (Fusion attachments or archive). Spot-check sampling validates image integrity post-load.
Concur data migration is the process of moving expense reports (headers, entries, itemizations, allocations, approvals), receipts (images plus OCR metadata), travel itineraries, cash advances, mileage logs, corporate-card transactions (T-feeds from Amex/Visa/Mastercard) and Concur Invoice records from your SAP Concur tenant into Oracle Fusion Expenses, Payables and GL. The technical heart is two-fold: streaming structured data through Concur REST API v3/v4 with OAuth2, and bulk-transferring multi-TB receipt-image archives through the Receipts API. Syntra ETL handles both with pre-built extractors, governed crosswalks for Concur Custom Fields to Fusion DFFs, and Oracle-validated FBDI Expense Report and Payables Invoice output.
The terms get used interchangeably, but the distinction is useful: migration is the end-to-end project (extract + transform + load + reconcile + cutover), while conversion is the transformation layer specifically. Syntra ETL's Concur data conversion engine ships pre-built rules for expense-type to Fusion expense-template mapping, cost-center allocation translation, Custom Field to DFF routing, corporate-card transaction matching, receipt-image attachment binding and OCR metadata preservation. These are rules that on a consultant-led project would otherwise eat 3–4 months of bespoke REST client and SQL development.
Receipt-image archives are the single biggest data volume in Concur migration — multi-TB common, with single tenants exceeding 40 TB across a decade of retention. Syntra ETL streams images through Concur's Receipts API in parallel (typically 25 concurrent connections, respecting REST API rate limits), preserves the original Concur receipt-image-id, and stages images to cloud object storage with hash signatures. For Fusion-target loads, each image is bound to the corresponding Fusion Expense report attachment slot via FBDI's attachment metadata. For archive-target loads, images stay in object storage indexed by receipt-id, satisfying IRS Pub 463 7-year substantiation with signed, timestamped read-access logs.
Yes. Concur Custom Fields are the equivalent of PeopleSoft ChartFields or EBS DFFs — they drive cost-center coding, project tagging, location routing and a long tail of customer-specific dimensions. Syntra ETL's Concur converter walks every active Custom Field in the source tenant, identifies which fields drive material reporting splits in Fusion's 6-segment COA, and proposes routing: required Custom Fields collapse into Fusion COA segments, optional ones route to Fusion Expense DFFs, and analytical-only ones route to OTBI dimensions or to the long-term Concur archive. Allocations (multi-way cost splits per expense line) are converted to Fusion Expense Distribution lines with full traceability.
Syntra ETL emits Fusion-native load formats for every Concur data domain: FBDI Expense Report Import for expense reports, entries, allocations and attendees; FBDI AP Invoice Import for Concur Invoice records and reimbursement payment files; HCM Data Loader (HDL) for any worker-side context that needs to be re-asserted; and REST API payloads for incremental delta loads during parallel-run and post-cutover. Receipt images are bound via FBDI attachment metadata (file path + content-type + receipt-id). Every payload is validated against the current Oracle Fusion 26x release schema before submission, so validation errors surface locally — not in a 4-hour Fusion ESS job that fails on row 47,000.
Every expense report extracted from Concur is hashed at the source (header hash + entry hashes + attachment hashes). Every report loaded into Fusion is re-hashed post-load. The reconciliation engine compares counts (reports, entries, attachments), sum totals (amount, tax, reimbursable amount per currency) and hash signatures per business unit per period. Any record that fails Fusion validation is captured with the exact field-level reason ready for bulk fix. Output is a signed timestamped reconciliation pack: Concur expense register vs Fusion expense register to the cent, AP reimbursement aging vs aging, receipt-image attachment count vs count. Internal audit signs off on the pack directly.
Yes. After the initial bulk load, Syntra ETL captures Concur deltas via the REST API's modified-since watermark on each domain (expense reports, receipts, corporate-card transactions) and replays them into Fusion through REST APIs. This supports the standard parallel-run pattern: Concur continues taking expense submissions for 1–2 month-end cycles while Fusion is validated to the cent. Once finance, T&E ops and compliance sign off, new submissions cut to Fusion and the Concur tenant moves to read-only archive mode. Corporate-card feeds are cut over to Fusion at the provider level during this window.
SOX requires 7-year retention of financial records with auditable trace from GL entry back to original supporting evidence — the receipt image in this case. EU/UK VAT recovery rules (HMRC, EU VAT Directive) similarly require 6 years of receipt-image substantiation to support reclaim filings. Syntra ETL's Concur data migration preserves the full chain: GL line in Fusion → Expense Distribution → Expense Entry → Receipt Image, with every hop signed and timestamped. Whether the receipt image lands in Fusion's attachment store or in the long-term Concur archive, the read-access log is captured for SOX and VAT audit evidence. No reconstruction needed when auditors arrive.
30-minute call. Walk through your Concur volumes, Custom Field design, receipt-image depth and corporate-card programs — leave with a concrete concur data migration plan.