Data Panda brings your SAP Concur data together with the data from the rest of your business. From one place, we turn it into dashboards, automations, AI workflows and custom apps your team uses every day.
Concur Technologies was founded in 1993 in Bellevue, Washington by Steve Singh, Rajeev Singh and Mike Hilton, went public on NASDAQ in 1998, and was acquired by SAP in September 2014 in a deal that closed in December 2014 at 8.3 billion dollars. The product line covers three modules that most enterprises buy together: Concur Expense for expense reports and corporate-card reconciliation, Concur Travel for booking and itinerary management, and Concur Invoice for accounts payable. The customer base sits squarely in the Fortune 500 and the wider large-enterprise segment, with a long tail of mid-market accounts that inherited the platform through an SAP relationship.
SAP Concur is rarely the system finance teams talk about with affection, but it is the system the data lives in. Submitted expense reports, individual expense entries with their attendee and project allocations, audit-rule violations, approver queues, traveller itineraries with hotel and flight segments, supplier invoices and three-way-match status, employee profiles with their cost centre and country, and per-card transaction feeds all sit inside Concur before anything reaches the ledger. Pulling that into a warehouse is how a CFO answers questions the Concur dashboards never line up: out-of-policy expense rate per region, approval-cycle drift per approver, audit-rule false-positive rate per rule, and travel cost per traveller class set against the deals or projects the trips were booked for.
Out-of-policy rate, approval drift and audit false positives on one cut, next to GL actuals.
Keep Concur aligned with the ledger, the CRM and the travel and HR systems around it.
Use Concur history for audit-rule tuning, fraud screening and travel-spend work the standard packs do not draw.
Internal tools on Concur data for people who should not need a Concur seat.
A list of concrete reports, automations and AI features we have built on SAP Concur data. Pick the one that matches your situation.
Which audit rules are catching fraud and which are just teaching approvers to click through?
Per audit rule, the share of flagged expense lines that ended up rejected versus approved as filed, split by region and report type. Rules with a false-positive rate above ninety percent get retired or rewritten, so the audit queue stops being noise the approvers route around.
Where is the approval cycle quietly drifting out per approver?
Median and ninetieth-percentile days from submission to approval per approver, per cost centre and per report type, with the bottleneck approvers at the top. The conversation moves from a generic reminder about month-end close to a list of three approvers and two regions where reports sit longest.
What does the average customer-facing trip really cost us per closed-won deal?
Travel cost per traveller class on customer trips, joined to the Salesforce account and opportunity the trip was coded against. Cost-of-sale per account stops being a generic T&E line and becomes a per-deal number that survives a QBR.
Out-of-policy rate, approval-cycle days, audit false positives and three-way-match success refreshed daily, with the Concur workflow data sitting next to the ERP actuals. Month-end accruals stop being a guess about which expense reports and invoices will land in time, and the audit-rule library gets tuned on numbers instead of intuition.
Customer-facing travel and entertainment in Concur joined to the Salesforce accounts and opportunities the trips were booked against. The deal that consumed three flights and a steakhouse dinner shows up next to closed-won, so cost-of-sale per account is a real number rather than a generic T&E bucket.
Travel cost per traveller class, hotel-chain consolidation and per-business-unit policy-violation rate visible per site and per booker. Operations leads catch the region quietly booking business class and the supplier whose invoices keep failing the three-way match before the next quarterly review names them.
Approved expense reports and three-way-matched Concur Invoice transactions post into Sage Intacct as journal entries with location, department and project dimensions filled in. Reimbursable totals, card clearing and supplier payments land in the GL within hours, so month-end stops waiting on a manual Concur export.
For groups running Dynamics 365 F&O as the enterprise ERP, Concur expense reports, traveller itineraries and invoices flow into the right legal entity in F&O with cost centre, project and product dimensions filled in. Concur stays the system of record for travel and expense workflow, F&O stays the ledger, and the two stop diverging on open commitments and supplier master.
Concur trips and expense reports tagged to a customer or prospect are matched to the Salesforce account and opportunity they were booked against, on traveller, attendee and date. The dinner, the demo flight and the conference badge land on the account timeline, so cost-of-sale per account is visible to the AE who owns the deal rather than buried in a quarterly T&E summary.
Expense reports and Concur Invoice payment requests above a configured threshold trigger an approval prompt in the relevant Slack channel or DM, with submitter, amount, audit-rule hits and cost-centre coding on the card. The approver decides in Slack, the answer flows back into Concur, and the approval queue stops waiting on email reminders to clear.
You keep the reporting tool you already have. We connect it to the warehouse where your SAP Concur data lives.
OAuth authentication. Read-only by default. We sign a DPA and your admin keeps the keys.
Data flows into your warehouse on your schedule. Near real time or nightly, your call. You own the data.
We build the first dashboard, workflow or AI feature with you, then hand over the keys. Or we stay on for ongoing delivery.
We set up the foundation. Your team builds on top.
Best fit Teams that already have a BI analyst or data engineer and want to own the build.
We build the whole thing, end to end.
Best fit Teams without in-house BI or dev capacity. You tell us what you need and we deliver it.
You do. It lands in your warehouse, on your cloud account. We don't resell or aggregate it. If you stop working with us, the warehouse stays yours and keeps running.
Near real time for most operational systems. For heavier sources we schedule hourly or nightly. You pick based on what the reports need.
No. If you don't have one, we help you pick one and set it up as part of the first delivery. Common starting points are Snowflake, Microsoft Fabric, or a small Postgres start.
The connector reads the surface that Concur exposes through its API: expense reports and entries, allocations, attendees, cash advances, corporate-card transactions, traveller itineraries with bookings, Concur Invoice payment requests and purchase orders, suppliers, employees and the cost-centre and project lists behind them. Add-on packs like Concur Detect or Compleat are not part of the standard pull and get scoped separately if your tenant uses them.
A T&E migration off Concur typically takes twelve to eighteen months at large-enterprise scale, and during that window finance still needs the historical data to answer audit and forecasting questions. Pulling Concur into a warehouse decouples the reporting layer from the source system, so the day you cut over to Brex, Ramp or TravelPerk, the dashboards keep working and the historical T&E baseline stays queryable next to the new source.
We review your SAP Concur setup and the systems around it. Together we pick the first thing worth building.