Concur rolled out a major update to its mobile app, focusing on smarter authentication and streamlined access for business travelers. This update tightens security while reducing friction at every login point.
The redesign aligns with current travel industry standards, ensuring that professionals can check in, manage expenses, and book trips with greater confidence on the go.
| Login Method | Security Level | Typical Authentication Time | Device Support |
|---|---|---|---|
| Password + SMS OTP | Medium | 8–12 seconds | iOS, Android |
| Biometric + Push Approval | High | 3–5 seconds | iOS, Android |
| Federated SSO (SAML/OIDC) | High | 5–7 seconds | iOS, Android, Web |
| Hardware Token + PIN | Very High | 10–15 seconds | iOS, Android (near field) |
Enhanced Identity Verification in Concur Mobile
The update introduces adaptive risk-based authentication that evaluates sign-in context such as location, device posture, and network behavior. Travelers signing in from a recognized device and stable network experience faster flows, while unusual patterns trigger additional verification.
This approach balances strong governance with day-to-day usability, letting consultants and frequent flyers move swiftly through airport check-in or hotel booking steps without repeated interruptions.
Streamlined Trip Onboarding Experience
Beyond login, the Concur mobile app update simplifies trip onboarding with clearer summaries of approvals, per diem rules, and receipt expectations. Each itinerary now highlights action items up front, so travelers know exactly what to submit or confirm before departure.
Booking flows have been optimized to reduce taps, while prominent calls-to-action guide users from search to confirmation in fewer steps, improving completion rates for last-minute arrangements.
Improved Security and Policy Enforcement
Security enhancements include stricter session timeouts, just-in-time elevation for sensitive actions, and continuous validation of device compliance. These controls help enterprises enforce travel policies without adding unnecessary burden at every interaction.
IT administrators gain better visibility into authentication events, making it easier to detect anomalies, respond to potential breaches, and maintain alignment with corporate risk frameworks across regions.
Operational Reliability and Performance
The updated app benefits from improved backend routing and optimized asset delivery, resulting in more consistent performance across regions. Travelers in time-sensitive situations, such as airport lounges or customer offices, experience fewer loading interruptions and quicker data sync.
Comprehensive availability monitoring and staged rollouts ensure that issues are caught early, allowing support teams to keep downtime minimal during critical travel windows.
Adopting the Updated Concur Mobile Authentication Flow
- Enable biometric or push-based approval for faster, more secure access.
- Review device compliance settings to ensure smooth adaptive authentication.
- Test SSO integration before travel to confirm seamless sign-in under company policies.
- Monitor session timeouts and adjust per-diem or approval rules to match your travel cadence.
- Keep the app updated to benefit from security patches and performance improvements on the road.
FAQ
Reader questions
Will I need to re-authenticate more often after the update?
Not necessarily. Adaptive risk-based authentication may maintain longer sessions on trusted devices, while it requests re-verification only when context changes or risk indicators appear.
Can I use my corporate SSO to sign in to Concur on my phone?
Yes, federated SSO is fully supported, letting you sign in with your company identity provider using the same credentials you use on the web.
What happens if I travel to a region with limited connectivity at login?
You can still authenticate when online, and the app caches essential trip details so you can access key details offline until you reconnect.
Are older devices still supported after the new login methods are introduced?
Devices running the minimum supported operating system versions are still supported, though some advanced authentication methods may require newer hardware features like biometric sensors.