SAP Concur
Finance and operations
Sync SAP Concur expense, report, trip, and user data into your warehouse. Ingest builds this connector the first time a customer asks for it, then keeps the tables current in a data warehouse you own, on the schedule you choose.
The SAP Concur connector syncs your travel and expense management data into analytics-ready tables in your data warehouse. Pull expenses, reports, trips, and users from the SAP Concur API, with Ingest handling auth, pagination, and retries so the tables stay current.
What you would get
Each of these arrives as its own table, kept current on the schedule you choose:
- Expenses
- Reports
- Trips
- Users
How it gets built
- Choose SAP Concur when you set up a pipeline, with the warehouse it goes to and a schedule.
- Ingest reads SAP Concur's documentation, and you choose the tables you want.
- Ingest builds the connector and tests it against SAP Concur itself.
- A person at Ingest reviews and publishes it, and your pipeline starts on its own.
What you will need
OAuth 2.0. Not self-serve: contact your SAP Concur Partner Enablement Manager or Partner Account Manager to register an application before receiving a clientId/clientSecret.
You enter it once, in a form in Ingest, and it is kept in a secret store set aside for your organization.
Questions
- Does Ingest have a SAP Concur connector?
- Not as a finished connector yet. Ingest builds it from SAP Concur's own documentation the first time a customer asks, tests it against the real service, and lists it once it passes.
- Which warehouses can SAP Concur data go to?
- Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL and Snowflake, in an account you own.
- Do I need to write code?
- No. Ingest builds, runs and maintains the connector. Someone with access to your warehouse connects it once, following a short guide.
SAP Concur API documentation: https://developer.concur.com/api-reference/authentication/getting-started.html
Where this would land, and what else connects
Setting up the destination is its own short guide, one per warehouse or lake: Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL, Snowflake.
Other sources Ingest connects for ERP teams: SAP, Oracle NetSuite, Microsoft Dynamics 365, Workday, Odoo, Acumatica.