> ## 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.
# Defining Business Unit Currency
> Set the currency on a Business Unit record after enabling multi-currency in your org.
A Business Unit is the fusionCore record that groups the products, payment types, and orders a part of your association sells. When your org runs in multi-currency mode, each Business Unit carries a **Currency** value so its records report in the right currency.
In Salesforce, "multi-currency mode" is a one-way org setting that adds a standard **Currency** field (the `CurrencyIsoCode` field) to records and tracks conversion rates between your org's corporate currency and each currency you activate. The corporate currency is the single currency your org rolls everything up to for consolidated reporting.
## Prerequisites
* Multi-currency must already be enabled in your org. See [Enabling Multi-currency](/end-user-guides/accounting/multi-currency/enabling-multi-currency). The **Currency** field only appears on records after this is done.
* The currency you plan to assign must be activated in **Setup > Currency Setup**.
* You need permission to edit Business Unit records.
## How to Define Business Unit Currency
In your Salesforce instance, click the **Business Unit** tab. You can also find Business Units by searching in the **App Launcher**.
Select the Business Unit you want to update from the list.
On the Business Unit detail page, click the pencil icon next to the **Currency** field.
The **Currency** field only appears after multi-currency has been enabled. If you just enabled multiple currencies and do not see the **Currency** field — or you see it but it is missing recently added values — refresh the screen.
Choose the appropriate **Currency**, then click **Save**.
A Business Unit only transacts cleanly with records in its own currency. fusionCore filters products so an order or opportunity sees only products in the same currency as that record. Because of this, a Business Unit that sells in more than one currency needs its own Products and Payment Types for each of those currencies, with each of those records set to the matching currency.
## Limitations and Common Pitfalls
* The order currency is taken from the **Account** or **Contact** the order is created from — not from the Business Unit. When you use the **Create Order** quick action, the new order inherits the source record's currency automatically and you are not prompted to pick a currency. Set the **Account Currency** or **Contact Currency** correctly before creating orders. See [Creating Multi-Currency Orders](/end-user-guides/accounting/multi-currency/creating-multi-currency-orders-from-account-contact).
* A product is only available on an order or opportunity when the product's currency matches that record's currency. If a Business Unit's currency has no products set to that currency, those products will not appear when staff build orders.
* A currency must be activated and rated in **Setup > Currency Setup** before you can transact in it. Selecting a currency that is not activated leads to conversion errors elsewhere in fusionCore.
The fusionCore source code sets an order's currency from the originating Account or Contact record, not from the Business Unit. We could not confirm any fusionCore logic that reads the Business Unit's **Currency** field to drive order or transaction currency. This page documents how to set the field; the feature owner should confirm exactly what consumes it before relying on the Business Unit currency for downstream behavior.