Illustrative scene of two colleagues comparing printed reports at a working desk

KADE / PERSPECTIVE

When two reports
disagree.

Why the evidence behind a number matters as much as the number itself.

← All insights

INTELLIGENCE

A portfolio report shows a fall in exposure to an issuer. The risk team’s report shows an increase. Both arrive before the same morning meeting.

In this illustrative case, neither team has made a simple arithmetic error. The portfolio report uses settled holdings from the previous evening. The risk report includes an unsettled purchase and a derivative exposure. The figures answer different questions, but the headings make them look comparable.

Before choosing the correct number, establish what each number represents.

A useful reconciliation needs the observation time, the instruments included, the treatment of unsettled trades and the definition of exposure. It also needs the version of the calculation. Without those details, the same disagreement can return at the next meeting even after someone has manually aligned the totals.

Agreement between reports is not enough either. Two systems can reproduce the same figure while relying on the same stale input. Several apparently independent views may share a source or a model assumption. Their agreement should not be treated as additional evidence until those dependencies are understood.

For an investment committee, the practical outcome should be a clear account of the disagreement: what changed, which definitions differ, what remains unresolved and whether the difference could affect the decision. A small timing discrepancy and a missing source of economic exposure need different responses.

Retaining evidence alongside an analytical result allows the institution to examine its basis, compare it with another view and decide what needs further work. That judgement still belongs to the institution.

KADE’s development work addresses this wider requirement for analytical context across existing workflows. The example illustrates the problem; it does not describe a live client implementation.

Illustrative image generated with AI.