Reasonable care: making your customs data defensible
The importer has a legal duty of reasonable care in classification, valuation, and declarations, and must keep the records to prove it. Why that turns data quality into defensible compliance.
Key takeaways
- Under reasonable care, the importer is legally responsible for correct classification, valuation, and declarations, CBP informs, but the importer must get it right.
- Importers must keep import records, generally for five years, and be able to produce them.
- That turns data quality into legal exposure: error rates and undocumented decisions are compliance risks, not just inefficiencies.
- An audit trail that ties every number back to its source is what makes a position defensible.
- The same analytics that model duty can measure compliance health: error rates, corrections, and documentation coverage.
Customs law puts the responsibility for getting imports right on the importer, not the broker and not CBP. Under reasonable care, you must classify, value, and declare correctly, and you must keep the records to prove you did. That single principle changes what data quality means: a wrong number is not just an inefficiency, it is a potential failure of a legal duty. The defense is not perfection; it is being able to show the care you took, from every declared figure back to its source.
Reasonable care is a legal duty
The reasonable-care standard makes the importer of record responsible for correct declarations. CBP informs and issues rulings, but the obligation to get classification, valuation, and declarations right sits with you. That matters most when something is wrong: CBP judges whether an error reflected reasonable care or a failure of it, and that judgment affects the consequences. An honest mistake inside a careful process is treated differently from a pattern of errors with no process behind it.
The record is part of the requirement
Being right is not sufficient; you also have to be able to show how you got there. Importers must keep their import records, generally for five years, and produce them on request. That includes the documentation behind the decisions, the basis for a classification, the build-up of a customs value, not just the entry forms. A correct declaration with no supporting record is weaker than it looks, because the requirement is both the right answer and the ability to demonstrate it. Recordkeeping completeness is itself something an audit checks.
Data quality becomes legal exposure
Once correctness and documentation are legal obligations, data quality stops being an operational nicety. A high classification error rate, frequent post-summary corrections, inconsistent valuations, and decisions with no recorded rationale are not just messy, they are the signals that reasonable care may not be met, and they are precisely what an audit probes. The same errors that quietly cost duty also create compliance risk, which means cleaning them up pays twice: lower duty leakage and lower exposure.
An audit trail is the defense
What makes a position defensible is lineage: the ability to trace every declared number back to the data and the decision behind it. When an auditor or a regulator asks why a good was classified or valued as it was, the answer should come from a record, not a memory. An audit trail that ties each entry to its source data and its documented rationale turns a question into a report. That traceability is the practical form reasonable care takes: not a claim that you were careful, but evidence of it.
Measuring compliance health is analytics
The signals of reasonable care are measurable. Classification error and correction rates, valuation consistency, screening coverage, and documentation completeness are all views over the import data, the same data the analytics already use to model duty. Tracking them turns compliance health from an annual scramble before an audit into a number you watch, and keeping the lineage intact means the audit trail is a byproduct of the analytics, not a separate project. Reasonable care, measured, is just good data discipline with legal weight behind it.
If an audit asked you to justify a classification or a value, the question is whether you could answer from a record. Tell us how your compliance data is kept, or read how we handle security and your tenant.
Frequently asked questions
What does 'reasonable care' mean in customs?
Reasonable care is the legal standard, established by the Customs Modernization Act, that puts responsibility for correct import declarations on the importer of record. CBP provides information and rulings, but the importer must use reasonable care to classify goods correctly, value them correctly, and declare them accurately. It is not a vague aspiration; it is the duty against which CBP judges whether errors were honest mistakes or a failure to take the care the law requires, which affects whether and how they are penalized.
What records does an importer have to keep?
Importers must keep the records that support their entries, generally for five years from the date of entry, and be able to produce them if CBP asks. That includes the documentation behind classification and valuation decisions, not just the entry itself. The practical implication is that a correct number is not enough; you also need to be able to show how you arrived at it. Recordkeeping completeness, whether the supporting documentation actually exists and is findable, is itself auditable.
How does reasonable care relate to data quality?
Directly. If classification and valuation are legal responsibilities and must be documented, then the quality of that data is a compliance matter, not just an operational one. High error rates, frequent post-summary corrections, and decisions with no recorded rationale are all signs that reasonable care may not be met, and they are exactly what an audit examines. Measuring those, and keeping an audit trail from every declared number back to its source, is how an importer demonstrates the care the law requires.