Regulatory and electronic invoices

How can you identify missing documents before customs clearance?

To identify missing documents before customs clearance, you must first determine the list of documents required for the transaction (based on the goods, their code, origin, customs procedure, and mode of transport), then compare it with the documents actually received, verifying that each one is valid and properly covers the goods. A fixed checklist is not enough: the list varies from one case to another, and a document that appears to be “present” may be unusable. The best time to do this is upon receipt of the first document, not the day before filing; this allows time to follow up with the sender.

An incomplete shipment is often not discovered until the time of customs declaration, when the goods have already arrived. This means having to follow up with a supplier on the other side of the world, wait, and pay for the goods to be held in storage. Here’s how to avoid this, using a method that can be done manually or automated.

Why a Missing Document Can Be Costly

The declarant must have the documents supporting the declaration in their possession at the time of filing and must make them available to customs (Article 163 of the Union Customs Code, or UCC).The declarant is responsible for the accuracy and completeness of the declaration andfor the authenticity of these documents (Article 15). A missing document therefore has direct consequences:

  • the declaration is blocked, or must be filed in simplified/provisional form, with the extra work that this entails: without proof of origin, there is no preferential treatment; without the certificate required by a regulation, there is no release of goods;
  • The goods are in temporary storage, with storage and demurrage charges accumulating;
  • The risk of reassessment remains after the release if supporting documentation is missing during a subsequent audit (Article 48 of the CDU).

Documents in a customs clearance file: a foundation and variables

The European Access2Markets portal distinguishes between general documents and specific documents. In practice, an import dossier consists of four categories:

FamilyCommon DocumentsWhat Makes Them Mandatory
Retail and Transportation SectorCommercial invoice, packing list, shipping document (Bill of Lading, AWB, CMR)Standard base
Documents Related to the GoodsHealth or phytosanitary certificates, licenses, quota-based import certificates, excise documents (DAE), and documents specific to certain productsThe commodity code and the associated TARIC measures
Documents Related to Origin and RegimeProof of preferential or non-preferential origin, authorizations (processing, warehousing), RCOThe origin, the trade agreement cited, and the requested customs status
Documents required by the client or the companyInsurance certificate, purchase order, technical data sheet, internal certificateInternal business rules: contracts, procedures, and client requirements

The foundation is solid. Everything else is subject to change, and that's where the documentation is lacking.

Why a Fixed Checklist Isn't Enough

The expected list is being calculated

The required documents depend on a combination of factors:

  • the commodity code: In France, the RITA tariff encyclopedia specifies, for each code, the applicable regulations and the documents, certificates, and authorizations that must be submitted. When a commodity is not subject to a specific regulation, a specific document code is often used to declare it;
  • Origin: Claiming preferential treatment requires proof of origin in accordance with the relevant agreement;
  • The procedure: Inward processing or a warehouse requires authorization;
  • mode of transportation: bill of lading, air waybill, or CMR;
  • Internal rules: A certain customer always requires proof of insurance, and a certain supplier always sends its technical data sheet separately.

A single shipment may thus include three different goods, each requiring its own set of documents. A single checklist may omit some or incorrectly require others. This is why tariff classification errors—discussed in our article “How Can AI Assist with HS Code Classification?”—also have documentation implications: an incorrect code results in an incorrect list of required documents.

"Present" does not mean "valid"

The most common pitfall isn't a missing document; it's a document that has been received but is unusable. There are four types of "missing" documents:

FormExampleHow to Detect It
AbsentCertificate of Origin Never ReceivedCompare the expected list with the items received
IncompleteUnsigned certificate, missing page, empty required fieldRead the document's content, not just its type
InvalidCertificate expired, license expired, version revoked and replacedCheck dates, part numbers, and quantities
Does not cover the merchandiseCertificate covering 3 out of 5 lines, different invoice number, lower quantitiesCompare the document with the rest of the batch

The last two discrepancies can only be identified by comparing the documents with one another: this is the principle of document reconciliation. Discrepancies in content between the invoice, packing list, and shipping document are detailed in our article on detecting inconsistencies between the invoice, packing list, and bill of lading.

Documents are coming in as they become available

Invoice by email, packing list via the portal, bill of lading via EDI, certificate by mail a week later: a file is compiled over several days, often in multiple languages. Without an updated file status upon each arrival, no one knows what’s missing until they open the file to file the declaration.

‍

An example: shrimp imported from Vietnam

Let’s consider a typical case. A French importer receives a container of frozen shrimp from Vietnam, consisting of two types: farmed shrimp and wild shrimp. The importer requests the preferential treatment provided for under the free trade agreement between the European Union and Vietnam.

Step 1: Determine what is required. The invoice, packing list, and bill of lading form the foundation. Products of animal origin must pass through a border control point with an official health certificate and a Common Health Entry Document (DSCE), which the importer or their representative must complete in TRACES. Wild-caught shrimp require an additional catch certificate to combat illegal fishing; farmed shrimp do not. Finally, to qualify for preferential treatment, proof of origin in accordance with the agreement is required.

