Skip to content
P4 Software P4 Software / cifraHQ

Add these docs to Claude

Ask Claude questions about these docs. Claude reads the published pages and links you back to them. Copy this address:

https://p4-software.opendocs.page/mcp

In claude.ai or Claude Desktop: open Settings, then Connectors, choose Add custom connector and paste the address.

In Claude Code, run:

claude mcp add --transport http docs https://p4-software.opendocs.page/mcp

Assembly Receipts

Assembly Receipts

An assembly receipt is what makes production official: it records the finished units that came off the line, removes the consumed components from Inventory, and adds the finished goods to your warehouse in a single posted transaction. One assembly order can have many receipts — so whether you build in daily batches or complete the whole run at once, the receipt fits your workflow.

Assembly receipts are created from an Assembly Order, not directly from this list.

Assembly Receipts list page in CifraHQ.

Assembly Receipts list, the put-away of finished goods from Assembly Orders.

How to create an Assembly Receipt

  1. Open a Released Assembly Order (see Assembly Orders).
  2. Click Create Receipt.
  3. Enter the Quantity Built — the number of finished units produced in this run.
  4. Set the Posting Date.
  5. CifraHQ loads the component lines automatically, scaled to the quantity being built.
  6. Verify the component quantities consumed are correct.
  7. Post the receipt.

What posting does

  • Component Inventory is reduced by the quantities consumed per the Bill of Materials.
  • Finished goods Inventory is increased by the quantity built.
  • A journal entry is created reflecting the transfer of cost from components to finished goods.

How the cost is worked out

Production is valued at system cost, the cost on each product's card at the moment you post:

  • Each component is consumed at its current cost. For a component bought in packs, the pack's cost is used. The cost written on the assembly order when it was created is not used, so a price change since then is picked up automatically.
  • The finished product is valued at exactly what was consumed: the total component cost divided by the quantity built. The value leaving component stock always equals the value entering finished goods.
  • Posting updates the finished product's Cost on its product card to this figure, so its next sale uses the real production cost.
  • While the receipt is a draft, the Cost Summary shows this same calculation, so you see the cost before you post. A posted receipt shows the cost it was posted at.
  • A component with no cost on its product card stops the post. Set the cost first: consuming it at zero would undervalue the finished product.

Field reference

  • Assembly Order — the parent order this receipt belongs to; set automatically and cannot be changed.
  • Quantity Built — the finished units produced in this specific run. If you built 200 units across two days, you would post two receipts of 100 each.
  • Posting Date — the date the Inventory changes and Accounting entry are recorded. Use the actual production completion date for accurate period reporting.
  • Component lines — the raw materials consumed; quantities are automatically scaled from the BOM based on the Quantity Built. Adjust them here if actual consumption differed from the standard recipe.

Document lifecycle

State Meaning
Draft Editable; no Inventory impact yet
Posted Components consumed; finished goods added to stock
Archived Closed and read-only

Tips

  • Adjust for real-world yield. If your BOM calls for 10 kg of resin per unit but this batch used 10.5 kg due to rework, update the component quantity on the receipt before posting. Accurate consumption data keeps your Inventory costs honest.
  • When the full production run is complete, go back to the parent Assembly Order and close it. This prevents accidental additional receipts and signals to the team that the work order is finished.

Related: Assembly Orders · Products · Inbound Adjustments · Product Bundles · Inventory by Location · Audit Trail · Account Priming

Was this page helpful?