Discover a Treasury Foreign Currency Exposure

A finance team that pays overseas suppliers will eventually ask its treasury specialist a question that sounds simple and is not. What is the currency going to do next month. Nobody knows the answer, and a specialist who tries to guess walks straight into a role they do not have license to play. The real job in that moment is discovery, not prediction. You map the exposure, find out who owns the decision, and set up the next step. Handled well, this conversation builds trust. Handled badly, it turns into a guess dressed up as advice.

Why this conversation goes wrong

The pressure comes from the customer, not from you. A finance lead who just watched an invoice cost more than expected wants comfort, and comfort often sounds like a prediction. If you fill that silence with a rate opinion or a product pitch, you have answered the wrong question. The customer did not ask you to manage their currency risk. They asked because they are anxious about a number they cannot control, and they want someone to tell them what to do about it.

The second failure mode is moving to a solution before you understand the problem. A specialist who hears "foreign currency" and jumps straight to hedging products skips the step that actually matters, which is finding out where the exposure comes from. Sometimes the pain is a rate move. Sometimes it is a slow approval process that stretches the gap between invoice and payment. Sometimes it is a reporting gap that makes the finance team look surprised by numbers they should have seen coming. Each of those has a different owner and a different fix, and none of them get solved by a specialist quoting a forecast.

How to prepare

Before the call, pull whatever you already have on the account. Know which currencies the company transacts in, how large the payment volumes are, and whether this is the first time the topic has come up or a recurring worry. If the company has raised fraud concerns before, review how that was handled, because a customer anxious about currency swings often has related worries about payment security. The Create a Treasury Fraud Response Tree guide walks through building a decision path for that adjacent conversation, and it is worth having in mind even when fraud is not the topic today.

Write down the four or five questions you actually need answered. Which currencies are involved. How often payments go out. Who approves invoices and how long that takes. Who owns the internal forecast for currency needs. You are not trying to sound thorough, you are trying to find the one fact that explains where the pressure is coming from. Decide in advance what you will say if the customer asks you to predict a rate or recommend a specific hedge. Have the sentence ready so you do not improvise one under pressure.

What to say

Picture a call with Harlow Trading, a company that pays two overseas suppliers and has started to notice its invoice costs shifting between the day an invoice is approved and the day it is paid.

The finance lead opens with the question everyone dreads. "Our supplier costs keep moving on us. What do you think the currency is going to do over the next quarter."

You do not answer that question, you replace it. "I can't forecast a rate, and I would not want to guide a payment decision based on a guess. What I can do is help map where the swing is actually hurting you. Can you tell me which currencies you're paying in, and roughly how many days pass between when an invoice gets approved and when it gets paid."

The finance lead explains that one supplier is paid in euros and the other in yen, and that approvals sometimes sit for a week or more before payment goes out. You follow with the question that actually locates the problem. "Who owns your internal forecast for currency needs right now, and does anyone track the gap between approval and payment on a calendar."

The answer might be that nobody owns it, or that it lives in a spreadsheet nobody updates. That is your opening. "That gap is worth looking at closely. Bring me one recent invoice that shows the approval date, the currency owed, and the payment date. That single example will tell us whether the pressure is coming from approval delays, the timing of purchases, or a reporting gap, and it points us toward the right review path once we know."

Notice what did not happen in that exchange. You did not name a rate, a product, or an outcome. You asked for a document, named a process gap, and pointed toward a next step that other people, not you, will decide on.

Mistakes to avoid

A few habits sink this conversation more often than any other.

1. Answering the rate question directly, even with a hedge like "just my personal view." A customer will remember the number, not the disclaimer.

2. Recommending a specific hedging product or strategy before a qualified advisor has reviewed the account. That decision belongs to the company's finance leaders and their advisors, not to you.

3. Skipping the paperwork request. Without one real invoice showing approval and payment dates, you are working from impressions instead of facts, and the next person in the review chain has to start over.

4. Closing the call without naming a next step. If the customer leaves without knowing what happens next and who they will hear from, the conversation was a nice chat, not progress.

5. Treating every currency question as a hedging conversation. Sometimes the fix is faster internal approval, not a treasury product at all, and if you skip past that you send the customer down the wrong path.

How to practice and score it

This is a conversation worth rehearsing before you have it live, because the instinct to reassure a worried customer is strong and it takes repetition to override. Run the scenario with a manager or a peer playing the anxious finance lead, and have them push on the rate question two or three times in different ways. Score yourself on whether you ever named a number, a product, or an outcome. Score whether you asked for the one document that actually clarifies the problem. Score whether the call ended with a concrete next step and a named contact.

DealSpeak is built for exactly this kind of rehearsal. You can run the Harlow Trading scenario against an AI counterpart that pushes back the way a real customer would, and get scored on whether you held the discovery line instead of drifting into forecasting. If foreign currency exposure often shows up alongside broader cash flow worries on your desk, the Use a Liquidity Forecast for Treasury Discovery guide covers the related conversation about forecasting cash needs, and it pairs well with this one. For more scenarios built around this kind of desk work, look at Banking practice conversations.

Closing thought

A treasury specialist earns trust by staying inside the boundaries of the role, not by having an answer for everything. Ask better questions, get the one document that reveals the real problem, and hand off to the right review path with confidence. That is a more useful outcome for the customer than any guess about where a currency is headed.