> For the complete documentation index, see [llms.txt](https://docs.xorosoft.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xorosoft.com/xoroerp-1/admin/company/currency-centre.md).

# Currency Centre

The Currency Centre is a comprehensive repository that stores all possible currencies available for transactions. This is pivotal for businesses operating on a global scale, enabling them to engage with customers and partners in a wide variety of currencies. Whether you're invoicing an international client or purchasing supplies from overseas, the Currency Centre ensures every transaction is possible, regardless of the currency.

### Key Features of the Currency Centre

* **Multiple Currencies Support**: The currency centre serves as a centralized hub for storing all supported currencies and allows for transactions in an array of international currencies, enabling global business operations.
* **Unique Currency Identification**: Each currency is assigned a unique code, ensuring precise identification and handling in the system.
* **Home Currency Designation**: The currency centre explicitly distinguishes the home currency that serves as the primary reference point for financial activities within the system.
* **Active Status Indicator**: Indicates whether a currency is currently active, aiding in transaction validity and system accuracy.


---

# 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.xorosoft.com/xoroerp-1/admin/company/currency-centre.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.
