From the EAD stack to the arrival notification: the first step to automating the customs declaration (SAD, “DUA” in Spain)
An indirect-export truck arrives with a stack of scanned export accompanying documents (EAD, “DAE” in Spain) in several languages, and someone at your agency types them in one by one for the arrival notification. Sia reads them, checks them against the loading list and prepares the CC507: the first step of the customs declaration, rolling out today. Import, export and transit come next: they are in development.
- scanned pages
- 79
- declarations
- 22
- in one test
- 6 min 27 s
Measured by us in September 2026 on the scanned PDF of a real truck.
Sia for clearance is the Seautomatiza platform that reads the export accompanying documents (EADs) on every indirect-export truck, splits them by MRN, checks them against the loading list and prepares the arrival notification (CC507) for your team to review. It is rolling out; import, export and transit are in development.
A test with a truck
One truck, timed
A truck of 79 scanned pages, split into 22 declarations and read in 6 min 27 s. Measured by us in September 2026 on the scanned PDF of a real truck. How long each truck takes depends on its pages and on how they were scanned.
79
Scanned pages
Those of a real truck, in the test.
22
Declarations
Into which the truck was split.
6 min 27 s
Reading time
Measured by us in that test.
How it works
From the email with the PDFs to the CC507
You upload the truck
Upload the truck’s PDF or drag in the email it came with, attachments and all. The EADs can arrive scanned, split across several PDFs or in a single batch, and in the language of the customs office that issued them.
Sia splits and reads each EAD
I split the stack into declarations using each MRN and its barcode. From every EAD I take the commodity code, MRN, packages and gross weight, and if two readings disagree, I flag it.
I check the truck and prepare the CC507
I check the EADs against the loading list and tell you which one is missing, with its MRN, packages and weight. The arrival notification is left ready: your team reviews it and your clearance software transmits it.
Guide: how to automate the customs declaration (DUA) step by step (in Spanish)
By hand vs Sia
What changes on every truck
| What changes | By hand | With Sia |
|---|---|---|
| Splitting the truck’s PDF | By handSomeone leafs through page by page to see where each declaration starts | With SiaSia splits it by MRN and barcode |
| Reading each EAD | By handThe commodity code, MRN, packages and weight are hunted down in each one, sometimes in another language | With SiaSia pulls out the four fields, ready to copy in one click |
| Checking against the loading list | By handPackages and weights are added up by hand | With SiaSia flags what doesn’t match and which EAD is missing |
| Arrival notification (CC507) | By handThe MRNs are typed in one by one | With SiaSia prepares it; your team reviews and transmits it |
FAQ
Questions about clearance
Does Sia submit the customs declaration or the CC507 for me?
No. Sia reads the documents and leaves the data and the arrival notification ready, but it does not transmit anything to the Spanish Tax Agency (AEAT). Someone at your agency reviews it and your clearance software transmits it, as it does today. Responsibility for the clearance and the final say stay with you.
What does it do today and what is in development?
We are currently rolling out indirect export: reading the EADs on each truck and the arrival notification at the office of exit (CC507). Import, export and transit (T1) are in development, and before you use any of them we tell you exactly where each one stands, without selling as finished what isn’t.
Does it work with scanned EADs and other languages?
That is what it is built for: EADs arrive scanned, in several PDFs or in one stack, and in the language of the customs office that issued them. Sia first reads what can be checked without AI, such as the barcode or the PDF’s text layer, and uses AI for the rest. If two readings disagree, it flags it for you to look at.
Do I have to change my clearance software?
No. Sia works alongside your clearance software: it leaves the commodity code, MRN, packages and weight of every EAD ready to copy, and the arrival notification prepared. Today it does not feed data straight into any clearance software; if yours can import a file, we will look at it with you.
Where do the truck’s documents go?
Documents are processed in the EU: the server is in the EU and the Google AI that reads them runs in a European region. We sign a data processing agreement (Article 28 GDPR) with each agency, and everyone on your team logs in to the platform with their own user account.
What is an EAD?
The export accompanying document, called “DAE” in Spain. According to the Spanish Tax Agency, in indirect exports (where the office of export and the office of exit are different) it is still made available to the declarant, because the customs offices of some countries ask for it to confirm exit. It is the paper that comes with each truck and the one Sia reads.
What is the CC507?
It is the message that notifies the arrival of the goods at the office of exit. When the export was declared at another customs office and the goods leave through your port, your agency does not file the declaration: it reports that the goods have arrived, with the MRN of each EAD. The AEAT explains it in its information note 22/2024.