Every PAPS shipment has a story that's supposed to be told twice — once by the carrier, once by the broker — and both versions need to match before the driver ever sees the primary booth. The Pre-Arrival Processing System (PAPS) is CBP's default clearance path for commercial highway freight entering the U.S., and on paper it's simple: the carrier assigns a number, the broker files an entry against it, CBP accepts the entry, and the truck rolls through in minutes. In practice, that three-way handoff is where most avoidable border delays actually happen.
This isn't a "what is PAPS" primer. It's about the coordination problem sitting underneath it: getting the PAPS number to the broker with enough lead time, making sure that number matches the ACE eManifest character-for-character, and confirming CBP has actually accepted the entry before dispatch sends the driver toward the line. Get that sequence right and a PAPS release is one of the most boring, predictable parts of the trip. Get it wrong, and you've got a tractor idling at the booth while three people scramble to figure out whose paperwork is missing.
1) PAPS in one paragraph — and why it's a three-party handoff
PAPS is the process CBP built so that commercial highway freight can be reviewed before it reaches the border, instead of holding trucks at the booth while paperwork gets sorted out. The broker files a formal customs entry ahead of arrival, referencing a PAPS number that the carrier generated for that shipment. When the entry is on file and CBP has reviewed it, the officer at primary can pull it up in seconds and release the truck.
The part that gets lost in most explainer content is that PAPS isn't a document — it's a handoff between three parties, and each one has a distinct job:
- The carrier assigns the PAPS number and transmits the ACE eManifest that references it.
- The broker receives that exact number (usually via the commercial invoice or BOL) and files the formal entry against it.
- CBP matches the broker's entry to the carrier's eManifest and either accepts it — clearing the way for release — or flags it for review.
If any one of those three legs is late, mismatched, or missing, the chain breaks — and the truck waits at the booth while people figure out why the officer's screen doesn't show what the driver's paperwork says.
2) Anatomy of a PAPS number: SCAC + control number
A PAPS number always starts with the carrier's SCAC — the Standard Carrier Alpha Code, a four-letter identifier issued by the National Motor Freight Traffic Association (NMFTA) — followed by a unique shipment or control number, typically numeric, for a total length of up to roughly 16 characters. The SCAC is non-negotiable: it's the first thing CBP and the broker's system check, because it identifies which carrier's eManifest the entry needs to match against.
Why this structure matters for coordination
Because the SCAC is fixed and only the control number portion changes shipment to shipment, most of the errors we see aren't in the SCAC — they're in the control number. A transposed digit, a dropped leading zero, or a number that was reused from a prior load will all produce the same result: the broker's filed entry doesn't line up with the carrier's ACE eManifest, and CBP has nothing to accept.
3) Getting the PAPS number to the broker early
The single biggest lever carriers have over their own border wait times is lead time to the broker. The PAPS number and the commercial invoice or BOL it appears on need to reach the broker with enough runway to file the entry, get it reviewed, and get it accepted — all before the truck is anywhere near the line.
"Early" in practice usually means as soon as the load is booked and the paperwork is final, not when the driver is already en route. Brokers can't file an entry against a number they don't have yet, and a broker racing a filing deadline is a broker who's far more likely to make a data-entry mistake under pressure.
What "early enough" looks like operationally
- PAPS number assigned and documents finalized before the driver is dispatched — not after
- Broker has the invoice/BOL with the PAPS barcode in hand well ahead of the carrier's own ACE eManifest transmission window
- Dispatch has a single point of contact confirming "broker has it" rather than assuming email delivery equals receipt
4) Format discipline: why "close enough" paperwork gets rejected
Brokers process huge volumes of PAPS paperwork every day, often through semi-automated intake systems, and many of them are strict about submission format for exactly that reason. It's common for a brokerage to require one PRO or shipment per email, a subject line that's just the PRO number with no spaces or dashes, and a single clean PDF attachment rather than a scanned stack of unrelated paperwork. Think of Estes-style broker submission rules as a representative example — the details vary by broker, but the underlying principle doesn't: format inconsistency creates manual sorting on the broker's end, and manual sorting is where numbers get mistyped or documents get matched to the wrong file.
Ask your broker directly what their submission format requirements are and build your paperwork process around them. It's a five-minute conversation that prevents hours of delay later.
5) Matching the PAPS number to the ACE eManifest
Once the broker has the PAPS number, the next coordination point is making sure it matches — exactly — the number referenced in the carrier's ACE eManifest. CBP's system is looking for that match to connect the broker's filed entry to the carrier's advance conveyance data. If the two don't line up character-for-character, CBP has an entry on one side and a manifest on the other, with no way to automatically connect them.
Common mismatch scenarios
- Broker files against a PAPS number that was updated or corrected after the fact, but the eManifest still shows the old one
- SCAC on the entry doesn't match the SCAC on the eManifest (can happen with interline moves or co-broker arrangements)
- A typo introduced when the number was manually retyped instead of copied from the source document
The fix is almost always procedural rather than technical: whoever assigns the PAPS number should be the single source of truth for it, and every downstream party — broker, dispatch, driver — should be pulling that number from the same document rather than re-keying it independently.
6) The 1-hour rule and why timing math matters
For standard highway shipments, the carrier's ACE eManifest needs to be transmitted at least one hour before arrival at the border — filed either through a service provider (BorderConnect is a commonly used example) or directly via the ACE Secure Data Portal. That one-hour window is the outer limit, not a comfortable planning number, because it doesn't account for the broker's own filing time or CBP's review time on top of it.
Carriers running tight schedules sometimes treat the one-hour rule as the moment to start the process instead of the deadline to finish it. That's backwards, and it's one of the most common reasons a truck arrives at a booth with an entry that's still "in progress."
7) Confirming CBP ACCEPTED the entry before dispatch
This is the step that separates carriers who rarely get held from carriers who get held constantly: checking the PAPS status before the driver is sent toward the border, not after. Brokers — C.H. Robinson is one commonly referenced example — and many carrier software platforms offer a PAPS tracker or status lookup that shows exactly where an entry stands.
The status that matters is "accepted," not "submitted"
"Submitted" only means the broker sent the filing into the system. It does not mean CBP has reviewed or cleared it. "Accepted" means CBP has matched the entry to the eManifest and it's ready for release at the booth. Dispatching a driver on a "submitted" status alone is a gamble — sometimes it works out, and sometimes the driver arrives to an entry that's still pending or has been flagged.
8) What actually breaks the handoff
Most PAPS delays trace back to a small, repeatable list of failure points rather than anything exotic:
- The broker didn't receive the documents early enough to file before the truck's arrival window
- The broker filed against a different or mistyped PAPS number than the one on the carrier's eManifest
- SCAC mismatch between the entry and the eManifest
- A PAPS number was reused across shipments instead of being unique per load
- Documents arrived late, in the wrong format, or bundled in a way the broker's intake process couldn't parse cleanly
- The driver was dispatched before anyone confirmed the entry status had moved from "submitted" to "accepted"
Notice that none of these are CBP being unpredictable — they're upstream coordination gaps between carrier, broker, and shipper that show up as a CBP delay only because that's where the truck happens to be sitting when the mismatch gets discovered.
9) The cost of a broken handoff
When the handoff breaks, the consequences aren't limited to a few extra minutes. A truck with no accepted entry on file can sit at primary while the broker scrambles to refile, get referred to secondary for manual review, or in some cases be directed to move in-bond to a bonded facility further inland before the entry issue gets resolved. Any of those outcomes can blow a delivery appointment window, tie up equipment for hours, and create a domino effect for the next load that tractor was supposed to run.
Compare that to a clean handoff: PAPS number assigned early, broker has it in the right format well ahead of time, eManifest matches exactly, status confirmed "accepted" before dispatch — and the booth interaction is a scan and a wave-through, often in minutes. The difference between those two outcomes is almost never about the freight itself. It's about whether three parties were looking at the same number at the same time.
10) 2026 ACE/CAPE modernization — what carriers should check
CBP has been modernizing the ACE portal through 2026, including interface updates, faster status responses, and rebuilt reporting tools, alongside the rollout of CAPE Phase 1 (April 20, 2026) inside ACE for entry processing and duty refund functions. None of this changes the fundamentals of PAPS coordination, but it does mean brokers need to be operating on the current ACE schema, and carriers should double-check that their eManifest filing software or service provider is up to date so transmissions aren't rejected on a technical formatting issue rather than a genuine data problem.
It's also worth remembering that CBP and ACE do experience occasional outages, and during those windows carriers fall back to contingency procedures. Pre-printed, scannable paperwork still matters in exactly those moments — a barcode on paper doesn't depend on system uptime.
11) PAPS barcode labels: rolls, sheets, and PARS/PAPS combos
Direct thermal, Code 39 barcodes sized for fast, reliable scanning at the primary booth — built for carriers running PAPS shipments daily.
- Roll format for print-on-demand label printers on high-volume lanes
- Clean barcode contrast that scans quickly even in a rushed booth interaction
Shop the PAPS barcode labels (rolls).
Rolls aren't the only format that makes sense depending on how your operation runs. If you print occasionally rather than on a dedicated label printer, PAPS labels in sheet format work with a standard office printer. For lanes where a load might release under either program depending on the broker's strategy, a combined PARS/PAPS label roll combo or the equivalent PARS/PAPS combo in sheet form keeps both barcode types on hand without stocking two separate products.
If PAPS labels are a recurring need across your fleet, the full PAPS labels collection shows every format side by side so you can match supply to how your dispatch team actually works.
It's worth keeping the bigger picture in view too: PAPS and PARS solve the same coordination problem for two different directions of travel — PAPS for U.S.-bound freight, PARS for Canada-bound freight — and both depend on the carrier's advance electronic manifest (ACE on the U.S. side) being filed on time and matched correctly by the broker. The barcode label itself is a small piece of that system, but it's the piece that makes the number fast to scan and hard to mistype once it's in the driver's hands.
Related reading:
- PAPS barcode labels explained (the fundamentals)
- PARS rejections explained (avoiding re-labeling and delays)
12) FAQ
Why is my PAPS shipment held at the border?
In most cases it's a coordination gap rather than anything wrong with the freight itself: the broker didn't receive the PAPS number early enough to file, the number on the entry doesn't match the carrier's ACE eManifest, or the driver was dispatched before CBP had actually accepted the entry. Confirming an "accepted" status before the truck leaves is the single best way to avoid this.
How early should the broker get my PAPS number?
As early as the shipment and paperwork are finalized — ideally well before the driver is dispatched, and with enough runway for the broker to file and for CBP to review before the carrier's ACE eManifest transmission deadline (at least one hour before arrival for standard highway shipments). Waiting until the truck is en route leaves little margin for corrections.
Is a PAPS barcode sticker required?
A barcode sticker itself isn't a government mandate. What CBP requires is advance ACE data tied to a valid SCAC and control number that the broker can file an entry against. Barcode labels simply make that number fast and accurate to scan and reference throughout the trip, reducing the manual re-keying that causes mismatches.
Authority references: U.S. Customs and Border Protection (CBP) — ACE / PAPS. Broker submission format practices referenced generically; confirm current requirements directly with your broker.