A U.S. importer should keep the records needed to reconstruct and support every material customs decision—not merely the documents transmitted to the customs broker. That normally includes entry and transportation records, commercial documents, product specifications, classification analysis, valuation support, origin and preference evidence, admissibility records, broker instructions, approvals, correspondence, and proof of payment.

Why customs recordkeeping matters

Customs records allow U.S. Customs and Border Protection (CBP) to assess duties, collect statistics, and determine whether legal requirements were met. 19 U.S.C. § 1508 requires covered parties to make, keep, and render for examination records connected with import activity and information required by the customs laws. The statute expressly includes electronically generated and machine-readable data.

Recordkeeping is also how an importer demonstrates its decision process. An HTS code in a spreadsheet shows the conclusion, but not the product facts, legal authority, reasoning, reviewer, or effective date behind it. An invoice shows an amount charged, but may not establish whether additions to customs value were considered. A country printed on a document may not prove the origin rule was correctly applied.

When evidence is missing, the importer may be unable to answer a CBP request even if the original decision was sound. A defensible program therefore preserves both transaction records and the evidence supporting the customs determinations used in that transaction.

The conventional approach: keep the entry packet

Many importers retain an electronic packet containing the commercial invoice, packing list, bill of lading, arrival notice, entry summary, and broker statement. This is a useful foundation. It documents the shipment and what the broker filed.

Where recordkeeping breaks down

Records become fragmented when each function retains only its own artifact. Logistics keeps shipment documents. Finance keeps payments. Engineering keeps specifications. Sourcing keeps supplier correspondence. Trade compliance keeps HTS codes. The broker keeps its filing file. No one can reconstruct the full decision without asking several people to search several systems.

The key distinction: filing records versus decision evidence

Filing records show what happened at entry. Decision evidence shows why the information was considered accurate. An effective customs record contains both views.

For classification, the entry shows the declared HTS number. Decision evidence may include detailed product specifications, composition, function, drawings, explanatory notes considered, rulings, analysis, and approval. For valuation, the entry shows the declared value. Decision evidence may include purchase agreements, payment records, related-party analysis, assist data, royalty agreements, allocation methodology, and reconciliation support where applicable.

This distinction follows the broader principle described in What Is Import Compliance?: documents are evidence produced by an operating system, not the underlying truth by themselves.

A practical example: the product record that cannot be reproduced

An importer classifies a machine component using a detailed drawing and an engineer’s explanation of its function. The classification is approved and sent to the broker. Two years later, CBP asks for support. The current product database contains only a short description, the engineer has left, and the original drawing was overwritten when the part was revised.

The importer can produce the entry summary and invoice, but cannot demonstrate which version of the product was imported or why the classification was selected. The problem is not merely document retention. It is the absence of a version-controlled decision record connected to the imported SKU and effective period.

A practical customs-record framework

1. Entry and release records. Retain the entry data and documents needed to identify what was filed, including relevant entry summaries, release information, invoices, packing information, transportation records, permits, declarations, and broker communications.

2. Product and classification evidence. Preserve the product description, materials, composition, function, dimensions, manufacturing information, drawings, photographs, technical literature, classification analysis, rulings, reviewer, and effective dates that support the declared classification.

3. Valuation evidence. Keep purchase orders, invoices, contracts, payment records, price adjustments, related-party support, assists, royalties, proceeds, packing costs, commissions, freight allocations, and the reasoning used to determine customs value. The relevant set is transaction-specific.

4. Origin and preference evidence. Retain manufacturing facts, bills of material, supplier certifications, production records, origin analysis, certifications, and supporting calculations used for an origin, marking, or trade-program claim.

5. Admissibility and agency records. Preserve licenses, permits, registrations, test reports, declarations, certificates, and other records required by CBP or a partner government agency for the imported merchandise.

6. Broker governance records. Keep powers of attorney, approved instructions, broker profiles, data transmissions, questions, responses, corrections, service reviews, and evidence that the importer verified what was filed.

7. Control and remediation evidence. Retain procedures, training records, testing results, exception reports, investigations, corrective actions, approvals, and documentation of how recurring causes were addressed.

8. Retrieval metadata. Store the importer entity, entry number, SKU, supplier, broker, transaction date, effective period, record owner, and retention trigger needed to find and connect records. Good product and account master-data management makes evidence traceable to the decisions and entries it supports.

How long should customs records be retained?

19 C.F.R. Part 163 contains the principal CBP recordkeeping regulations. CBP’s current public guidance states that entry-summary records generally must be retained for five years from the date of entry or the activity that required creation of the record. However, the correct trigger and period can vary by record type, program, claim, transaction, or other agency requirement.

Importers should not convert “five years” into a universal deletion rule. Drawback, reconciliation, free-trade-agreement claims, litigation holds, audits, disclosures, partner-agency rules, and other circumstances may create different or longer needs. A qualified expert should approve the retention schedule and any destruction protocol.

How to make records audit-ready

Assign ownership. Identify who owns each record category and who is responsible for responding to CBP.

Capture evidence when the decision is made. Do not plan to reconstruct product facts, calculations, approvals, and advice years later.

Connect versions and effective dates. Preserve which product facts and customs determination applied to each transaction.

Test retrieval. Select an entry and require the team to reproduce the filing, supporting decisions, and source evidence within a defined time.

Control broker-held information. A broker’s copy does not eliminate the importer’s responsibility. Ensure records remain accessible if the relationship or system changes.

Protect integrity and access. Apply appropriate security, backup, change history, and access controls to electronic records while keeping them readable and producible.

Related questions

Are electronic customs records acceptable? Customs law recognizes electronically generated and machine-readable data, and Part 163 addresses alternative storage methods. The system must still preserve required information and support production in an acceptable form. Confirm technical requirements with an expert.

Can an importer rely on its broker to keep everything? No. Brokers maintain records under their own obligations, but the importer should control access to the evidence supporting its entries and decisions.

Should every email be retained? Retention should be based on content and applicable requirements, not the communication channel. Material facts, instructions, advice, approvals, and changes may need preservation even when communicated by email or chat.

Authoritative starting points

Statutory recordkeeping obligation: 19 U.S.C. § 1508.

CBP examination authority: 19 U.S.C. § 1509.

Recordkeeping regulations: 19 C.F.R. Part 163.

CBP guidance: Recordkeeping — What Every Member of the Trade Community Should Know About.

Keep the reasoning, not just the paperwork

The purpose of customs recordkeeping is not to accumulate files. It is to preserve an intelligible chain from business facts to customs decision to filed result. 3rdwave’s automated customs capabilities connect product, shipment, and customs information so evidence can remain attached to the transactions and determinations it supports.

This article provides general educational information and is not legal advice. Record requirements and retention periods are fact-specific and can vary by transaction, program, claim, agency, and procedural posture. Importers should obtain review from qualified customs counsel and other appropriate experts before adopting or changing a retention schedule or responding to CBP.