Processes in SMEs7 min read

Delivery note processing: read, check, forward

Contents

Delivery note processing in an SME means that every incoming delivery note, whether on paper, scanned or as a PDF, is read, checked against fixed rules and forwarded as a task to the warehouse, quality assurance or accounting, in the ERP or inventory system you already run. Five steps get you there:

  1. Choose one Vorgang: one intake, one task, one destination, such as all the delivery notes that goods-in reads and passes on by hand today.
  2. Make the intake digital: paper delivery notes are scanned once the goods are received; PDF delivery notes arrive by email in a fixed inbox.
  3. Write down the checks: which details every delivery note should carry and which remarks on it point to a discrepancy.
  4. Fix the destinations: when a delivery note goes to the warehouse, to quality assurance or to accounting, in exactly one target system.
  5. Hand over reading, checking and forwarding: an AI employee takes on these three steps for every delivery note. When it is unsure, it hands the case to a person.

A scanned delivery note is not yet a digital process

In many businesses, digitisation stops at the scanner. The delivery note sits as a PDF in a folder, but someone still has to read it, copy the details and pass it to the right place. The pile of paper is smaller; the manual work is not.

A delivery note is digitised only when its details arrive where they are needed: as a task in the warehouse, in quality assurance or in accounting. Scanning is the first step, not the result.

Every delivery note goes through the same three steps

For every delivery note, the AI employee follows the same sequence:

  1. Read: it recognises the supplier, delivery note number, date, order number and the line items with quantities.
  2. Check: it checks the details against the rules agreed in week one, for example whether the order number is missing or whether a remark such as "goods damaged" appears on the document.
  3. Forward: it creates the task in the target system for the warehouse, quality assurance or accounting, with the recognised details as metadata.

It records every forwarding with timestamp and reasoning in the decision log. When its certainty falls below the agreed confidence threshold, it stops and hands the case to a named person in goods-in.

Goods-in still receives the goods

The AI employee does not replace any work at the loading bay. It does not accept goods, post a goods receipt or raise a complaint with the supplier. The only change is who reads the delivery note and passes it on.

WhoTask with an incoming delivery note
Goods-inreceives the goods, counts, signs and scans the delivery note, as today
AI employeereads the delivery note, checks the details and creates the task for the warehouse, quality assurance or accounting
Warehouseposts the goods receipt in the ERP and puts the goods away, as today
Quality assuranceresolves discrepancies and damage and decides whether to raise a complaint
Accountingmatches delivery note and invoice, as today
Agentivobuilds the AI employee in the first two weeks and then operates it: monitors, corrects, takes responsibility

A digital delivery note needs every party to take part

"Digital delivery note" usually means something else: a standard through which shipper, carrier and recipient exchange the delivery note as a data record. GS1 Germany describes it as the digital replacement of the paper delivery note, exchanged through a neutral cloud platform with a standardised interface, starting with consumer goods. The same solution outline notes that in 2022 deliveries from consumer goods manufacturers to retailers were still accompanied by paper delivery notes (GS1 Germany, 2022, in German).

For a business with many suppliers, such a standard helps where supplier and carrier use it. Everything else keeps arriving on paper or as a PDF: from the wholesaler, from the local trade business, from the supplier abroad. Reading, checking and forwarding those delivery notes is the Vorgang this page is about. One does not rule out the other.

One Vorgang is the right place to start

A Vorgang is everything that arrives daily, answers the same question and lands in the same system. For incoming delivery notes the question is: where does this document belong, the warehouse, quality assurance or accounting?

Starting with one Vorgang means the result can be measured with one number. Incoming invoices, customer orders or complaints by email later become separate Vorgänge, each measured on its own. For invoices, see invoice capture and invoice processing automation. How one Vorgang after another adds up to AI process automation in SMEs is covered in the guide.

Connecting to your ERP is not an IT project

The AI employee writes into exactly one target system: your ERP, your inventory management system or your DMS. It uses access that already exists: a standard API, a watch folder, sFTP or email. Custom development against a legacy system does not belong in a Pilotbetrieb, our fixed-price entry engagement.

For your business this means no new system for goods-in and no IT project. We agree the right access in the first week. Where a new generation is taking over the running of the business, this is often the first step that works without an IT department of its own; more in AI in SMEs.

From paper pile to ERP task in seven weeks

The Pilotbetrieb takes seven weeks. Four of them are productive operation on your real delivery notes.

WeekWhat happens
1Process conversation with the Fachbereich (the department that owns the Vorgang), define classes, review examples, clarify access
2We build and train the AI employee, set up quality checks and test on real documents
3Acceptance against the agreed hit rate, go-live, handover
4 to 7Productive operation on real volume; we monitor and correct
End of week 7Written evaluation: hit rate achieved, cases processed, time saved

The hit rate is agreed before the start. If it is met, operation begins under a monthly operating agreement that can be cancelled monthly. If it is missed, the Pilotbetrieb ends with no further obligation.

Frequently asked questions

Do we have to keep the paper delivery notes?

For tax purposes, section 147(3) of the German Fiscal Code (AO, in German) ends the retention period for received delivery notes that are not accounting records when the invoice arrives. If a delivery note serves as an accounting record in your business, the period for accounting records applies. Whether other periods apply, for example under commercial law, is for your tax adviser to confirm. The AI employee deletes nothing.

What happens to handwritten remarks?

Remarks from goods-in, for example on short deliveries or damage, are part of the check. When the AI employee recognises such a remark, it forwards the delivery note to quality assurance. How reliably your remarks can be read shows in the examples reviewed in week one and in acceptance in week three. Whatever it cannot read with certainty falls below the confidence threshold and goes to a person.

Who decides on a complaint?

Quality assurance. The AI employee forwards a delivery note with a remark to quality assurance as a task, with the recognised details and the reason for forwarding. Whether a complaint goes to the supplier is settled there. The AI employee does not accept goods, post a goods receipt or delete anything. Every forwarding is recorded in the decision log with timestamp and reasoning.

Which delivery notes are a good place to start?

Delivery notes that arrive every day, raise the same question and land in the same system. A typical start is the delivery notes of a central goods-in that are read by hand today and passed to the warehouse, quality assurance or accounting. What matters is a manageable list of checks and examples for each destination. Invoices or customer orders become separate Vorgänge later, each with its own hit rate.

What happens after the seven weeks?

If the agreed hit rate is met, operation begins under a monthly operating agreement that can be cancelled monthly. We keep monitoring the AI employee, correct it when suppliers, documents or responsibilities change, and take responsibility for the result. If the rate is missed, the Pilotbetrieb ends with no further obligation. The price is settled beforehand either way: fixed price, agreed before we start.

The next step

If goods-in reads delivery notes and passes them on by hand today, that is the Vorgang for a Pilotbetrieb: one intake, one task, one destination. Fixed price, agreed before we start. Seven weeks, four of them productive operation on your real documents.

Request a Pilotbetrieb

← Back to insights