Confirm that the Concur account has the Travel Allowance module enabled; this API is not available to all Concur configurations and has geographic restrictions for certain features
Obtain a company-level access token; the Travel Allowance v4 API requires company token authentication, not individual user tokens
Call the Expense Report v3 API first to retrieve the target expense report ID, as the Travel Allowance API operates against an existing report
GET the travel allowance days endpoint using the report ID to retrieve the fixed allowance days and associated meal deduction breakdowns calculated by Concur
Parse the itinerary segments in the response to identify departure and arrival locations and durations that drove the per-diem calculation
Surface the allowance amounts and any mandatory meal deductions in your expense workflow UI so travelers can verify before submitting the report
Known gotchas
The fixed-allowance-days endpoint is documented as available only for Finland customers in some API versions; verify scope and availability with the Concur account team before building against it
Per-diem rates in Concur are configured by travel policy administrators and pulled from rate tables, not a live government feed; out-of-date rate tables in the tenant produce incorrect calculations silently
You must call the Report v3 API to get the report ID before calling Travel Allowance v4; there is no direct lookup by traveler or date range
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp