An inventory movement type explains why a product's recorded quantity or location changed. The best type is not simply the option that produces the desired final number. It is the option that describes the physical event a later reviewer should see in the history.
This guide explains the movement categories used in Invoice Master and how to choose between them. For the complete relationship between products, locations, invoices, and plan limits, read Invoice Master's inventory workflow. You can also review the invoicing and inventory feature overview.
What a useful stock movement record contains
At minimum, a movement should identify:
- the product;
- the quantity added, removed, or moved;
- the source or destination location when applicable;
- the movement type;
- the time of the event; and
- enough context to explain unusual activity.
The movement type answers the reason question. The quantity answers how much changed. The location answers where it changed. Combining those details makes the stock-on-hand figure reviewable instead of leaving only a current total.
Addition
Use an Addition when stock enters the recorded inventory and no more specific workflow is required. Examples include establishing a verified opening quantity, receiving a simple restock outside a purchase-order workflow, or adding previously unrecorded units whose arrival is known.
An Addition should not be used to hide a counting difference. If the system quantity is wrong and the original inbound event cannot be established, a Correction describes the situation more accurately.
Sale
Use a Sale movement when a customer-facing physical handoff reduces stock. The operating procedure should define the trigger, such as dispatch, delivery, installation, or collection.
Creating an invoice is not the trigger by itself in Invoice Master. A draft may be changed or cancelled, a deposit invoice may precede delivery, and a paid invoice may describe stock that moved earlier. Record the Sale when the physical event occurs, then use the invoice as related evidence when useful.
Removal
Use a Removal when stock leaves ordinary inventory for a reason that is not represented more accurately by Sale, Damage, Expiry, Sample, or another specific type. Add context when the reason would otherwise be unclear.
Specific types make reports and reviews easier. If every decrease is recorded as Removal, the final quantities may be correct while the business loses the explanation for why stock disappeared.
Transfer
Use a Transfer when stock moves from one recorded location to another. A transfer should preserve both sides of the event: where the quantity left and where it arrived.
For example, moving five filters from Main Warehouse to Van A should reduce the first location and increase the second without changing the company-wide total. Confirm the destination after the physical handoff so stock is not shown in the van while it remains on the warehouse shelf.
Return and rental
Use a Return when stock comes back from a customer or another external handoff. Check its condition before treating it as ordinary available stock.
Use a Rental movement when the item is temporarily handed out or returned under a rental workflow. A rental is different from a sale because ownership and the expected return remain part of the operational context.
Invoice Master records these as explicit inventory events. It does not provide a full rental-management system with contracts, availability calendars, deposits, or automated return schedules.
Damaged, expired, and lost stock
Use the specific type that explains why stock is no longer usable or present:
- Damaged for items that cannot remain in ordinary available stock because of physical damage;
- Expired for products removed because their usable date has passed; and
- Lost for stock that cannot be located after reasonable investigation.
These categories should not be interchangeable with a Correction. A correction says the record was wrong. Damage, expiry, and loss say a known operational event changed the usable quantity.
Recall
Use a Recall when stock must be removed or controlled because of a recall event. Invoice Master can record the movement reason, but it does not provide regulated recall orchestration, batch tracing, serial tracking, customer notification, or compliance reporting.
If those controls are required, keep the authoritative recall process in a suitable specialized system and use Invoice Master only within its documented scope.
Sample
Use a Sample when stock leaves available inventory for demonstration, testing, promotion, or another sample handoff. Separating samples from sales makes it possible to review product usage that did not create an ordinary customer sale.
Correction
Use a Correction after a verified count shows that the recorded quantity is wrong and a more specific missing event cannot be reconstructed confidently.
Suppose the system shows 24 units at a location and a physical count confirms 22. If movement history proves that two units were delivered but the Sale movement was missed, record the Sale. If the cause cannot be established, record a correction of minus two with the count date and investigation note.
The inventory reconciliation checklist explains the full count, investigation, and correction workflow.
A movement-type decision rule
Ask these questions in order:
- Did stock physically move between two recorded locations? Use Transfer.
- Did a known customer, return, rental, sample, damage, expiry, loss, recall, or removal event change stock? Use the matching specific type.
- Did a known inbound event add stock? Use Addition.
- Did a verified count prove the record is wrong without a recoverable cause? Use Correction.
This order prevents a correction from replacing a known event merely because it is faster to enter.
Common stock movement mistakes
Treating an invoice as a stock movement
Billing and physical stock are related but separate. Creating, sending, or paying an invoice does not change stock-on-hand in Invoice Master.
Choosing a generic type for every decrease
Overusing Removal or Correction produces the right total but a weak history. Use Sale, Damage, Expired, Lost, Sample, or another specific type when the cause is known.
Completing a transfer on only one side
A transfer is incomplete when the source decreases but the destination is not confirmed. Review both locations and the company-wide total.
Editing history instead of recording the repair
Keep the original movement visible and add the correcting event. A reviewable sequence is more useful than a history that was rewritten to look perfect.
A monthly movement review
Group movements by type and look for unusual patterns. Frequent corrections may point to a broken handoff. Repeated loss or damage may require storage changes. Transfers that remain unresolved may indicate that destination confirmation is missing. Sales without corresponding dispatch evidence may signal that the trigger is poorly defined.
The goal is not merely a correct total. It is a movement history that explains how the business reached that total.
Inventory movement questions
What is the difference between an addition and a correction?
An addition records a known inbound stock event. A correction repairs a recorded quantity after verification when the original cause cannot be represented more accurately.
Is a transfer an increase or a decrease?
It is both across two locations. The source decreases and the destination increases, while the company-wide quantity stays the same.
Should I record a sale when I create the invoice?
Record the Sale at the physical trigger chosen by the business, such as dispatch or delivery. Creating the invoice alone does not prove that stock moved.
Which movement type should I use after a stock count?
Use the specific missing movement when the cause is known. Use Correction when the verified count differs from the record and the original event cannot be reconstructed safely.