What an AI Goods Receiving Clerk Does and Where a Person Stays

What a goods receiving clerk actually does all day

A goods receiving clerk sits where the paperwork meets the delivery. Job postings describe the same core every time: check the delivery against what was ordered, count and inspect it, record what arrived, and tell someone when it does not match. In a busy warehouse the day is physical and loud. In a restaurant group or a clinic the day is shorter, but the paperwork follows the same logic.

The recurring tasks, in the words most businesses use, look like this:

1. Receive the driver, sign the delivery note and record the arrival time.
2. Match the delivery note or packing slip to the purchase order number.
3. Count, weigh or measure each line and compare it with the ordered quantity.
4. Inspect for visible damage, wrong items, expiry dates and broken seals.
5. Enter the goods receipt in the stock or accounting system, line by line.
6. Record shortages, overages and damage, with photos taken at the door.
7. Send the discrepancy to the supplier and ask for a credit note or a replacement.
8. Put accepted goods away in the right rack, bin, fridge or site store.
9. Pass the signed receipt to accounts payable so the supplier invoice can be checked.

Pay attention to the words your own team uses. Some businesses say goods received note, others say GRN. Some say delivery note, others say packing slip or delivery docket. A short delivery is a shortage in one business and a short shipment in another. An AI worker needs the same labels your staff and your system use, so the first job in any setup is to write down your own terms for each step.

Which of those tasks an AI worker takes over

The repeatable part of this role is matching, entering, logging and chasing. The AI worker reads documents and writes into systems. It does not touch the goods, and it should not decide whether a crate is acceptable. Below is how each repeatable task works in practice.

Matching starts with the documents. Supplier delivery notes often arrive as PDFs, scans or phone photos in an inbox, and the AI worker reads them with document extraction. Tools built for this, such as Nanonets, Suparse, Affinda and Koncile, are designed to pull out the supplier name, delivery note number, purchase order reference, product codes and quantities. Their pages describe handling many layouts without a separate template for each supplier. Test that claim on your own paper before you rely on it, because handwritten notes and faded carbon copies still cause errors.

Entering the receipt is the next step. The worker compares the extracted lines with the open purchase order in your ERP or purchasing tool. Where every line matches, it creates the goods receipt. Systems such as SAP, Oracle NetSuite, Microsoft Dynamics 365 Business Central, Odoo and QuickBooks all have receipt or receiving functions, and the exact field names differ. NetSuite's own explanation of three-way matching describes checking the purchase order, the supplier invoice and the delivery receipt before payment. The receipt is the piece this worker creates, so it sits at the centre of that check.

Logging shortages, overages and damage is where the worker saves the most typing. When a line does not match, the worker opens an exception record in a shared sheet or ticket queue. It attaches the photos your staff send, usually from a phone, and tags the line with the reason. Photos help the record, but their value depends on context, so keep the original files with the delivery reference and the signed note.

Chasing credit notes is repetitive and easy to forget. The worker drafts a claim that quotes the delivery note number and the affected lines, and sends it from the purchasing inbox once a person has approved the wording. It then follows up on a fixed schedule. When the supplier issues a credit note, the worker matches it to the open exception and closes the item. A credit note that is larger than your agreed limit should go to a person before anything is closed.

To do this, the worker needs a short list of access points:

• Read access to the purchasing or receiving inbox, where supplier delivery notes arrive.
• Read access to open purchase orders and the supplier list in your ERP or purchasing system.
• Write access to create goods receipts, limited to lines that match exactly.
• A shared exception sheet or ticket queue in Google Sheets, Microsoft Excel or your ticketing tool.
• A staff channel for photos, such as WhatsApp Business, if your team already uses it, with the data rules for personal details set in advance.

What stays with a person, and why

Inspection stays with a person. Deciding whether goods are fit to accept means judging smell, temperature, bruising, leaks, weight, expiry and the condition of packaging. A photo can show a dent. It cannot tell you whether the dent affects the product. The worker sees the data your staff enter, not the crate itself, and that is the limit that matters most in this role.

