FX rollover management: they see me rollin' they hatin'

Ask any operations lead at a multi-mandate asset manager what eats the most time on the FX desk and the answer comes back fast: Rollovers. The bulk roll cycle that hits when forward contracts approach expiry across a portfolio of mandates with similar hedge programs.

The mechanics are surprisingly straightforward: A fund holds USD-denominated assets, the mandate requires a hedge back to base currency, the hedge sits in a 1-month or 3-month forward, and at expiry the FX position needs to roll. Easy, except for the fact that this is a tedious task and oftentimes more than one fund is affected. Multiply that across 30 funds, four base currencies, and a hedge ratio that needs to be respected within a tolerance band, and the ops team is suddenly running a workflow that looks like a small trading desk in its own right.

Most PMS treat FX hedging as a portfolio problem. The hedge gets calculated based on exposure, the trade gets executed, the position sits there until it expires. At the moment of roll, the system either supports a bulk operation or it does not. If it does not, the operations team builds the roll list manually, sense-checks it against the hedge policy, gets it approved, sends it out one ticket at a time, and reconciles the responses. That is a full day of work for one analyst every month.

This is the work that does not appear in vendor demo and when it goes wrong it creates a lot of noise: A missed roll leaves a hedge open after expiry. A wrong tenor on the new leg breaks the hedge ratio. A counterparty restriction that updated overnight gets discovered in the middle of the bulk send. None of these are exotic failure modes. All of them happen all the time.

A useful FX rollover capability does three things:

• 1. It identifies what needs to roll,
• 2. automatically and on a schedule,
• 3. with awareness of mandate-specific tolerances.

The proposed rolls are then validated against hedge policy and counterparty rules before anything is sent. Exceptions must surface early, in a queue someone can work through, rather than mid-execution.

Vendors in this space keep building flashier pre-trade analytics and skipping over rollover operations. The ROI calculation is fairly straightforward if you consider an analyst spending two days a month on rolls. In this day and age, this is the kind of process that should be automated, audited, and forgotten. But rollovers are still treated as an edge case by most PMS vendors, even though it happens every month.

Solving this isn't exciting, it doesn't get celebrated in the way that completing this tedious task every month might have gotten celebrated by front and back office. Nothing newsworthy happens. That's the point; and maybe that is more worth celebrating.