Driving Licence Issue Number UK Explained

The driving licence issue number UK is a separate two-digit version counter on the photocard, and it increases by one every time DVLA issues a new card. It is not part of the 16-character driver number.

That distinction sounds small until you're staring at a licence scan in a fleet system, the driver has just renewed after moving house, and the record won't match what the verifier expects. In compliance work, that's usually where the admin headache starts.

Table of Contents

• What the Driving Licence Issue Number Is
  • Why this matters in practice
• Where to Find the Issue Number on Your Photocard
  • A simple reading order
• Common Mistakes That Break Licence Verification
  • Where fleets go wrong
• Great Britain vs Northern Ireland Licence Formats
  • The jurisdiction split that trips teams up
• How to Verify a Driver Licence Using GOV.UK
  • The practical workflow
  • What usually breaks the check
• Building a Reliable Licence Check Workflow
  • What to store and when

What the Driving Licence Issue Number Is

A transport manager can enter the right name and the right driver number, then still get a failed match if the issue number has been treated like part of the identity. That is the common trap in fleet admin. The issue number is a version marker, not a person marker, and DVLA uses it to show the latest card version rather than to identify the driver, as explained in Northern Ireland's photocard guidance.

The underlying driver record stays with the person, while the issue number changes when the card changes. That covers renewal, replacement, and updates to details, so a licence can look different on paper without being a different licence in operational terms. GOV.UK's live licence service also shows that online checks key off the driver number, National Insurance number, and postcode, which is a clear reminder that the issue number sits outside the main identity fields. See the official view driving licence service.

Why this matters in practice

If your team stores the issue number in the wrong field, the problem goes beyond tidy records. A mismatched version can make a valid driver look unverified, especially when the workflow assumes every card should carry the same sequence forever. DVLA guidance in the INS57P licence information PDF says the issue number is separate from the 16-character driver number and should be treated as a version marker in verification workflows.

For GB and NI fleets, that distinction matters even more because admins often compare a photocard from one jurisdiction with a record built from another. The printed card can change, the person does not, and the verification step has to follow the card version rather than guess from appearance. Keep the driver number and the issue number in separate fields, then verify through GOV.UK instead of trying to infer identity from the printed sequence alone.

That is the operational reason this two-digit field matters. It tells you which physical card version you are holding, and nothing more. If your workflow treats it as identity data, you are setting yourself up for false mismatches, stale records, and avoidable re-check failures.

Where to Find the Issue Number on Your Photocard

A driver hands over a photocard, and the first mistake is often looking for the issue number as if it were a standalone label. It isn't. On Great Britain cards, it sits next to the long driver number, usually as a short two-digit field that's visually separated from the 16-character sequence. If you're reading the long alphanumeric block, you've already gone past the point where the issue number lives.

On newer photocard layouts, the issue number appears on the front face in a small field close to the driver number. On older cards, it may sit on the reverse near the machine-readable area. The exact print position shifts with card generation, but the layout logic doesn't change, the issue number is grouped with the driver number and separated by spacing or a line break.

The fastest way to avoid a transcription error is to scan the whole card before typing anything into a system. In most fleet onboarding work, I've found that admins who jump straight to the main driver number are the ones who later have to reopen the record. A careful read takes longer at the desk, but it saves a re-check when the licence comes back as a mismatch.

A simple reading order

1. Find the driver number first. That is the long 16-character identifier, not the issue number.
2. Look directly beside or beneath it. The issue number is physically close, but separate.
3. Check that you are not copying the full string. If the field looks like one long line, slow down and split it correctly.

If the card layout feels unfamiliar, stop and compare the front and back before entering anything into your records.

That habit matters because older and newer card designs don't place the field in exactly the same spot. A system can only verify what it is given, and a rushed entry is usually worse than a delayed one. The goal is not speed at the desk, it's accuracy that survives the audit trail.

Common Mistakes That Break Licence Verification

Most failures in licence checking don't come from the GOV.UK service itself. They come from admin handling. The most common one is simple, someone pastes the issue number onto the end of the driver number and creates a longer string than the verifier expects. That turns a valid licence into a bad input before the check has even started.

Where fleets go wrong

Another common error is holding on to an old issue number after a replacement card has been issued. Because the issue number changes when DVLA issues a fresh photocard, the old version is no longer the current card version, even if the driver is the same person. Systems that keep a single static value at onboarding often miss that change and later struggle to match the live licence record.

A third failure mode is defaulting every issue number to the same value in software, usually because someone assumed the field would be stable. That is a dangerous shortcut. It creates records that look complete but don't reflect the card in the driver's hand, which means your audit file can look clean while the live check does not.

Common Issue Number Mistakes and Their Audit Impact	What Happens	Audit Consequence
Concatenating the issue number with the driver number	The input becomes the wrong length and the verifier rejects it	Licence check fails before validation
Keeping an old issue number after reissue	The record no longer matches the latest photocard version	Current licence can look like a mismatch
Auto-filling the same issue number for every driver	The system stores a false version marker	Audit trail looks tidy but is unreliable

A lot of the pain here is version control, not identity. The driver is still the driver, but the card version has changed. That's why fleet admins should check whether the licence image or scan is the newest one before saving the record, especially after address changes, photo updates, or replacement cards.

Audit reality: a licence record that doesn't track card version properly can fail even when the driver is fully entitled.

The fix is boring but effective, separate the fields, recapture them when a new card is issued, and never assume the issue number is static. That's the difference between a tidy spreadsheet and a defensible compliance file.

Great Britain vs Northern Ireland Licence Formats

