Here is a test you can run this week, at no cost, with nothing more than four emails.

Ask four people in four different functions to write down their definition of market value for the same portfolio. Do not let them confer.

You will get four documents. They will agree on the arithmetic. They will differ on the pricing source hierarchy, on the treatment of accrued interest, on what happens when a price goes stale, and on which day's rate applies to the currency leg.

Nobody in that exercise is wrong. Each of them is right for their own purpose. The trouble starts later, when the four answers meet inside the same report and somebody has to explain the variance to a client.

The dictionary nobody has time to write

Most institutions we work with do not have a data problem so much as a definitions problem. The fix is a centralized data dictionary with a named owner for every domain — written once, agreed once, and referred to when people disagree. It takes weeks, it is nobody's favorite work, and it quietly removes a category of argument that otherwise recurs every quarter forever.

Exceptions are a workflow, not an inbox

An exception that arrives as an email and is resolved by whoever is free is not being managed; it is being absorbed. What turns that around is deciding, in advance and in writing, who may override what, what gets recorded when they do, and what has to happen before the same exception is allowed to occur next period.

The test of a healthy exception process is not how few exceptions you have. It is whether last month's are explained rather than closed.

Reconciliation that runs without being asked

If reconciliation is a task somebody performs, it will be performed under pressure at the worst point in the cycle. If it is a process that runs continuously and raises its hand, the same team spends its month investigating twelve real differences rather than proving nine thousand matches.

Why the tedium is worth it

Friction between the front and back office, and between the business and IT, is almost always blamed on personalities or on priorities. In our experience it is a definitions problem wearing a personality costume. Two capable teams, both correct, working from different dictionaries, gradually deciding the other one is being difficult.

Writing the dictionary is not a glamorous project. It is the one that makes every other project shorter.