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

# Currency

> Plan across currencies with everything summable in your base currency.

Novaplan is multi-currency by design. You plan and hold values in native currencies where it matters, and every report translates to your base currency so totals across entities are always summable.

## How It Works

* Each entity and account carries its native currency.
* FX rates are applied per month, so currency drift over your forecast window is reflected in the numbers (a salary in euros costs a different base amount in December than in January if the rate moves).
* Cost surcharges are applied after translation, the same order the forecast engine uses, so a loaded cost matches what the engine computes.
* Amounts on dashboards and reports show in base currency unless a column is explicitly labeled native.

## Managing Rates

In **Planning -> Currency**, manage the FX rates used for translation. Changing a rate re-translates the affected plans and reports automatically, so you do not rebuild anything by hand.

<Note>
  Never sum mixed native currencies. Novaplan converts to base currency before summing, so roll-ups are always apples to apples. A native-currency column is the only exception, and it is always labeled as such.
</Note>

## Common Questions

<AccordionGroup>
  <Accordion title="What is my base currency?">
    It is the single reporting currency your roll-ups and dashboards present in. Every native amount is translated to it before it is summed.
  </Accordion>

  <Accordion title="When does an FX rate change take effect?">
    Per month. Rates are applied at monthly granularity across the forecast window, so a rate move shows up in the months it applies to, not as a single flat conversion.
  </Accordion>

  <Accordion title="Can I see a number in its native currency?">
    Yes, where a column is explicitly a native-currency column. Those are labeled, and you should not sum across them since they may mix currencies.
  </Accordion>

  <Accordion title="I changed a rate but a report did not move.">
    Translation re-applies on the affected plans and reports. If a report still looks stale, re-run the relevant forecast so the derived GL re-posts with the new rate.
  </Accordion>
</AccordionGroup>

## If the Numbers Look Off

* A roll-up looks wrong across entities: confirm you are reading base currency, not a native-currency column folded into the sum.
* A loaded cost in a foreign entity drifts month to month: that is expected. FX is applied per month, so currency drift over the window is real, not a bug.
* A rate edit did not propagate: re-run the forecast for the affected universe so the derive bridge re-translates and re-posts.