eCMR is not a PDF. This is the single point most often missed by hauliers who think they are already compliant because their drivers email a signed scan from the cab.
The eFTI common data set defines exactly which data fields must be captured, in which structure, and in which machine-readable format. The dataset mirrors the data fields of a paper CMR (consignor, consignee, place of taking over, place of delivery, dates, goods description, packaging, weight, charges, dangerous goods information under ADR, special instructions and so on) but adds the fields that only a digital record can carry: precise timestamps, geolocation, signature blocks compliant with eIDAS, transmission logs, and a unique eFTI identifier.
The
eIDAS Regulation (EU) 910/2014 defines three levels of electronic signature: simple, advanced, and qualified. To give an eCMR the same evidential weight in court as a paper CMR, most legal commentators
recommend at least an Advanced Electronic Signature, with Qualified Electronic Signatures used where the highest evidential standard is needed. A photograph of a fingerprint or a typed name is not enough.
Practically, this means three things.
Your platform must support eIDAS-compliant signatures. The data must be
exported and exchanged in the eFTI schema, not in a free-form PDF. And the
audit trail (who signed, where, when, what changed, who accessed)
must be retained and produceable for the duration required by national rules.
The takeaway is: a digitised paper workflow is not the same as an eCMR, and an eCMR is not the same as eFTI compliance. The first is a habit improvement. The second is a legal document. The third is a regulated, certified data exchange. By July 2027, only the third counts.