Cycle Count / Physical Inventory is where ERP discipline either begins or breaks.
Cycle Count Scheduling and Execution 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: Inventory accuracy ≥99.5% for A-items; shrinkage and discrepancies identified and posted within the count period; no year-end wall-to-wall count required.
The control flow a finance team actually needs.
Step 1
Configurable Count Schedules By ABC...
Step 2
Count Tasks Assigned To Users With...
Step 3
Quantity Hidden Until Count Is Submitted
Step 4
Variance Threshold Configuration
Step 5
Multi-Counter With Recount Workflow For...
The ERP surface involved.
Module
Cycle Count / Physical Inventory
Actors
Inventory Control Analyst, Warehouse Counter, Platform API
Tier
Tier 1
Finance area
Inventory & Warehouse Management
Region lens
US and UK finance teams
Publication date
May 2, 2026
Configurable count schedules by ABC class, zone, item, or location; count tasks assigned to users with mobile device support; system quantity hidden until count is submitted (blind count); variance threshold configuration (absolute qty and % of value); multi-counter support with recount workflow for high-variance items; approval workflow for adjustments above value threshold; GL adjustment journal posted on approval (Dr/Cr Inventory Adjustment expense account and Inventory asset account); count history retained for 7 years; performance: generate count sheet for 10,000 locations in <30 s.
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 | Configurable count schedules by ABC class, zone, item, or location | Given a configured cycle count schedule and assigned count tasks |
| Control 2 | count tasks assigned to users with mobile device support | when counters submit physical counts without seeing system quantities |
| Control 3 | system quantity hidden until count is submitted (blind count | then variances above tolerance are flagged, supervisor approves adjustments, approved adjustments post a GL inventory adjustment journal atomically, and on-hand quantities update |
| Control 4 | variance threshold configuration (absolute qty and % of value | negative) when an adjustment above the value threshold is submitted without approver sign-off then 403 APPROVAL_REQUIRED. |
| Control 5 | multi-counter support with recount workflow for high-variance items | Inventory accuracy ≥99.5% for A-items; shrinkage and discrepancies identified and posted within the count period; no year-end wall-to-wall count required. |
| Control 6 | approval workflow for adjustments above value threshold | Inventory accuracy ≥99.5% for A-items; shrinkage and discrepancies identified and posted within the count period; no year-end wall-to-wall count required. |
Audit evidence is a chain, not a folder.
| Evidence layer | What should be preserved |
|---|---|
| Business event | Inventory control analyst schedules cycle counts by zone, ABC class, or location using a configurable frequency (A-items weekly, B-items monthly, C-items quarterly). On count date, the system generates count sheets or mobile task assignments without displaying current system quantities. Counters scan bins and enter physical counts. The system compares physical count to system on-hand and flags variances above a configurable tolerance. A supervisor reviews and approves adjustments; approved adjustments post a GL inventory adjustment journal and update on-hand quantities. |
| Control rules | Configurable count schedules by ABC class, zone, item, or location; count tasks assigned to users with mobile device support; system quantity hidden until count is submitted (blind count); variance threshold configuration (absolute qty and % of value); multi-counter support with recount workflow for high-variance items; approval workflow for adjustments above value threshold; GL adjustment journal posted on approval (Dr/Cr Inventory Adjustment expense account and Inventory asset account); count history retained for 7 years; performance: generate count sheet for 10,000 locations in <30 s. |
| Acceptance proof | Given a configured cycle count schedule and assigned count tasks; when counters submit physical counts without seeing system quantities; then variances above tolerance are flagged, supervisor approves adjustments, approved adjustments post a GL inventory adjustment journal atomically, and on-hand quantities update; (negative) when an adjustment above the value threshold is submitted without approver sign-off then 403 APPROVAL_REQUIRED. |
| 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
`cycle_count_schedule` { id: string, entity_id: string, abc_class: string, zone: string, frequency: string, next_run: date }; `count_task` { id: string, schedule_id: string, location_id: string, item_id: string, assigned_to: string, counted_qty: int, system_qty: int, variance_qty: int, status: enum(PENDING,COUNTED,VARIANCE_REVIEW,APPROVED,ADJUSTED) }; `cycle_count_adjustment` { id: string, count_task_id: string, gl_journal_id: string, approved_by: string }; (reference, product may differ).API and events
`POST /v1/cycle-count-tasks/generate` { schedule_id } -> 201 { tasks:[...] }; `POST /v1/cycle-count-tasks/{id}/submit-count` { counted_qty } -> 200 { variance_qty, requires_approval: bool }; `POST /v1/cycle-count-tasks/{id}/approve` -> 200 { gl_journal_id }; `GET /v1/cycle-count-schedules/{id}/count-history`; emits `inventory.count_adjustment_posted` event; idempotent via `external_id`.State transitions
`PENDING -> COUNTED -> VARIANCE_REVIEW -> APPROVED -> ADJUSTED`; terminal `REJECTED`; guard: system qty hidden until count submitted; recount required if variance > high-value threshold before APPROVED.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.