How to Read Outbound Pipeline Reports Across Currencies
Read an outbound pipeline total only after confirming the currency of the source opportunities, the report's currency, the conversion policy, and the reporting snapshot. Amounts denominated in different currencies are not a meaningful combined monetary total until a documented conversion puts them on a common basis.
A changed total can reflect new or changed opportunities, exchange-rate changes, or a restatement of historical data. Separate those explanations before describing the movement as outbound performance. Currency conversion changes the reporting representation of an amount; it does not by itself create commercial value or recognized revenue.
Start with the currency attached to each source amount
Identify the opportunity record and the amount being reported. Record its denomination explicitly rather than inferring it from a currency symbol, a company address, or the viewer's account settings. Preserve the source value alongside any reporting value.
Unify's standard-object reference describes opportunity amount as a Currency attribute. The attribute value-type documentation defines Currency as a nonnegative amount paired with a currency code. That documents the value type; it does not establish automatic cross-currency aggregation or the exchange-rate policy of a particular dashboard.
Use the record inspection workflow to examine actual attribute values and record identifiers. A report label that says “pipeline” is insufficient evidence of what monetary field it selected or how that field was transformed.
Identify the reporting basis before adding amounts
Ask the report owner to name the reporting currency and show how each source amount becomes a reporting amount. The conversion policy should identify the rate source, the applicable date, the direction of the rate, and any rounding conventions.
| Component | Question to answer | Evidence to retain |
|---|---|---|
| Source amount | Which opportunity field and currency are being used? | Record ID, field, amount, and denomination |
| Reporting currency | In which currency is the total expressed? | Report configuration or documented definition |
| Conversion date | Which date determines the rate? | Explicit date rule and the date used for the record |
| Rate source | Where does the exchange rate come from? | Source and version or retrieval evidence |
| Rate direction | How does the source currency convert to the reporting currency? | Formula or transformation definition |
| Rounding | At what point are values rounded? | Documented precision and aggregation rule |
| Historical treatment | Can a prior period change when rates change? | Restatement or snapshot policy |
Do not choose a rate convention because it makes the result look favorable. Use the organization's approved reporting policy and keep it consistent across the population being compared. If there is no agreed policy, show source-currency subtotals while the reporting basis is resolved.
Follow the data from the CRM to the report
Confirm which system maintains opportunity data and which system produces the total. Unify's Salesforce sync documentation and HubSpot sync documentation describe opportunity context read into Unify from those CRMs. These integration descriptions do not prove a report's FX policy.
Review the relevant Salesforce field mappings or HubSpot field mappings. Verify which field supplies the amount, which values are available, and whether a transformation happens before or after the data reaches the report.
Keep sync timing separate from conversion timing. A source record can change before the reporting system reflects it. A newly displayed amount may therefore be a data-refresh effect rather than a new opportunity or a rate change. Retain the report snapshot and relevant source timestamps when reconciling differences.
Unify's analytics product page describes dashboards, attribution, and ways to export data. It does not specify every currency supported by every report, a universal rate provider, or whether historical totals are restated. Verify those details for the actual report before making a monetary comparison.
Distinguish current-rate views from historical snapshots
A report may use a rate associated with a source transaction or reporting date, a maintained rate table, or another documented convention. It may preserve a historical snapshot or recompute earlier periods when underlying data changes. These are reporting choices to identify, not assumptions to make from the chart's appearance.
Ask whether reopening the same period later can produce a different total. If it can, determine which inputs are allowed to change: opportunity amounts, currencies, inclusion criteria, rates, or the transformation itself. A historical label does not guarantee an immutable snapshot.
For a comparison across periods, retain both the report definition and the conversion policy. If the policy changed, either reconcile the difference or clearly label the views as using different bases. Do not attribute the full movement to a campaign until the monetary basis is comparable.
The distinction between new opportunity flow and an open-pipeline snapshot is a separate issue, covered in the pipeline-flow guide. Keep that population definition fixed while resolving currency differences.
Use a blank currency reconciliation sheet
Copy this sheet for each source opportunity or maintain the same fields as columns in a spreadsheet. Leave the observations blank until the source and report have been inspected. Preserve the original values rather than replacing them with converted amounts.
| Reconciliation field | Observed value | Evidence or unresolved question |
|---|---|---|
| Report name, owner, and snapshot time | ||
| Source opportunity ID and system | ||
| Included population and attribution rule | ||
| Source amount and currency code | ||
| Source amount field and source timestamp | ||
| Reporting currency and reporting amount | ||
| Conversion date and date-selection rule | ||
| Exchange-rate source and rate used | ||
| Rate direction and rounding rule | ||
| Historical snapshot or restatement policy | ||
| Reconciled, excluded, or unresolved status |
This is a proposed reconciliation method, not an observed audit result. An unresolved row remains unresolved even if its amount appears plausible. Missing denomination or rate evidence should not silently become a zero amount or a default currency.
Define a total that another person can reproduce
State the population as the unique opportunities included by the report's existing filters and attribution rule at the chosen snapshot. Keep one record per opportunity for monetary aggregation unless the report explicitly uses an allocated measure. Identify duplicates before summing; duplicated joins can inflate a total even when currency conversion is correct.
For the monetary total, sum only amounts reconciled to the same reporting currency under the stated policy. A sum has no denominator. Report the count and known source-currency values of unresolved or excluded opportunities separately; do not mix them into a single unqualified total.
If you also report reconciliation coverage, the numerator is included opportunities whose amount and conversion basis have been verified. The denominator is all unique opportunities in the defined population. Unresolved records stay in the denominator and are reported separately. If the population is empty, label coverage not applicable. An empty, verified population can have a zero total; an unknown population or incomplete currency basis is not evidence of zero pipeline.
When data is extracted through Unify's API, the query-job guide helps establish complete retrieval. A partial export cannot validate the full report even if the rows retrieved reconcile correctly.
Keep currency interpretation separate from attribution and forecasting
Currency reconciliation answers whether amounts share a defensible monetary basis. It does not decide which campaign deserves credit, whether an opportunity will close, or when revenue should be recognized.
Use the existing CRM attribution architecture and marketing-run outbound contribution framework to establish which opportunities belong in the report. Then apply the currency checks to that population. Avoid changing attribution rules at the same time as the conversion policy unless the comparison explicitly explains both changes.
When sharing the number, include the reporting currency, snapshot, conversion policy, historical treatment, and unresolved coverage. That gives the reader enough context to distinguish an operating result from a change in how it is represented.
Frequently asked questions
Can opportunity amounts in different currencies be added directly?
Not as a meaningful combined monetary total. Preserve each denomination and convert using a documented common reporting basis, or show separate source-currency subtotals.
Does Unify's Currency attribute prove automatic FX conversion?
No. The documentation defines an amount paired with a currency code. It does not establish the conversion or restatement policy of a particular report.
Can a pipeline total change without new opportunities?
Yes. Source amounts, inclusion rules, exchange rates, or historical restatements can change a total. Reconcile those inputs before attributing the movement to outbound performance.
What should a report do with an unresolved currency value?
Keep it visible as unresolved and outside an unqualified converted total. Report the unresolved population separately rather than substituting zero or guessing a denomination or rate.
