Changes after DUA submission cannot just replace email attachments; the customs broker should submit corresponding commercial documents or modify fields through electronic messages based on the customs observation type or declaration status, and keep records of each sending and acceptance.
Uruguayan car importers and dealers who have submitted a DUA by a customs broker are required to keep public rules separate from current vehicle information. Public rules are used to limit the outer boundaries of document version change registration. Only the original record of the current vehicle or order determines the action in this case.
Look at the node where DUA is located
Subsequent actions are determined by the following judgment: decide to use the file class observation reply and data modification message in the DUA process, or to withdraw and re-declare when the current status cannot be modified.
Record whether the change occurred in the commercial document itself, the DUA declaration field, or the vehicle-by-vehicle details in the vehicle and document evidence list, and record the second electronic message and file hash/identification in the status and disposition evidence list; the two tables support the document version change registration conclusion only when they refer to the exact vehicle or transaction, the applicable document revision, and the relevant date.
Category F Observation and Business Document Supplementary Submission
| Change object | Current status of DUA | Processing entrance | Required records | Whether goods can be picked up |
|---|---|---|---|---|
| Attachment to commercial invoice | Category F observation has not been accepted or received | Submit electronic documents or reply to observation | Old and new documents, message number, attachment hash, receipt | Subject to customs acceptance status |
| DUA declaration fields | Nodes that have been submitted but are allowed to be corrected | The customs broker selects the formal correction path | Correction application, system receipt, approver | No delivery until accepted |
| Vehicle-by-vehicle details or VIN | Affect vehicle identity or taxes | Judgment correction, withdrawal or re-declaration | Original declaration, new declaration and related instructions | Suspended when the identity chain is not closed |
| Major changes after acceptance | Existing entrances are not covered | Confirmed by the customs broker to the customs | Written consultation and final reply | Self-release without internal forms |
Completing the table core verification does not mean obtaining access to Uruguay or a warranty conclusion. It only closes the registration information gap for this document version change.
How to leave electronic traces when changing vehicle details
Official website of the Uruguayan government provides requirements that can be converted into verifiable fields: In Uruguay’s DUA digital import process, customs can use Type F observation requirements to submit commercial documents or modify declaration data, and the response should be completed within the system process.
This information is used to establish vehicle and documentary evidence inspection items and does not replace the physical vehicle, the contract, or records from the accountable organization. During the review, it should be determined whether the change occurred in the commercial document itself, the DUA declaration field or the vehicle-by-vehicle details.
Compare the change object, system entrance, required receipt and whether the goods can be picked up
- Freeze the approved version.
- Mark changes occurring in the business document itself.
- Check whether the second electronic message is synchronized.
- Save the system receipt and submit.
The final version confirmed by the customs broker and the buyer
Checking the Uruguayan government official website can confirm that the electronic customs document creation and declaration documents are submitted through a subsequent electronic message mechanism, which provides a basis for recording the message serial number, document identification and final acceptance status.
The public source explains how to check the status and disposal of evidence, and the conclusion of a case still depends on the second electronic message, file hash/identification and its date.
First determine which version the change belongs to
Stop conditions should be written directly into the order, acceptance form or service record: when the documents required by the customs are not submitted through designated electronic channels, the modified fields are inconsistent with the attached version, or the DUA status does not allow changes, the pickup and subsequent release arrangements will be suspended. The original version that triggered the document version change registration suspension is retained, and the supplementary document, reviewer and closing date are associated item by item; the any unresolved field remains open.
Changes in business documents and changes in DUA declaration fields must be recorded separately. Whether to add, correct, withdraw or resubmit is determined by the customs broker based on the current system status. The historical table cannot directly overwrite the system receipt.
Which fields must version information capture?
When dealing with "Uruguay DUA has been submitted and it is found that the commercial invoice or vehicle details need to be adjusted, the importer should submit electronic documents, respond to customs observation or re-declaration", do not just record a general "compliant" or "certified". The model version, year, energy type, configuration differences, document number, date of issuance or update, scope of application and responsible person should be separated. Each field must be able to return to the corresponding official page, original document or project parameter sheet; the public rules can only explain the processing method and cannot replace the proof that a certain vehicle or a certain version has been approved.
When multiple versions of the same file appear, the original file name, version number, receipt time and reason for change are retained. Divide "Confirmed", "To be added" and "Not applicable" into different states to avoid misinterpreting blank fields as unnecessary. If the version name is inconsistent with the parameters, VIN range or invoice description, first establish a difference record before deciding to repair, redo or suspend it. It should not be replaced by an analogous model name.
Use the following record structure to keep the review fields, evidence sources, and release conditions traceable:
| Verification field | Recording requirement |
|---|---|
| Car model/version field | Record the current value, direct source, and applicable scope |
| File number and version | Record the date, method, reading, and supporting evidence |
| Applicable markets and validity period | Record the document name, version, page, or original URL |
| Differences and affected nodes | Describe the discrepancy and the decisions it affects |
| Reviewer, date, disposition | Assign an owner, deadline event, and reopening condition |
Use this table to keep the evidence and affected decisions traceable. The final decision must still be checked against the original record and the current vehicle or batch.
On inconsistent files, which nodes are checked first?
Version differences may only affect page descriptions, but may also affect quoting, declaration, insurance, registration or vehicle delivery. During processing, the differences are first mapped to actual nodes: which fields have changed, who needs to be re-signed, which generated files can no longer be used, and which actions must wait for review. After receiving the new document, the old version cannot be deleted directly. The replacement relationship and effective time should be retained to facilitate explanation of why the conclusion has changed.
After completing the supplement, backfill the effective date, scope of application and replacement relationship to Uruguay's version record of "After the Uruguay DUA has been submitted, it is found that the commercial invoice or vehicle details need to be adjusted. The importer should submit electronic documents, respond to customs observation or re-declare", and then decide whether to restore subsequent nodes.
FAQ
Can the public page directly prove that the document version change registration has been passed?
No. Public pages only provide the outer boundaries of vehicle and documentary evidence or status and disposition evidence; the current vehicle must still be confirmed with the change occurring in the business document itself, a secondary electronic message, and the original dated record.
Can you proceed to the next step first when the second electronic message is missing?
Keep this item as "pending", and indicate the person who will supplement the document, the required materials and the deadline in the document version change registration record. Changes occurring in the business document itself alone cannot be closed by a second electronic message.
What is required before the process can resume?
Keep the version when the document version change registration is suspended, write the new materials, reviewers and closing date into the same record, and then recheck from the node that triggered the suspension.
May compliance be stated when all we have is a public rules page?
No. The public page can only prove the meaning of rules, processes or fields; whether a specific car model is compliant still needs to be supported by the corresponding version, parameters and project files.
The files have the same name but different version numbers. Which one can I continue to use?
Based on applicable scope, issuance date and change history. When it is impossible to prove that the new version has covered the current transaction object, the affected node should be suspended and the responsible person should be asked to confirm.
Prepare materials to be verified for document version change registration
First confirm the vehicle or version in Starvia Automotive New Car Catalog, and then send it from Contact Page. Changes after desensitization occur in the business document itself, the second electronic message and the data catalog. Please mark the missing DUA declaration fields or vehicle-by-vehicle details or file hashes/identifications separately to avoid writing open items as completed.
Boundary Note: The disclosed sources in the article cannot directly prove that "after the DUA has been submitted and it is found that the commercial invoice or vehicle details need to be adjusted, the importer should submit electronic documents, respond to customs observation or re-declare" has been established in the specific order; the contract, date, vehicle record and the conclusion of relevant issuer, approver, or service provider still need to be matched item by item. No conclusion should be inferred for vehicle variants, destination markets or transaction terms not stated here.
This article explains a document-review method for the vehicle and transaction scenario described for Colombia. It does not determine local import eligibility, customs, tax, registration or technical outcomes, or guarantee a vehicle's price, availability, delivery or warranty. Each transaction depends on current official requirements, the contract, VIN-specific records, the vehicle's actual condition and confirmation by the competent local party. No conclusion should be inferred for vehicle variants, destination markets or transaction terms not stated here. Review date: 2026-09-28.