The application itself is pretty good, although if your implementation requires that you use AMEX, you end up with all the drawbacks of the American Express travel and card systems.

Where the application is strongest is in the area of currency translation and calculation, where the process is almost transparent for the user who submits charges in foreign currencies.

The application also has a good interface for selecting flights and hotels. Unless it is bound rigidly to the AMEX system, once the user submits proposed travel dates and times, the system returns a selection of appropriate options to choose from. This has two benefits.

First, it automates the itinerary selection and ticket purchase process, thus eliminating a "corporate travel" entity. In real terms this means you can avoid leaving for trips at stupid times, enduring ridiculous routings or excessively long connections.

Second, it provides options in terms of providers, and it seems to do a good job of providing a decent pricing. I have had team members who needed to work on a project in a specific location choose different carriers and routes according to their own preferences, and the cost differences where not significant enough for me to be concerned about overspending.

The downside in using it is the same as all applications, in that the deployment needs to be well run, otherwise the configurations selected upon implementation can serve the needs of the travelers and company less than perfectly.