Compared definition
MVE (Electronic Value Manifestation) is the formal customs-value declaration transmitted by the importer in VUCEM (E2) with e.firma. COVE (Value Acknowledgment) is a related acknowledgment/document that supports value information in the customs ecosystem, but does not by itself replace that electronic declaration. In real operations they usually complement each other inside the same pedimento file.
In the clearance WhatsApp someone writes “send the COVE” and another “is the MVE done?”. Not the same thing. If you mix MVE and Value Acknowledgment, you sign incomplete or pay the pedimento without a folio.
This comparison separates roles, timing, and owners. To build amounts see customs value and incrementables; for the full map, the MVE 2026 guide and common mistakes.
MVE vs COVE: side by side
Same family (value), different act. Use this table in the kickoff with broker and trade ops.
What it is
MVE: Electronic customs-value declaration
COVE (Value Acknowledgment): Value acknowledgment/support related to the operation
Typical channel
MVE: VUCEM format E2
COVE (Value Acknowledgment): COVE scheme / references in the file
Who signs / owns
MVE: Importer with e.firma
COVE (Value Acknowledgment): Per the acknowledgment and who generates it; not “the broker’s MVE”
Key output
MVE: Folio (~13) a pedimento
COVE (Value Acknowledgment): Amount support / document link
Does it replace the other?
MVE: Does not replace COVE
COVE (Value Acknowledgment): Does not replace MVE
When a gap hurts
MVE: No folio = electronic pedimento not tied
COVE (Value Acknowledgment): No support = weak MVE under audit
When you need both
Common 2026 scenario: import with goods invoice + international freight documented with COVE + signed MVE integrating value. Missing one piece and the broker cannot close confidently.
Not every operation looks the same (regime, Incoterm, one COVE vs several). Practical rule: cover declaration (MVE) and support (COVE/evidence) before pedimento payment once the electronic scheme applies. Verify SAT/DOF/RGCE.
In imports with multiple providers (goods + freight + insurance), one COVE per transport shipment plus an MVE integrating the total is common. The customs team must name roles at kickoff: who generates COVE, who transmits E2, who pastes the folio. If those names mix in WhatsApp, the pedimento pays late.
Select a step to see detail
Step detail · 01
Map value documents
Step 1
Mistakes when mixing MVE and COVE
1.Mistake: Treating COVE as if it already were the MVE
The Value Acknowledgment does not create the E2 folio or fulfill the importer’s signed declaration.
Symptom: pedimento waiting for folio
2.Mistake: MVE signed with amounts different from COVE
The authority sees inconsistency. Prior reconciliation is cheaper than later explanation.
3.Myth: “From June 2026 only MVE exists”
Mandatory electronic manifestation does not erase the usefulness/obligations of COVE-type supports. Review each obligation separately in official sources.
4.Mistake: Asking the broker to “just sign the COVE and we are done”
Even with a perfect COVE, MVE still belongs to the importer with e.firma.
Who does what on the team
Importer: signs MVE and owns the value. Trade ops/3PL docs: builds the folder and reconciles. Broker: pedimento + folio use. Tools: prepare data. VUCEM remains the MVE channel.
Value folder
Primary owner: Trade ops
Dependency: Invoices / freight / insurance
Quality check: Amounts reconcile
COVE(s)
Primary owner: Ops / broker per case
Dependency: Value data
Quality check: Reference ↔ shipment
MVE E2 + folio
Primary owner: Importer
Dependency: e.firma + folder
Quality check: Full folio ~13
Paid pedimento
Primary owner: Broker
Dependency: MVE folio
Quality check: Field captured
Quick myths
1.Myth: “Same procedure, two names”
Different names, different acts. Train the team with the table above.
2.Myth: “If OCL builds the support, I no longer sign”
OCL (or another agent) can prepare MVE/COVE per pedimento ready for VUCEM; the importer’s e.firma is not delegated by software.
Cross resources
Base definition: what is MVE. Incrementables: customs value. Goods classification: SAT code finder.
Keep verifying SAT/DOF/RGCE before every process change. Especially in 2026 with moving mandatory calendars.
Sources and further reading
- SAT/RGCE: MVE and COVE play different roles. Verify each obligation separately in official sources.
- OCL: MVE 2026 guide.
- Definition: what is MVE and incrementables.
- E2 process: how to file MVE.
- Failures: MVE mistakes and penalties.
Key takeaways5 points
- MVE = electronic customs-value declaration (importer, VUCEM E2, e.firma). COVE = Value Acknowledgment (related support).
- They are not synonyms and do not automatically replace each other: a strong file usually needs both roles covered.
- The MVE folio goes on the pedimento; COVE ties value/amount evidence to the operation.
- Costly mistake: “I already have COVE, so I skip MVE” (or the reverse: signed MVE with no COVE/freight support).
- 2026 MVE mandatory dates do not make COVE obsolete. Verify each obligation in SAT/RGCE.
MVE and COVE in one file
Frequently asked questions
No. MVE is the Electronic Value Manifestation (declaration signed by the importer in VUCEM). COVE is the Value Acknowledgment, a related support. They complement each other; they are not synonyms.
Once the electronic manifestation scheme applies, you need MVE (and its folio on the pedimento). COVE alone does not fulfill that role. Confirm current obligations in SAT/RGCE.
It depends on your operation and which supports the file requires. In practice, freight and other amounts are often backed by COVE or equivalent evidence. Ask your broker case by case.
The folio from the transmitted/signed MVE (about 13 characters). Do not confuse internal COVE references with that folio.
MVE is signed by the importer with e.firma. COVE follows the generation/acknowledgment rules of that document; do not use that as an excuse for the broker to “sign the MVE.”
The MVE agent builds per-pedimento support. Including incrementables via COVE. Ready for VUCEM, so you declare and sign without fighting folders on ETA day.