Inside a Formal Customs Entry: The Forms, the Data, and the Deadlines
When duty-free de minimis ended, it did more than add duty to low-value parcels. It pulled a whole category of trade into the formal entry process - the paperwork that, until recently, most e-commerce shipments never touched. A lot of teams now have to understand how a formal entry works, quickly.
So here is the anatomy of one, and why nearly every piece of it traces back to a document.
Two forms, one clock
A US import generally clears in two steps.
CBP Form 3461 - Entry/Immediate Delivery is the request to release the goods from CBP custody. It carries the essentials: the importer of record, a description of the goods, the port of entry, the mode of transport, and the bond covering the shipment. The mechanics live in 19 CFR Part 142.
CBP Form 7501 - Entry Summary is the detailed filing, due within 10 working days of release. It is where the full goods description, the HTS classification, the customs value, and the duties owed all have to be exactly right - see CBP’s 7501 form and instructions.
Release first, reconcile second - but the clock on the entry summary starts at release, and every number on it has to be defensible.
For ocean freight, the filing starts before the ship sails
If the goods move by sea, there is an earlier deadline that is easy to miss: the Importer Security Filing, better known as ISF “10+2.” The importer transmits 10 data elements to CBP and the carrier adds two more, and it has to be filed at least 24 hours before the cargo is loaded onto the vessel at the foreign port - measured against loading, not departure or arrival.
ISF has been mandatory since 26 January 2009 under the SAFE Port Act, and it applies to ocean shipments even when your cargo is a single pallet in a shared container. It also has teeth: CBP can assess liquidated damages of $5,000 per violation for a filing that is late, inaccurate, or incomplete (CBP’s ISF “10+2” program).
The bond and the responsibility
Every formal entry has to be backed by a customs bond - a guarantee that the duties, taxes, and fees will be paid. And the importer of record carries a legal duty of reasonable care: the classification, the valuation, and the declarations all have to be right, and “the broker handled it” does not transfer that responsibility.
That is what turns a volume problem into a compliance problem. More entries is not just more typing - it is more places to be wrong, each with a deadline and a penalty attached.
Why it comes down to your documents
Look at what those filings actually need: importer and goods details, an HTS code, a customs value, weights and quantities, party names and addresses, transport details. Now look at where that information lives - the commercial invoice, the packing list, the bill of lading, the certificate of origin. A formal entry is, in effect, those documents re-expressed as structured data that CBP will accept.
In the de minimis era, that translation barely had to happen. Now it has to happen for every shipment, accurately, against a deadline. Doing it by hand - reading each document, keying each field, checking that the invoice, packing list, and bill of lading agree - is exactly the work that buckles when entry volume jumps.
This is where a document layer earns its place. It does not file the entry for you, and it does not assume the importer’s reasonable-care duty. What it does is read the documents, pull the fields, recommend the HTS classification with the reasoning shown, check that the documents agree across the shipment, and surface only the values a person needs to confirm. The filing stays yours. The hours spent producing clean data for it do not have to.
The forms and the deadlines were always there. What changed is how many shipments have to run the gauntlet. The teams that keep up are the ones that turn the document-to-data step from manual work into something the documents largely do themselves.