A rejected GMR is one of those small-sounding problems that turns out to have an outsized impact on a day's work. It costs the truck's slot, it stresses the driver, it creates a chain of phone calls — and if it happens at 23:30 on a Friday, it costs real money. Here are the five causes we actually see most often, with what you can do about each.
1. A declaration inside the GMR went into query
This is by far the most common cause and the one most often blamed on GVMS itself. The GMR doesn't fail because GVMS has a problem — it fails because one of the declarations that the GMR points to has gone into a query status on CDS and never got cleared.
HMRC sends queries for all sorts of reasons: commodity code mismatches, valuation questions, missing origin evidence, wrong procedure codes. If nobody picks up the query and responds, the declaration sits in limbo. GVMS does its check at the gate, sees the declaration is not in a clear state, and refuses the GMR.
What to do about it. Every declaration that goes into query should trigger an alert to somebody responsible. "No news is good news" is a dangerous assumption with CDS — no news more often means "someone needs to look at this".
2. The vehicle or trailer on the GMR is wrong
GMRs are paired to a specific vehicle registration and (where relevant) trailer ID. If the tractor that actually shows up at Dover has a different plate from the one on the GMR, the check fails. Likewise if the trailer ID has been typed with a zero instead of an O, or hyphens where there should be none.
This sounds trivial. It is the source of a shocking number of delays. Driver swaps, last-minute vehicle changes and lazy copy-paste from an old spreadsheet all cause it.
What to do about it. Confirm the actual vehicle and trailer within the last 60 minutes before the GMR is built. Make that a hard rule, not a "usually we check".
3. The export declaration arrived too early
Export declarations have a time window on them. If you pre-lodge a declaration five days before sailing and the truck then doesn't arrive at the expected port until a week later, the declaration may have timed out. HMRC treats it as "arrived but never physically moved" and flags the associated GMR.
This is more common in planned network moves where the declaration is built weeks ahead and then the operational schedule slips.
What to do about it. For long lead times, lodge the commercial documentation but delay the actual declaration submission until closer to the sailing — or be ready to re-lodge if the ferry is pushed back.
4. The EORI has gone stale
It happens more than you'd think: a business changes address, changes directors, or re-registers for VAT, and the EORI on file somewhere becomes inactive. A declaration that quotes that EORI will fail, and every GMR it's attached to will fail with it.
An EORI can also go stale on the GVMS side — if the account linking between your EORI and your GVMS login was never completed, or was severed when the portal was re-credentialed, CDS and GVMS will refuse to talk to each other.
What to do about it. Once a quarter, do a dry-run declaration on your main EORI to prove it's still active and linked. It's five minutes of work and it catches the problem before the next operational crisis.
5. The ENS (safety & security) reference wasn't paired
Since UK S&S went mandatory for EU imports, a GMR without a paired ENS reference can fail even when the commercial declaration is perfect. This is the newest of the five common causes and still catches fleets that were set up before ENS went live.
What to do about it. Treat ENS as part of the declaration package, not a bolt-on. Every GMR for a GB import from the EU should have the ENS reference visibly included at build time. If your GMR confirmation email from your broker doesn't list an ENS reference, that's the moment to ask why.
The meta-pattern
Four of the five causes above share a common thread: they aren't random, they aren't GVMS playing tricks, and they aren't bad luck. They're a process gap between the person who builds the declaration and the person who builds the GMR, or between the fleet office and the driver on the road.
Fixing a rejected GMR at the gate is stressful. Avoiding a rejected GMR is mostly about three things: building up the declaration early enough to absorb queries, checking vehicle and trailer details in the last hour, and making sure somebody with GVMS access is reachable when the truck moves.
A good customs partner will close all three gaps by making them part of the standard workflow. A less good one will tell you, afterwards, which one broke.