Skip to content

The pre-transmission checklist for customs entry writers

9 min read

Ariel Serravalle

Ask entry writers which mistakes hurt most and the answers are rarely typos. One writer on r/CustomsBroker listed theirs: the wrong HTS or duty keyed, the wrong port, an entry transmitted without the in-bond, an entry transmitted with no ISF on file. All worse, they added, when you notice after the duty has been paid (thread).

Most of those are not keying errors. They are prerequisite failures: something that should have been true before anyone opened the entry screen, and wasn't. A checklist is the cheapest control against that kind of failure, because it runs at the one moment the mistake is still free to fix.

What follows is the one we would want pinned above every desk. It is written for the entry writer running it and for the LCB who owns the result. It doesn't replace your own procedures or your supervisor's judgement. It gives both a fixed order to work in, so that nothing gets skipped in a busy week.

How to use it

Run it on every entry, in order, before you transmit. The first four sections are about reading and comparing: does the packet exist, does it agree with itself, and are the prerequisites in place. The last three need judgement, and anything doubtful in them goes to the licensed broker, not back into the queue.

A new writer should run all seven sections out loud with a senior person for the first few weeks. An experienced writer on a repeat lane will get through it in a minute or two. Either way, the checklist only works if skipping a section is a decision someone makes on purpose.

1. Is the packet complete?

Before you key anything, confirm you have:

  • Commercial invoice, signed or otherwise final, not a proforma unless you have agreed to file on one
  • Packing list
  • Bill of lading (ocean) or air waybill (air)
  • Arrival notice from the carrier
  • Any certificates, permits or licences the goods or the trade programme need, such as a certificate of origin if you are claiming preference, or an agency permit

What the invoice itself must contain is set out in 19 CFR 141.86, and we go through it field by field in What 19 CFR 141.86 requires on a commercial invoice. At this step you only need to know the documents are all there.

2. Does the packet agree with itself?

The same shipment is described three or four times, by different people using different systems. Check that they agree on:

  • Quantity, by line and in total
  • Value, including that the line totals add up to the invoice total
  • Gross and net weight
  • Package count, across the invoice, packing list and B/L or AWB
  • Description and origin, line by line

Regulation 141.86(e) requires the invoice to state in adequate detail what merchandise is contained in each individual package, so a packing list that disagrees with the invoice is not a cosmetic problem. When the documents disagree, stop. What to do next (file, hold or go back to the client) is its own decision, covered in Invoice and packing list don't match? A broker's triage guide.

3. Are the parties right?

  • Importer of record number is the right one for this client
  • Ultimate consignee is correct, or correctly reported as the same as the IOR
  • Manufacturer or shipper is identified on the documents, with a real street address
  • MID can be built from that address, for every line that needs one

