Best practices for configuring option classes and rules in variant management for complex products

Our organization is expanding operations across multiple countries and we need to optimize our AP configuration for multi-currency transactions. Currently running OFC 22D and processing invoices in USD, EUR, GBP, and JPY.

We’re looking for community insights on best practices for currency conversion setup, payment terms management across different currencies, and vendor setup strategies. Specifically interested in how others handle:


wt.currency.defaultConversionRate=DAILY
wt.payment.currencyValidation=STRICT
wt.vendor.multicurrencyEnabled=true

What configuration approaches have worked well for handling exchange rate fluctuations and ensuring accurate financial reporting across multiple currencies?

These are all excellent points. The vendor site separation by currency makes a lot of sense. How do you handle the scenario where a vendor sends invoices in multiple currencies? Do you create multiple vendor records or just multiple sites under one vendor?

From a treasury perspective, vendor setup strategy matters enormously. We maintain strict vendor bank account currency matching - if a vendor’s bank account is in EUR, we only pay them in EUR regardless of invoice currency. This eliminates downstream currency conversion fees and banking complications. Also implement payment method restrictions by currency to prevent accidental cross-currency payments that incur unnecessary bank charges.

Currency conversion is critical. We use Corporate rate type for all AP transactions to ensure consistency with our treasury operations. Set up daily rate imports from your bank or use Oracle’s currency rate service. For vendor setup, create separate vendor sites for each currency - this prevents confusion and makes payment file generation much cleaner. Don’t try to handle multiple currencies through a single vendor site.