FindingcurrentGTM data

A CRM amount is a number whose currency sits in a separate field

Summing amounts across record currencies produces a meaningless total with no error.

SymptomA pipeline total mixes dollar and euro deals with no warning. A "largest open deal" answer returns a yen deal whose raw amount is far above the real largest.

In a multi-currency CRM, each opportunity's amount is stored in the record's own currency. The currency sits in a separate field, and its name differs from one CRM to another.

An amount without its currency still adds up cleanly. In a warehouse copy, or when summing raw records you pulled, a query that sums or ranks the amount field returns a confident number, and nothing flags it. In Salesforce, a grouped total comes back in the org's default currency. A plain query returns each amount in its own record's currency.

Ranking is worse than summing. A yen deal can top "largest open deal" with a raw amount many times that of the real largest.

Agents request only fields they know exist. If nothing names the currency field next to the amount, they never ask for it.

An agent given a clear error corrects itself. Refuse a mixed-currency total with a message saying to filter or group by currency, and the next question can come back split by currency.

In a synthetic test set of 90 opportunities in three currencies, ranking on the raw amount put a yen deal first that is worth less than the largest dollar deal, and the raw total came to 42 times the converted total. The set shows the mechanism, not how common it is.

Check your setup read-only

Count the distinct currency codes on open opportunities. Find the field that holds the record currency in each CRM you read. More than 1 code is a gap if any report or agent-tool aggregate doesn't group by that field.

Passes ifOpen opportunities carry one currency code, or every aggregate you read groups or converts by the record-currency field.

Access needed:crm-readlocal-config

If it fails: changes to make later (not part of the check)
  1. 01Find the record-currency field in each CRM you read. Name that field next to the amount wherever an agent reads the amount.
  2. 02Sum, average or rank amounts only within one currency, or use the CRM's own converted amount in the corporate currency.
  3. 03Split grouped totals into one line per currency.
  4. 04Label a top-N list when its cutoff splits a tie or the list spans currencies.
Applies ifYour reports, digests or agents total CRM opportunity amounts, and multi-currency is turned on or you read more than one CRM.

← Back to the stream

For your agent

Each post has a read-only check your agent can run against your own setup. Paste this into a read-only session:

Never asks your agent to change anything · send anything anywhere · fetch other pages · run code · read something you can't.

What each rule means, and how it's enforced
  • Change anything. Every check is a question answered by reading. Each one names what it reads. The steps under “If it fails” are for you to weigh later, never part of a check.
  • Send anything anywhere. No post asks an agent to email, post, submit, upload or report back. Your results stay with you; sharing them is your call.
  • Fetch other pages. Post text carries no links, and no post tells an agent to visit one. The only URLs in the feed point to this site's own post pages.
  • Run code. Snippets are illustrations, not commands.
  • Read something you can't. posts.json is generated from this page, field for field. Nothing is hidden from a human reader.

A gate enforces these rules before every publish: it refuses links, instructions aimed at an agent, write verbs inside a check, hidden Unicode characters and any check without an "access needed" line. Each published version carries a version number and a sha256 fingerprint, so you can pin the version you reviewed. Every post is reviewed by a person before it goes out.

Feed version 1.0 · 2026-11-16 · sha256 88d19978389827b7…

Found something that breaks these rules? Tell me on LinkedIn.