Can I leave the location code blank?

Yes. The ministry condition states the field must be blank or four numerics, so blank is explicitly acceptable. Where no valid code applies, blank is better than a guess.

How is V51 different from V62 and V64?

V51 is the location code, which may legitimately be empty. V62 and V64 concern the service location indicator on hospital diagnostic claims, which is required, so an absent value there is itself a rejection.

The code looks like a normal four-digit number. Why is it invalid?

Because validity is determined by the ministry Residency Code Manual rather than by format alone. A well-formed four-digit value that is not in the manual fails the second half of the test.

OHIP error report

V51

Claim validation

OHIP error code V51: invalid location code on an ohip claim

V51 means the location code on the claim is neither blank nor four numerics, or it is four numerics that are not valid against the ministry Residency Code Manual. Blank is acceptable. Wrong is not.

Ministry wording: Invalid location code. Most often affects All specialist practices.

You already know V51. A single rejection is rarely the whole pile. Specialists we work with recover $10,000 to $100,000+ from rejected and unpaid claims, then average a 20–40% revenue increase within 90 days.

Each minute looking this up is about $5 of clinic time.

1Why it fires
2What it costs
3What you can recover

See what you can recover

V51 at a glance

V51 is a V-series validation edit, rejected on the Claims Error Report before adjudication. The ministry condition sets out both halves of the test: the location code must be blank or four numerics, and if present it must be valid based on the ministry Residency Code Manual.

The structure of that rule is the useful part. A blank location code passes. A populated one is checked against a published list. So V51 never means a code was required and missing. It means a value was supplied and the value does not exist.

That makes V51 unlike the service location indicator cluster, where an absent field is itself a rejection. V62 and V64 police an indicator that hospital diagnostic billing has to carry. V51 polices a different field that may legitimately be empty, and only becomes a problem once something is written into it.

Why it fires

The location code contains something other than four numerics, such as letters, a shorter number, or a space.
The code is four numerics but is not a valid entry in the ministry Residency Code Manual.
A retired location code is still stored against a site or a template.
A different internal identifier, such as a clinic or room number, has been entered into the location code field.

Format failures are the simpler half. Four numerics means four, so a three-digit code, a code with a trailing letter, or a value that has lost a leading zero in a spreadsheet will reject on shape alone before the list is consulted.

The list half is where practices get stuck, because a code can look entirely reasonable and still not exist. Validity is determined by the Residency Code Manual rather than by plausibility, which means guessing a nearby number is not a strategy.

Retired codes are a recurring cause for the same reason they are in the service location indicator cluster. This field is configured rarely and inherited often, so a value that was valid when it was entered can stay in a template long after it stops being accepted.

The most avoidable cause is field reuse. Where a practice has an internal identifier for a site and the location code field happens to be free, the internal number ends up there. It will be four numerics often enough to pass the format test and will fail the list.

What it costs

The claim is rejected and nothing is paid until a corrected claim is accepted. The amount at risk is the full fee for the service.

There is no partial payment, because the claim did not reach adjudication. The entire fee for the service is outstanding.

Like most configuration-driven codes, V51 arrives in volume. The location code comes from stored data rather than from the encounter, so a bad value rejects every claim that inherits it until someone reads the report.

Services on or after 1 April 2023 carry a three-month submission window from the date of service under ministry INFOBulletin 230402. A stored invalid code can therefore put a long run of claims against the window at the same time, while each individual claim was correctable the day it rejected.

Step-by-step: how to clear this rejection

Confirm the line is V51 and not one of the service location indicator codes, since those concern a different field with different rules.
Read the location code the claim actually carried and check whether it is four numerics.
If the format is right, verify the code against the ministry Residency Code Manual rather than against local convention.
Where no valid code applies to the service, consider whether the field should be blank, which the condition explicitly permits.
Resubmit inside the three-month window and check how many other claims carry the same stored value.

