Peruvian import documents should be managed according to three categories: required, conditionally triggered and not applicable, and the issuer, date, VIN or bill of lading number and validity status should be recorded item by item.
Import support files are checked according to file categories
File complete matrix
| Field to check · How to Check All Supporting Documents for | How to record it | Evidence source | Action if unresolved |
|---|---|---|---|
| File Category | Save the original name, page number or number, record date and link of the file category | Verifiable original, downloaded file, system receipt, original image | The gap must not be closed when the file category is missing pages or issuance information |
| File name | Establish the issuing subject, file number, time and archive location index for the file name | Corresponding verifiable original, downloaded file, system receipt or original image | Return the supplement if the file name cannot be verified or the object does not match |
| Necessary or conditional triggering | Necessary or conditional triggering, write specific values, applicable conditions and exceptions | Contract attachments, site records, technical information or operation notices | Suspension of affected decisions when the scope of necessary or conditional triggering cannot be determined |
| Issuer | Save observation facts, occurrence scenes and collection time for the issuer | Missing part list | Record differences when the issuer does not match the original record |
| Issuance date | Register the date, local time, time zone and source channel of the issuance date | Corresponding time-stamped notification, system record or receipt form | If the issuance date lacks a timestamp or time zone, check the original timeline |
| VIN or bill of lading number | Copy the VIN or bill of lading number character by character, and record the issuer and related objects at the same time | Controlled documents, original issuance or acceptance receipt | If the VIN or bill of lading number cannot be connected to the vehicle or transaction under review, return it to the issuing party for confirmation |
| Valid status | Record the valid status conclusion, pending matters and documents supporting the conclusion | checklist, diagnostic records, inquiry results, signatures of both parties | When the valid status is still to be confirmed, it shall not be written as passed |
First determine whether the file category is applicable
This article splits the import support document into verifiable fields: the document category answers who is the target, the file name answers the applicable conditions, the required or condition trigger answers the current status, and the issuer answers who can close the difference.
How to mark required, conditionally triggered and not applicable: import support documents
This article assigns different tasks to two sources: the former answers the scope of the rules for import support documents, and the latter explains what materials need to be collected.
Peru SUNAT explains that SUNAT lists common supporting documents for import declarations, including transportation, commercial and insurance materials; the actual list depends on the business and declaration conditions.
Peru SUNAT explains that the Peruvian vehicle import page requires vehicle identity, business documents and access information to correspond to each other, and the complete set of checks should fall on the specific VIN.
missing part only returns affected steps: import support files
When actually filling in, use "File Category" as the search entry, and connect "File Name" and "Required or Conditional Trigger" to the same vehicle, order or event; blank items are reserved for filling, and records of similar items are not needed to fill in.
Fields to record for version information
When dealing with "How to check the complete set of supporting documents for Peruvian vehicle imports" in Peru, don't just record a general "compliance" 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. Do not swap in a look-alike 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.
Which checkpoints take priority when files conflict?
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 the supplement is completed, the effective date, scope of application and replacement relationship are backfilled to the Peruvian version record of "How to check the complete set of support documents for Peruvian vehicle imports", and then decide whether to restore subsequent nodes.
FAQ
How to replace the issuance document or the issuance authorization after it expires?
Check the validity period of the document and the authorization period of the issuer respectively, and obtain new documents or valid authorization certificates from the original issuer.
When can a conditional trigger file be marked as inapplicable?
State the triggering conditions, current facts and judge; if there is no basis for judgment, leave it pending for confirmation.
How are transportation, commercial and admission documents related?
Use VIN, bill of lading number, invoice number or case number to connect to prevent documents from different vehicles or batches from being mixed.
Public rules page only, no model documents — can that be recorded 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.
Which file do I keep when names match but versions differ?
Using applicable scope, issuance date and change history as the criteria. 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.
Submit the file category along with the source date
Redacted file categories, file names, required or conditional triggers and source dates can be sent via Starvia Automotive Contact Page, while candidates are checked using New Car Catalog.
The blank table in this article is used for review of import supporting documents; the actual conclusion shall be based on the original documents, physical condition of the vehicle and written records of relevant issuer, approver, or service provider. 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.