> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fusioncore.us/llms.txt
> Use this file to discover all available pages before exploring further.

# Multi-Currency Overview

> Set up fusionCore to sell, invoice, and report in more than one currency.

Multi-currency lets your association take payment, issue orders and invoices, and report financials in each member's local currency, while staff still manage one product catalog and see consolidated values in a single corporate currency.

These guides show you how fusionCore extends Salesforce to handle more than one currency.

## When You Might Use This

* An international organization accepts **membership payments** in USD, EUR, and GBP based on the member's location.
* An organization runs a **worldwide donation campaign**. Donors contribute in their local currency, and Salesforce converts donations to the corporate currency (for example, USD) for unified reporting.
* An organization **hosts events in Asia, Europe, and North America**, charging attendees in local currencies such as JPY, EUR, and CAD.
* **Sponsors for an annual conference** pay fees in their preferred currency, and Salesforce consolidates sponsorship income in a central currency for financial reporting.

## Key Concepts

A few terms come up throughout this section:

* **Multi-currency org** — a Salesforce organization that has been switched into multi-currency mode. Once enabled, every record that holds an amount gains a `CurrencyIsoCode` field, and Salesforce maintains conversion rates between currencies. This is a one-way, org-level setting.
* **Corporate currency** — the single "home" currency your org reports in. Salesforce converts every other currency back to this one for consolidated reporting. Each org has exactly one corporate currency; it does not have to be USD.
* **`CurrencyIsoCode`** — the standard three-letter currency field (for example, `USD`, `EUR`) that Salesforce adds to records once multi-currency is enabled. fusionCore reads this field to decide what currency an order or payment uses.
* **Currency config** — a fusionCore Custom Metadata record (`Currency_Config__mdt`) that maps an ISO code such as `USD` to a display symbol such as `$`. Nine currency configs ship by default.
* **Same-currency rule** — a Product and an Order or Opportunity only transact when they are in the **same** currency. This is why a Business Unit that sells in multiple currencies needs its own Products and Payment Types set up in each of those currencies.

## Where to Start

Work through these in order the first time you set up multi-currency, or jump straight to the area you need.

<CardGroup cols={2}>
  <Card title="Enabling multi-currency" icon="globe" href="/end-user-guides/accounting/multi-currency/enabling-multi-currency" arrow="true">
    Turn on multi-currency for your org and activate the currencies you sell in.
  </Card>

  <Card title="Defining Business Unit currency" icon="building" href="/end-user-guides/accounting/multi-currency/defining-business-unit-currency" arrow="true">
    Set the currency on each Business Unit record.
  </Card>

  <Card title="Supported currencies on Payment Type" icon="credit-card" href="/end-user-guides/accounting/multi-currency/supported-currencies-on-payment-type" arrow="true">
    Limit a payment method to the currencies it accepts.
  </Card>

  <Card title="Creating multi-currency orders" icon="cart-shopping" href="/end-user-guides/accounting/multi-currency/creating-multi-currency-orders-from-account-contact" arrow="true">
    Create orders that inherit their currency from an Account or Contact.
  </Card>

  <Card title="Updating the Standard Price validation rule" icon="tag" href="/end-user-guides/accounting/multi-currency/updating-standard-price-validation-rule" arrow="true">
    Adjust the price-book validation rule for per-currency pricing.
  </Card>
</CardGroup>

## Related Features

<CardGroup cols={2}>
  <Card title="Price books" icon="tag" href="/end-user-guides/products/product-set-up/price-books" arrow="true">
    In a multi-currency org, the standard price book holds one entry per currency for each Product.
  </Card>

  <Card title="Payment Types" icon="credit-card" href="/end-user-guides/accounting/payment-types/index" arrow="true">
    A Payment Type's Supported Currencies decide whether it appears for an order's currency.
  </Card>

  <Card title="Business Units" icon="building" href="/end-user-guides/accounting/business-units/index" arrow="true">
    Each Business Unit transacts in its own currency, so multi-currency selling needs Products and Payment Types per currency.
  </Card>

  <Card title="Accounts and Contacts" icon="address-card" href="/end-user-guides/accounts/index" arrow="true">
    An order inherits its currency from the Account or Contact it is created against.
  </Card>
</CardGroup>

## Limitations and Common Pitfalls

<Warning>
  **Enabling multi-currency is irreversible.** Salesforce does not allow turning multi-currency mode off once it is on. Test it in a sandbox first.
</Warning>

* **An order's currency is inherited, not chosen.** The **Create Order** quick action takes the order currency from the source Account or Contact (`CurrencyIsoCode`). If the source record has the wrong currency, the order is created in the wrong currency. Set the Account or Contact currency correctly before creating the order.
* **Supported-currency limits only apply in a multi-currency org.** A blank **Supported Currencies** on a Payment Type means "all currencies allowed." Outside a multi-currency org the check passes unconditionally.
* **Supported Currencies is a fixed list.** The field accepts only these ISO codes: AUD, GBP, CAD, EUR, INR, JPY, SGD, AED, USD. A currency you activate in Salesforce but that is not in this list cannot be selected as supported on a Payment Type.
* **Activate and rate every currency before transacting.** Currency conversion fails if either the source or target currency has no active, rated currency in Setup. Conversions use Salesforce's stored conversion rate and round to two decimal places.
* **Per-currency standard prices come from the Product, not the price-book entry.** In a multi-currency org the standard price book holds one entry per currency, but you set standard prices on the Product's **Standard Price** field, not by editing the entry. See [Updating the Standard Price validation rule](/end-user-guides/accounting/multi-currency/updating-standard-price-validation-rule).