Step 2: Compare the documents with the items received. The file, compiled as the sender’s shipments arrived, contains:

Expected DocumentWhyStatus
Invoice, packing list, bill of ladingThe foundation of any operationReceipts
Official Health CertificateProduct of animal originReceived but not signed: incomplete
Certificate of CatchWild shrimp onlyWas not received
Proof of OriginPreferential right requestedReceived, but refers to another invoice: does not cover the merchandise

On a generic checklist, this file would have appeared almost complete: five out of six documents received. In reality, three documents pose a problem: two prevent importation (health and catch certificates), and the third results in the loss of preferential treatment.

What this example shows:

  • The required list is derived from the goods themselves: it is the presence of wild shrimp—not the product “shrimp” in general—that makes the catch certificate necessary;
  • Every missing item must be explained: a useful alert does not simply say “certificate missing”; it specifies which certificate is missing, for which lines, and why;
  • "Presented" does not mean "valid": two of the three hold-ups involve documents that were in fact received.

This is the type of inventory that Docloop compiles when a file is opened, as shown in a demonstration reported by *Profession Logistique* (No. 11, Fall 2026): documents received, missing documents, and the reason each document is required, along with a confidence rating for each reading.

Do you want to be more productive?

Book a demo
Book a demo

The 6-Step Method

1. Open the file as soon as the first document is received

Arrival notice, booking, pro forma invoice: the first document is sufficient to create the file and identify the transaction (goods, origin, transportation). Waiting until everything has arrived means discovering shortages too late. This principle is discussed in our article “Why Must a Logistics AI Agent Analyze a Complete File?”

2. Compile a list of the required documents

Based on the goods and their code, origin, trade regime, and mode of transport, compile a list of the documents required by regulations (TARIC measures, proofs of origin, authorizations). Then add internal business rules: customer requirements and company procedures. These are the two categories of rules that Docloop distinguishes in its reconciliation module: external rules, derived from regulations, and internal rules, specific to each company.

3. File each document received and attach it to the file

Identify the type of each document (invoice, packing list, bill of lading, certificate, DAE) and link it to the correct transaction, regardless of its channel or language. A multilingual system must focus on meaning: a “certificado de origen” is a certificate of origin. The difference between OCR and document-based AI in this regard is explained in “OCR or Document-Based AI: What Are the Differences for Logistics?”

4. Make sure every piece is actually there

For each document expected and received: Is it complete, signed, and valid? Does its reference number match the invoice? Does it cover all the relevant line items and quantities? This is the step that turns a simple list of checked boxes into a real verification process.

5. Follow up early, with a specific request

A helpful follow-up message specifies which document is missing, why it is required, and for which lines on the invoice. It is sent to the sender or the customer as soon as the missing document is identified, not when it is reported. Eventually, Docloop envisions that an agent will draft the email to the partner themselves, with the human still retaining the decision to send it.

6. Plan, maintain, review

Keep a record of what was expected, received, followed up on, and approved. Documents must be retained for at least three years (Article 51 of the UCC), and a retrospective audit may request any of them. For an Authorized Economic Operator (AEO), this record supports self-auditing, which Docloop estimates accounts for about 2 to 3% of declarations: reviewing submitted files helps identify recurring deficiencies by supplier or by supply chain.

What is automated, what remains the responsibility of the filer

TaskCan be automatedRole of the Reporter
Classification and Filing of DocumentsYesHandling Unrecognized Documents
List of Required Documents (Regulations)Yes, based on the code, the source, and the regimeValidate the code and the plan, the list of which depends on
List of Required Documents (Internal Rules)Yes, once the rules have been set upDefine and update the rules
Attendance, Signature, Validity DatesYesCheck readings with a low confidence index
Coverage of the goods by each documentExplanation of the AlertResolving Ambiguous Cases
Exemptions, deferred documents, atypical casesReportDecide
Filing and Signing the DeclarationNoDecision-Making and Responsibility

The tool does not replace the expert; it generates alerts. AI may overlook a piece of context that is obvious to a human—such as an approved exception or a document sent through another channel. Each alert must therefore be explained so that the reporter can dismiss or confirm it within a few seconds. This principle of graduated human oversight is detailed in our article “Document-centric agentic AI: Definition.”

How to Measure Progress

  • the percentage of complete files upon receipt of the merchandise;
  • the time between the detection of a discrepancy and the receipt of the document;
  • the most common missing documents, by supplier, customer, origin, or type of goods;
  • the number of filings delayed due to missing documents;
  • the percentage of alerts deemed irrelevant by reporters, to refine the rules;
  • requests for supporting documentation received from customs after filing.

Identifying missing documents is one of the building blocks of a broader approach, described in our article “How to Automate Customs Document Verification,” and one of the checks performed by Docloop’s Customs Compliance Engine. For the French context, see also the changes introduced by DELTA I/E.

FAQs
No items found.