eManifest Rejected: Troubleshooting ACE/ACI Errors Fast

The confirmation email you were waiting for comes back with one word that ruins the schedule: rejected. Whether it's ACE for a US-bound load or ACI for a Canada-bound one, an eManifest rejection means the truck cannot legally proceed to the border until it's fixed and resubmitted — and the driver may already be twenty minutes out. Here's how to read the rejection fast, fix the actual field that's wrong, and get a clean filing back before the truck reaches the line.

Why Did the eManifest Get Rejected?

Rejections happen when the data submitted doesn't match what CBP or CBSA's system expects — either because a field is wrong, missing, or inconsistent with another linked filing (like the PARS/PAPS entry from the customs broker). The system checks aren't subjective; every rejection ties to a specific validation rule, which means every rejection has a specific, findable fix. The trick is reading the rejection code correctly instead of guessing at what might be wrong.

It helps to think of the eManifest system as running two categories of check. The first is internal consistency — does this filing make sense on its own, with all required fields present and formatted correctly. The second is cross-reference consistency — does this filing match up with everything else already in the system tied to the same trip, particularly the broker's PARS or PAPS entry. Most quick fixes are internal-consistency errors; most stubborn, repeat rejections are cross-reference errors that require a second party to correct their side before the carrier's filing can ever be accepted.

How to Read a Rejection Code

Both ACE and ACI return a rejection with a reason code and a short description pointing to the specific data element that failed validation. Resist the urge to skim past this and just resubmit — refiling without fixing the actual flagged field produces the same rejection again, burning more time. Pull up the original submission next to the rejection notice and locate the exact field named in the code before touching anything.

The Most Common ACE Rejection Reasons

• PAPS number not matching a customs entry the broker has on file — either it wasn't filed yet, or there's a digit mismatch
• Carrier SCAC code error — entered incorrectly or not recognized as active for that filing
• Conveyance data mismatch — truck or trailer plate entered in the wrong format, missing jurisdiction, or simply mistyped
• Port of arrival code incorrect — the filing references a different crossing than the one the truck is actually approaching
• Driver information error — name spelled differently than on the passport or FAST card, or a missing date of birth
• Missing or vague cargo description that doesn't meet the minimum specificity CBP requires

The Most Common ACI Rejection Reasons

• PARS number mismatch with the broker's filed entry — the mirror issue to the PAPS problem on the ACE side
• Carrier code not recognized or not associated with the account filing the eManifest
• Trip or conveyance data incomplete — a required field left blank during data entry
• Seal number formatting errors if the trailer is sealed and the number doesn't match the expected pattern
• Weight or quantity fields that are missing or implausible for the declared commodity

Step-by-Step: Fixing and Refiling

1. Read the exact rejection code and field name — not just "rejected," the specific reason
2. Cross-check that field against source documents — the bill of lading, the driver's passport, the broker's PARS/PAPS confirmation
3. Correct only the flagged field in the filing software or portal — changing unrelated fields risks introducing a new error
4. If the issue is a PARS/PAPS mismatch, call the broker to confirm the correct number before resubmitting, rather than guessing at a fix
5. Resubmit and wait for confirmation — most systems return an accept/reject response within minutes
6. Text or call the driver with the new confirmation once accepted, so they aren't relying on a filing that's already been superseded

How Fast Can You Refile Before the Driver Arrives?

If the rejection is caught the moment it happens and the fix is a simple field correction, resubmission and re-acceptance typically takes 5–15 minutes. This is exactly why filing the eManifest 2–3 hours before arrival — rather than the bare 1-hour minimum — matters so much: it builds in a buffer to catch and fix a rejection before the truck is anywhere near the booth. A rejection caught with the driver still 45 minutes out is a non-event. The same rejection discovered as the driver pulls up to primary turns into a real delay while everyone scrambles.

The math here is worth spelling out for anyone tempted to file right at the one-hour minimum to save time. Filing at the minimum means a rejection leaves almost no buffer to fix and resubmit before the truck arrives — the driver ends up idling at or near the port while dispatch works the phones. Filing three hours out costs nothing extra in effort and turns the exact same rejection into a problem that gets solved calmly, well before the truck is anywhere close to the line.

What If the Rejection Keeps Recurring?

A rejection that comes back after a correction usually means one of two things: the wrong field was corrected (the code pointed to something more specific than what got changed), or there's an upstream data problem — for example, the broker's PARS filing itself contains an error, so no PAPS/PARS number the carrier enters will ever match until the broker fixes their side. When a second rejection hits, escalate immediately: call the software provider's support line if it's a filing-platform issue, or get the broker on a three-way call with dispatch so both sides are looking at the same numbers in real time instead of relaying corrections back and forth by phone.

A third, less common but worth knowing about, is a genuine system-side lag — the correction was accepted but hasn't fully propagated through CBP or CBSA's backend yet. This looks identical to a real rejection from the filer's side, which is why it's worth waiting 10–15 minutes and resubmitting once cleanly before assuming the fix itself was wrong and starting to change fields that were already correct.

How to Stop Rejections From Happening in the First Place

• Confirm the PARS/PAPS number with the broker directly before entering it into the eManifest — don't rely on a number relayed secondhand from the shipper
• Double-check driver names against the passport or FAST card character for character, including middle names and suffixes
• File with a real buffer — 2–3 hours before arrival, not the bare legal minimum
• Use specific, detailed cargo descriptions on every filing, not generic terms that increase both rejection risk and secondary inspection odds
• Keep a saved template of correct conveyance data (SCAC, standard plate formats) to reduce manual entry errors on routine lanes

For carriers running the same lanes repeatedly, most eManifest software allows saved profiles for recurring drivers, trucks, and trailers, which removes a large share of manual re-entry and the transposition errors that come with it. The one-time setup cost pays back quickly on any lane run more than a few times a month, since the carrier stops re-typing the same conveyance data — and re-risking the same typo — on every single filing.

The full mechanics of lead times, required fields, and the PARS/PAPS linkage are covered in more depth in our ACE & ACI eManifest guide — worth reviewing alongside this one, since most rejections trace back to a gap in exactly those steps. Keeping the full document packet consistent across every filing is the single best prevention against repeat rejections.

An eManifest rejection is almost always fixable in minutes when someone catches it early and knows exactly which field to correct. A dispatcher who owns this process end to end — filing early, reading rejection codes correctly, and confirming PARS/PAPS with the broker before submission — is the difference between a five-minute fix and a truck sitting at the border. Get dispatched with TRUCC for a desk that treats eManifest accuracy as core to the job.