> ## Documentation Index
> Fetch the complete documentation index at: https://docs.arcuserp.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Receive Inventory

> Use Receive Inventory for standalone stock receipts such as found stock, opening balances, or non-PO inbound inventory.

## Choose the Right Receiving Path

Arcus has two receiving paths. Choose the path based on why the stock
is coming in.

* **Purchase order receiving**: use the PO detail page when stock is arriving against an open purchase order.
* **Standalone receiving**: use Inventory Receive for found stock, beginning balances, or other inbound stock that is not tied to a PO.

<Warning>
  **Use the PO flow for purchase orders**
  If the inventory is arriving from a purchase order, open the purchase
  order and receive it there. The PO flow carries vendor, expected
  quantity, unit cost, receipt progress, and later bill matching context.
</Warning>

<Frame caption={"The page reminds operators to use PO-driven receiving when stock belongs to an open purchase order."}>
  <img src="https://mintcdn.com/arcuserp/MrJkb10V6EpIZu0o/images/support/screenshots/inventory/inventory-receive-main.png?fit=max&auto=format&n=MrJkb10V6EpIZu0o&q=85&s=947fc7c6848a5b2445c0de0ad0915a80" alt="Receive Inventory page with a purchase order receiving guidance banner, standalone receive form, and Recent Receives table" width="1620" height="760" data-path="images/support/screenshots/inventory/inventory-receive-main.png" />
</Frame>

## Before You Receive

Confirm the product, location, quantity, and unit cost before posting.
Receiving changes inventory immediately and establishes the cost layer
used by future fulfillment and cost reporting.

* The product must be a stocked product. Services and non-stock records are not valid receiving targets.
* The location should be the physical place where the stock is being added.
* Quantity must be positive.
* Unit Cost is required and must be greater than zero.
* Notes should explain why the receipt was posted, especially for found stock or opening balances.

<Note>
  **Unit Cost is not optional**
  A receipt creates inventory cost basis. Arcus blocks blank, zero, and
  negative unit cost because future FIFO cost and COGS depend on this value.
</Note>

## Receive Standalone Stock

1. Open **Inventory**.
2. Open **Receive**.
3. Select the stocked product.
4. Select the receiving location.
5. Enter the quantity being added.
6. Enter the unit cost for the stock.
7. Add a note that explains the receipt.
8. Select **Receive Inventory**.

<Frame caption={"The standalone form requires product, location, quantity, and a positive unit cost before it can post."}>
  <img src="https://mintcdn.com/arcuserp/MrJkb10V6EpIZu0o/images/support/screenshots/inventory/inventory-receive-form.png?fit=max&auto=format&n=MrJkb10V6EpIZu0o&q=85&s=d8e228b9f7fa3c6b46bd57eab43a7253" alt="Standalone Receive Inventory form with Product, Location, Quantity, Unit Cost, Notes, and disabled Receive Inventory button" width="760" height="520" data-path="images/support/screenshots/inventory/inventory-receive-form.png" />
</Frame>

## What Happens After Posting

After a successful receive, Arcus updates stock and cost records
together so the inventory view, transaction audit trail, and accounting
value stay aligned.

* On-hand and available stock increase at the selected location.
* A receiving transaction appears in Inventory Transactions.
* A FIFO cost layer is created at the unit cost entered on the receipt.
* Inventory value increases based on quantity times unit cost.
* The Recent Receives table refreshes with the new receipt.

<Tip>
  **Check the transaction when cost matters**
  Open Inventory Transactions after posting if you need to confirm the
  receipt date, location, quantity, unit cost, and total value.
</Tip>

## Review Recent Receives

The Recent Receives table shows the latest inbound standalone receipts.
Use it as a quick confirmation that the receipt posted to the expected
product and location.

* **Date**: when the receipt posted.
* **Product**: the stocked item received.
* **Location**: where the stock was added.
* **Qty**: the received quantity.
* **Unit Cost**: cost entered for each unit.
* **Total**: quantity times unit cost.

<Frame caption={"Recent Receives is the fastest confirmation that the standalone receipt posted."}>
  <img src="https://mintcdn.com/arcuserp/MrJkb10V6EpIZu0o/images/support/screenshots/inventory/inventory-receive-recent.png?fit=max&auto=format&n=MrJkb10V6EpIZu0o&q=85&s=1f6c0e99dad6a487f6b6f91482e9bf40" alt="Recent Receives table showing receipt date, product, location, quantity, unit cost, and total value" width="760" height="820" data-path="images/support/screenshots/inventory/inventory-receive-recent.png" />
</Frame>

## When Not to Use This Page

* **Open PO receipt**: receive from the purchase order detail page.
* **Counting stock**: use Inventory Adjustments or cycle counts so the change records the counted quantity.
* **Moving stock**: use warehouse transfers so source and destination locations stay balanced.
* **Returned customer stock**: receive through the return workflow so condition and disposition are recorded.
* **Damaged or scrapped stock**: use the correct return, adjustment, or writeoff workflow instead of adding stock here.

## Recovery Scenarios

* **You received a PO item here by mistake**: stop receiving additional lines, review the PO, and use a documented correction so inventory and PO receipt history both tell the truth.
* **Unit cost was entered incorrectly**: review the receiving transaction immediately. If the cost layer is wrong, escalate to inventory or accounting before fulfillment consumes it.
* **The wrong location was used**: move the physical stock and post the appropriate transfer or corrective adjustment so on-hand follows the warehouse.
* **The quantity was too high**: post a documented adjustment for the overage instead of deleting history.

## Common Blocks

* **Receive button is disabled**: product, location, quantity, or positive unit cost is missing.
* **Product is missing from the picker**: the record may not be stockable.
* **Unit Cost will not accept zero**: receiving at zero cost is blocked to protect FIFO and COGS.
* **Wrong location was selected**: correct the stock through the appropriate adjustment or transfer workflow.
* **Receipt belongs to a PO**: cancel the standalone attempt and receive from the purchase order instead.
* **Recent Receives is empty**: no standalone receipts have posted yet, or the page is still loading.

## Related Articles

<CardGroup cols={2}>
  <Card title="Warehouse Overview" href="/support/inventory/warehouse-overview">
    Use the Warehouse workspace for bins, pick lists, receiving, returns, relocations, transfers, and cycle counts.
  </Card>

  <Card title="Inventory Overview" href="/support/inventory/overview">
    Monitor stock health, location balances, low-stock alerts, and inventory value warnings.
  </Card>

  <Card title="Inventory Transactions" href="/support/inventory/transactions">
    Audit stock movement history, movement types, supply and demand rows, and FIFO layer detail.
  </Card>

  <Card title="Purchase to Pay" href="/support/purchasing/purchase-to-pay">
    Follow the full PO, receipt, vendor bill, and payment workflow.
  </Card>

  <Card title="Create and Manage Purchase Orders" href="/support/purchasing/create-manage-pos">
    Create POs, add vendor items, receive inventory, and handle approval, cancellation, billing, and close-short blocks.
  </Card>

  <Card title="GRNI and PO-Linked Vendor Bills" href="/support/accounting/grni-po-bills">
    Create vendor bills from received purchase orders and clear received-not-billed balances.
  </Card>
</CardGroup>
