Goods receipt verification is the check that what physically arrived matches what was ordered and invoiced, recorded against serial numbers rather than quantities. It is the single point where your asset register becomes true or false, because every later process inherits whatever you wrote down here.
TL;DR
- Counting boxes is not verification. Capturing serials is.
- Direct to employee delivery removes the receiving step entirely.
- Specification substitution is common and rarely noticed at arrival.
- A register built from invoices describes what you bought, not what you have.
- This is the cheapest control in the whole lifecycle to get right.
The moment this becomes real
Say you order twenty five laptops for a hiring wave. The invoice lists twenty five identical machines at one price. The boxes arrive at a storage unit and somebody confirms the pallet count so finance can pay.
Eight months later an audit samples the register. Four serial numbers do not exist on any machine anybody can find. Two laptops in use have a different amount of memory from what the register says. One machine in the sample was never entered at all, because it arrived in a later shipment that nobody logged.
None of this is fraud. Suppliers substitute specifications, split shipments and occasionally make mistakes, and all of that is normal. The real issue is that the only moment when the paperwork and the hardware were in the same place, somebody counted boxes instead of reading serial numbers.
When this is lighter than you think
Four stages where this does not need formalising.
- Under about ten devices a year. You will remember each one. Record the serial when you set it up and that is enough.
- Devices go straight to a configuration step. If every machine is imaged before use, the serial gets captured there anyway.
- One supplier with reliable documentation. Some send a packing list with serials. That is most of the job done for you.
- No asset register yet. Build the register first. Verification against nothing is just counting.
It matters at volume, with multiple suppliers, and wherever devices go directly to employees without passing through anybody who could check them.
The five questions teams actually ask
What are we actually verifying? Three things: that the quantity matches, that the specification matches what was ordered, and that each physical serial number is recorded. The third is the one that gets skipped and the only one that makes the register real.
How do we verify when devices ship direct to employees? This is the hard case for distributed teams and it is now the normal case. Options are asking the recipient to report the serial, capturing it at enrolment, or having the shipper record it before despatch. Enrolment is the most reliable of the three.
Does enrolment count as verification? Partly. It proves a device exists and reached somebody, which is most of what you need. It misses anything never switched on, including spares, and it happens after you have already paid.
What about specification substitution? More common than people expect, particularly on larger orders and during supply constraints. A machine with different memory or storage is still a working laptop, so nobody notices unless somebody checks against the order.
Who should do it? Whoever physically handles the device first. That used to be IT and now is often the employee, which is why the check has quietly disappeared from many companies without anybody deciding to remove it.
Three ways teams handle it, and where each breaks
Count and pay. Confirm the quantity against the delivery note so finance can settle the invoice. Fast and extremely common. It breaks because quantity tells you nothing about which specific machines you now own, and the register ends up built from purchase orders.
Capture serials at configuration. IT records each machine as it images it. Good data and no extra step. It breaks for devices that ship direct to employees, which increasingly means most of them, and it leaves spares unrecorded until they are deployed.
Verify at despatch. Whoever sends the device records the serial against the person before it leaves. The most reliable approach for distributed teams. It breaks if you are not the one despatching, which means it only works when the shipper is inside your process.
Five questions to test your own process
Whether you need better goods receipt verification is answerable in ten minutes.
Where did the serials in your register come from? If the answer is the supplier’s invoice, you have not verified anything.
Who sees a device first? If it is the employee, your check depends on them, so make it easy and ask explicitly.
Are spares recorded? Devices that never get switched on never get enrolled, so they are invisible to every automated method.
Has a specification ever differed from the order? Ask IT. They usually know and rarely report it.
Could you match every device to a purchase? That is the audit question, and it is decided at receipt.
What is actually available
Five honest options, including ours.
Manual check against the packing list. Best for bulk deliveries to one location. Cheap and effective if somebody actually reads serials. Struggles on direct to employee shipping, where there is no receiving location.
Capture at MDM enrolment. Best general purpose answer. Accurate and automatic for anything switched on. Struggles on spares, on timing relative to payment, and on devices that are never enrolled.
Ask the employee to report the serial. Best as a backstop for direct shipments. Costs nothing. Struggles on compliance, since a request in a welcome email competes with everything else in week one.
Require serialised packing lists from suppliers. Best structural fix and often overlooked. Many suppliers will do it if asked at contract stage. Struggles because it still describes what they say they sent.
RemoAsset. Best when devices ship directly to people in many countries and there is no receiving step anywhere in your process. Asset tracking tied to despatch means the serial is recorded against the person by whoever sends the machine, which is the only point in a direct shipping model where a human handles it. Where it struggles: if you buy through your own supplier and receive into your own warehouse, this is a process fix rather than a vendor one, and asking your supplier for serialised packing lists costs nothing. It publishes an entry subscription price but no per device rates.
Where to start, by situation
| Situation | Scale | Setup | Primary pain | Recommended starting point |
|---|---|---|---|---|
| Very low volume | Under 10 a year | No register | Nothing formalised | Record the serial when you set each one up |
| Bulk delivery to one site | 25 plus at once | Storage location | Counting rather than checking | Read serials against the packing list |
| Direct to employee shipping | Any | No receiving step | Nobody ever sees the device | Capture at MDM enrolment as the primary method |
| Spares held in stock | Any | Spare pool | Unenrolled devices invisible | Record spares manually before storing them |
| Many markets, several suppliers | High volume | No single process | Register built from invoices | A service such as RemoAsset that records at despatch |
What the gap actually costs
Almost nothing immediately, which is exactly the problem. A register built from invoices looks identical to one built from verified devices, right up until somebody checks.
The cost appears everywhere downstream. Warranty claims need a serial that matches. Insurance needs an accurate list. Security questionnaires ask how many managed devices you have. Disposal records have to tie a certificate to a specific machine. Every one of those inherits whatever was recorded at receipt, and none of them can correct it.
The third cost is the audit finding you cannot explain. Being unable to match devices to purchases does not look like a missed process step. It looks like you do not know what you own, which invites a much broader look. So the question is not whether to check serials on arrival. It is what else you are currently asserting on the strength of a supplier’s invoice.
When nobody receives anything any more
Goods receipt verification was easy when hardware arrived at an office. Somebody opened boxes, read labels and typed serials into a system. The control was natural because the devices physically passed through a place you controlled.
Direct to employee shipping removed that place without replacing the control. The device goes from a supplier to a home address and the first time your organisation touches it is when it checks in to device management, which is after payment and after the asset should already have been recorded.
There are two honest answers. Ask your supplier for serialised packing lists and treat enrolment as the confirming check, which costs nothing and works for most teams. Or move despatch to a party that records the serial against the person as part of sending it, which is what a laptop lifecycle management service does across the markets you ship to. Pick based on whether you still have a receiving step anywhere.
Related reading
- Asset register accuracy
- The fields an asset register needs
- Running an IT asset audit
- Asset tags for IT equipment
- Knowing precisely what you hold underpins most security frameworks. ISO 27001 covers asset inventory, and the UK NCSC publishes device security guidance that assumes an accurate device list.
Frequently Asked Questions
What does goods receipt verification actually involve?
Checking three things when equipment arrives: that the quantity matches the order, that the specification matches what you bought, and that every physical serial number is recorded. The third is the one most often skipped, and it is the only one that makes your asset register reflect reality.
How do we verify devices that ship straight to employees?
You have three options: ask the recipient to report the serial, capture it automatically when the device enrols in your management platform, or have whoever despatches it record the serial against the person. Enrolment is the most reliable for most teams, with a despatch record better still.
Is capturing the serial at MDM enrolment enough?
For most purposes yes, with two gaps. It misses any device that is never switched on, which includes spares and anything held in stock. And it happens after you have already paid the invoice, so it cannot catch a quantity or specification problem early enough to query it.
Does specification substitution really happen?
More than teams expect, particularly on larger orders and when supply is constrained. A machine with different memory or storage still works, so nobody notices unless someone compares against the original order. Asking IT whether they have ever seen it usually produces a yes.
Should we ask suppliers for serialised packing lists?
Yes, and many will provide them if it is raised at contract stage rather than afterwards. It is close to free and removes most of the manual work. It still describes what the supplier says they sent, so treat it as a strong starting point rather than as verification on its own.
Who should be responsible for this check?
Whoever physically handles the device first. That used to be an IT team receiving into an office, and is now frequently the employee at home. The check has quietly disappeared from many companies not by decision but because the receiving step stopped existing.
What goes wrong later if we skip it?
Warranty claims that need a matching serial, insurance lists that are wrong, security questionnaires you cannot answer confidently and disposal certificates that cannot be tied to a specific machine. Every downstream process inherits what was recorded at receipt and none of them can correct it.