Remember that blank is a valid state. Where a practice cannot establish which code applies, leaving the field empty satisfies the condition, and that is a better answer than a plausible guess that will reject again or, worse, be accepted while describing the wrong location.

Verify against the manual rather than by trial. Cycling through nearby four-digit numbers until one is accepted produces a claim that passes validation and asserts something the practice has not checked.

Treat a repeat V51 as a stored-data problem. The field is not typed per claim in most systems, so the second occurrence is confirmation that the source record is still wrong.

Money you already earned, still unpaid

Recovery is separate work from ongoing billing. Charging only a percentage of what we recover, we review the backlog, correct what your documentation supports, and resubmit. Recent engagements have recovered five- and six-figure amounts, including rejected claims well past the 3-month stale dated deadline going back into 2023.

The alternative is usually your evenings or admin blocks, not billable clinic time. No setup or service fees. Every dollar recovered is money already written off, you keep most of it, and you pay nothing if nothing comes back.

“These claims weren’t chased up on. These claims have been stale dated. You add up the volume of money in there and it’s a consequential sum.”

Dr Sanjay Acharya, on what the recovery review found

Show me what is still recoverable

How to fix it going forward

Validate stored location codes against the ministry Residency Code Manual when a site is set up and whenever sites change.
Enforce the format locally, so a value that is not four numerics cannot be saved into the field.
Keep internal site identifiers out of the location code field entirely.
Leave the field blank rather than populating it speculatively, since the condition permits blank.

Validating at setup is the whole control. This field changes almost never, so the cost of checking it properly once is small and the cost of not checking it is a configuration error that persists for years.

A local format rule removes half the failure modes for nothing. Four numerics is a trivial constraint to enforce and it catches every lost leading zero before submission.

Give internal identifiers their own field. Most V51 caused by field reuse happens because there was nowhere else to put a number the practice genuinely needed to record.

Is it recoverable?

Recoverable by resubmission inside the window

Supply a location code that is valid under the ministry Residency Code Manual, or leave the field blank where no code applies, and resubmit inside the three-month window.

V51 is recoverable as a routine correction while the claim is inside the window, and the correction is administrative rather than clinical.

Where the right answer is blank, use blank. The condition accepts it, and a claim submitted with an empty location code is a correct claim rather than an incomplete one.

After the window closes, INFOBulletin 230402 allows claims that reached the Claims Error Report inside three months to be corrected and resubmitted through the ministry stale-date process, with the report line as evidence of timely submission. A claim never submitted inside the window runs through a written application instead, which this page does not describe.

For in-province services on or after 1 April 2023, claims must be submitted within three months of the date of service, not six. Ontario INFOBulletin 230402 is the Ministry notice. Many third-party pages still quote six months. That window is closed for current work. If the original claim reached the Claims Error Report inside three months, a corrected resubmission can still be filed after the window in the Ministry's stale-date process. If the claim was never submitted in time, payment may be recoverable by written application. That is not a routine resubmit.

Related codes

Frequently asked questions

What does OHIP error code V51 mean?: V51 means the location code is neither blank nor four numerics, or it is four numerics that are not valid under the ministry Residency Code Manual.
Can I leave the location code blank?: Yes. The ministry condition states the field must be blank or four numerics, so blank is explicitly acceptable. Where no valid code applies, blank is better than a guess.
How is V51 different from V62 and V64?: V51 is the location code, which may legitimately be empty. V62 and V64 concern the service location indicator on hospital diagnostic claims, which is required, so an absent value there is itself a rejection.
The code looks like a normal four-digit number. Why is it invalid?: Because validity is determined by the ministry Residency Code Manual rather than by format alone. A well-formed four-digit value that is not in the manual fails the second half of the test.

References

For how error reports relate to the remittance advice, see how to read your OHIP remittance advice and what rejection codes actually mean. Official wording for this code: Ministry of Health, Error Report Rejection Conditions (December 2022).