Item Master is where ERP discipline either begins or breaks.
Item / SKU Master Creation and Maintenance looks operational from far away. In a real finance team, it is a chain of assertions: the right actor started the work, the required records existed, the control policy was applied, the state change was preserved, and the outcome can be explained later without rebuilding the transaction from emails and spreadsheets.
The expected business outcome is specific: Single authoritative item master consumed by all modules; zero duplicate SKUs; new items available for transactions within 30 seconds of creation.
The control flow a finance team actually needs.
Step 1
Unique Item Code Per Entity
Step 2
Mandatory Fields: Description, Primary...
Step 3
Optional: Alternate UOMs With...
Step 4
Field-Level Audit Log
Step 5
Bulk Import Via CSV With Validation Report
The ERP surface involved.
Module
Item Master
Actors
Inventory Manager, Product Data Steward, Platform API
Tier
Tier 1
Finance area
Inventory & Warehouse Management
Region lens
US and UK finance teams
Publication date
April 29, 2026
Unique item code per entity (`item_<snowflake>`); mandatory fields: description, primary UOM, costing method (FIFO/LIFO/weighted-avg/standard), GL inventory account; optional: alternate UOMs with conversion factors, barcode(s), lot/serial tracking flag, expiry tracking flag, minimum shelf-life-on-receipt days, ABC class, reorder point, safety stock qty, preferred vendor; field-level audit log; bulk import via CSV with validation report; deactivation (not deletion) of items with open transactions; search by code, description, barcode, category.
US and UK teams have different compliance hooks, but the same control problem.
US teams usually care about clean evidence for audit support, vendor records, payment controls, tax reporting, and management review. UK teams usually care about VAT-ready records, approval evidence, digital-record discipline, and traceable postings. The country-specific details differ, but the operating pattern is the same: the ERP needs controlled records, explicit ownership, defensible state changes, and evidence that survives beyond the person who completed the task.
The control matrix.
| Control area | Requirement | Acceptance proof |
|---|---|---|
| Control 1 | | Given an entity with no existing item code "SKU-001" |
| Control 2 | mandatory fields: description, primary UOM, costing method (FIFO/LIFO/weighted-avg/standard), GL inventory account | when inventory manager creates an item with code, description, primary UOM, costing method, and GL inventory account |
| Control 3 | optional: alternate UOMs with conversion factors, barcode(s), lot/serial tracking flag, expiry tracking flag, minimum shelf-life-on-receipt days, ABC class, reorder point, safety stock qty, preferred vendor | |
| Control 4 | field-level audit log | negative) when a duplicate item code is submitted for the same entity then 409 DUPLICATE_ITEM_CODE. |
| Control 5 | bulk import via CSV with validation report | Single authoritative item master consumed by all modules; zero duplicate SKUs; new items available for transactions within 30 seconds of creation. |
| Control 6 | deactivation (not deletion) of items with open transactions | Single authoritative item master consumed by all modules; zero duplicate SKUs; new items available for transactions within 30 seconds of creation. |
Audit evidence is a chain, not a folder.
| Evidence layer | What should be preserved |
|---|---|
| Business event | Inventory manager creates a new SKU by entering item code, description, unit of measure (UOM), item category, costing method, reorder point, safety stock, and storage attributes. The system validates uniqueness of item code within the entity, assigns a system ID, and persists the master record. Linked records are auto-created: default costing layer entry, GL account mapping, and UOM conversion factors. The item is immediately available for PO, SO, and transfer transactions. |
| Control rules | |
| Acceptance proof | |
| Data record | |
| System event | |
| Lifecycle state | |
The useful version of this workflow is not only fast. It is inspectable. A controller, auditor, or operator should be able to move from source event to system record to state transition to final business outcome without guessing.
Implementation contracts.
Reference data model
`inventory_item` { id: string, external_id: string, entity_id: string, item_code: string, description: string, primary_uom: string, costing_method: enum(FIFO,LIFO,WEIGHTED_AVG,STANDARD), gl_inventory_account_id: string, reorder_point: int, safety_stock_qty: int, lot_tracked: bool, serial_tracked: bool, expiry_tracked: bool, abc_class: enum(A,B,C), status: enum(ACTIVE,INACTIVE) }; `uom_conversion` { item_id, from_uom, to_uom, factor: decimal }; (reference, product may differ).API and events
`POST /v1/inventory-items` { item_code, description, primary_uom, costing_method, gl_inventory_account_id, external_id, ...optional_fields } -> 201 { id, status: ACTIVE }; `GET /v1/inventory-items/{id}`; `PATCH /v1/inventory-items/{id}` { status: INACTIVE } for deactivation; `POST /v1/inventory-items/bulk-import` { csv_data } -> 202 { job_id }; emits `inventory.item_created` event; idempotent via `external_id`.State transitions
`ACTIVE -> INACTIVE`; guard: deactivation blocked if open PO/SO/transfer lines reference the item; no hard delete; reactivation allowed.Common implementation traps.
Treating the workflow as data entry
If the ERP only stores the final record, the team loses the decision trail that explains how the record became valid.
Hiding exception logic
Exceptions need owners, reason codes, and time stamps. A vague pending state is not a control.
Posting without recovery design
Retries, duplicate submissions, and partial failures must be explicit so the system does not create inconsistent records.
Skipping evidence design
A workflow that cannot produce evidence on demand will eventually push finance teams back into manual screenshots and spreadsheets.
Where Rivane fits.
Rivane is built for finance workflows where automation must stay tied to source documents, approvals, state transitions, ledger impact, reporting, and audit evidence. Use this guide as a checklist for evaluating whether an ERP workflow is merely digitized or actually controlled.
References and source basis.
These sources provide the standards, regulatory, or government context around the flow. They are included so the guide is useful to finance operators, auditors, and implementation teams, not only buyers reading software copy.