Currencies

Companies with different LCY

Normally, transactions in local currency (LCY) do not have a currency code.
When companies exchange data and have different local currencies, the system applies conversion rules to get the correct currency.

Example
Sending company LCY: EUR
Receiving company LCY: GBP

In this scenario, the blank currency code must be converted to the sending company’s currency code. To support this, correct configuration is required in:

• Party
• Topic
• Subscription

This is how it works

Currency code is blank

If the currency code in the Subscription message is blank: The system uses the currency code from the sending company’s Party setup.

Example:
Subscription message: Currency code = blank
Sending company Party currency: EUR
Result: EUR is used

Currency code matches the sending company

If the currency code in the Subscription message matches the currency code in the sending company’s Party setup: The system uses the local currency from the receiving company’s General Ledger Setup.

Example:
Subscription message: EUR
Sending company Party currency: EUR
Receiving company LCY: GBP
Result: GBP is used

Setup

Party

1. Choose the 🔎 icon, enter Parties (IDM), and select the related link.
2. Add the currency code that is used in the company’s General Ledger Setup.

Topic

1. Choose the 🔎 icon, enter Topics (IDM), and select the related link.
2. Open the Topic tables.
3. Open the Job table.
4. Add the fields Invoice currency code and Timesheet currency code.

Subscription

1. Choose the 🔎 icon, enter Subscriptions (IDM), and select the related link.
2. Open the subscription for Project.
3. Open the the Job table.
4. Add the fields Invoice currency code and Timesheet currency code in the Job table.
5. Set the Mapping type = Currency on the fields you just added.
6. Open the Subscription for Project ledger entries.
7. Open the Job ledger entry table.
8. Set the Mapping type = Currency on the field Currency code.