A retention table for 19 CFR part 163 needs more than one start date, and a schema that stores only an entry date will misclassify every packing list in the system.
The problem is that the regulation states several different clocks. Under 19 CFR 163.4(a), a record required to be made, kept, and rendered for examination and inspection by Customs is kept for 5 years from the date of entry if the record relates to an entry, or 5 years from the date of the activity which required creation of the record. Those are two distinct start events, and the second one is not a fallback for the first. Paragraph (b) then carves out exceptions with their own anchors. Records behind a drawback claim survive until the third anniversary of payment. Packing lists run 60 calendar days past the close of the release or conditional release period, or past whichever of those dates lands later, and a second 60-day clock attaches to redelivery where Customs has demanded the goods back. Where the consignee is neither owner nor purchaser but names a customs broker, that consignee keeps a record pertaining to an informal-entry record, which runs 2 years from that entry date.
A single entry_date + 5 years column cannot express any of that. The table has to carry the anchor as data.
record_row:
record_id
record_type # entry record, packing list, drawback record, informal entry record
obligated_party # person described in 19 CFR 163.2(a)
obligation_basis # 163.4(a) entry / 163.4(a) activity / 163.4(b)(1) / (b)(2) / (b)(3)
start_event_type # entry, activity, claim payment, release end, redelivery demand, informal entry
start_event_date
retention_rule_id
computed_expiry
storage_form # original, or alternative under 19 CFR 163.5(b)
alt_storage_notice_date
alt_storage_ack
demand_received_at
production_due_at
The storage fields are not decoration. Under 19 CFR 163.5(a), records must be maintained as original records, whether paper or electronic, unless alternative storage methods have been adopted under paragraph (b), and must be capable of being retrieved upon lawful request or demand by CBP. Paragraph (b)(1) allows an alternative format only where advance written notification goes to Regulatory Audit at least 30 calendar days before implementation. A row that says "stored electronically" without the notice date and the acknowledgment is a row that cannot answer the retrieval question. Record the notice date and confirm whether any written instruction against alternative storage was received.
The delivery clock belongs in the same row. Under 19 CFR 163.6(a), entry records a Customs officer demands have to be handed over within 30 calendar days after that demand arrives, or faster when Customs sets a shorter window because the records bear on admissibility or release. A request for additional time must be received before the applicable due date and must explain the circumstances. So production_due_at is derived from demand_received_at plus the demanded period, and the shortened case has to be representable. Agree with the obligated party who computes that field and record the basis used.
Two modeling mistakes recur.
The first is collapsing everything into entry plus 5 years. That rule is correct for records that relate to an entry and wrong for records keyed to an activity, to a drawback payment, to the end of a release period, or to an informal entry. The failure is quiet, because the row still has a date in it. Consider splitting retention_rule_id into a closed enumeration and refusing to write a row whose rule does not match its start_event_type. Confirm the enumeration against the paragraph text rather than against a prior system.
The second is treating "we can produce it" as authority to decide what the importer keeps. The duty in 19 CFR 163.2(a) attaches to the persons listed there, including the owner, the importer, the consignee, the party entered as importer of record, entry filers, anyone else who imports merchandise, files a drawback claim, or moves or stores merchandise held under bond, plus their agents and anyone whose activities require filing a declaration or entry. A fulfillment operator holding copies of documents is not thereby the party that decides retention scope for someone else. Record who the obligated party is on each row and agree in writing which party owns which record class. Where a party wants to rely on the voluntary Recordkeeping Compliance Program in 19 CFR 163.12, note that certification is a matter between that party and CBP and that certification leaves CBP free to compel records by summons, court order or another legal process.
Engineers should treat 19 CFR 163.6 delivery as a service level field, not as a deletion policy. Deletion answers "when do we drop this." Production answers "how fast can we hand it over when demanded." Those are different columns with different owners. Keep computed_expiry immutable once written, keep demand_received_at append-only, and agree with the obligated party how a shortened production period is flagged and escalated. Confirm that a record marked for alternative storage can still be retrieved in the original format within the demanded window, and record the result of that check rather than assuming it.
Nothing here determines whether a given record is required, and no table design settles an enforcement outcome. The schema exists so that the anchor, the party, and the clock are visible on the same row.
FulfillNexa by SBT (fulfillnexa.com) works from a data layer of inbound and outbound event rows across 24,000 square meters in China. Suzhou carries 13,000 of that for consolidating East China suppliers, Dongguan 8,000 for ecommerce stock and per-order picking with apparel and toys in scope, and Shenzhen 3,000 for oversized freight on sea-air and air-sea legs. The records described in 19 CFR part 163 belong to the persons named in the regulation. We supply the layer where reconciliation can happen and do not replace anyone's recordkeeping obligation.
Top comments (0)