Transfers, stock counts and cycle counting

Moving stock between sites and keeping the books equal to the shelf.

Baca dalam Bahasa Indonesia

On this page
  1. Stock transfers
  2. Why counts matter
  3. Cycle counting
  4. Posting differences with a reason
  5. In Voltrus
  6. Checklist

Two things make stock figures drift away from reality: goods that move without a document, and errors nobody notices until the year-end count. Transfers fix the first. Counting, done often and in small pieces, fixes the second.

Stock transfers

A stock transfer moves goods from one warehouse (or bin) to another. It changes where stock is, not what the company owns, so it does not change inventory value.

In Voltrus a transfer goes draft → done (or cancelled). Marking it done writes both movements at once: one out of the source, one into the destination. Nothing can be "half moved". Bin-to-bin moves inside one warehouse use the same document.

Two dates on the transfer feed planning: ship_date and expected_date. While it is still a draft, MRP counts it as demand at the source on the ship date and as supply at the destination on the expected date. Transfer lead time defaults from the item's warehouse setting, then from the warehouse, then zero.

Goods on the road

A Voltrus transfer completes in one step; there is no built-in "in transit" status. When goods take days to travel and you need to see them on the way, model the truck as a warehouse:

  1. Create a warehouse of kind transit (for example TRANSIT-SBY).
  2. When the truck leaves, post a transfer from the source to TRANSIT-SBY.
  3. When it arrives, post a second transfer from TRANSIT-SBY to the destination.

Transit warehouses are valued but not counted as available, so nobody sells goods that are still on the road, and the balance sheet still shows them. Anything left in transit at month end is a question to chase.

Why counts matter

Every ERP's stock figure is a model of the shelf. Theft, breakage, wrong picks, a receipt posted to the wrong item: each one makes the model drift. Auditors test inventory by counting a sample, and companies traditionally do a full stock opname at year end: close the warehouse, count everything, post the differences.

The full count works but has problems. It stops operations, it is done by tired people in a hurry, and errors found in December may have distorted margins since March.

Cycle counting

Cycle counting replaces (or reduces) the annual count with small counts every working day, so every item is counted several times a year without closing the warehouse. The standard way to decide what to count is ABC classification by consumption value:

ClassShare of consumption valueTypical share of itemsCounts a year in Voltrus
Afirst 80%~10–20%12
Bnext 15%~20–30%4
Clast 5% (and items with no use)~50–70%1

A items are where money and mistakes concentrate, so they are counted monthly; C items once a year.

Voltrus ranks items by the value of shipments and issues (less returns), and you can pin an item to a class by hand. On each working day the schedule drafts one count per warehouse with the items that are due, capped so the workload is spread evenly over the year.

Blind counts

A counter who can see the book quantity tends to "find" it. Cycle counts in Voltrus are blind by default: counters enter what they see, and only a supervisor sees the book quantity and the variance once the count is entered.

Recount tolerance

Not every difference should be posted immediately. A recount tolerance (a percentage, a value, or both) flags lines whose variance is too large. A flagged line needs a second count before posting, or an admin override. Most big variances turn out to be counting errors or unposted documents, not real losses.

Posting differences with a reason

When a count is posted, Voltrus records the book quantity and writes an adjust movement and journal for each variance. Every adjustment carries a reason code, and each code points to a GL account, so losses land where management can see them:

CodeMeaningDirection
COUNTStock count difference (default for counts)In or out
CORRECTIONBooking correctionIn or out
DAMAGEDamagedOut
EXPIREDExpiredOut
THEFTTheft or lossOut
SAMPLESamples given awayOut
WRITE_OFFWritten offOut
FOUNDFound stockIn

A count that finds 4 units missing of an item costing Rp 50,000 posts:

AccountDebitCredit
5-9000 Cost Variance (or the reason's account)200,000
1-1300 Inventory200,000

The setting require_adjust_reason makes a reason mandatory on every manual adjustment as well. Turn it on: an adjustment without a reason is an unexplained loss.

In Voltrus

Checklist

  • Create a transit warehouse for every route where goods spend more than a day on the road.
  • Recalculate ABC classes and draft cycle counts every working day.
  • Keep counts blind; let supervisors review variances.
  • Set a recount tolerance and investigate before posting large differences.
  • Turn on mandatory reason codes and review the adjustments-by-reason report monthly.
  • Keep a year-end count only for items your auditors ask for, once cycle counting runs reliably.

Run it in Voltrus ERP

Everything in these guides is built in: documents that post to the ledger as they happen, Indonesian tax, MRP and costing, with AI agents that propose and people who approve.

See Voltrus ERP