Multi-currency portfolio returns are easiest to understand when you separate two effects: the investment’s return in its local currency and the currency move against your base currency.
The local currency is the currency the asset trades in. The base currency is the currency you use for total portfolio value, allocation, gains, and review. If those two are blended into one converted number, you can misread whether a position moved because the security performed well or because FX moved in your favor or against you.
If you want to measure performance without mixing up FX and returns, the practical answer is to review every foreign holding in three parts: local return, FX impact, and total base-currency return.
The three numbers to calculate first
For each foreign holding, separate the return into these components:
| Measure | Formula | What it tells you |
|---|---|---|
| Local return | (current local price ÷ cost local price) − 1 | Security performance before currency translation |
| FX impact | (current FX rate ÷ cost FX rate) − 1 | Currency effect against your base currency |
| Base-currency return | (1 + local return) × (1 + FX impact) − 1 | Total return in the currency you use to review the portfolio |
Assumptions used: FX rate means the price of one unit of the local currency in your base currency. The example below excludes dividends, fees, taxes, broker FX spreads, hedging, and multiple purchase lots so the return mechanics stay visible.
Worked example. You bought HSBC at £6.00 when GBP/USD was 1.30. Today HSBC is £7.20, and GBP/USD is 1.25.
- Local return = (7.20 ÷ 6.00) − 1 = +20.0%
- FX impact = (1.25 ÷ 1.30) − 1 = −3.85%
- Base-currency return = (1.20)(0.9615) − 1 = +15.4%
The 4.6-point gap between the local return and the USD result is the currency effect. If you only look at the USD number, you understate how well HSBC performed as a security. If you only look at the local number, you overstate how much wealth the position created in your base currency.
Why these returns are easy to misread
When all your holdings are in one currency, performance feels straightforward. When they are not, interpretation gets messier.
Suppose you own a stock priced in GBP while your portfolio base is USD. The stock can rise in GBP terms while the pound weakens against the dollar. Or the stock can stay flat while FX makes the USD value move anyway.
If your tracker only shows one converted number without context, you can end up asking the wrong question. You may think the stock underperformed when the real issue was currency translation, or you may give the investment too much credit when FX did part of the work.
Use one vocabulary and stick to it
For a cross-currency holding, keep the labels simple:
- Local currency: the currency the asset trades in
- Base currency: the currency you use to review the whole portfolio
- FX rate: the value of one unit of local currency in your base currency
The local return tells you how the asset performed before translation. The base-currency return tells you what the position did inside your actual portfolio.
Both matter because they answer different questions:
- Was the investment good on its own terms?
- What did it actually contribute to my portfolio?
That distinction is the main discipline. Judge security selection by the local return, judge allocation impact by the base-currency return, and avoid collapsing the two into one unexplained number.
Where base currency still matters
A portfolio still needs one reference point. Without a base currency, you do not really have one portfolio view. You have several currency-specific fragments that are hard to compare.
You need a base-currency view for:
- Total portfolio value
- Allocation by holding
- Total gain or loss
- Rebalancing decisions
- Overall performance review
This is the balancing act: preserve the local-currency truth of the asset while still making the whole portfolio readable in one base currency.
What goes wrong when investors track this manually
Spreadsheets can handle foreign holdings, but they create more chances for silent error.
Common spreadsheet problems include:
- Using inconsistent FX rates across positions
- Applying current FX to current value but not to cost basis correctly
- Forgetting to normalize pence-versus-pound style quote differences
- Mixing local-currency prices with base-currency totals in the same sheet
- Not being sure whether a gain came from the security or the currency move
The complexity is structural, not cosmetic. If the same position can show one return in its trading currency and another in your portfolio currency, the tracker has to make that split visible.
The two questions a tracker should answer clearly
A good tracker should help you answer two questions without confusion:
- What is this holding doing in its local currency?
- What is this holding doing in my base currency?
If you can answer both clearly, you can evaluate the position sensibly. If you can answer only one, the picture is incomplete.
Scope limits to keep in mind
The simple three-part framework is useful, but it is not the whole accounting picture.
- Dividends: foreign dividends should be translated using the FX rate that applies when the dividend is received or recorded.
- Fees and taxes: commissions, withholding tax, transaction charges, and tax treatment can change the realized result.
- Multiple lots: each purchase lot can have a different cost price and cost FX rate, so lot-level tracking is cleaner than averaging everything too early.
- Realized vs unrealized gains: a closed trade and an open position should not be mixed without labeling them clearly.
- Hedged positions: currency-hedged ETFs or overlay hedges need separate treatment because the FX exposure may be partly or mostly offset.
- Broker FX spreads: your actual broker conversion rate may differ from an interbank or market spot rate.
Those details do not invalidate the framework. They just define what must be added when you want performance reporting to match brokerage records or tax records more closely.
Common mistakes that distort performance
If your setup is weak, a few errors show up repeatedly:
- Treating FX-driven moves as if they were pure security performance
- Ignoring FX entirely and assuming local returns tell the full story
- Using inconsistent or stale conversion logic across holdings
- Forgetting that cost basis also needs currency handling
- Reviewing allocation without converting everything into one base currency
The result is usually a portfolio that looks less precise than it should, even when the source data itself is fine.
Why standardized currency handling matters
One of the hardest parts of manual tracking is consistency.
You need one system for how prices are normalized, how values are translated, and how totals are compared. Without that, small inconsistencies compound over time.
That includes quote conventions. A UK share may be quoted in pence while the economic exposure is usually thought about in pounds. If that is handled inconsistently, both cost basis and current value can be wrong before FX is even applied.
A cleaner setup is to store the local-currency price correctly, store or retrieve the relevant FX rate, and then calculate base-currency value from those inputs in a repeatable way.
How currency affects allocation
Currency issues are not only about return. They also affect how you understand concentration.
If holdings are not translated consistently into one base currency, allocation can become misleading. A position may appear smaller or larger than it really is relative to the rest of the portfolio.
This matters because allocation is one of the main things a portfolio tracker is supposed to help you see clearly. If conversion logic is weak, concentration risk becomes harder to interpret too.
When this support becomes essential
You do not need industrial-grade FX logic if you only own one occasional foreign holding and review it loosely. But it becomes essential when:
- You own multiple international positions
- You think and report in one base currency
- You compare allocation across domestic and foreign holdings
- You care about performance attribution
- You want a portfolio total you actually trust
At that point, “I’ll just handle it manually” usually turns into recurring maintenance work.
How to review a foreign holding clearly
Run the three-part decomposition at each quarterly review. Keep the calculation mechanical:
- Start with the local-currency cost and current local price.
- Use the cost FX rate and current FX rate on the same basis.
- Calculate local return, FX impact, and base-currency return separately.
- Explain any gap between local return and base-currency return before making a decision.
The operational rule is simple: local return explains the investment; base-currency return explains the portfolio impact.
Why this matters for real decisions
Currency mistakes do not only create accounting ugliness. They change decisions.
If you misread a gain, you may overcredit security selection. If you misread a decline, you may sell a holding whose business performance was actually fine. If you misread allocation, you may think you are diversified when you are more exposed than you realized.
That is why clean FX-aware tracking is not a luxury feature. It is part of seeing the portfolio accurately enough to make calm decisions.
Where Portfolio Tracker fits
Portfolio Tracker is built to keep both views visible: local-currency context for the holding and base-currency totals for the portfolio. It supports USD, GBP, EUR, and JPY, and normalizes quote quirks like pence-based listings before rolling values into a consistent portfolio view.
That is the practical standard to look for in any system: not more currency detail for its own sake, but enough structure to make performance, cost basis, gains, and allocation interpretable.
Calculation and data-source notes
This article uses simplified return math for educational portfolio review, not tax reporting or investment advice. The examples exclude dividends, fees, taxes, broker spreads, and hedging unless stated otherwise.
For live tracking, use the same FX-rate source consistently across cost basis, current value, and performance calculations. If your broker records a different execution or conversion rate than a market spot feed, broker records may be the right source for reconciliation even when spot data is useful for ongoing review.
Author: Deep Digital Ventures editorial team, writing from practical product work on portfolio tracking, cost basis, allocation, and investor reporting workflows.
Last updated: April 24, 2026.
FAQ
Should I use my broker’s FX rate or a market spot rate?
Use the broker’s actual FX rate when reconciling trades, cash movements, or realized gains. Use a consistent market spot source for ongoing portfolio estimates if broker-level conversion data is not available, but label it as an estimate.
How should foreign-currency dividends be handled?
Track the dividend in the currency it was paid, then translate it into your base currency using the applicable receipt-date or broker-recorded FX rate. Otherwise income return and price return can get mixed together.
What happens when I bought the same foreign stock in multiple lots?
Each lot can have its own local cost price and cost FX rate. Lot-level tracking gives a clearer result than averaging too early, especially if you later sell only part of the position.
Do hedged ETFs need the same FX treatment?
They still need currency-aware tracking, but the interpretation changes. A currency-hedged ETF is designed to reduce or offset some FX exposure, so the hedge effect should be understood separately from the underlying asset return.
Does Portfolio Tracker support cross-currency portfolios?
Yes. Portfolio Tracker preserves local-currency context while consolidating portfolio totals, gains, and allocation into a base-currency view.