A customs broker handling aircraft parts retypes the same fields on every file: invoice lines into the declaration, the AWB number into the cargo control reference, pieces and weight into the release request. Automating that starts with a field list per document and a rule for what happens when two documents disagree.
TL;DR. From the commercial invoice, extract seller, buyer, invoice number, currency, and per line the part number, description, quantity, unit and total value, origin and HS code if given. From the AWB, extract the AWB number, shipper, consignee, airports, pieces, gross and chargeable weight, and nature of goods. Check invoice pieces and weight against the AWB before filing. Doana reads invoice lines in its web app, and builds custom extraction pipelines for invoices, AWBs and other customs files on a broker's own document set, with CSV output for the broker's customs software.
What should be extracted from the commercial invoice?
| Level | Fields |
|---|---|
| Header | Seller, buyer, ship-to, invoice number and date, PO number, currency, Incoterm, total value |
| Each line | Part number, description, quantity, unit of measure, unit price, line total, country of origin, HS code if the seller gives one, weight if given |
| Aviation extras | Condition (new, overhauled, repaired, exchange), serial numbers, core charge or exchange fee |
Canada lists invoice requirements in D1-4-1. An exchange unit invoiced as a repair fee plus a core charge needs both amounts, because the declared value depends on the transaction.
What should be extracted from the AWB?
| Field | Use |
|---|---|
| AWB number (3-digit airline prefix + 8 digits) | Cargo control reference, tracking |
| HAWB number, if consolidated | House-level reference for the broker's client |
| Shipper and consignee | Must match invoice parties or explain the difference |
| Airports of departure and destination | Port of arrival |
| Pieces, gross weight, chargeable weight | Checked against the packing list and invoice |
| Nature and quantity of goods | Description quality ("aircraft parts" is weak for ICS2) |
The last digit of a master AWB number is a check digit: the remainder of the 7-digit serial divided by 7. A mistyped AWB number fails that check, which makes it one of the few fields an extractor can validate on its own.
What should be checked between the two?
- Parties. Invoice buyer and AWB consignee differ often (a forwarder, a repair shop). That is normal but needs to be explained in the file.
- Pieces and weight. Invoice or packing list weight against AWB gross weight. A large gap means a missing box or a wrong invoice.
- Description. A specific invoice line against a vague "consolidated" AWB description.
- Release certificate. Part number and serial against the Form 1 or 8130-3. See Form 1 part number does not match the invoice.
How does Doana handle this?
Two levels:
- Standard product. The Doana web app reads invoice lines (part number, HS code, quantity, total price, country of origin, weight) and release certificates, and matches invoice lines to certificates by part number. EASA Form 1 extraction box by box is self-serve over MCP.
- Custom extraction pipeline. For a broker's full file (invoices, AWB and HAWB, packing lists, T1, certificates of origin), Doana sets up an extraction pipeline on the broker's own documents. The fields and the CSV layout follow the customs software the broker already uses. Pipelines start from the contact form.
Doana does not file the declaration. The broker reviews the extracted data and files it.
Next
List the fields your team retypes today, per document. That list is the specification for a pipeline. Related: The 7 aviation customs documents to automate first.
Sources
- https://www.cbsa-asfc.gc.ca/publications/dm-md/d1/d1-4-1-eng.html
- https://www.cbsa-asfc.gc.ca/publications/dm-md/pdf/d17-1-10-eng.pdf
- https://www.kuehne-nagel.com/how-to/air-freight/import-control-system-2-ics2
- https://doana.ca/en/contact