If the demo does not address all three perspectives, you will end up with a system that finance loves but employees circumvent.
It looks magical. But the magic often fades when real-world data enters the mix. concur software demo
For public companies or those with strict compliance needs (e.g., SOX or GDPR), the audit log is crucial. A polished demo shows the "happy path." You need to see the : an expense that was rejected, re-submitted, partially approved, and then audited six months later. Can you trace every single change, comment, and approval timestamp without exporting to a separate spreadsheet? If the demo does not address all three
By looking past the slick interface and focusing on exceptions, offline functionality, and real integration pain points, you will know whether Concur is a solution—or simply a newer, more expensive version of your current problem. For public companies or those with strict compliance
Bring a copy of your company’s actual chart of accounts to the demo. Ask the presenter to map a complex expense—one with a project code, a cost center, a class, and a custom approval matrix—from Concur into your ERP. Watch how many dropdowns and custom fields are required. If the demo requires a professional services engagement to solve mapping, you are looking at a 3-to-6-month implementation, not a 30-day rollout.
Too often, only the finance team watches the Concur demo. That is a mistake. You need three distinct audiences in the room (physical or virtual):
Perhaps the most glossed-over section of any Concur demo is the ERP integration. The demo will show a beautiful "Export to QuickBooks/SAP" button. What it won't show you is the middleware (often required) that maps custom fields between Concur and your ERP.