SuiteProcurement Now Handles Multicurrency with Trading Partner Currency Conversion

What changed

SuiteProcurement now supports multicurrency workflows, but the conversion logic is opinionated and tightly coupled to the Trading Partner Currency configured on the vendor relationship — not the vendor's Primary Currency or any currency selected during manual conversion.

Currency conversion flow

1. When a purchase requisition is created, the system converts the Trading Partner Currency into the vendor's Primary Currency format on the requisition record.
2. When that requisition is converted to a purchase order, the system converts back to the Trading Partner Currency before transmitting the transaction to the trading partner.
3. The purchase order currency always follows the Trading Partner Currency, regardless of any currency selected during the conversion step. Manual overrides are silently ignored.

Silent failure on bill payments

If the account selected on the SuiteProcurement Preferences page does not share the same currency as the Trading Partner Currency, bill payment records will not be created for credit card-related vendor bills when the bill is approved. There is no documented error — the payment record simply does not generate.

Prerequisites

• The Multiple Currencies feature must be enabled.
• The Trading Partner Currency must already appear as a supported currency on the vendor record's Financial subtab.
• The account configured in SuiteProcurement Preferences must use the same currency as the Trading Partner Currency.

What to do

1. Audit vendor records. For every vendor used with SuiteProcurement, confirm the Trading Partner Currency is listed on the Financial subtab. If it is missing, add it before processing any requisitions.
2. Check SuiteProcurement Preferences. Navigate to the Preferences page and verify the selected account's currency matches the Trading Partner Currency. A mismatch will silently prevent bill payment creation on credit-card vendor bills — there is no runtime warning.
3. Do not rely on manual currency selection during PR-to-PO conversion. The system overrides any user-selected currency and always sends the PO in Trading Partner Currency. Update any internal SOPs or training that suggest otherwise.
4. Review integrations and scripts. If you have SuiteScript automations (e.g., beforeSubmit or afterSubmit User Event scripts) on Purchase Order or Purchase Requisition records that read or set currency fields, verify they account for the automatic conversion behavior. The currency on the PO will not necessarily match what was on the requisition.
5. Test bill approval workflows. If you use credit-card vendor bills through SuiteProcurement, run an end-to-end test with matched and mismatched currencies to confirm bill payment records are created as expected.

Note: Oracle's documentation does not specify which release introduced this behavior or whether it applies retroactively to existing SuiteProcurement configurations. Verify in your sandbox before relying on these mechanics in production.