Rejection decisions stay with a person too. Refusing a delivery, signing for it under protest, or accepting it with a note all have consequences for the supplier relationship and for payment. Those calls need someone who knows the contract, the history with that supplier and the effect on production or customers.

Relationships stay with a person. When a driver is in a hurry, a supplier disputes a count, or a long-standing supplier needs a conversation rather than a template email, a person should make the call. A claim email can be automated. A negotiated replacement usually cannot.

Sign-off stays with a person. Approving a receipt where lines do not match, approving write-offs, and approving credit notes above a limit should be named tasks with a named owner. This is also a control. If nobody checks the worker's receipts, a mistake in matching can hide a short delivery for months.

Regulated goods need a named person. If your business handles food, medicines, chemicals or other hazardous materials, the acceptance and release decisions belong to someone who is qualified and accountable under the rules that apply to your sector. The worker can record batch numbers, expiry dates and certificates. It should not release stock, and it should not decide whether a product meets a standard.

How this role differs by business type

The core tasks are the same across industries, but the detail changes what a clerk checks and what the worker can handle. The table below covers six common settings where this role exists.

How the switch happens, week by week

The safest switch keeps the clerk in place at the start and moves work over in steps. The plan below assumes one receiving team, one purchasing inbox and an ERP or stock system that already holds current purchase orders. The pace depends on how clean those records are, so the first week is mostly checking them.

In week one, pick five to ten suppliers that send most of your volume. Collect four weeks of their delivery notes and the matching purchase orders. The clerk keeps doing everything as normal. The AI worker runs in read-only mode and writes what it would have done into a shared sheet. The clerk compares the two each day and notes every difference.

In week two, the worker drafts goods receipts for exact matches only. A person approves each one in the ERP. Every line that does not match goes straight to the clerk's exception queue, and nothing is created for those lines.

In week three, approval is removed for exact matches on the chosen suppliers. The worker creates the receipts and sends a daily summary to the clerk. Shortage logging starts here, with photos sent from the dock. The clerk reviews the summary each morning and corrects any receipt that looks wrong.

In week four, the worker starts drafting claim emails. A person approves the template wording and sends the first set of claims. After that, the worker sends standard claims on the agreed schedule and tracks each one until a credit note arrives. Anything with a value above the agreed limit still goes to a person.

In weeks five to eight, add suppliers in small groups and watch the exception queue. The clerk's time shifts toward inspection, rejections and supplier calls. The clerk stays on the dock, because the physical checks are the part the worker cannot do.

After about eight weeks, the role should shrink to review. The clerk reviews the exception queue daily and checks a sample of twenty receipts against the paper each week. Any change to someone's hours, pay or duties needs to follow the notice, consultation and severance rules that apply in your country, and it should be agreed with the employee or checked with a lawyer before it takes effect.

Risks, and when not to automate this role

Do not automate this role if most of your deliveries arrive without a purchase order. Cash buying, market purchases and ad hoc orders leave nothing to match against. In that case the worker creates work instead of removing it.

Be careful with messy purchase order data. If the ERP holds old orders, duplicate supplier codes or wrong unit measures, the worker will match against bad information and write bad receipts. Clean the purchase order list before the worker touches it.

Watch for early credit note closure. A worker that closes an exception as soon as a credit note appears may close it before the amount is right. Keep a person checking the credit note value before the item is closed.

Delivery notes contain personal details, such as driver names and recipient contacts. Limit the worker to the fields it needs, keep the photo folder access-controlled, and check the data protection rules that apply where you operate before you connect a messaging channel.

Low volume is a risk to the case itself. If your team receives a handful of deliveries a week, the setup time may cost more than the saving. In that case a clear checklist and a better shared sheet may be the better investment.

Removing the human check also removes a control. Receiving checks protect against short shipments, substitutions and invoices for goods that never arrived. A sample audit by a person keeps that protection in place after the switch.