Currency differences can make contractor purchasing reviews harder, especially when teams compare supplier prices, project commitments and receipts across purchase documents. A practical control is to review the purchase order’s currency and rate evidence alongside the item’s documented purchasing history before approving or accounting for the commitment.
What to check before approving a purchase order
Start with the supplier, project, item and document date. Then compare the purchase order with the relevant item price history. BlueberryERP’s Items Price History screen supports filters for date ranges, activity, sub-activity, project, store and item. Its documented latest order price is based on the most recent unit price from any LPO, determined by the latest document date.
| Review stage | Evidence to compare | Control question |
|---|---|---|
| 1. Identify the commitment | Purchase order, supplier, project, item and document date | Is this the correct supplier, project and item? |
| 2. Check the currency basis | Order currency, stated exchange rate and converted value where applicable | Are the currency and rate explicitly recorded and internally consistent? |
| 3. Compare purchasing history | Item Price History filtered by item, date, project or store | Is the difference from recent LPO prices understood? |
| 4. Reconcile downstream evidence | Receipt and accounting records | Does the received and accounted value follow the approved purchasing basis? |
Use item price history to investigate exceptions
When a new order appears higher or lower than recent purchases, select the item in Item Price History to refresh the results. If no item is selected, the screen shows only the top 100 records; selecting an item or applying filters provides a more focused review. Use a custom from-date and to-date range when the comparison needs to match a tender, project phase or reporting period.
Review the project, store, activity and sub-activity dimensions when available. A price difference may reflect a different project requirement, store context, specification or purchase period. The purpose of the check is to create a documented question for purchasing and finance, not to assume that every variance is an error.
Separate currency review from price-variance review
A currency check answers whether the order’s currency and exchange-rate basis are clear and consistently carried into the review. An item-price check answers whether the unit price differs from comparable purchasing history. Keeping these questions separate helps the team avoid treating a foreign-currency conversion difference as a supplier-price change.
Before the order proceeds, record the exception, its supporting document and the person responsible for resolving it. Where the value cannot be reconciled, hold the review for clarification rather than presenting an unverified rate as a system-generated fact.
A practical review routine for UAE contractor teams
- Confirm the supplier, project, item, document date and order currency.
- Record the stated exchange-rate basis and check the arithmetic independently.
- Open Item Price History and filter by the relevant item and comparison period.
- Compare recent LPO prices while accounting for project, store and activity differences.
- Document the reason for any unexplained currency or price variance.
- Pass the resolved evidence to the responsible purchasing or finance approver.
BlueberryERP provides documented purchasing-history filters that can support this review. The final decision remains with the contractor’s authorized purchasing and finance team, using its approved commercial and accounting policies.
To discuss how BlueberryERP can support construction purchasing and project-control workflows, visit the Blueberry consultation page or review the BlueberryERP overview.
