A framework for exception handling in multi-currency books

An exception in a multi-currency book is rarely one problem. It is usually two or three small disagreements, a rate, a translation, a cash sweep, that only look like one problem once they hit the NAV.

Classify before you chase

Not every exception needs the same response. A rate that is a rounding difference of a fraction of a basis point is not the same problem as a cash balance that is missing an entire wire. Sorting exceptions into severity tiers before assigning them saves an ops team from spending a full morning on something that does not move NAV.

Route to the source, not the symptom

A currency exception almost always originates upstream, at the trade, the corporate action or the rate feed, not at the NAV calculation itself. A good exception framework routes the alert back to where the data entered the ledger, so the same root cause gets fixed instead of patched every month.

Tracking exceptions by source over time also tells you where to invest next. If the same custodian feed produces the same class of exception every quarter, that is a integration problem worth fixing once, not a recurring line item on someone's to-do list.