A single version of the imported data is managed by the project responsibility matrix: the master file location, modifier, approver, effective date, invalid version and distribution target should all be traceable.
The master file of customs declaration information first confirms who is qualified to act.
The document supervisor first designates a controlled library as the master file, and saves the system record ID, current version number, permissions and data owner for each document. Modifiers are responsible for submitting changes, and approvers decide when the new version will take effect; distribution records are responsible for proving who has received the new version and who still holds the old version. Project roles are not equivalent to Colombian Customs legal roles.
Contractual responsibilities and legal qualifications are checked separately: Customs declaration data master file
How the master file management answer document is saved, approved and distributed; application qualifications are confirmed by applicable Colombian rules and local authorities. The two responsibilities shall be documented separately. After internal approval is completed, if the applicant's qualifications or DIAN acceptance status have not been confirmed, the file can only remain "internally current and externally pending".
Create a responsibility matrix using the master file storage location
The public page of the main file of customs declaration information only supports explicit content; vehicles, contracts and on-site facts will continue to be obtained from the original records of this case.
Colombia DIAN explains that the Colombian DIAN import page provides centralized entry points related to import declaration, valuation and customs clearance. The project information should be retained in the current applicable version.
Colombia DIAN explains that the DIAN customs service portal shows that the import procedure consists of multiple declarations and supporting documents. The document owner and change record need to be clear.
The division of responsibilities or cut-off points set in this article for the master file of customs declaration materials belong to the project governance method, and these internal fields are not directly specified on the public page; local qualifications or carrier acceptance status still require separate written confirmation.
What to do if written confirmation is not obtained: Customs declaration data master file
The responsibility matrix simultaneously controls library location, versions, approvals, and distribution. The fact that the file becomes the current version in the library does not automatically mean that the applicant or DIAN has accepted it; the external status is listed separately.
Master version and distribution table
| Check fields | Fill in format | Direct evidence | Action if failed |
|---|---|---|---|
| Master file storage location | Record the controlled library name, directory or system record ID, data owner, access permissions and backup location | File system page, permission list and backup record | Migrate into the controlled library first if it can only be obtained from a personal computer or chat attachment |
| Current version | Indicate the file name, version number/revision number, file date, current status and corresponding business object | Current controlled files, version history and approval records | Stop external distribution when the version number or object is inconsistent |
| Modifier | Record name, role, change application number, modification time and modified fields | Change order, version history or system audit log | Return instructions when the modification cannot be traced back to the application and specific fields |
| Reason for modification | State the triggering file or event, old value, new value, scope of impact and correction period | Customs/agent correction notice, contract change or internal difference order | Do not approve the new version if the reason does not correspond to the change field |
| Approver | Record name, role, scope of authorization, approval conclusion, approval time and remarks | Authorization matrix, approval flow or signature record | Keep the last approved version valid when approval authority is insufficient |
| Effective date | Record the date, time, time zone and the approval or external acceptance event that triggered the new version to take effect | Approval receipt, system release time or written confirmation from the relevant local authority or service provider | Marked as "Approved, not effective" when the effective conditions have not occurred |
| Obsolete version | Record the old file name, version number, expiration date, replacement version, read-only archive location and obsolescence identification | Version library, obsolescence list and system audit records | Suspend distribution while the old version can still be edited or downloaded for use |
| Distribution objects | Record the received version, sending time, channel and receipt confirmation time by organization/name | Distribution log, email receipt or document system confirmation | Do not assume that the other party has adopted the new version when the receipt is not confirmed |
| Mis-delivered withdrawal | Record mis-delivered version, recipient range, withdrawal time, substitution notice and whether it has been used for declaration | Withdrawal notice, recipient reply and affected link inspection | Immediately upgrade and recheck when the old version has been used for declaration or delivery |
Version recovery starts with the affected object: first confirm the delivery range of the old version and whether it has been used, then send the replacement version and obtain receipt confirmation. The master file retains the old version and does not overwrite the audit trail.
What must be recorded under version information?
When dealing with "Who should maintain a single valid version of Colombian vehicle import data" in Colombia, don't just record a blanket "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. Never substitute a similar model name for it.
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.
Which points should be verified first if files are inconsistent?
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, the effective date, scope of application and replacement relationship are backfilled to the version record of "Who should maintain a single effective version of Colombian vehicle import data" in Colombia, and then decide whether to restore subsequent nodes.
FAQ
Does the owner of internal documents belong to the legal role of customs?
Doesn't belong. The file owner is a project governance role responsible for maintaining master files, versions, approval and distribution records.
How to prevent the obsolete version from being used anymore?
Move into a read-only archive, mark expiration date and replacement version, and recall the old copy in the shared directory.
How to restore the old version after mistakenly sending it?
Confirm the scope of receipt, send withdrawal and substitution notices, record affected links and check whether the old version has been used for declaration or delivery.
A public rules page alone, with no vehicle model documents: may it be written up as compliant?
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. This question should be reviewed in conjunction with Colombia's "Who should maintain a single valid version of Colombian vehicle import data" plus the matching original records.
Which version of a same-named file can still be used?
According to 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. This question should be reviewed in conjunction with Colombia's "Who should maintain a single valid version of Colombian vehicle import data" along with the corresponding original records.
Prepare a traceable customs declaration data master package
The data package at least contains the controlled library or system record ID, current version, change request, approval record, invalidated archive, distribution list, receipt confirmation and mis-delivery withdrawal status. Candidate versions can be checked with the help of Starvia Automotive New Car Catalog, and the redacted file catalog can be submitted from the Contact Page; application qualifications and DIAN processing results will still be confirmed by the local authority.
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.