Rectification is the legal mechanism to correct data on a pedimento already validated or already cleared. The general rule allows rectification, but not every field follows the same path: some correct directly, others have assumptions and conditions, and some imply paying duty differences with updates.
- steps
- 4
- < request
- Spontaneous
- the origin
- Close
- Customs Law
- Art. 89
What sets the cost of the error is not the error itself but who finds it first.
Cluster: prevalidation · pedimento · DODA.
Four-step procedure
Start by stopping the problem, not filling forms. Freeze recurring data before fixing the past.
Four-step procedure
Start by stopping the problem, not filling forms.
Select a step to see detail
Step detail · 01
Stop
Freeze the data
Classify the wrong data
Descriptive, classification, value, quantities, and identifiers: assuming everything rectifies the same way is the second source of fines.
Classify the wrong data
Assuming every field rectifies the same way is the second source of fines.
| Type | Example | Implication |
|---|---|---|
| Descriptive | Description, supplier | Documentary rectification |
| Classification | HS, NICO | May change duties |
| Value | Customs value | Differences with updates |
| Quantities | Packages, UoM | Critical in IMMEX |
| Identifiers | Permits, e-docs | Specific assumptions and deadlines |
Origin matters more
The data entered via a bad invoice, unvalidated datasheet, stale catalog, or prevalidation that passed because it was syntactically valid.
Origin matters more than the error
If you close the rectification without closing the origin, you bought the same problem with a future date.
01
Supplier
Bad invoice or unvalidated datasheet.
02
Catalog
Stale template at your shop or the broker.
03
Prevalidation
It passed because the data was syntactically valid though false.
Spontaneous vs request
Coordinate with your broker in writing: who files, deadline, cost, and whether differences apply. Related: prevalidation, expense account.
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
Stop
Freeze
Classify
Field
Evidence
Source
File
Broker
6–8 week pilot (rectification)
Rectified pedimentos this quarter: root cause, field, spontaneous vs requested, and cost. Goal: zero repeats of the same origin.
Elige un paso para ver el detalle
Detalle del paso · 01
Freeze recurring data
Key takeaways5 points
- Stop propagation before fixing the past.
- Each data type has a different path.
- Gather evidence of the correct source before touching the pedimento.
- Who finds the error first sets the cost.
- Close the origin or you will buy the same problem again.
Do you find pedimento errors first, or does someone else find them for you?
Related reading
Frequently asked questions
The general rule allows rectification, but some fields have conditions, deadlines, or authorizations. Confirm with your broker and the current rule.
Spontaneous rectification is usually the lower-risk option. A pattern of frequent same-field rectifications does attract attention.
The error expires or is detected. Detected, it brings omitted duties, surcharges, and fines, and can compromise IMMEX.
No. Descriptive, classification, value, quantities, and identifiers have different implications.
It cross-checks operations against evidence before the authority finds them. It can stamp invoice and Carta Porte for the inland leg.