Self-serve historical lookups for finance, audit, tax and compliance — expense reports per FY, vendor spend, employee category, VAT recovery, FCPA review. Sub-second SQL/REST against queryable Parquet archive. No Concur subscription required.
Once live T&E moves to Oracle Fusion Expenses, the live Concur tenant exists only to answer historical questions. Concur historical reporting replaces that tenant entirely — at a fraction of the cost.
Concur — acquired by SAP in 2014 — uses per-active-user pricing that punishes any tenant kept alive solely for historical access. Finance asks closed-period spend questions monthly. Internal Audit walks SOX expense controls quarterly. Tax queries IRS Pub 463 substantiation annually. Legal asks FCPA review questions on demand. Each of those interactions hits maybe 1% of the tenant's data — and yet the full subscription remains payable for the privilege.
Syntra ETL's concur historical reporting flips the model. Every Concur expense report, receipt image, itinerary, corporate-card transaction and Invoice record archived to cloud object storage in Parquet, queryable through a standard SQL interface that any BI tool already knows. Finance runs spend rollups in Tableau. Audit pulls policy-violation analysis in Power BI. Tax runs VAT recovery queries in Alteryx. Legal pulls FCPA-flagged spend in Looker. Every query logged for SOC 2 audit, every receipt-image drill-down satisfying IRS Pub 463 substantiation.
And because the archive is multi-tenant by design, M&A scenarios where multiple legacy Concur tenants need consolidated historical reporting work natively — a single SQL query across parent and acquired-entity expense history, partitioned by tenant_id for fast filtering.
Standard SQL templates ship pre-loaded, covering the Cognos-equivalent reports that finance and audit teams ran most often on Concur.
Total reimbursable amount and entry counts broken down by fiscal year and business unit. Pre-built drill from rollup to expense report to entry to receipt image.
Ranked employee expense totals per fiscal year, with category breakdown (airfare, lodging, meals, entertainment) and policy-violation flags.
EU/UK VAT-recoverable amount by member state by quarter, with receipt-image substantiation drill and vendor VAT registration validation.
Spend tied to government-official interactions, gift logging, sensitive-vendor categories — FCPA and ABAC review-ready with audit-rule trigger evidence.
Corporate-card T-feed transactions without matching expense entry — historical chargeback dispute resolution and unmatched-charge investigation.
Department × policy-rule heatmap showing violation frequency, override pattern and approver chain — feeds policy-design review and training prioritization.
From discovery to first auditor self-serve query, typically 4–6 weeks.
Identify the user groups (finance, audit, tax, legal, HR) and the report categories each needs. Map to role-based access: who sees what, who can drill to receipt images, who can see executive-level data.
Concur REST extractors pull every in-scope expense report, receipt image, itinerary, corporate-card transaction and Invoice record. Stage as Parquet partitioned by fiscal year, period and business unit. Multi-TB receipt-image archives streamed in parallel.
SQL endpoint (JDBC/ODBC) and REST API provisioned. Pre-built saved queries materialized for the standard 30–50 audit/finance/tax/legal report templates. Role-based access enforced at the query-engine layer.
User-facing BI tools (Tableau, Power BI, Alteryx, Looker, Excel/Smart View) connected to the SQL endpoint with appropriate service-account credentials and row-level security. Existing user dashboards re-pointed to the archive.
User group walkthroughs (one per group, typically 60–90 minutes). Cognos report equivalence mapping. Concur tenant moves to read-only; new historical queries route to the archive. Concur subscription cancellation scheduled.
Six concrete advantages — measured in dollars, speed, governance and risk reduction.
Concur per-active-user subscription cancelled in full. Mid-large customers save $200K–$1.5M annually.
Auditor queries return in sub-second; multi-year aggregations in 3–20 seconds. Materially faster than Concur Cognos for typical historical reporting workload.
Standard SQL means Tableau, Power BI, Alteryx, Looker and Smart View all work without translation. No Cognos report-developer dependency.
Every query, every receipt-image fetch, every drill-down logged with user, timestamp, scope and result. Logs ship to SIEM via syslog or CloudTrail.
Single unified query layer across 50+ legacy Concur tenants from acquired entities — same SQL, same role model, partitioned by tenant_id.
Finance, audit, tax, legal and HR get separately scoped roles. FCPA-flagged data gated behind compliance-only access. Receipt images masked by default for non-substantiation queries.
Concur historical reporting is the ability for finance, audit, tax and compliance teams to query historical Concur expense data — expense reports, receipts, itineraries, corporate-card transactions and Invoice records — without keeping the live Concur tenant running. After migrating live T&E to Oracle Fusion Expenses or decommissioning Concur entirely, organizations still need to answer auditor questions: 'What did this executive expense during FY22?'; 'How much VAT did we reclaim across the EU in 2023?'; 'Show all expenses tied to vendor X for FCPA review.' Syntra ETL's concur historical reporting exposes this via SQL/REST against a queryable Parquet archive with sub-second response for typical queries — replacing the need for a live Concur subscription.
Five primary user groups: (1) Finance, for closed-period spend analysis, accruals tie-out and prior-period comparatives; (2) Internal Audit, for SOX walkthroughs, expense-pattern review and policy-violation investigation; (3) Tax, for IRS Pub 463 substantiation, state nexus analysis, VAT recovery (EU/UK), 1099-MISC and 1099-NEC contractor expense substantiation; (4) Legal & Compliance, for FCPA review, ABAC anti-bribery review, regulatory-filing support and litigation hold response; (5) HR & Executive Comp, for executive expense disclosure prep, severance reconciliation and equity-grant context. Each group gets role-scoped access with separate audit logging — finance never sees the FCPA legal-review queries, legal never sees the HR comp queries.
Concur's historical reporting layer was Cognos-based after the SAP acquisition in 2014 — limited to predefined report templates, requires Concur subscription to run, runs in the Concur UI only. Syntra ETL's concur historical reporting is SQL-native against your own cloud — standard ANSI SQL through JDBC/ODBC, any BI tool (Tableau, Power BI, Alteryx, Looker), zero Concur subscription dependency, and queryable by your existing data team using their existing tooling. Pre-built saved queries cover the most common Cognos report equivalents (top-spender analysis, policy-violation heatmap, VAT recovery by quarter) so the migration from Cognos to Syntra is conceptually a one-day knowledge transfer for the report-consumer team.
Yes. The archive preserves Concur's original receipt-image-id as a stable cross-reference, so any historical query that returns an expense entry includes the resolvable URL to the original receipt image (JPG/PNG/PDF) plus the OCR metadata. The image fetch is gated by role-based access (finance vs audit vs tax vs legal) and logged for SOC 2 audit. For IRS Pub 463 substantiation, the drill returns: expense entry detail, receipt image, OCR'd merchant and amount, and the audit-rule trigger evidence (if any rule fired at submission time). This satisfies the substantiation requirement that an auditor be able to retrieve the original receipt in seconds, not days.
Anything you would have asked of a live Concur tenant: total T&E spend by business unit by fiscal year; top spenders ranked by reimbursable amount; expense categorization rollups (airfare vs lodging vs meals vs entertainment); policy-violation rate by department; VAT-recoverable amount by EU member state by quarter; corporate-card reconciliation gaps; FCPA-flagged spend tied to government-official interactions; mileage-reimbursement totals by employee; cash-advance aging by reportee; per-diem usage vs limit by location. Pre-built saved queries cover the standard 30–50 audit, finance and tax reports. Custom queries are just SQL — no Cognos report development cycle, no Concur consulting engagement.
As long as your retention policy requires — typically 7 years for IRS Pub 463 and SOX, 6+ years for EU/UK VAT, effectively indefinite for FCPA-flagged data. Syntra ETL's archival policies are configurable per domain and per retention regime, so receipt images covering executive-level FCPA-flagged spend can be retained indefinitely while routine meal-receipt data drops off after 7 years to control storage cost. The archive supports tiered storage classes (hot for current-year + prior-year, warm for 2–4 years back, cold for 5+ years back) without changing the query interface — auditors don't see the storage tier, just the data.
Yes. Customers who acquired companies running separate Concur tenants commonly archive each tenant separately, then expose a unified query layer where the same SQL works across all of them with a tenant_id column. This supports the M&A reconciliation use case where an acquiring company needs to see consolidated historical T&E across the parent and acquired entities for the years before they unified onto a single platform. The archive supports up to 50+ source Concur tenants in a single unified query layer, partitioned by tenant_id for fast filtering.
Yes. The archive's Parquet files can be queried directly from Athena, BigQuery, Snowflake or Spark — no copy needed. Or you can use the Syntra extractor to push a curated subset to your warehouse on a scheduled basis (daily, weekly, monthly), with deduplication and slowly-changing-dimension handling for the expense_reports, expense_entries, receipts and corporate_card_transactions tables. This is the common pattern when concur historical reporting feeds a single source-of-truth dashboard alongside Fusion Expenses operational data — same KPIs, before and after the Concur cutover, no break in the time series.
30-minute discovery call. We'll walk through your user groups, report inventory and retention requirements — and quantify the Concur subscription savings you'd see in year one.