Mixed-UK fleets get caught here because the rules look similar from a distance and very different up close. Great Britain and Northern Ireland do not use the same licence structure, and software that assumes one pattern across both jurisdictions is going to create false failures. The issue number is part of that problem, because the card layout and the underlying number format are not interchangeable.

The jurisdiction split that trips teams up

Great Britain photocard licences use the familiar 16-character driver number, and the issue number sits as a separate two-digit field on the card. Northern Ireland uses a different licence number format, and its card structure does not map neatly onto Great Britain parsing rules. That means a regex or onboarding template written for GB can reject a perfectly valid NI card, even when the driver is legitimate.

This matters most in agencies, logistics firms, and PSV operators that recruit across the border or move drivers between depots. One admin may be looking for a GB-style sequence while another is entering a Northern Ireland record into the same system. The result is often a false mismatch rather than a real compliance issue.

For a broader view of how licence coding differs across card types, see the driving licence codes guide.

GB vs NI Driving Licence Format Comparison	Great Britain (DVLA)	Northern Ireland (DVA)
Driver number structure	16-character format	Different 8-digit driving licence number format
Issue number position	Separate field on the photocard	Different position on the card
Parsing approach	GB-specific rules work if they stay jurisdiction-aware	GB-style rules do not map cleanly
Typical fleet risk	Confusing the issue number with the driver number	Rejecting valid cards because the format is different

The operational fix is to make jurisdiction a first-class field in your process. If your system can't distinguish GB from NI at capture stage, your team will keep wasting time on avoidable exceptions. That is especially true when admin teams share templates or outsource onboarding and expect one validation rule to fit every driver.

Mainstream guidance still tends to explain the card layout without making the jurisdictional split obvious, which is why the same data entry error keeps repeating. The safest approach is to treat GB and NI as related but separate verification paths, not as one UK-wide pattern.

How to Verify a Driver Licence Using GOV.UK

The licence image is only the starting point. A photocard shows what the driver has handed over, but the live GOV.UK check shows what DVLA currently holds. In practice, the usual failure is simple, a fleet admin enters the issue number as if it were the driver number, or copies a GB format into a Northern Ireland record and gets a false mismatch.

The practical workflow

Capture the driver number and issue number exactly as they appear on the photocard, then keep them separate in your system. Use the GOV.UK check flow with the identity inputs it asks for, including the driving licence number and National Insurance number. If the postcode, number, or issue data is stale, the check can fail before you ever reach the entitlement screen. The government service is available through the view driving licence service.

If you use a check code, treat it as a single-use item. Once it has been issued and passed around an inbox, it is easy for a colleague to reuse an old code or try it after the driver has already moved on to a replacement card. That is one reason live verification is more dependable than copying an earlier result into a file and calling it current.

The practical habit is to store the result with the date it was checked, not just the fact that a check happened. That gives you a cleaner audit trail when a card changes or a dispute lands on your desk. If you want a process view built for operators, the driver licence checks for operators guide is a useful reference for setting up your admin steps.

What usually breaks the check

The common blockers are out-of-date postcode data, the wrong issue number, and reusing the same check code for more than one review. If the driver has moved and the DVLA record has not caught up, the postcode mismatch can stop the process even when the licence itself is valid. The system is doing what it should. Your record is the part that has drifted.

That is also why the issue number and the 16-character driver number cannot live in one blurred field. One identifies the person, the other helps confirm the card version. If your capture screen or spreadsheet treats them as interchangeable, you will spend time chasing false exceptions, especially where GB and NI records are being handled in the same workflow.

For teams tightening identity capture as well as licence checks, the guide to digital identity verification is a useful companion read. It shows the same operational pattern. Clean source data gives you a usable check, while sloppy input turns a valid record into an avoidable admin problem.

Building a Reliable Licence Check Workflow

A reliable workflow starts with a simple rule, separate the identity field from the version field. That means scanning or manually entering the driver number and issue number as distinct data points, then attaching the GOV.UK result to the same record. If those pieces live together from the start, you've got a defensible trail when a card changes later.

What to store and when

At onboarding, capture the photocard, the driver number, the issue number, and the verification outcome. If your system also stores the check date and the method used, the record becomes much easier to review during an audit. That is where a platform such as OperatorCompliance can sit naturally in a workflow, because it stores licence-check history and evidence alongside the licence data rather than leaving them in separate folders.

The next control point is re-verification. Don't treat licence checks as a one-time onboarding task. When a replacement card is issued, or when driver details change, the issue number should be recaptured and the live GOV.UK check rerun. If the issue number changes unexpectedly, that's a signal to review whether the underlying card version has changed and whether the previous evidence is still relevant.

Good audit files tell a story: who checked, what they checked, when they checked it, and which card version they used.

For teams that want to tighten document handling and identity capture, the identity document verification API overview is a practical reference point for how structured document workflows are usually built. The key lesson is the same in fleet compliance. Good data models reduce human error before the audit stage exposes it.

The final step is to make your process jurisdiction-aware. GB and NI records should not share one blind validation pattern, and any driver who presents a newer card version needs a fresh check trail. That is also why it helps to keep your licence review process tied to your wider compliance calendar, alongside documents that can affect retention or penalty review. For a wider policy context, see the guide to driving convictions retention.

---

If you want to stop licence-check errors before they hit your audit file, build the process around separate fields, current GOV.UK verification, and jurisdiction-aware rules. OperatorCompliance supports that kind of workflow for UK fleets, with evidence storage and driver-licence monitoring designed for transport admin work.