If you import into Mexico in 2026, the Electronic Value Manifestation (MVE) stops being “clearance paperwork” and becomes a digital control of customs value: the base for duty, VAT, and related contributions. Whoever improvises the file at the border pays with delays - or with a poorly supported value.
This guide is the hub: operational definition, effective dates, who signs, VUCEM flow, incrementables, and checklist. For short definitions and steps, use the linked glossary articles.
What is MVE and why it matters in 2026?
MVE is the mechanism through which the importer declares the elements needed to determine the customs value of goods entering national territory. Under the electronic scheme it is transmitted via VUCEM (Single Window), typically under RGCE format E2.
It is not a “broker formality.” It is the declaration of the owner of the commercial operation. If the value is wrong or support does not exist, the risk sits with the importer - even if the broker or customs agent runs the pedimento.
Expanded definition: what is the Value Manifestation (MVE).
Effective dates and coexistence (verify SAT/DOF)
Market reference
Electronic enforceability cited from 1 June 2026, after SAT extensions in communications and RGCE 2026 amendments.
Prior coexistence
Until earlier cutoffs (e.g. 31 May 2026 in several notes), traditional and electronic schemes coexisted. Do not assume: read rule 1.5.x in force on the pedimento date.
Who signs and who prepares?
| Role | Can prepare data | Signs MVE |
|---|---|---|
| Importer | Yes | Yes (e.firma) |
| Legal representative | Yes | Yes, with the authorized representative’s e.firma |
| Customs broker | Support / consult if authorized | Does not replace the importer |
Flow: file, VUCEM, and folio a pedimento
- 1
Build the file per shipment
Invoice, transport, payments, contracts/POs, evidence of incrementables.
- 2
Align COVE / value acknowledgments
Without COVE–MVE–pedimento coherence, VUCEM or customs sends you back.
- 3
Capture and sign E2 in VUCEM
Valid e.firma (.cer, .key, password). Generate the folio.
- 4
Declare the folio on the pedimento
Before duty payment. Without the correct folio, you cannot close the electronic circuit.
Detailed step-by-step: how to file MVE in VUCEM.
Customs value and incrementables
Customs value is not always “the invoice price.” Freight, insurance, commissions, and other concepts can be incrementables and must be documented. MVE is where that story is declared; the file is where it is proven.
Dedicated guide: customs value and incrementables for MVE. Comparison with acknowledgments: MVE vs COVE.
For SAT freight/service codes in your document chain, use the SAT code finder.
Preparation checklist (importer)
- Valid e.firma for the importer / representative
- Inventory of pedimentos / shipments for the cutoff period
- Invoices and payment proofs locatable per shipment
- Transport docs (BL, AWB, carta porte by mode)
- Evidence of freight, insurance, and other incrementables
- COVE / acknowledgments aligned to the value you will declare
- Process: who captures in VUCEM vs who signs (clear RACI)
- Pilot / sandbox test before the mandatory cutoff
Typical mistakes and how to avoid them: MVE mistakes and risks.
How OCL’s MVE agent fits in
OCL Cargo includes a Value Manifestation (MVE) agent built for the real bottleneck: assembling support per pedimento, reconciling incrementables via COVE, and leaving the package ready for VUCEM - instead of hunting PDFs on clearance day.
File per pedimento
Structured documents, not a chaotic folder
Reconciled incrementables
What you declare matches what you can prove
Ready for VUCEM
Less manual capture; sign with your e.firma
Is your MVE ready - or improvised?
In a demo we review a real pedimento: docs, incrementables, and gaps before VUCEM.
Book a demoKey takeaways5 points
- MVE is the electronic customs-value declaration: the importer signs it in VUCEM (E2), not “the broker for you.”
- Without an MVE folio declared on the pedimento (before paying duties), clearance stalls under the electronic scheme.
- The mandatory date has moved; treat 1 June 2026 as a market reference and verify RGCE/SAT on the day you operate.
- The file (invoice, transport, payments, incrementables) is 80% of the work; VUCEM is the last mile.
- OCL builds MVE support per pedimento so you do not improvise documents in the clearance window.
Frequently asked questions
It is the electronic declaration through which the importer states to customs the elements needed to determine the customs value of the goods. It is transmitted via VUCEM (format E2), signed with the importer’s e.firma, and generates a folio that must be declared on the pedimento before duties are paid.
Multiple industry sources and SAT communications cite electronic enforceability from 1 June 2026, with prior coexistence periods. Dates have shifted: always verify current RGCE, DOF, the SAT portal, and VUCEM before you operate.
The obligation and the signature sit with the importer (or a representative with authorized e.firma). The customs broker can support with information and consult if authorized in VUCEM, but does not replace the importer’s responsibility.
COVE (Value Acknowledgment) is a distinct document/acknowledgment; in the electronic flow it is often linked to value information. MVE is the formal value manifestation. You need both correctly aligned. See the MVE vs COVE comparison in the glossary.
At minimum: invoices or equivalents, transport documents, payment proofs, evidence of incrementables (freight, insurance, commissions, etc.), and contracts/POs when they apply. Article 81 of the Customs Law Regulation and the RGCE detail annexes - confirm the current list.
The Value Manifestation agent builds support per pedimento: gathers documents, reconciles incrementables via COVE, and leaves the file ready to transmit in VUCEM with e.firma - instead of assembling everything by hand per shipment.