HDbeammachineBeam Machine Docs
Help Center

Working in Procurement

How to use the Beam Machine procurement module for requisitions, purchase orders, and goods received, with notes on current delivery gaps.

publicusers

Working in Procurement

This page shows you how to use procurement screens for spend requests, purchase orders, and goods received in Beam Machine.

Product: Beam Machine
Module: Procurement
Role: Procurement User, Finance User, Operations Admin, Approver
Difficulty: Beginner to Intermediate
Time: 10 minutes first read
Last Updated: 2026-03-10
Version: Current Beam Machine app build in this repo

Before You Start

  • You need access to the procurement routes.
  • You should know whether you are raising a requisition, preparing a PO, or recording goods received.
  • The supplier should already exist if you are creating a purchase order.

What is the Procurement module?

On paper, this is your purchase request file, order book, and goods-received register. In Beam Machine, the procurement routes are where you try to keep demand, order issue, and receipt connected instead of losing them across emails and spreadsheets.

When do you use this?

Use this module when:

  • the business needs to request a purchase,
  • a supplier order must be prepared,
  • or received goods need to be recorded.

If procurement work is undocumented, later approvals, payables, and stock or asset records become harder to trust.

Where do you find it?

Primary path: Operations -> Procurement

Important routes:

  • /dashboard/procurement/requisitions
  • /dashboard/procurement/requisitions/new
  • /dashboard/procurement/requisitions/[id]
  • /dashboard/procurement/orders
  • /dashboard/procurement/orders/new
  • /dashboard/procurement/orders/[id]
  • /dashboard/procurement/received
  • /dashboard/procurement/received/new

How to work in Procurement

  1. Open the procurement area from the sidebar.
  2. Decide whether the job is:
    • request creation,
    • purchase-order creation,
    • or receipt recording.

To raise a requisition

  1. Open Purchase Requisitions.
  2. Create the requisition.
  3. Confirm description, department, and amount before submission.

To create a purchase order

  1. Open Purchase Orders -> New Purchase Order.
  2. Select the supplier.
  3. Enter the expected delivery date.
  4. Add the optional reference.
  5. Add line items with description, quantity, unit price, and VAT.
  6. Review totals before submission.

To record goods received

  1. Open Goods Received.
  2. Confirm the receipt against the order or requisition context.
  3. Record the receipt cleanly so the next financial step has real support.

āœ… Checkpoint: You should be able to trace the purchase from request to order to receipt. If you cannot, the spend trail is already weakening.

Common Questions & Issues

"The purchase order page is visible, but creation does not feel complete"

Why this happens: The current new PO form exists, but the code still marks purchase-order creation as not fully implemented end to end.

Fix: Use the page honestly for current workflow support, but do not promise a complete production-ready PO lifecycle without confirming your environment behavior.

"I have the bill, but I skipped procurement"

Why this happens: Teams often jump straight to payables.

Fix: Use procurement when the business needs a controlled spend trail. Then move into invoicing or approvals only after the request/order/receipt context is clear.

What's Next

Related Pages

Still Stuck?

Was this page helpful?

[Yes] [No]