A shipment can clear the border in minutes and still create exposure for five years. That is the operational reality behind this CBP recordkeeping requirements guide. If CBP asks how merchandise was classified, valued, originated, or entered, the answer cannot live in a former employee's inbox, a broker's shared drive, and three versions of an invoice.
For importers moving freight through the US-Mexico corridor, recordkeeping is not back-office administration. It is the control layer behind compliant entries, accurate duty payments, defensible origin claims, and fast responses when Customs asks questions. The goal is not to save every attachment forever. It is to build a complete, retrievable record that ties the commercial transaction to the customs declaration.
What CBP Requires Importers to Keep
Under CBP's recordkeeping rules, importers must maintain records required for entry for five years from the date of entry. That period applies whether records are created on paper, received by email, stored in a transportation management system, or maintained by a customs broker. The importer of record remains responsible for producing required records when CBP makes a lawful demand.
The practical test is simple: could this document support or explain a data element reported to CBP? If the answer is yes, it belongs in the import file. Records may include source documents, data files, correspondence, calculations, and reports used to prepare or validate the entry.
CBP generally permits electronic recordkeeping, but digital storage needs to be more than a folder full of scans. Records must remain accurate, legible, complete, and capable of being produced in a usable form. A blurry invoice image or an export from a system no one can access is not a workable compliance process.
The core entry file
A defensible file starts with the commercial and transport documents: commercial invoice, packing list, bill of lading or airway bill, purchase order, arrival data, and delivery records. These documents establish what moved, who sold it, who bought it, quantities, shipment terms, and the path of the freight.
Then preserve the customs support behind the declaration. That commonly includes the HTS classification analysis, country of origin support, declared value calculations, assists, royalties, commissions, freight and insurance treatment, and any antidumping, countervailing, quota, or partner government agency requirements that apply.
The entry package itself matters just as much. Retain the entry and entry summary data, CBP messages, payment or statement information, liquidation notices, protests when applicable, and post-entry corrections. If the entry was changed after release, keep both the reason for the change and the evidence supporting it.
CBP Recordkeeping Requirements Guide: What Changes by Shipment
Not every import has the same documentation burden. A low-value replenishment shipment and a high-value automotive component program may both require entry records, but the risk drivers are different. Your retention process should reflect the transaction, not force every shipment into a generic checklist.
For USMCA claims, retain the certification of origin or the records supporting the claim, including production information where needed. A supplier statement alone may not answer every question. If eligibility depends on tariff shift, regional value content, or component origin, preserve the analysis and supplier support used to reach the conclusion.
For related-party transactions, valuation documentation deserves closer attention. Keep transfer-pricing materials, intercompany agreements, price lists, proof of payment, and documentation showing whether the relationship influenced the price. CBP valuation reviews often turn on the business facts behind the invoice, not the invoice alone.
For goods that require licenses, permits, test reports, or agency filings, keep the approval and the product-level connection to the imported goods. A general certificate stored outside the shipment file can be difficult to defend if the part number, lot, model, or importer data does not clearly match.
Imports arriving by ocean trigger separate Importer Security Filing obligations. ISF records should be maintained for five years from the date of importation. Do not assume the entry file alone proves ISF compliance. The filing data, submission confirmation, and supporting source records should be recoverable together.
Your Broker Has Records. You Still Need Control.
A licensed customs broker maintains its own required records, but that does not transfer the importer's recordkeeping obligation. This gap becomes visible when an importer changes brokers, a provider's retention period ends, or a review requires commercial records the broker never received.
The better operating model is shared visibility with a defined system of record. The importer should be able to retrieve the source documents, customs data, broker communications, and final entry package without opening a ticket and waiting days for a response.
That does not mean every shipper needs a major platform rollout. It means the workflow needs an owner. Documents received from vendors, carriers, warehouses, and brokers should be indexed to a common shipment identifier, purchase order, commercial invoice number, and entry number where available. Those reference points make a document request a retrieval task instead of an investigation.
For high-volume US-Mexico freight, this matters at the handoffs. A truck may move from a Mexican plant to a Laredo crossing, through US entry, then to a domestic distribution center under separate operational teams. The commercial documents, broker data, crossing information, and proof of delivery must remain connected even when different parties touch the move.
Build a Recordkeeping Workflow That Holds Up
Start at document intake, not after entry summary. Require suppliers to send commercial invoices and packing lists in a consistent format before freight reaches the border. Validate basic fields early: seller, buyer, importer of record, currency, Incoterms, quantity, part number, description, country of origin, and unit value. Missing or conflicting data should be resolved before it becomes entry data.
Next, separate source documents from derived customs decisions. An invoice is the source. An HTS classification worksheet, ruling, or broker instruction is the decision support. Both matter, but they should not be confused. When CBP asks why an item was classified a certain way, the team needs the reasoning, not just the ten-digit number on an entry.
Create a controlled exception process. If a vendor description is vague, an origin statement conflicts with prior shipments, or a value changes unexpectedly, capture the resolution in writing. A short documented decision at the time of entry is far stronger than a reconstructed explanation two years later.
Finally, test retrieval. Select a sample of entries each quarter and ask the same questions CBP might ask: Can the team produce the invoice, packing list, bill of lading, classification support, origin support, entry summary, and proof of duty payment? Can it do so quickly, with a clear chain from shipment to declaration? If the answer is no, the process is not yet under control.
Common Failures That Create Avoidable Exposure
The most common failure is treating the broker's entry data as the complete record. Entry data is only the reported outcome. It may not contain purchase orders, supplier communications, assist calculations, origin analyses, or other source evidence needed to support that outcome.
Another failure is relying on email as the archive. Email is useful for intake, but it is a poor compliance repository when documents are scattered across individuals, attachments are renamed, and old accounts are disabled. The same problem appears when files are saved by date alone rather than by shipment and entry reference.
Teams also underestimate changes. A new supplier, revised bill of materials, changed Incoterm, new tooling arrangement, or price adjustment can alter customs treatment without changing the physical product. Recordkeeping should capture those commercial changes before they create repeat-entry errors.
Penalties for recordkeeping violations can be significant, and CBP can assess them separately from duty loss issues. More immediately, weak records slow responses, extend audits, and force operations teams to spend days reconstructing shipments that should be visible in minutes.
A controlled recordkeeping process gives customs, transportation, and finance teams the same operational truth. Keep the evidence close to the entry, preserve the decisions behind the data, and make every file retrievable before CBP has to ask.