Purchasing, inventory, and project costing should share the same requirement and transaction history while keeping each stage distinct. A requisition or supplier order shows planned or committed spend; a receipt records arrival; an inventory issue or other accepted event records use; and the project-cost view explains what is baseline, committed, actual, and forecast.
Purchasing, inventory, and project costing describe different parts of the same operational story. Problems arise when each team keeps its own version and combines the numbers only at month end.
A connected setup does not collapse every event into cost. It preserves the meaning of each event and lets the project view bring them together.
One chain, several meanings
The requirement identifies demand. The supplier order records an approved commercial commitment. The receipt confirms quantity and condition. Inventory movements explain where material went. The project-cost view applies clear rules to show the resulting position.
Keeping these links means a user can investigate a project variance without guessing which spreadsheet, bill, or warehouse transaction produced it.
Keep cost states distinct
| State | Typical evidence | What it helps answer |
|---|---|---|
| Baseline | Approved project estimate or budget | What was expected? |
| Planned | Current material or work requirement | What do we now expect to need? |
| Committed | Approved open supplier orders and other commitments | What spend is already agreed? |
| Actual | Accepted operational and accounting events | What has been recorded? |
| Forecast | Actuals plus remaining work under defined assumptions | Where may the project finish? |
Use labels and calculation rules consistently. A single figure called “cost to date” is not enough if nobody can tell which states it includes.
Explain the inventory boundary
Receiving material does not always mean the project has consumed it. The goods may sit in a warehouse, be reserved for a job, move between locations, be issued to work, or be returned. Each step changes a different operational question.
Inventory valuation method and landed-cost treatment also affect the value attached to a movement. The project view should use the platform's controlled calculation and retain the transaction that supports it, rather than accept a value typed into a separate report.
Handle changes and exceptions visibly
Real work includes partial receipts, supplier price changes, damaged quantities, substitutions, returns, cancelled requirements, and bills that do not match the order or receipt. These should appear as reviewable events.
Do not repair the history by changing an old quantity without explanation. Use controlled revisions, returns, cancellations, or corrections so the current position and the path to it remain understandable.
Questions your system should answer
- What material is required, available, reserved, ordered, expected, and issued for this project?
- Which open commitments are included in the project forecast?
- Why did the projected cost change since the last baseline?
- Which supplier order, receipt, inventory movement, or bill supports this amount?
- What exceptions still need review?
Ask these questions using a real project during evaluation. A credible answer should identify its cut-off, currency, and supporting records.
How Datum connects these records
Datum links project requirements to purchasing, inventory, builds, and project-cost views. Teams can distinguish the published baseline, commitments, recorded cost, and forecast, then follow figures back to the operational records behind them.
Purchasing includes requisitions, approvals, supplier quotations, orders, receipts, matching, and variances. Inventory retains reservations, movements, issues, returns, and cost layers. The exact accounting and implementation path is agreed for the selected edition and business requirements.
Related questions
Does a purchase order count as actual project cost?
Normally it represents a commitment, not completed activity. The exact accounting treatment depends on policy, but the operational view should not hide the distinction.
When does inventory affect a project?
That depends on the controlled event and costing policy. An issue to the project is a common operational boundary; the platform should show the movement and the value used.
How should returns be handled?
Record a reversing or return movement linked to the original project and material activity. Do not silently edit the earlier event.
Why do project-cost reports disagree?
They may use different cut-off dates, currencies, cost layers, or definitions of commitment and actual cost. Agree those rules and retain links to the underlying records.