Reconciled MVE file per pedimento ready to sign in VUCEM

Definition

OCL Cargo’s MVE agent (Agent 05, «Value Manifestation») builds Electronic Value Manifestation support per pedimento: gathers documents, reconciles incrementables (via COVE and freight/insurance evidence), and leaves the file ready for the importer’s e.firma in VUCEM. It does not replace the signature or provide a customs legal opinion.

Gathering invoices, COVE, and freight by hand per operation is the pre-VUCEM bottleneck. Landing Agent 05 detects the operation, collects, reconciles incrementables, and leaves support ready.

What the MVE agent means in practice

Landing cycle: operation detected, documents collected y incrementables reconciled a MVE support ready. Manual: gather docs by hand, declare without support, key everything into VUCEM.

The agent prepares; it does not sign the MVE for the importer. Legal/operations detail of the act: MVE glossary and 2026 guide.

Why it matters (importer / 3PL / broker)

1.Importer

File ready for their e.firma; less pedimento friction.

2.Trade operations / 3PL

Standardizes packages per pedimento.

3.Customs broker

Gets consistent support; still uses the folio on the pedimento.

How it works / when it applies

It fits imports already on (or migrating to) electronic MVE. Confirm RGCE. Strong in manufacturing/nearshoring with international freight and incrementables.

It connects OCL spine freight (invoice, GPS, POD) to customs value when freight is incrementable.

PieceRoleNote
Commercial invoiceGoods basisCoherent with pedimento
COVERelated value acknowledgmentNot the MVE
Freight / insuranceTypical incrementablesCase and rules dependent
Importer e.firmaMVE signatureDo not delegate to broker
The agent reconciles; value responsibility stays with the importer.

Per-pedimento checklist

1.Base docs

Invoices, COVE, contracts if applicable.

2.Incrementables

Freight/insurance/commissions reconciled.

3.Consistency

Vs pedimento and transport operation.

4.Ready for e.firma

Package for VUCEM E2.

Zen flow

  1. Detect

    Operation

  2. Collect

    Documents

  3. Reconcile

    Incrementables

  4. VUCEM

    Ready e.firma

Always verify SAT/DOF; the diagram is operational.

Common mistakes

1.Broker «signs for the importer»

Electronic design requires importer e.firma.

2.Confusing MVE with COVE

See MVE vs COVE.

3.Declaring without freight support

Incomplete incrementables = observation risk.

OCL and the shipment file (light)

OCL builds MVE support on the same trip/pedimento file. Can stamp invoices and Carta Porte; not a substitute for broker advice. Map: freight agents.

Sources and further reading

  1. Glossary: MVE.
  2. Guide: MVE 2026.
  3. Vs: MVE vs COVE.
  4. Hub: freight agents.
Key takeaways5 points
  1. Landing note: electronic mandate often cited from 1 Jun 2026 — verify RGCE/SAT/DOF.
  2. Builds per-pedimento support; the importer signs with e.firma (not the broker «for you»).
  3. MVE concept: what is MVE. This agent automates the file.
  4. OCL can stamp invoices and Carta Porte; it is not a customs authority; operating playbook — confirm with your broker/tax advisor.
  5. Hub: freight agents.

Is your MVE still built folder by folder?

30-minute diagnostic on one corridor: what the agent closes alone vs what escalates to your team. 6–8 week pilot.
Book a diagnostic

Frequently asked questions