## TL;DR
Fix this in CRM pipeline export by acting on the exact problem first: split the CRM pipeline export by currency before parsing, convert each currency group to the reporting currency at the approved period rate, recombine the converted groups, and check the combined pipeline total against the CRM home currency report total. Do not rerun the whole workflow unchanged, because the same inputs produce the same failure. Prove the fix on one account, period or department first, then rerun the full scope and reconcile the results.

```text
parser failed on CRM pipeline export with mixed currency amounts for tie out the revenue variance to the CRM pipeline error parsing failure
```

## Use this when
- The operation in CRM pipeline export fails with this exact problem: parser failed on CRM pipeline export with mixed currency amounts for tie out the revenue variance to the CRM pipeline error parsing failure.
- The same failure repeats on retry with unchanged inputs.
- A variance report, forecast, commentary or board pack step is blocked until this is resolved.

## Not for this skill when
- The notice is a platform outage from the vendor. Resolve that first, then return here if this problem remains.
- The operation completes and you only disagree with a business judgement such as the budget itself or a materiality call. That is an FP and A decision, not this failure.

## Steps
1. Reproduce the failure on one named account, period or department in CRM pipeline export and record the full problem text plus the account, period or report involved. Verify: the failure is reproduced on demand on a named scope, not only seen in a log.
2. Apply the specific fix for this problem: split the CRM pipeline export by currency before parsing, convert each currency group to the reporting currency at the approved period rate, recombine the converted groups, and check the combined pipeline total against the CRM home currency report total. Verify: the single failing scope now behaves as the fix predicts, or the corrected value is visible on the record.
3. Check neighbouring accounts, periods or departments that share the same mapping, template or load, because this class of failure rarely affects only one scope. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Rerun the original operation in CRM pipeline export on the previously failing scope, watching for the same problem rather than assuming success from a quiet log. Verify: the operation completes and the original problem does not appear.
5. Compare the result against the source of truth, the GL actuals, the approved budget or the planning system record, so a silent partial success is caught. Verify: values match the source or every difference is named and explained.
6. Record the fix, the triggering input and the verification result on the report or close file so the next occurrence is recognised immediately. Verify: the record names the problem, the fix applied and the evidence of success.

## Variant phrasings

### parser failed on CRM pipeline export with mixed currency amounts for tie out the revenue variance to the CRM pipeline error parsing failure
The verbatim form searchers paste from the console, report or run log. Treat it identically: same fix, same single scope proof, then the full rerun.

### How to fix - parser failed on CRM pipeline export with mixed currency amounts for tie out the revenue variance to the CRM pipeline error parsing failure
The how to phrasing for the same failure in CRM pipeline export. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

### CRM pipeline export troubleshooting for this failure
The symptom first phrasing used when the console hides the full problem. Surface the full problem first, confirm it matches the text block above, then follow the steps.

## Why it happens
A column of amounts in mixed currencies sums numbers that are not comparable, and the parser failure or wrong total comes from the currency mix in the file, not from the revenue figures themselves.

## Edge cases
- The period was closed, the budget was reloaded or the org mapping changed after the failing run started. Refresh the scope state and reapply the fix against the current values, not the values from the failed run.
- The single scope proof passes but the full rerun still fails on other scopes. Treat each remaining failure as its own scope, because a shared load or mapping can hide more than one cause.
- The source systems disagree on the correct value. The GL governs actuals, the approved budget version governs plan figures, and the planning system governs forecast; record which source won and why.

Compatibility: CRM pipeline export at current versions, plus Power BI, Excel, Tableau, Looker, NetSuite and Adaptive Planning where the query names them; sources of truth are GL actuals and the approved budget, and no extra tooling is needed beyond access to those source records.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_CteOICd6EuJHYNB1AdDJeQ