Deutsch (Deutschland) 
Polski (PL) 
Independent IFS Cloud practice · Procurement
The order looked right in one currency, and cost the wrong number in another
A purchase order in IFS Cloud carries a currency and an exchange rate, and depending on your setup both are fixed when the line is created. The supplier has a default currency on its record. The company reports in a base currency. When the order currency does not match what the supplier or the agreement expects, or when the rate on the line is stale by the time the goods are received, the converted cost differs from the intended one from the start. The goods can arrive exactly as ordered and the value on the receipt still be off. Whether anything lists the lines where the currency, the rate and the supplier default disagree depends on your setup.
Key takeaways
- A purchase order stores its own currency and exchange rate. Depending on your setup, the base-currency value is fixed at order time and does not follow the market until someone changes it.
- A currency that differs from the supplier default, or from the agreement the line should follow, produces a converted cost that no one chose on purpose.
- A stale rate is a separate failure from a wrong currency. The currency can be correct while the rate belongs to a date that no longer reflects the market.
- A unit price can match the agreement exactly and still convert to a wrong cost, because the currency or the rate is off.
- The order currency, its rate, the rate date and the supplier default are recorded in IFS Cloud (worth confirming the exact projections in your environment), so a read-only monitor can list the lines where they disagree without writing anything back. The SCM Automation Pack runs no such rule today; it would be an additional rule built to order.
1.Where a purchase order takes its currency and rate from
A purchase order in IFS Cloud has a currency and an exchange rate on the header, and the line values convert to the company base currency using that rate. Depending on your setup, the rate is taken from the currency rate table valid on the order date and does not follow the market afterwards; whether your orders refresh it is worth checking.
The supplier record carries its own default currency, the one the company agreed to trade in with that vendor. A blanket or price agreement can also state the currency a line should use. So there are three places a currency lives: the supplier default, the agreement, and the order line itself. When an order is raised, IFS Cloud can propose a currency from one of them, and a buyer can change it.
An order raised in a currency the supplier does not normally invoice in, or against a rate captured weeks before the goods are received, produces a base-currency cost that looks settled but was never the intended one. Where nobody compares the three places, the difference stays on the record.
2.Which currency differences change the cost
A foreign-currency order is normal for any company that buys abroad. The risk is a currency or rate that no one chose deliberately for that line. Whether the order agrees with the supplier default and whether its rate still reflects the market can both be read from the record.
| What you see | What it can point to |
|---|---|
| Order currency differs from the supplier default currency | The invoice may arrive in the supplier currency while the order was valued in another, so receipt and matching diverge from the start. |
| Rate on the line is older than a window you set before the receipt date | The base-currency cost reflects a market that has moved, so margin and landed cost are calculated on a number that may no longer hold. |
| Order currency differs from the price agreement it should follow | The line is priced against an agreement in one currency but converted in another, so the agreement protection is lost. |
| Same supplier, same part, two orders in two currencies | A process where currency is chosen per order, which makes spend and margin hard to compare across the same vendor. |
A part ordered correctly, with a unit price exactly right, can still carry a wrong converted cost into inventory valuation and margin. A buyer approving one order at a time does not see that this line departs from the supplier default. A comparison of the order currency with the supplier default and of the rate date with the receipt date lists the mismatched lines.
3.Finding the lines where currency or rate disagrees
The order currency, its exchange rate, the rate date and the supplier default currency are recorded in IFS Cloud and can be read through OData projections without touching a record (the exact projections are worth confirming in your environment). Detection runs on a schedule, with the first scan after you have set the rate-age window, and compares three facts already present on the data:
- Currency against supplier default - order lines whose currency differs from the currency on the supplier record, so the ones that departed from the agreed trading currency appear as a list instead of staying among the open orders.
- Rate age against receipt - lines whose exchange rate belongs to a date well before the goods were received, where your setup values the receipt at the order rate (worth checking), so a rate that may no longer reflect the market is listed before it feeds valuation.
- Currency against the agreement - lines priced against a blanket or price agreement in one currency but raised in another, so the protection the agreement was meant to give is not converted away unnoticed.
Because it is a read-only monitoring pattern, it runs beside purchasing and writes nothing back to IFS. It adds no object inside the client system, so a release update leaves nothing of ours in your IFS to retest. Before each release I check that the standard projections it reads still match, as part of the subscription. The SCM Automation Pack’s three rules (unconfirmed purchase orders, late deliveries, stock below minimum) do not compare currencies, so this would be an additional rule built to order. Choosing the currency stays with the buyer, and the monitor only lists the lines for a person to check.
4.Rolling it out without noise
- Start with suppliers you buy from in one currency - vendors with a single agreed trading currency give the cleanest signal, so an order that breaks from it is unambiguous and worth watching first.
- Dry-run first - in the first week the rule only logs which lines it would have listed, and nothing reaches a buyer.
- Set a rate-age window that fits your market - a stable currency pair and a volatile one tolerate different staleness, so tune the threshold per currency rather than one number for all.
- Read only, no footprint - standard OData reads, nothing written back, no new object inside IFS Cloud.
Related reading
5.Frequently asked questions
What is a purchase order currency mismatch in IFS Cloud?
A purchase order currency mismatch is a purchase order line whose currency or exchange rate does not agree with the supplier default currency, the governing price agreement, or the market on the receipt date. Where the order fixes its rate when it is created, a wrong currency or a stale rate produces a base-currency cost that flows into inventory valuation and margin even though the goods arrive exactly as ordered.
Why is the cost wrong when the unit price on the order is correct?
The unit price is stated in the order currency, and IFS Cloud converts it to the company base currency using the exchange rate on the order. If the currency is not the one the supplier invoices in, or the rate belongs to an earlier date, the conversion differs from the intended one even though the unit price matches the agreement, so the landed cost is off.
Does the SCM Automation Pack check purchase order currencies today?
No. The SCM Automation Pack runs three rules today: unconfirmed purchase orders, late deliveries, and stock below minimum. A rule that compares order currency and rate with the supplier default and the agreement would be an additional rule built to order, and a 30-minute call checks whether it fits your data.
Does this monitoring write anything to IFS Cloud?
No. The order currency, its exchange rate, the rate date and the supplier default currency are read through OData projections and compared outside IFS. Nothing is written back, so there is no upgrade footprint and no new object inside the client system. Choosing or correcting the currency stays a purchasing decision.
6.About the author
Dariusz Myśliwiec brings 18 years hands-on with IFS (Apps 7.5–10 and IFS Cloud). IFS Certified Associate Consultant. PRINCE2® 7. Based in Kraków, delivering remotely across Europe and globally as an independent practice, so you talk to the consultant who builds it.
Selected clients: Fugro · LGC · BVI Medical · Betafence (PRÆSIDIAD) · Barlinek · NGK Ceramics · Newag · Oleofarm.
IFS is a registered trademark of IFS AB; this practice is not affiliated with IFS AB.
Know which orders converted at the wrong number
Tell me where currency drift hurts your landed cost most. On a 30-minute fit call we check whether a rule that compares open purchase orders with the supplier default currency and the rate date fits your data. The SCM Automation Pack runs three rules today (unconfirmed purchase orders, late deliveries, stock below minimum), so this would be an additional rule built to order, with a dry-run week before anything reaches a buyer.
