Material receipt on site

Material receipt on site applied to the real purchasing cycle: need, quote, order, delivery, delivery note, incident, and invoice connected to know what was ordered, what arrived, and what remains to be resolved.

Material receipt from procurement: quantities, order, and delivery

Material receipt from the procurement perspective confirms what part of an order actually arrived and under what commercial conditions. The key data is reconciling order, delivery, and delivery note before administration receives an invoice that assumes different quantities.

This process doesn't replace the technical quality control in receipt. Procurement verifies quantities, reference, order, dates, and discrepancies; quality also determines whether the material meets specifications, certificates, and acceptance criteria.

What to check against the purchase order

Vendor, order number, item, quantity, unit, and committed date should be comparable to what was delivered. If there is a substitution or quantity change, it's good to document it before marking the line as received.

A partial delivery should keep a pending balance. Marking the order complete as received because a delivery note arrived prevents distinguishing what still needs to be supplied and can lead to approving invoices for undelivered quantities.

Delivery note and delivery evidence

The delivery note identifies the delivery, but shouldn't be the only source of truth. The receiver records the quantity actually counted or accepted and can attach a photograph, observation, or incident when there is a difference.

Digitizing the delivery note helps prevent loss of paper, but the real value appears when its lines are related to the corresponding order and update the pending balance.

Quantity or reference discrepancies

If 120 units were ordered and 110 arrive, the system should record 110 received and 10 pending, not modify the original order. If the vendor also invoices 120, the difference becomes visible in reconciliation before payment.

A different reference also needs explicit treatment. It might be a supply error or an acceptable substitution, but shouldn't be integrated as if it were the contracted item without a documented decision.

Rejected, conditional, or pending delivery

Not all receipts are binary. There may be materials unloaded pending verification, rejected units, or quantities accepted with incidents. Defining statuses prevents warehouse and administration from interpreting the same delivery differently.

When material is blocked, the incident must have an owner and next action: return, replacement, credit, or technical review. The order status updates when that action is resolved.

Impact on inventory and planning

A receipt increases physical availability and can release planned activities. Relating it to warehouse and planning allows knowing whether a front can start or supply remains a constraint.

The actual date also serves to evaluate vendors. Repeated delays or partial deliveries can influence future awards even if the quoted price was competitive.

Reconciliation with the invoice

Before approving an invoice, it's good to compare quantities and prices with order and receipt. The invoice shouldn't become the first notice that a different quantity was delivered.

Differences can be classified by price, quantity, concept, or condition. That classification accelerates resolution with the vendor and prevents administration from having to reconstruct the delivery by calling the site.

How Bloqbase can help

Bloqbase has purchase orders and receipts linked to project and vendor, which allows preserving ordered, received, and pending quantities along with incidents and documents.

Digital receipt improves traceability, but the physical verification of quantities and technical acceptance remain dependent on responsible persons on site.

Also available inEspañolCatalàEuskara

Keep exploring

Site Warehouse Control

Site Warehouse Control: how to connect need, vendor, order, receipt, delivery note, and invoice without losing quantities, dates, or approvals.

Read

See BLOQBASE in action on your own project.

Request a demo