About Configuring Multiple Currencies for a Data Source

Service Administrators can configure the use of multiple currencies for a data source by creating a Text attribute with the Currency option selected. This allows every transaction to be associated with a currency, thereby enabling Transaction Matching to use a single match type to handle transactions in multiple currencies.

Currency must be configured if you need to load transactions with more than one unique currency into a single reconciliation. If you need to load transactions with one unique currency into a single reconciliation, then the default currency from the lowest enabled bucket of the profile is assumed to be the currency code. In this case, a currency attribute need not be configured.

When you configure currency:

  • A bucket attribute mapping is created for the currency attribute
  • A match rule condition, with Matches Exactly, is created for the currency attribute
  • The Overview tab in the Matching dialog shows a drop-down for Currency. Select a currency to display the balance summary for the selected currency in the reconciliation.

Considerations When Configuring Multiple Currencies

  • Only one Text attribute within a data source can be defined as a currency attribute.
  • If a currency attribute is defined for one data source in a match type, then you must configure a currency attribute for all the other data sources in this match type.
  • A currency attribute cannot be defined for a data source that already contains transactions.
  • Transactions that use different currencies cannot be matched.

    When performing matching, both the Amount and the Currency are considered.

  • If a currency attribute is changed to a non-currency attribute (by deselecting the Currency option), the bucket attribute mapping and rule conditions that were added for this currency attribute (both auto match and manual match rules) are automatically deleted.
  • In the User Interface, the precision used when displaying transaction amounts is the precision of the currency that is associated with the transaction.

    For example, a currency attribute is configured for a data source, and the data source contains transactions with currencies USD, JPY, and BHD. The precision used for USD transactions is 2, for JPY is 0, and BHD is 3, which is the configured precision for these currencies.

  • If currency is configured for data sources in the match type, the Balance Report Transactions includes the currency code. The precision used for the amounts is that of the currency associated with the transaction.
  • When importing pre-mapped transactions:
    • If the import file contains a Currency attribute, each row in the file must contain a currency code. If one or more transactions don't have a currency code, an error occurs and the import is not completed.
    • If the import file does not contain a Currency attribute, then the default currency of the lowest enabled bucket of the profile is used, and the import is completed.
    • If the import file contains an invalid currency code, then the import job is not completed and the log file indicates which the currency code is missing.