When did anyone last look at your Concur configuration?

Almost nobody configures SAP Concur badly. It gets configured carefully, for the business as it was at go-live, by people who understood it well. Then the business changes and the configuration does not, because there is rarely a moment that obliges anyone to look at it again.

That gap does not announce itself. There is no error, no outage, no red light on a dashboard. It shows up instead as friction: a process that takes longer than it should, a report nobody fully trusts, a workaround that has been running so long it has stopped looking like one.

The signs worth taking seriously

Somebody maintains a spreadsheet. Almost every drifted configuration has one. It exists because the system does not produce something the business needs, so a person makes it instead. Ask what it is for and you will usually find the answer to a configuration question nobody has asked.

The expense type list has grown. Expense types accumulate – a category added for one country, another for a project that finished two years ago, three that mean roughly the same thing. Users cope by picking whichever looks closest, which quietly degrades the accuracy of every report built on that data. It is common for organisations to be confident they have a few dozen active types and to find, on inspection, several times that number.

Approval routes do not match the org chart. Restructures, acquisitions and new entities change who should approve what. Approval hierarchies are rarely revisited at the same pace, so claims route to people who left, or skip people who should see them.

Nobody can say who owns it. The people who originally configured the platform have often moved on, and the knowledge went with them. What remains is a system everyone uses and nobody feels able to change.

Tax and reclaim look too simple. If VAT reclaim on employee expenses has never been reviewed, it is worth checking whether the configuration supports it at all. This is one of the more common findings, and one of the few that pays for the exercise on its own.

What to check first

You do not need a formal engagement to start. Five things are worth an afternoon:

• Count your active expense types, then ask the finance team how many they think there are.
• Take three recent claims and follow the approval path. Does it match how the business is organised today?
• Check whether tax and reclaim configuration is active for the countries you operate in.
• Ask whether any integration to your ERP or HR system is failing silently and being corrected by hand.
• Ask the people who use it every day what they work around. They will tell you immediately.

Why an outside view helps

The difficulty with reviewing your own configuration is that the workarounds have become normal. When a process has been done a particular way for three years, it stops reading as a problem and starts reading as how things are done. That is not a failure of attention; it is what familiarity does.

An independent review is useful mainly because it does not share those assumptions. It asks why a step exists, notices where the system is being compensated for, and separates the things that are genuinely fine from the things everyone has stopped seeing.

Whether that review comes from us, from your own team, or from a fresh pair of eyes internally matters less than that it happens. A configuration that has never been revisited since go-live is, at best, a good fit for a business that no longer exists.