offer agent generated the offer in the wrong currency - the location said London and the template defaulted to USD

offer agent generated the offer in the wrong currency - the location said London and the template defaulted to USD

TL;DR

The offer template defaulted to USD and nobody told it the role was in London. Derive the currency from the work location explicitly, and require it as a field on every offer, never a default. Currency is not a detail; it is the offer.

offer agent generated offer in wrong currency - London role defaulted to USD

Steps

1. Confirm the default: check the template's currency handling for missing location data. Expected: USD is hardcoded as the fallback.

2. Make currency a required field derived from the work location (London maps to GBP), with no silent default. Expected: Every offer names its currency.

3. Fix the sent offer with a corrected letter and a clear explanation to the candidate. Expected: The candidate sees the real numbers.

4. Add a pre-send check: currency must match the work location's currency. Expected: Mismatches are caught.

5. Cover the edge cases: remote roles (currency follows the employment entity), multi-location roles (currency per location). Expected: The policy handles the variants.

When to use

• an offer has the wrong currency
• the template defaults currency
• hiring across currencies

When not to use

• the currency is contractually USD regardless of location (then document the exception)
• the candidate is paid through an EOR with its own currency rules (follow the EOR)
• the offer is equity-only (different calculation)

Tool compatibility

• any offer-generation agent
• multi-currency hiring

Variant phrasings

• "offer wrong currency London USD"
• "currency default offer template"
• "offer currency mismatch location"

Why it happens

Templates are written where the company started, usually the US, and USD becomes the invisible default. The agent filled the template without questioning the default because defaults do not look like decisions. But the candidate reads the number in their own currency, and a USD figure for a London role is either a pay cut or a windfall, depending on the day's rate.

Edge cases

• exchange rates move; the offer should name the currency, not convert on the fly
• remote-first companies need an explicit currency policy per employment entity
• the pre-send check needs the location-to-currency mapping maintained

Provenance

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