1. Inventory Valuation System
  2. Features
  3. Cost foundations
Feature · Cost foundations

Cost foundations

The first valuation decision is which entity owns the goods and which product standard applies on the transaction date.

OverviewPending human decisions
Inventory Valuation System · Cost foundations

Pending human decisions

Approval conditions

New
Decision numberActionScopeRequested atAssigned toRequested by
AD-27978Master activationSCP-94404 Oct
AD-27846Policy activationSCP-49822 Oct
AD-50199Order acceptanceSCP-55109 Oct
AD-49814Credit exceptionSCP-32019 Oct
AD-31357Purchase approvalSCP-35117 Oct
6 of 6 records
SCP-944Approval decisions · AD-27978
Master activation
Requested at04 Oct
StatusPending
Example screen with sample data

What you can do

Cost foundations in practice

The first valuation decision is which entity owns the goods and which product standard applies on the transaction date. Finance Manager works with Warehouse Manager to establish the approved basis before receipts, assembly and adjustments use it. An effective cost version gives the team a stable reference; changing a master later does not silently rewrite a posted movement.

How the work is organized

  • Entity ownership. Choose the owning entity before associating stock positions or monetary postings.
  • Product basis. Keep the product, base unit and active standard together when reviewing a receipt or output.
  • Approval. Record the independent decision that activates the master or policy version.

What to agree during setup

Agree the functional currency, the product base unit, the effective dates for standards and the policy thresholds for a count difference. Finance Manager should inspect the cost basis and confirm who can prepare a version and who can approve it. Warehouse Manager should confirm warehouse assignments and how held stock is distinguished from available stock. A new standard applies to future eligible work; existing source history remains traceable.

Check the handoff on an actual case

Take a stocked product whose standard changes at a new effective date. Inspect the earlier receipt and its remaining layer before activating the new version. Then prepare another receipt after the date. The two source records should retain the evidence used at their respective times. If an approval is rejected, the draft version remains out of use; it must not become the basis for a stock posting.

What your team sees

  • Cost versions in force — Inspect the active unit standard, date window and cost basis before a receipt or output.
  • Open cost layers — Check which earlier source layers still carry value after the change.

The setup review should follow one named product into a real transaction. Check the effective date beside the receipt date and the owning entity beside the warehouse. If the product’s unit or standard changes, confirm which version the later work uses and which earlier layers remain open. This makes the activation decision concrete for both teams. Accountant can then reconcile the source value without assuming a master edit changed a posted balance. Keep the approved policy version with the rule that governed a count or stock release.

Use the effective date as a handoff control. Accountant can compare a receipt just before the change with one just after it, using each receipt’s recorded standard and rate evidence. Finance Manager should check that the new version has the intended owning entity and product, and that an older open layer still points to its original source. If the date window or cost basis is wrong, correct the draft and seek a fresh decision before any new acceptance uses it.

Follow the work through

Follow the related process and check the data model when mapping your source records. During rehearsal, compare the source document, the decision and the resulting value effect. Keep the accountable person visible at each handoff.

What it keeps track of

Data model
Organizations
Separate legal books and stock ownership; shared masters do not consolidate balances.
Stock items
Trade goods and assembly outputs; master values do not rewrite transactions.
Standard costs
Entity/product standard per base unit with immutable effective versions.
Distribution policies
Versioned operational and financial rules with explicit finite limits.
Master changes
Protected master activation without direct Manage permission bypass.
Approval decisions
Authoritative human decisions independent of document lifecycle.

Who uses it

Permissions
Finance Manager
Owns the financial basis and independent activation decision.
Warehouse Manager
Validates operational scope.
Admin
Maintains users and configuration without taking the commercial decision.

Set up Inventory Valuation System your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started