Declarations drafted from shipment data; your filer still signs

The question this file answersWhat happens to our cross-border flow when the one person who knows the HS codes goes on holiday?

Fits: cross-border operators and forwarders whose declarations are still assembled by a clerk from TMS or ERP data — the logistics playbook gives no per-day figure here; volume varies by trade lane.

Not for: operators who already hand the whole filing to an external broker and never see the data — there is no assembly desk to shorten.

Typical day

What the desk looks like today

Typical, from the logistics playbook — not a client's day. Volume varies too much for a published figure — the playbook calls it critical for anyone crossing borders — so count yours. For each consignment a clerk pulls shipment data out of the TMS, builds the declaration, the certificate of origin and any dangerous-goods paperwork, picks HS codes, submits, then watches for the rejection. It bites when a code is wrong, because a wrong code is expensive; and again now, as the EU's AES and ICS2 transitions change what the portal accepts.

What changes

What Monday looks like after

Thursday afternoon, the cut-off for tomorrow's departures. The filer opens drafts, not blank forms: declaration, certificate of origin and DG document already filled from the TMS, the suggested HS code beside each line with the last declarations that used it. Their time goes to the consignments the checker marked — a new commodity, a value that does not match the invoice, an origin the certificate does not support — and to the submission itself, still their click. Rejections come back to the same person. You can see, per lane, how many went out right first time. WCO (2023) measured shorter processing with automated pre-clearance — an authorities' figure, in the metric block above.

Typical, not a measured client result. Every figure here comes from the playbook source named below.

~40–60%

faster pre-clearance — World Customs Organization reports (2023)

Before: a clerk assembles declarations and certificates from shipment data by hand. After: WCO reports (2023) put automated pre-clearance 40–60% faster — filing still belongs to a named person.

Where this number comes from

WCO (World Customs Organization) reports (2023): automated pre-clearance systems reduce processing time by 40–60% — an authorities' figure about processing, not our measurement of a desk. The logistics playbook's own range for customs documentation is 30–50%, deliberately lower for regulatory work.

What we install

What we put in front of the systems you already run

Nothing about who files changes — your named person, your licence, your filing software or portal. What changes is how much is already filled when they open the form:

shipment data is read from the TMS or ERP — SAP TM, CargoWise, Oracle Transportation or the one you run
the declaration and certificate of origin are drafted from it, field by field
an HS code is suggested with its reasoning and the past declarations behind it
the draft is checked against the rules you already apply — origin, value, DG flags — and failures marked
the filer reviews, corrects and submits — logged with what was proposed and what changed.

First scope: one trade lane with repeat commodities.

What stays human — and what this will not do

Complex classifications. Reading a new regulation and deciding what it means for you. Every letter to and from the authority. The signature — a wrong code is expensive, and a person owns it.

What can go wrong — and what we do about it

HS classification of a new commodity is judgement, not lookup; the system proposes and shows its basis, sometimes wrongly, which is why nothing submits without the filer. Regulations change — AES and ICS2 are changing now — and a rule the checker does not yet know is one it will miss; updates are your compliance lead's decision. Incomplete shipment data in the TMS produces incomplete drafts, not clever ones. The playbook's 30–50% is the lowest logistics range: regulatory work is slower, and complex classifications and authority correspondence are outside it.

How long it takes, and what we need from you

Audit, about two weeks (€1.5–3K): we sit with the person who files, count declarations by type and destination, and check what your customs software accepts electronically. Pilot, 5–8 weeks — high complexity in the logistics playbook, because the rules move and a wrong code costs money (€10–20K): one trade lane, every draft reviewed and signed by your named filer. Production: further lanes, same sign-off, DG documents last. From you: two months of past declarations, time with the filer.

The path: free 60-second estimate → free 20-minute review → paid audit of this one process (€1.5–3K, typically two weeks) → pilot with your people in the loop (€10–20K, weeks, not quarters). No transformation programme. Prices are public, on the services page →

This is about you if…

Are declarations still built by a person copying fields out of the TMS or ERP?
Do the same commodities and destinations repeat week after week on at least one lane?
Is filing done in software or a portal your team controls, rather than entirely by an outside broker?

What does this mean in euros?

That depends on your volumes and wage costs — this page will not invent the number. The free 60-second estimate runs that calculation from your answers, with every multiplier sourced.

Get your free savings estimate 60 seconds · no sales call Or write first → Map a logistics process like this one — free, 60 seconds →

Not a named Aperanda client. Process file · Logistics.

Deep-dive process file. Volumes, weeks and sources come from the industry playbook; nothing here is a named client.

All process files