Guides
SAP Concur expense approval: see where each expense report waits
Connect SAP Concur to Duaer. It reads each expense report's steps, from submission through manager and finance approval to payment, so you see where reports wait and for how long.
What does Duaer read from SAP Concur?
Each expense report is a case, with the submitter, department, currency and amount. The steps are:
- Submitted, Manager approved, Finance approved, Paid.
- The steps match the expense approval template, so the boards in My processes on the employee portal work as they are.
How do you connect SAP Concur to Duaer?
- In SAP Concur, register an application for the company and get the client ID, the client secret and a company-level refresh token (exchanged from a company request token).
- In Duaer, create an SAP Concur API credential with the API host (for example us2.api.concursolutions.com), the client ID, the client secret and the refresh token.
- As an owner or admin, open Data sources, select Add source, choose SAP Concur under Expense approval, choose the credential, select Check connection and confirm.
How often does it read, and how much?
Each run lists expense reports by modification time and reads each report's approval history; a first read starts two years back and finishes over several runs. A step is never written twice. Read only: Duaer never writes to Concur.
What are the limits?
- The tables, views, models and fields read follow the vendor's published documentation and are not yet checked against a real system; the first real read may need adjustments.
- Expense reports only; travel bookings and Concur Invoice are not read.
Questions
How are manager and finance approval told apart?
By the role in the approval history: an approval by an expense processor, accounting, audit or finance role is finance approval, any other is manager approval. Without a finance approval, the date the report went to payment processing is used.
In this section
Add a process source in Duaer
A process source tells Duaer where to read the steps of your cases: a CSV or XLSX file, files dropped in an S3 or SharePoint folder, PostgreSQL, MySQL, Microsoft SQL, Oracle, TiDB, OceanBase, KingbaseES, SAP HANA, IBM Db2, Dameng DM8, Teradata, Vertica, Snowflake, BigQuery, Databricks, Microsoft Fabric, Amazon Redshift, Azure Synapse Analytics, ClickHouse, Trino, a Feishu Base, or Feishu, DingTalk or WeCom approvals. The wizard takes you through columns, mapping, a preview of issues and a schedule; after you confirm, Duaer reads new rows on that schedule.
ProcessSee the process in your data and generate workflows in Duaer
Duaer reads the steps every case went through from the tables, databases or Feishu apps you already have: where cases wait too long, where they branch and who did each step. From that it generates three kinds of workflow, Watch, Coordinate and Execute, and replays each over past days before you publish it.
ProcessProcess findings and SOP conformance in Duaer
Process findings list the steps where cases wait too long or are done again, and which kind of case they happen to most. Propose any of them as a card rule and compare the 30 days before and after it was adopted. SOP conformance compares the SOP in your knowledge base with the steps cases really took.
Follow-throughWorkday purchase to pay: see where each purchase order waits
Connect Workday to Duaer. It reads the requisitions, receipts, supplier invoices and payments of each purchase order through Workday Web Services, so you see where orders wait and for how long.
Follow-throughCoupa purchase to pay: see where each purchase order waits
Connect Coupa to Duaer. It reads the requisitions, receipts, invoices and payments of each purchase order through the Coupa Core API, so you see where orders wait and for how long.