SAP Concur is the enterprise standard for travel and expense management, used by thousands of mid-market and large companies to manage employee travel booking, expense reporting, and invoice processing. It exposes integrations through the SAP Concur partner portal using OAuth 2.0.
Pull submitted, approved, and paid expense reports with line items, merchant details, amount, and GL allocation. Create new expense reports or update line items from your finance or ERP product.
Read confirmed flight, hotel, and car rental bookings from Concur Travel. Use this to correlate travel costs with projects, clients, or cost centers in your analytics or project-accounting product.
Pull itemized receipt data and attached receipt images from Concur expense reports. Useful for AP-automation products that need to validate receipts against card statements or reimbursement requests.
Pull aggregated spend by cost center, employee, merchant category, and time period. Askel handles Concur's reporting API so your product can pull summary spend data without reading every expense report individually.
Read Concur user profiles, assigned cost centers, and delegate permissions. Use this to provision users in your product automatically when they are added to Concur, or to validate that the correct approver hierarchy is configured.
Pull vendor invoices processed through Concur Invoice including approval status, payment method, and GL coding. Useful for ERP reconciliation products that need to match Concur payments against the GL.
Irongate Project Partners uses SAP Concur for all employee travel and expense management and tracks project costs in your project-accounting platform. Project managers need to see approved Concur expense reports coded to their projects appear in the platform automatically so they can track actual spend against project budgets without waiting for month-end exports.
Irongate's Concur administrator logs into the SAP Concur partner portal, creates an OAuth application for Askel, and requests access to the Expense, Travel, and User API scopes. SAP Concur's team reviews and approves the application. The admin notes the client ID and client secret.
Irongate's admin enters the Concur data center URL (us.api.concursolutions.com), client ID, and client secret into the Askel setup screen inside your project-accounting platform. Askel initiates the OAuth consent flow and Irongate's Concur admin approves access. Askel confirms connectivity by fetching the user list.
Askel reads the available Concur API objects and identifies ExpenseReport, ExpenseEntry, Itinerary, and User resources along with the GL allocation codes and cost object fields Irongate has configured in Concur. Your CS team sees a mapping draft within minutes.
Irongate uses Concur's custom allocation fields to tag expenses to project codes. A CS rep maps the Concur project code allocation field to the accounting platform's project dimension and runs a dry-run against the prior month's approved expense reports to confirm costs land on the correct projects.
The daily expense sync is enabled. When a Concur expense report is approved and paid, Askel pulls the report and its line items into Irongate's project-accounting platform. Project managers see approved travel and expense costs posted to their projects the morning after approval.
The customer's Concur administrator registers an OAuth application in the SAP Concur partner portal and requests the required API scopes. After SAP Concur approves the application, the admin provides the client ID and client secret to Askel. Askel completes the OAuth consent flow, stores the access and refresh tokens, and refreshes them automatically.
© 2025 Askel.ai. All rights reserved.