Deep dive on the Expense data model: report headers, line entries, distributions, allocations, attendees, mileage, per-diems, multi-currency, audit-rule evidence, approval history and multi-TB receipt images. Five validation layers; zero data loss.
The Expense data model is denser than most ERP modules: report headers, entries, allocations, attendees, mileage, per-diems, three currencies per entry, audit-rule evidence and multi-TB receipt images. All of it has to port cleanly to Fusion Expenses.
SAP Concur — acquired by SAP in 2014 — models expense data across roughly a dozen related entities. The expense report is the parent: employee, purpose, dates, totals, status, approval chain. Underneath sit the line entries: expense type, transaction amount, three currencies, vendor, location, payment type, audit-rule triggers. Underneath the entries sit distributions and allocations (the accounting-segment splits), attendees (for meal and entertainment expenses), itinerary legs (for travel), mileage detail (for per-mile reimbursement), per-diem detail (for location-rate allowances) and receipt images (multi-TB binary content with OCR metadata).
Concur expense data migration has to preserve every layer. Lose the audit-rule evidence and compliance defensibility breaks. Lose the FX rate at transaction date and FX gain/loss reporting breaks. Lose the attendee detail and FCPA review of historical entertainment becomes impossible. Lose the allocation split detail and historical cost-centre rollups in Fusion don't match Concur source. Lose receipt-image integrity and IRS Pub 463 substantiation of any historical expense fails. Migration that ports headers and entries but skips the substructure is migration that breaks under the first auditor inquiry.
Syntra ETL's concur expense data migration covers the full data model — every field on every entity — with automated validation at five layers. Receipt images stream in parallel from Concur to the Syntra archive with SHA-256 hash verification end to end. Three-currency FX rates port intact. Audit-rule evidence ports intact. Allocation splits reconcile to parent-entry amounts on every migrated entry. The result is a Fusion Expenses estate that answers every question the Concur estate answered — and the legacy data access archive answers every closed-period question the Fusion estate can't.
Each entity class is independently extracted, transformed, loaded and validated. None is treated as optional.
Employee, purpose, business justification, dates, totals, status, policy ID, approval chain summary, submit/approve/extract/pay timestamps. Native Concur ID + new Fusion ID cross-reference.
50–80 fields per entry — expense type, three currencies, transaction date, vendor, location, payment type, receipt-image cross-reference, audit-rule trigger detail, comments.
Cost-centre, project, account segment values per entry. Drives GL posting on reimbursement. Reconciles to Fusion COA mapping defined in migration design.
Per-entry split rules — percentage or fixed amount, target segments, parent entry reference. Sum of splits = parent entry amount validated on every migrated entry.
Internal (employee cross-ref) and external (name, company, title, classification) participants. Material for IRS Pub 463 and FCPA-sensitive entertainment review.
Per-leg lodging, meals, mileage from Concur Travel and manual itinerary entries. Auto-imported e-receipts cross-referenced to entries.
Start location, end location, route, total miles, vehicle type, per-mile rate, calculated reimbursement, route polyline (mobile GPS capture).
Location-based allowances (GSA US / published rates elsewhere), trip duration, meal-by-meal breakdown, partial-day proration, company-policy overrides.
Corporate-card T-feed transactions matched to expense entries. Amex, Visa, Mastercard. Match status, reconciliation flag, original T-feed payload preserved.
Multi-TB binary content with OCR metadata (merchant, amount, date, line items). SHA-256 hash verified end to end. Resolvable URL from any migrated entry.
Every rule that fired in Concur — rule ID, trigger reason, severity, override decision, override approver, override justification. Compliance defensibility critical.
Every approver, every action (approve/return/comment), every timestamp, every comment thread. Approval-chain reconstruction for SOX and audit.
Each stage has automated validation gates. Migration doesn't progress until prior-stage gates pass.
Catalogue Concur custom fields, custom expense types, custom audit rules, allocation rules. Map every Concur field to Fusion target field. Define exceptions and transformation rules.
Concur REST API extract of expense types, policy bands, audit rules, approval routing, cost-centre/project/account segment values. Reconcile against Fusion COA. Block migration if delta unresolved.
Full transactional extract: report headers, entries, allocations, attendees, itineraries, mileage, per-diems, card transactions, audit-rule evidence, approval history. Parquet staging with hash signing.
Multi-TB receipt-image extract streamed in parallel from Concur to Syntra archive. SHA-256 hash verified per image. OCR metadata preserved. Resolvable URL provisioned for every image.
Transform and load to Fusion Expenses staging. FBDI bulk load or REST API per entity. Reference data first, then headers, then entries, then substructure (allocations, attendees, etc.).
Row count parity, monetary sum parity, receipt-image integrity, allocation reconciliation, audit-rule evidence preservation. All five must pass for sign-off. Failures investigated and resolved before cutover.
Each is recoverable but each costs weeks of project time when it surfaces late. Syntra's concur expense data migration approach catches all six in discovery.
Migration preserves transaction amount and organisation amount but drops the FX rate at transaction date. FX gain/loss analytics breaks. Caught in discovery if all three currencies are scoped explicitly.
Migration ports the expense entry but skips the attendee list. FCPA review of historical entertainment becomes impossible. Caught by explicit attendee entity scope.
Sum of allocation splits doesn't equal parent entry amount post-migration. Cost-centre rollups in Fusion don't match Concur source. Caught by allocation reconciliation validation.
Some receipt images don't migrate (oversize files, retry exhaustion, corrupted source). Caught by SHA-256 hash integrity check on every image — gap investigated and re-fetched.
Migration ports the report header and entries but skips the audit-rule trigger detail. Compliance defensibility breaks. Caught by audit-rule evidence preservation validation.
Migration ports the report-level approver but skips the per-action approval history. SOX approval-chain reconstruction breaks. Caught by approval history validation.
Concur expense data migration moves the full Expense data model from SAP Concur to Oracle Fusion Expenses: expense report headers (employee, purpose, dates, totals, status), expense report entries (line-level: expense type, amount, currency, transaction date, vendor, location), expense distributions (cost-centre, project, account, segment values), allocations (split percentages, multi-cost-centre rules), attendees (business meal participants with role classification), itineraries (per-leg lodging, meals, mileage), corporate-card transactions (matched to entries via T-feed), receipt images (multi-TB binary content with OCR metadata), audit rule evidence (which rules fired, override approvals), approval chain history (every approver, every action, every timestamp), comments and exceptions. Concur expense data migration also covers reference data — expense types, policy bands, audit rules, approval routing — needed to reconcile historical data against Fusion.
Three structural differences. (1) Receipt-image volume — Concur expense data migration carries multi-TB of binary receipt images that no other migration class typically does. Streaming, chunking, retry and integrity-verification design is harder. (2) Currency complexity — every expense entry can have a transaction currency, a reimbursement currency and an organisation currency, with FX rates captured at the transaction date and the report-submission date. Concur expense data migration has to preserve all three rates per entry or downstream FX gain/loss analytics breaks. (3) Audit-rule evidence — Concur Audit Service applies dozens of policy rules per report and the historical evidence (which rules fired, what the override justification was, who approved the override) is material for compliance defensibility and has to port intact to Fusion.
Header: report ID (Concur native + new Fusion ID with cross-reference), employee, purpose, business justification, report dates (start/end), report status (submitted/approved/extracted/paid), policy ID, currency, total reimbursable amount, total non-reimbursable, total claimed, total approved, exception count, audit-rule trigger summary, approver chain summary, submit/approve/extract/pay timestamps. Line: entry ID (Concur native + new Fusion ID), expense type, transaction date, transaction amount, transaction currency, reimbursement amount, reimbursement currency, organisation amount, organisation currency, vendor name, location (city/country), payment type (cash/card/personal-card), receipt-image cross-reference, audit-rule trigger details, comment threads, attendee references. Roughly 50–80 fields per entry depending on Concur configuration.
Allocations are how a single expense entry splits across multiple cost-centres, projects or accounting segments — e.g. a $1,000 conference fee 60% Cost Centre A and 40% Cost Centre B, or 100% to Project XYZ. Concur's allocation model is per-entry with percentage or fixed-amount splits and a flexible accounting-segment hierarchy. Concur expense data migration preserves the full allocation detail: each split as a row with parent entry reference, split percentage, split amount, target cost-centre/project/account segment values, and any allocation rule reference. Fusion Expenses models allocations similarly so the port is functionally clean. Reconciliation: sum of allocation splits = parent entry amount, validated on every migrated entry.
Concur captures attendees on business meals and entertainment expenses — internal employees, external attendees (with name, company, title, relationship classification: customer/prospect/partner/government), and attendee role (host, participant). This is material for IRS Pub 463 substantiation and for FCPA-sensitive entertainment review. Concur expense data migration carries the full attendee list per applicable entry: internal attendees cross-referenced to employee ID, external attendees with their captured profile, role on the expense, and any FCPA-flagged classification. Fusion Expenses supports the attendee model similarly. Compliance reviewers querying the migrated archive get the full attendee detail for downstream FCPA, government-official-interaction and customer-entertainment review.
Mileage: Concur captures start location, end location, route, total miles, vehicle type, per-mile reimbursement rate (IRS standard or company-specific), calculated reimbursement and any waypoints. Concur expense data migration preserves the full mileage detail including the route polyline if captured via mobile GPS. Per-diems: Concur models per-diem allowances with location-based rates (GSA in US, equivalent published rates elsewhere), trip duration, meal-by-meal calculation (breakfast/lunch/dinner/incidentals) and partial-day proration. Migration preserves the per-diem entry detail including the location-rate reference, the calculation breakdown and any company-policy overrides. Fusion Expenses models both similarly with a clean mapping path.
Three currencies per entry, always preserved. Transaction currency: the currency the expense was actually incurred in (e.g. JPY for a Tokyo hotel). Reimbursement currency: the currency the employee is reimbursed in (e.g. USD for a US-based employee). Organisation currency: the currency the company reports in (e.g. EUR for a Frankfurt-headquartered company). Concur captures FX rate at transaction date and at report-submission date for each conversion. Concur expense data migration preserves all three currencies, both FX rates, the calculation method (Concur-provided vs manually overridden) and any FX gain/loss flag. Downstream analytics on transaction-currency vs organisation-currency requires this detail intact, and Concur expense data migration that loses any of it produces broken FX gain/loss reporting in Fusion.
Five validation layers, all automated. (1) Row count parity — Concur source row count = Fusion target row count per data class per fiscal period. (2) Monetary sum parity — sum of transaction amounts, reimbursement amounts and organisation amounts match within $0.01 across the migration window. (3) Receipt-image integrity — every receipt image SHA-256 hash matches between Concur and the Syntra archive; resolvable URL from migrated entry returns the original binary. (4) Allocation reconciliation — sum of allocation splits = parent entry amount on every migrated entry. (5) Audit-rule evidence preservation — every audit-rule trigger that fired in Concur is present in the migrated record with original rule ID, trigger reason and override decision. Concur expense data migration sign-off requires all five passing.
Syntra ETL's concur expense data migration delivery covers the full Concur expense data model — twelve entity classes, three currencies, multi-TB receipt images, audit-rule evidence and approval history — with five-layer automated validation. Zero data loss; defensible against any auditor inquiry.