---
title: "Manufacturing: building a verifiable delivery evidence pack"
canonical: https://www.billabex.com/en/blog/manufacturing-delivery-evidence-pack/
lang: en
alternate: https://www.billabex.com/fr/blog/industrie-dossier-preuve-livraison.md
alternates:
  fr: https://www.billabex.com/fr/blog/industrie-dossier-preuve-livraison.md
  en: https://www.billabex.com/en/blog/manufacturing-delivery-evidence-pack.md
  de: https://www.billabex.com/de/blog/industrie-akte-mit-liefernachweis.md
  es: https://www.billabex.com/es/blog/industria-componer-expediente-de-entrega-verificable.md
  it: https://www.billabex.com/it/blog/industria-pratica-con-prova-di-consegna.md
  nl: https://www.billabex.com/nl/blog/industrie-dossier-met-leveringsbewijs.md
  pl: https://www.billabex.com/pl/blog/przemysl-dokumentacja-z-dowodem-dostawy.md
  pt: https://www.billabex.com/pt/blog/industria-processo-comprovativo-entrega.md
updated: 2026-11-19
index: https://www.billabex.com/llms.txt
---

# Manufacturing: building a verifiable delivery evidence pack

An industrial customer asks for delivery evidence before releasing an invoice. The supplier sends a bundle containing a transport note, delivery note, certificate and several emails. The reply says that the document for the relevant batch is still missing. The quantity of attachments has increased, but the original question remains unanswered.

A verifiable file is not necessarily a large file. It allows someone unfamiliar with the operation to connect an invoice line to an order, physical movement and, where the agreement requires it, technical acceptance. Every document needs an identifiable purpose and references precise enough to avoid matching records merely because they look similar. This article uses the French B2B and document-retention context.

## Start with the statement the document must support

Before attaching a record, state what it is intended to establish. “The goods left our factory,” “the recipient received them” and “the contractual inspection accepted them” are different statements. A transport record may support the first without answering the other two.

The [July 2019 GS1 Logistic Label Guideline](https://ref.gs1.org/guidelines/logistic-label/), pages 36 to 38, distinguishes information about dispatch, carrier delivery and receipt by the destination. That prevents every event being compressed into one “delivered” status. The checks performed still depend on the arrangements between the partners.

In the invoice record, identify evidence expected and evidence available. If the customer requests technical acceptance and you hold only an unloading acknowledgment, the next step is to locate or clarify the former. Resending the latter does not resolve the gap. This also helps collections route the request to someone able to answer it instead of treating every missing document as an accounting problem.

## Build a short index that guides the reader

Begin the index with the customer entity, purchase order and invoice. Then identify affected lines, product references and relevant batches or serial numbers. Link to documents in identifiable versions and state any reservations that limit what they establish.

| Record                             | Question answered                            | Point to check                      |
| ---------------------------------- | -------------------------------------------- | ----------------------------------- |
| Order and applicable specification | What did the customer request?               | Agreed version and scope            |
| Dispatch note                      | What did the supplier announce at departure? | References and quantities sent      |
| Receipt evidence                   | What did the recipient record?               | Date, location and reservations     |
| Agreed technical document          | What inspection result is established?       | Batch, criteria and author          |
| Invoice and any correction         | What amount is requested?                    | Lines, prices and related documents |

This structure is a proposed method to adapt to the agreement. It does not make every listed document mandatory for each sale. Its purpose is to show the conditions that actually apply without adding new requirements after the transaction. Where a record is unnecessary, say why it does not belong in the file rather than creating it merely to fill an empty slot.

## Check the references between different levels

In manufacturing, one pallet can contain several batches and one machine can contain several assemblies. A document for an assembly should not be assigned to a component simply because their names resemble one another. The [August 2017 GS1 Global Traceability Standard](https://ref.gs1.org/standards/global-traceability/), pages 29 and 54, discusses retaining links between aggregation levels and components in technical industries.

For payment evidence, that means retrieving the relationship between delivered objects and invoice references. A certificate for a neighbouring batch does not answer the request. A generic certificate may explain a product characteristic but should not be presented as a specific inspection result if that is not its scope.

[Matching deliveries to invoices](https://www.billabex.com/en/blog/wholesale-partial-deliveries-invoice-collections/) provides the quantity foundation. The evidence index adds provenance so accounts payable can pass the relevant document to its technical team without reconstructing the whole chain. A precise relationship is more useful than a large collection of plausible-looking certificates.

## A fictional file involving two batches

Consider 120 parts divided into 80 from batch A and 40 from batch B. The invoice has two lines at the same unit price of €45 excluding VAT: €3,600 for A and €1,800 for B, totalling €5,400 excluding VAT. Both batches arrive on the same pallet on the same day.

The customer requests the agreed technical document for B. Sending the pallet receipt establishes a shared physical event but does not supply that document. Sending the report for A does not answer the question either, even though all 120 parts have the same commercial product reference.

The useful record states that physical receipt is documented for both batches and that the technical document for B must be retrieved or established under the agreement. The competent owner then assesses the consequence for the invoice. The €1,800 amount locates the affected line; it does not establish that the remaining €3,600 is automatically payable under every contractual arrangement.

This simulation illustrates documentary scope. It describes no mandatory certification practice or customer performance. The price and quantities were chosen only to make the relationships understandable and reproducible by a reader who has not seen the shipment.

## Prepare a version suited to the recipient

The internal file may contain laboratory findings, drawings, manufacturing information and details of other orders. They do not all belong in the customer’s accounting mailbox. On page 20, the GS1 traceability standard distinguishes information suitable for sharing from internal data whose access needs assessment.

Select evidence answering the request. If preparing an extract, identify it as an extract, preserve its reference to the original and avoid removing a reservation that changes the document’s meaning. Removing irrelevant information must not become a misleading presentation of the technical finding.

[Collections software security](https://www.billabex.com/en/blog/compliance-and-security-in-debt-recovery-software/) also concerns these exchanges. The recipient should be able to open the relevant document without receiving access to an entire production directory. The technical owner confirms what can be disclosed, while the follow-up record retains what was actually sent and to whom.

## Plan retention before the link disappears

[Service Public Entreprendre states a ten-year retention period from the financial year’s closing date for accounting support documents](https://entreprendre.service-public.gouv.fr/vosdroits/F10029), including purchase, delivery and receipt notes and invoices. That does not automatically define retention for every technical record associated with an industrial product, which may be subject to other obligations.

A link to a carrier’s portal or a former employee’s mailbox is not a retention policy. Decide which records the company must keep in a controlled location, together with their version and connection to the file. Check that an authorised person can still retrieve them after the operation has ended.

Retention should preserve readability and meaning. A file without a batch reference, an image with the reservation cropped out or successive records all called “final” will not support a reliable answer months later. The index should remain understandable when the people who handled the delivery are no longer available.

## Review the pack as a new reader would

Ask someone absent from the project to open the index. They should find the document answering a specific request, identify what it establishes and see what remains missing. If they must contact several teams merely to understand the references, the index still needs work.

The next [payment reminder](https://www.billabex.com/en/blog/tips-for-following-up-on-unpaid-invoices/) can then use targeted evidence and a clear question. The [Billabex customer view](https://www.billabex.com/en/product/customer-view-360/) helps bring that context together. Its usefulness depends on the quality of the relationships between documents, established facts and the amount requested, so the customer can act on the evidence instead of asking for another unexplained bundle.
