Prevalidation is the electronic review an authorized prevalidator runs on the pedimento file before it reaches the customs authority system. It checks syntax, catalogs, and data congruence: that the heading exists, keys are valid, and required fields are complete. It is not a customs approval or a legal sign-off: it only confirms the file is well-formed. When it errors, the pedimento does not advance to validation, and your operations clock keeps running.

authority
Before
catalogs
Syntax
of the data
Source
trip file
100%

The difference between losing two hours and losing the day is knowing which field is wrong, what its source is, and who fixes it.

Cluster: pedimento · expense account · freight audit.

Prevalidation is not validation

Confusing them costs: “it already passed prevalidation” does not release the operation or guarantee value or regulations. It means the file has no obvious capture errors.

Prevalidation is not validation

Clearing the prevalidator only means the file is well-formed.

PrevalidationValidation
WhoAuthorized prevalidatorAuthority system
ChecksSyntax, catalogs, structureRegulatory congruence
OutputReceipt or error listSignature for payment/clearance
Passing meansWell-formed fileClearance can continue
Source · SAT / ANAM · 2026 shipper playbook

How to read the error message

Errors arrive with a code and a short description. The method is always the same: flagged field, data source, fix at origin, log the cause.

How to read the error without guessing

Field, source y fix at origin a log the cause.

Select a step to see detail

Step detail · 01

Field

Not the symptom

Identify the flagged field. An “invalid HS” error may be a bad NICO, not the heading itself.
Three rejections of the same field in a month are a file problem, not a keying problem.
Clipboard with a foreign-trade document file
Fix the error against the data source, not against the keyer’s memory.

Errors that keep repeating

Document keys that do not match the regime, obsolete HS or NICO, inconsistent RFC, bad COVE reference, quantities that do not reconcile. None are “the system’s fault”.

Errors that repeat most

None are “the system’s fault”: each has an unreconciled source.

01

Catalogs

Missing/obsolete HS or NICO, or wrong regime key.

02

Identity

Importer RFC inconsistent with the registry; bad COVE or e-document reference.

03

Quantities

Units of measure that do not reconcile across lines and origin documents.

Source · MX pedimento playbook 2026

Trip file and broker

If you only patch the file and the error was born in the trip file, the same rejection returns. Ask your broker for the template where the data lives. Cluster: rectification, pedimento, DODA.

What OCL runs

OCL Cargo is an autonomous TMS with agents and computer use (operating screens and portals like an analyst). It builds the trip file per shipment, cross-checks evidence, and leaves exceptions to humans. It coexists without a day-one TMS migration. OCL can stamp invoice and Carta Porte. On the Mexico–US corridor, the value is closing the trip file before paying.

Trip file

Flow control

  1. Ingest

    Source

  2. Match

    Catalog

  3. Fix

    Origin

  4. Resubmit

    Receipt

6–8 week pilot (prevalidation)

Take your last 100 pedimentos with prevalidation rejection: baseline by field, root cause in catalog, and recovered yard hours. Metric: % of repeated rejections of the same field.

Elige un paso para ver el detalle

Detalle del paso · 01

Rejection log by field and month

Rejection log by field and month
Pilot checklist
Key takeaways5 points
  1. Prevalidation confirms syntax and catalogs, not legality or classification.
  2. Every error is fixed against the data source, not against memory.
  3. Recurring errors live in the catalog or template, not in one-off keying.
  4. Clearing prevalidation does not prevent a later rectification.
  5. OCL builds the trip file per operation and reconciles before the yard bills.

Do your pedimentos bounce on the same errors every month?

Related reading

Frequently asked questions