> For the complete documentation index, see [llms.txt](https://docs.revelator.com/pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.revelator.com/pro/platform/finance/adding-adjustmens-and-fx-rates.md).

# Adding adjustmens & FX rates

## **Prerequisites**

1. **Access to Finance**: You must have the appropriate user permissions to view and manage the Finance section.
2. **Supported File Formats**: Ensure your report is in a format Revelator can parse. For example, CSV, or TXT from recognized DSPs or distributors.
3. **Catalog Management**: Ideally, you have a clean catalog with accurate metadata (ISRC codes, track titles, etc.), to minimize unmatched lines upon import.

### **Adding or Adjusting Foreign Currency**

1. **Identify a Multi-Currency Report**: Look for a report labeled with FX details (e.g., a currency symbol or note indicating foreign currency usage).
2. **Open Currency Settings**: From the **Report Details** page or **Actions** menu, click **Currency Adjustment** (or similar label) to view or modify currency rates.
3. **Set Conversion Rates**:
   * **Option A**: Use **Auto-Fetched Rates** if Revelator fetches rates automatically from integrated providers.
   * **Option B**: Manually enter or adjust a rate to reflect a specific exchange date.
4. **Apply Adjustments**: Save changes to update how revenue lines in that report are calculated or displayed.
   * *Note*: These changes can automatically recalculate final payouts if you have distribution rules set.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.revelator.com/pro/platform/finance/adding-adjustmens-and-fx-rates.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.