Purchase Orders, Vendors, and nested objects

Purchase Orders and Vendors

Purchase Orders include additional currency consistency logic.

The Vendor list is filtered by the current Currency Code so that the Purchase Order and Vendor use the same currency.

For example:

• If a Purchase Order is in JPY, the Vendor should also match JPY

• If the Purchase Order already has line items, changing Vendor or Currency Code should be restricted or validated

• Workflow rules help prevent inconsistent financial data

Nested objects

Nested financial objects inherit currency from their parent object. They do not have an independent Currency Code selection.

Nested object	Currency source
PO Items	Parent Purchase Order
Invoices	Parent Purchase Order
Invoice Items	Parent Invoice / Purchase Order chain
Vendor Products	Parent Vendor

The system default currency cannot be changed after activation. Individual records can still use another available Currency Code when workflow rules allow it. If a parent record's currency changes, related nested monetary values follow the parent currency logic.

Nested records do not have their own Currency Code field. For example, if a Purchase Order uses EUR, all monetary fields in its PO Items, Invoices, and Invoice Items use EUR as well, without independent currency selection on those nested records.