Currencies

Currencies are system reference objects used by INTERA to identify financial values consistently across Assets, Metrics, Dashboards and connected systems.

Examples include:

• EUR — Euro
• USD — US Dollar
• GBP — Pound Sterling

Currencies are managed centrally under System Settings → Currencies.

The key principle is:

A currency is shared system reference data, not an ordinary business Asset.

Why Currencies Are System Assets

Internally, INTERA represents currencies using the same structured Asset model used elsewhere in the platform.

This allows currency information to have a defined structure and to be referenced consistently by other INTERA objects.

However, currencies are different from normal Assets such as Customers, Products, Vessels or Bank Accounts.

They describe the INTERA environment itself rather than a business object being monitored.

For this reason, Currency is a System Asset Type.

Currency Assets:

• use the INTERA Asset model;
• are managed centrally;
• are available to other INTERA objects where currency information is required;
• do not appear in the normal Assets list.

This keeps the everyday Assets workspace focused on actual business objects.

Managing Currencies

Currencies are managed from:

System Settings → Currencies

Administrators can maintain the currencies required by their INTERA installation from this section.

A company operating primarily in Cyprus, for example, may use EUR as its main currency while also working with USD and GBP through customers, suppliers, bank accounts or external systems.

Only currencies that are relevant to the organisation need to be maintained.

Where Currencies Are Used

Currency information may be required wherever INTERA works with financial amounts.

Typical examples include:

• revenue;
• customer balances;
• bank balances;
• invoices;
• purchase values;
• inventory values;
• sales orders;
• supplier costs;
• financial Metrics;
• Reconciliations involving monetary values.

Keeping currencies as common system objects avoids different parts of INTERA defining the same currency independently.

Currencies and Integrations

Connected systems may identify currencies in different ways.

For example, an accounting system may return:

EUR

while another external system may use its own internal identifier.

An Integration or configuration can map the external representation to the corresponding Currency in INTERA.

The objective is that once data reaches the INTERA model, its currency has a consistent meaning regardless of where the original value came from.

Currency Does Not Mean Conversion

Defining a Currency tells INTERA what currency a value represents.

It does not, by itself, mean that INTERA converts one currency into another.

For example:

Outstanding Balance = EUR 82,150

and

Outstanding Balance = USD 24,300

are two values with explicitly identified currencies.

Any conversion or exchange-rate logic must be defined separately where required.

Why This Matters

Financial information often enters INTERA from several independent systems.

Without a common currency reference, similar values can become ambiguous:

• Is 25,000 EUR or USD?
• Does the accounting system use the same currency definition as the sales system?
• Can values from two DataSources be compared directly?
• Is a Reconciliation comparing amounts expressed in the same currency?

A centrally managed Currency model gives INTERA one consistent reference for answering these questions.

Currencies Versus Ordinary Assets

A simple distinction is:

Business Assets represent things the organisation works with.

Examples:

• Customer
• Product
• Vessel
• Bank Account
• Server

System Assets support the INTERA environment itself.

Currency is one such system object.

This is why Currency uses the Asset architecture internally but is administered through System Settings rather than appearing alongside normal business Assets.