Transport Canada's Digital Trade Consultation: What Canadian Importers Should Actually Care About

The Consultation

Transport Canada and Global Affairs Canada opened a comment period (closing July 10) on a digital-trade strategy—specifically, replacing paper invoices, bills of lading, certificates of origin, and customs declarations with digital equivalents. They’re calling it “paperless trade.”

If you file CADs regularly, you know most of this shift already happened. CBSA moved the Commercial Accounting Declaration to the CARM Client Portal in 2024. eManifest captured cargo control numbers and ACI years ago. The GST remittance, bond management, and monthly K84 statements all sit in CARM now. The “digital” part isn’t aspirational—it’s operational.

What remains on paper, or in hybrid form, are the edges: certain certificates of origin under CUSMA, phytosanitary certificates from CFIA, some commercial invoices that still arrive as PDFs by email but require manual keying, and bills of lading that live in carrier portals but don’t push data automatically into customs filings. That’s where friction still lives, and that’s what this consultation should address.

Where Paper Still Costs Time

The biggest pain point isn’t the CAD itself. It’s the supporting documents that don’t arrive in machine-readable format or don’t arrive at all until the importer chases them down.

Certificates of origin are a common example. Under CUSMA, you can self-certify on letterhead. No standard schema, no digital handshake, just a PDF or Word doc that meets the minimum data elements in D11-4-16. If the exporter sends it late or with a missing field—tariff classification, producer name, date range—you’re either filing without preference or holding the CAD while you chase the correction. A proper digital certificate standard, with mandatory fields and a submission deadline tied to cargo release, would close that gap.

Phytosanitary certificates from CFIA are another. Some commodities require the original paper certificate at the port of entry. CFIA has piloted electronic phytos under the IPPC ePhyto hub, but adoption is inconsistent, and when the certificate doesn’t arrive digitally, your cargo sits until CFIA clears it manually. That delay compounds when you’re running cold-chain freight and the product has a short shelf life.

Commercial invoices remain a hybrid mess. Most importers send PDFs by email. Brokers key the line items into the CAD. If the invoice is missing the country of origin, the HS code, or the correct currency conversion date, you’re back to the importer for clarification. A structured data standard (JSON, XML, EDI 810) would eliminate the re-keying step and reduce errors at filing.

What CBSA Already Digitized

CARM handles the core customs transaction. You file the CAD, declare duties and GST, post financial security through an RPP bond or transactional security, and settle monthly through the portal. The K84 statement reconciles your releases, payments, and adjustments.

eManifest captured the cargo control number, the ACI data (shipper, consignee, HS code, value), and the PARS or RMD release notification. That happens before the truck crosses the border. The cargo release is digital. The only paper left is the CCN barcode on the driver’s paperwork, and even that’s a printed reference, not a primary document.

If you’re filing under CUSMA and claiming preference, the certification itself can be digital—most importers maintain a database of certifications and attach them as PDFs to the CAD. CBSA doesn’t require original ink signatures. The issue isn’t whether digital is allowed; it’s whether the exporter actually sends the cert on time and in usable form.

Where the Strategy Should Push

Transport Canada’s consultation should focus on three areas: interoperability, deadlines, and OGD alignment.

Interoperability means carrier data, commercial invoices, and certificates flow into CARM without re-keying. The bill of lading contains the shipper, consignee, HS code, and declared value. That data should populate the CAD automatically. Right now, it doesn’t. Brokers pull the data from the carrier’s portal, the importer’s email, and sometimes a separate freight forwarder system, then manually enter it. A common data schema and API access would cut filing time and reduce errors.

Deadlines matter when the document is required for release. If CFIA needs a phytosanitary certificate, the exporter should be required to submit it digitally before the cargo arrives, not three days later when the truck is already sitting in our Montreal sufferance warehouse. Tie the document submission deadline to the ACI window or the cargo control document. Make late submission a penalty event, not a routine delay.

OGD alignment means CFIA, Health Canada, and Transport Canada (TDG, vehicle imports) need to accept digital submissions in the same format and timeline CBSA does. Right now, each agency has its own portal, its own document requirements, and its own release workflow. If the product requires both a CBSA release and a CFIA import permit, the digital permit should trigger the CBSA release automatically. That integration exists in concept but not in practice.

What to Flag in Your Comment

If you’re submitting feedback to [email protected] by July 10, here’s what Canadian importers should emphasize:

• Mandate structured data formats for commercial invoices and certificates of origin. PDFs aren’t good enough. Require JSON, XML, or EDI standards that populate the CAD without re-keying.
• Require exporters to submit certificates of origin and phytosanitary documents before cargo arrival. Tie the deadline to the ACI submission window. Penalize late submission the way CBSA penalizes late CAD filing.
• Build API bridges between CARM and OGD portals. CFIA permits, Health Canada NOCs, and Transport Canada approvals should flow into the CAD automatically. Stop making brokers toggle between four portals to file one entry.
• Publish a timeline for full digital adoption. If the government wants paperless trade by 2027, say so, and give importers and exporters a deadline to transition their systems.

What Doesn’t Need Fixing

CARM works. The CAD filing process is stable. The RPP bond math is clear. Monthly settlement through the K84 is predictable. The CARM Client Portal has its quirks, but the core transaction is digital and functional.

eManifest works. ACI submissions happen on time. PARS and RMD releases process automatically. The cargo control number links the shipment to the CAD without manual reconciliation.

The problem isn’t CBSA’s infrastructure. It’s the upstream documents that arrive late, incomplete, or in formats that require manual translation. That’s where the strategy should focus.

If your team wants to submit a comment, the government portals and procedural context for Canadian customs compliance are worth reviewing first. We file CADs every day and see where the paper still causes delays. Get in touch if you want to talk through what’s worth flagging before the July 10 deadline.

Source: CSCB