The manufacturer ID is reported on every entry summary on CBP Form 7501 (see CBP's Form 7501 page). When the invoice shows a trading company and no factory, flag it now rather than at keying. Building the code itself is covered in How to build an MID code from a commercial invoice.

4. Are the prerequisites on file?

  • ISF (ocean only): filed, and consistent with the invoice you now have, especially manufacturer, country of origin and HTS
  • In-bond: if the freight is moving in bond to another port, the in-bond is on file, and the entry is going in at the port of destination rather than the port of unlading
  • Bond: a continuous bond is active for this IOR, or a single transaction bond is arranged, and it looks sufficient for the value and duty on this entry

ISF elements have to be transmitted no later than 24 hours before the cargo is laden at the foreign port (19 CFR 149.2), so by entry time the question is whether the filing on record still matches the shipment. CBP's ISF mitigation guidelines describe liquidated damages of $5,000 per violation, and the common ISF mistakes are in ISF mistakes that cost $5,000. In-bond movements are governed by 19 CFR Part 18. The factors CBP weighs when it decides whether a bond is sufficient are listed in 19 CFR 113.13.

5. Do classification and value make sense?

This section is a sanity check, not a classification exercise.

  • The HTS number the importer supplied plausibly matches the description on the invoice
  • The HTS number matches the one used on the ISF and on previous entries of the same product, or there is a reason it changed
  • The value is consistent with previous shipments of the same goods, and any assists, royalties or other additions the client has told you about are accounted for
  • Anything that looks wrong is flagged for the LCB, with a note of what looked wrong

The importer of record is responsible for using reasonable care to enter, classify and value the goods under section 484 of the Tariff Act, and CBP's Reasonable Care publication explains that duty and sets out advisory questions for importers. The broker's own obligation is different: a licensed broker must exercise responsible supervision and control over the business done under the licence (19 CFR 111.28). For the entry writer, it means that a classification or value that looks wrong goes to the licence holder before transmission.

6. Does another agency have an interest?

Read the description once more, this time asking only one question: could any other agency regulate this?

  • Food, drugs, cosmetics, medical devices, or anything that touches food (FDA)
  • Chemicals, pesticides, engines or vehicles (EPA, and NHTSA for vehicles)
  • Plants, seeds, animal products or other agricultural goods (USDA)
  • Wildlife, fish, shells, leather from wild species (Fish and Wildlife Service)
  • Alcohol, tobacco, firearms or ammunition (TTB, ATF)
  • Consumer products, especially children's products (CPSC)

This is a list of prompts, not a guide to any agency's rules. A tick here means "the LCB looks at this before it goes", not "file the PGA data yourself". CBP keeps a list of partner government agency import guides to start from.

7. Are you inside the deadlines?

  • Entry within 15 calendar days of the goods landing, or of arrival at the port of destination for goods moved in bond (19 CFR 142.2)
  • Entry summary, with estimated duties, within 10 working days after entry, where it wasn't filed at the time of entry (19 CFR 142.12)

A late entry summary is not only an administrative miss. Under 19 CFR 142.15, the port director makes a demand for liquidated damages. If ACE rejects the entry summary, a different and shorter clock starts, covered in Entry summary rejected: the two-day clock.

For field-level detail on what goes where, CBP publishes ACE Entry Summary Instructions.

A worked example

The following is an invented example, with realistic but made-up details.

An ocean shipment of stainless kitchenware arrives at Long Beach for a client in Illinois, moving in bond to Chicago. The packet has a commercial invoice from a trading company in Ningbo, a packing list, a house bill of lading and an arrival notice. Running the checklist:

  • Section 1 passes. All four documents are there, and no certificates are needed because no preference is being claimed.
  • Section 2 stops the entry. The packing list shows a gross weight of 1,840 kg and the B/L shows 1,480 kg. The package counts agree, so a transposed figure is the likely cause. That is a question for the client, and a note for the file, before anyone keys a weight.
  • Section 3 finds a second problem. The invoice names only the trading company, so there is no factory address to build an MID from. The ISF, filed three weeks earlier, lists a manufacturer the invoice doesn't mention.
  • Section 4: the in-bond is on file to Chicago, so the entry goes in at Chicago, not Long Beach. The continuous bond is active.
  • Sections 5 and 6: the HTS supplied matches the description and previous entries. Nothing in the description points to another agency, and the writer notes that the question was asked.
  • Section 7: the goods are still at the port, so there is time to wait for answers without risking the 15-day entry deadline.

Two emails go to the client at 10am, one about the weight and one about the factory. The alternative was finding both at 4pm, halfway through keying.

When something slips through anyway

No checklist catches everything. If an error is found after the entry summary is accepted, the options (a post-summary correction, a protest or a prior disclosure) depend on timing and on what went wrong. The checklist's job is to make that conversation rarer.

The first four sections are reading and comparing. EntryWrite runs the ones that live in the packet when it arrives: whether the documents are all there, whether they agree with each other, and whether the manufacturer's name and address are good enough to build an MID. Whether the ISF, in-bond and bond are on file is a question for your filing system, and that, like sections 5 to 7, stays with the broker.