Approved Concur expense reports flow to Fusion Payables for reimbursement — invoice creation, employee-vendor handling, GL distributions, project costing, VAT recovery. Batch or near-real-time. 3–8 business days from filing to bank account.
Without this integration, finance teams export from Concur and re-key into Payables manually. With it, approved expense reports become Payables invoices and bank payments automatically — 3–8 business days end to end.
SAP Concur — acquired by SAP in 2014 — sits in front of the expense-filing experience: employees file, managers approve, audit rules check policy compliance. Oracle Fusion Payables sits behind the reimbursement experience: invoice created, payment batch run, bank file generated, ACH settlement to employee. The two have to talk. Concur to oracle payables integration is the data and process flow that makes the reimbursement loop close.
Three stages. Extract: Concur REST API v3/v4 pulls approved-and-not-yet-extracted expense reports with their entries, distributions, allocations, attendees and supporting metadata. Transform: data maps to the Fusion Payables invoice structure — expense report becomes invoice header against the employee vendor record, expense entries become invoice lines with cost-centre/project/account distribution values, allocations become invoice distribution splits. Load: FBDI bulk import (AP_INVOICES_INTERFACE_ALL + AP_INVOICE_LINES_INTERFACE) or REST API creates the invoice in Fusion Payables. Next payment batch picks it up; reimbursement lands in the employee's bank account 1–2 business days later.
Syntra ETL builds and operates concur to oracle payables integration for customers running Concur in front of Fusion ERP — typically a 3–4 week build with steady-state operation thereafter. The integration handles employee-vendor sync, payment terms, GL distributions, project costing, VAT recovery and the full operational concerns (error handling, retry, reconciliation, monitoring) finance teams need to trust the flow. It's also a common interim architecture during Concur to Fusion Expenses migration projects — letting finance keep paying employees normally while the new Fusion Expenses tenant is built and tested.
Six operational concerns the integration covers so finance teams can trust the flow.
Pre-sync nightly HCM-to-Payables vendor creation or inline just-in-time vendor creation. Bank details, address, payment terms inherited from supplier defaults.
Expense report becomes Payables invoice header against employee vendor. Entries become invoice lines. Allocations become distribution splits. FBDI bulk import or REST.
Cost-centre, account, department segments carry from Concur expense entry to Payables invoice distribution. GL journal entry posted on payment.
Project segment from Concur allocation carries to Payables distribution. Fusion Project Accounting picks up as project transaction during next cost collection cycle.
Concur tax detail (VAT amount, recovery percentage, jurisdiction) carries to Payables. Fusion Tax computes reclaimable VAT. EU/UK VAT recovery programmes supported.
Daily reconciliation: Concur extracted reports = Fusion Payables created invoices. Variance flagged for investigation. Receipt-image cross-reference preserved for audit drill.
From discovery to steady-state operation, typically 3–4 weeks for the integration build plus ongoing managed operation.
Catalogue Concur custom fields, accounting segments, allocation rules, employee population. Map to Fusion COA, Payables supplier model, project structure. Design employee-vendor sync pattern.
Build HCM-to-Payables nightly sync (or inline alternative). Vendor creation, update, deactivation. Bank-detail handling with appropriate security. Payment-terms and payment-method defaults.
Concur REST extract job, mapping layer, Fusion Payables FBDI or REST load. Error handling, retry, idempotency. Test against representative sample of expense reports.
Daily reconciliation report (Concur extracted vs Fusion created). Monitoring alerts on integration failure, retry exhaustion, mapping error. Dashboard for finance team visibility.
Finance team UAT with full expense-to-payment flow on UAT environment. Reconciliation sign-off. Production cutover plan agreed including rollback criteria.
Production concur to oracle payables integration live. Daily reconciliation. Monthly close support. Syntra-managed operation with SLA on extract latency, invoice creation success rate and reconciliation completion.
Six concrete benefits over manual export-and-rekey or one-off integration efforts.
5–8 business days filing to bank account (3–4 days for premium daily-cycle customers). Manual export-and-rekey typically runs 10–15 business days with error rework.
Re-keying errors (wrong cost-centre, transposed amount, missed line) eliminated. Auto-validation catches data quality issues before invoice creation. Materially fewer reimbursement disputes.
End-to-end traceability — every Concur report ID cross-referenced to Fusion invoice ID. Approval chain preserved. Receipt-image drill from Payables. SOX walkthrough trivial.
Project allocations from Concur reach Fusion Project Accounting automatically. Project managers see expense load in near-real-time. No month-end true-up exercise.
Concur tax detail flows to Fusion Tax for VAT reclaim computation. Material recovery in EU/UK programmes — typical reclaim 5–15% of in-scope spend recovered automatically.
Common interim architecture during Concur to Fusion Expenses migration. Lets finance keep paying employees normally while new Fusion Expenses tenant built and tested.
Concur to oracle payables integration is the data and process flow that takes approved SAP Concur expense reports and pushes them into Oracle Fusion Payables for reimbursement — creating expense invoices against employee vendor records, generating payment batches and posting GL entries on payment. Customers running SAP Concur for T&E and Oracle Fusion ERP for finance need this integration to close the loop: expense filed and approved in Concur becomes a real payment in Fusion Payables, with reimbursement landing in the employee's bank account. Without it, finance teams export from Concur and re-key into Payables manually — error-prone, slow, and a control weakness most internal audit teams flag. The integration runs as a scheduled batch or near-real-time flow depending on payment SLA.
Three-stage flow. (1) Extract: Concur extract job (REST API v3/v4 with OAuth2, or Concur's Extract service) pulls approved-and-not-yet-extracted expense reports — report header, entries, distributions, allocations, attendees and supporting metadata; (2) Transform: data is mapped to Fusion Payables invoice structure — expense report becomes invoice header (employee vendor, invoice number, invoice date, total), expense entries become invoice lines with distribution segment values, allocations become invoice distribution splits; (3) Load: Fusion Payables invoice creation via FBDI bulk import (AP_INVOICES_INTERFACE_ALL + AP_INVOICE_LINES_INTERFACE) or REST API. Invoice import workflow validates, creates the invoice, and the next payment batch picks it up. Concur to oracle payables integration runs the full cycle in under 15 minutes for typical batch size.
Employees who file expenses need to exist as Supplier (vendor) records in Fusion Payables before any invoice can be created. Concur to oracle payables integration handles this in two ways depending on customer preference: (1) Pre-sync — HCM-to-Payables employee-vendor sync job runs nightly, creating or updating vendor records for every active employee with bank-detail and address information; or (2) Inline — the integration creates the vendor record just-in-time when the first expense report arrives for an employee without one. Pre-sync is the more common pattern because it separates the master-data sync from the transactional integration, simplifying troubleshooting. Either way, the employee-to-vendor mapping is preserved as a stable cross-reference for ongoing concur to oracle payables integration runs.
Payment terms (Net 0, Immediate, Net 7 etc.) and payment methods (ACH, wire, cheque) are configured per employee vendor record in Fusion Payables — typically inherited from supplier defaults set during the employee-vendor sync. The expense report itself doesn't carry payment terms; concur to oracle payables integration relies on the vendor-side configuration. For special cases (e.g. urgent reimbursements, executive expense priority handling), the integration can override default payment terms at invoice creation by reading a Concur-side priority flag and applying a faster term. Payment method override works similarly. Most customers keep the default terms simple — Immediate or Net 0 — because expense reimbursements are typically expected within 5 business days.
From employee submitting expense report in Concur to payment landing in employee bank account: typically 5–8 business days. Breakdown: expense filing to manager approval 1–2 days (employee-dependent); manager approval to Concur extract pickup up to 1 day (batch schedule); concur to oracle payables integration run 15 minutes to 2 hours (batch size dependent); Fusion Payables invoice validation and approval 1 day (auto-approve common for expense reports); payment batch run 1–2 days (typical weekly or twice-weekly cycle); ACH settlement 1–2 days. Premium customers running daily payment cycles and near-real-time concur to oracle payables integration land 3–4 business days end to end. The integration itself is rarely the bottleneck — approval and payment-cycle cadence drive total elapsed time.
GL distributions: the expense entry's accounting-segment values (cost-centre, account, department) carry through to the Fusion Payables invoice distribution lines. On payment, Fusion Payables creates the GL journal entry posting the reimbursement liability (debit) and bank account (credit) on the appropriate accounting segments. Project costing: if the expense entry was allocated to a project in Concur (via the project-segment value in distributions), concur to oracle payables integration carries the project reference through to the Payables invoice distribution. Fusion Project Accounting picks up the expense as a project transaction during the next project cost collection cycle — landing the expense on the project ledger. The flow is identical to a procurement-side project expense, so project managers see a consistent expense view regardless of origin.
Concur captures expense-level tax data — VAT-included indicator, VAT amount, VAT recovery percentage, jurisdiction. Concur to oracle payables integration carries the tax detail to Fusion Payables invoice distribution lines, allowing Fusion Tax to apply the appropriate tax determination and recovery rules. For VAT-reclaim scenarios (EU and UK), Fusion Tax computes the reclaimable VAT amount, creates the appropriate input-VAT transaction, and Fusion Receivables-side tax registration handles the reclaim filing. Use tax (US) is handled similarly with the tax jurisdiction driving the rate determination. Customers running material VAT recovery programmes value this integration depth — Concur's tax detail port to Fusion Tax is functionally clean.
Yes — and it's a common interim architecture. During a Concur to Fusion Expenses migration, customers often run the legacy Concur system through to Fusion Payables (via concur to oracle payables integration) while the new Fusion Expenses tenant is built and tested. This lets finance keep paying employees normally throughout the migration window without disrupting reimbursement. At cutover, expense filing moves from Concur to Fusion Expenses; concur to oracle payables integration is decommissioned because expense-to-payables is now native within Fusion. Syntra ETL builds and operates the interim concur to oracle payables integration as part of broader migration delivery — typically a 3–4 week build, then steady-state operation through the migration window.
Syntra ETL builds and operates concur to oracle payables integration for customers running Concur in front of Fusion ERP — 3–4 week build, steady-state managed operation, 5–8 day filing-to-bank-account cycle and full reconciliation coverage.