top of page
Search

IRCC PR Refusal Over Inconsistent Work Evidence in Garg v Canada

norilynoligo201
Oct 26
9 min read

By: Norilyn Oligo-Sarma. RCIC


A permanent residence application can fail even when the applicant submits more documents, if those documents do not answer the exact concerns IRCC raised.


That is the practical lesson from Garg v. Canada (2026 FC 1242). IRCC questioned whether the applicant’s claimed work as a Data Administrator was genuine. The applicant responded to a procedural fairness letter with explanations, an employer letter, and supporting records. The problem was not that she ignored IRCC. The problem was that the response left key contradictions unresolved.


One inconsistency stood out. The employer said it had served more than 500 clients. Its website showed 18. IRCC had also asked about the unfinished state of the employer’s website, but the response did not explain that issue. Another inconsistency involved the employer’s address. The response said the business had operated at one address since 2013, while the employer’s tax records showed another.


IRCC excluded the employment. Without that employment, the applicant did not have the required year of qualifying Canadian work experience. The permanent residence application was refused. On judicial review, the Federal Court upheld the decision.


This post is informational only and is not legal advice. Immigration cases turn on their own records, evidence, and procedural history.


Close-up view of marked immigration papers on a kitchen table
Small inconsistencies in documents can become major issues in a PR application.

The case turned on whether the work evidence was credible


In Canadian permanent residence applications, work experience evidence does more than prove dates of employment. It helps show that the employment was genuine, that the applicant performed the claimed duties, and that the experience meets the program requirements.


In Garg v. Canada, IRCC focused on the applicant’s claimed employment as a Data Administrator. The officer had concerns about whether the job was real. That concern led to a procedural fairness letter, often called a PFL.


A PFL gives an applicant a chance to respond before IRCC makes a negative decision based on concerns that may be central to the application. It is not a casual request. It is a warning that something in the record may lead to refusal unless the applicant gives a clear and supported answer.


The applicant did respond. She provided explanations, an employer letter, and supporting records. But IRCC was not satisfied. The officer looked at the response as a whole and found that the evidence did not resolve the concerns.


That point matters. A PFL response is not judged by weight alone. A thick package can still fail if it does not deal with the actual concerns. An officer may accept some parts of the record and still reject the claimed work experience if the unresolved issues go to credibility.


Here, the officer found enough gaps and inconsistencies to exclude the employment. Once that happened, the applicant no longer met the required year of qualifying Canadian work experience. The refusal followed from that finding.


The Federal Court did not treat the case as an opportunity to rebuild the application from scratch. On judicial review, the Court looked at whether the officer’s decision was reasonable in light of the record. It accepted the officer’s assessment of the combined problems.


That is why this decision is a useful reminder. The issue was not one isolated typo or a harmless difference in wording. It was the combined effect of several unanswered concerns.


The client count issue was not just a numbers problem


The most striking inconsistency involved the employer’s claimed client base.


The employer said it had served more than 500 clients. Its website showed 18. On its own, that gap was large enough to attract attention. But the larger problem was that the response did not explain the gap in a way that satisfied the officer.


There may be innocent explanations for a mismatch like that. A website might show only selected clients. It might be outdated. It might list active clients rather than all historical clients. It might have been under construction. A business might serve clients through channels that are not reflected online.


But those explanations need to be stated, supported, and tied to evidence.


If IRCC asks about an unfinished website, a response should not simply submit more documents and hope the concern fades. The response should address the website directly. For example, it might explain when the site was built, why it was incomplete, who maintained it, what the 18 clients represented, and how the broader claim of more than 500 clients was calculated.


Then the records should support that explanation. Depending on the business, that might include invoices, anonymized client lists, contracts, tax filings, accounting records, or other ordinary business documents. The point is not to drown the officer in paper. The point is to make the explanation verifiable.


In this case, IRCC had specifically asked about the unfinished website. The employer did not explain why it remained unfinished. That left the officer with a sharp contrast between the employer’s claim and public-facing information.


A PFL response should not assume that an officer will fill in the blanks. If anything, the opposite is safer. When a concern is already in writing, the response should treat it as a required question.


The issue can be framed this way:


Concern raised by IRCC

Weak response

Stronger response

The website shows only 18 clients

Submit an employer letter saying the company has served more than 500 clients

Explain what the 18 clients represent and provide records showing how the 500-plus figure was reached

The website appears unfinished

Ignore the website because other documents were submitted

Explain why the site was unfinished and support that explanation with records or timelines

Business records conflict

Treat the conflict as minor

Identify the conflict, explain it, and attach evidence that resolves it


That distinction is central. More evidence helps only when it answers the right question.


The address inconsistency added to the credibility problem


The address issue was another concern in the record. The response said the business had operated at one address since 2013. The employer’s own tax records showed a different address.


Address differences are common in business records. A company may have a mailing address, registered address, physical location, accountant’s address, prior location, storage location, or home-based address. These differences are not always fatal.


But they become risky when no one explains them.


If the business used one location for operations and another for tax filings, the response should say that. If the company moved, the response should give dates and records. If the tax record reflected an accountant’s address or an old registered office, the response should explain why that address appeared and provide evidence.


The problem in Garg was not simply that two addresses existed. The problem was that the evidence made a firm claim about the address history, while another record appeared to contradict it. That contradiction sat inside a larger set of concerns about whether the employment was genuine.


An officer does not need to examine each inconsistency in isolation. Credibility often depends on the total picture. A client count mismatch, an unfinished website, and inconsistent address information may reinforce each other. Together, they can make an employment claim look less reliable.


This is why applicants and representatives should avoid treating inconsistencies as small clerical issues without checking their effect on the whole file.


A single mismatch might have a simple answer. Several mismatches, left unexplained, can create a pattern.


Overhead view of folders and sticky notes arranged by issue
Organizing each concern separately can make a PFL response clearer.

A PFL response needs answers, not just attachments


A common mistake in responding to IRCC is to treat the response like a document dump. The applicant gathers everything that seems helpful, attaches it, and writes a short explanation. That can backfire if the package creates new questions.


A strong response usually does three things:


  1. It identifies each concern raised by IRCC.

  2. It gives a direct explanation for each concern.

  3. It points to records that support each explanation.


That structure matters because officers review files under time and evidentiary limits. A response should make the path clear. If the explanation depends on a specific invoice, tax document, contract, payroll record, or business registration, the response should point the officer to that record.


For employment-based PR evidence, the following records often need to align:


  • Employer reference letters

  • Pay records and tax slips

  • Bank deposits

  • Business registration records

  • Tax filings

  • Website or public business information

  • Work location details

  • Job duties and title

  • Start and end dates

  • Hours worked

  • Supervisory or reporting structure


Not every case needs every document. But when documents are included, they need to be checked against each other.


For example, if an employer letter says the applicant worked at a specific location, and payroll records or tax records show a different business address, the response should explain why. If a business claims a large client base but public information shows a much smaller number, the response should explain the difference. If the website is incomplete, inactive, or outdated, the response should say so and provide context.


The key is to avoid making IRCC guess.


A useful PFL response reads like a guided explanation of the evidence. It does not leave the officer to search through attachments and infer the applicant’s position.


How to spot inconsistencies after reading the file several times


The harder part is that inconsistencies often become invisible to the person preparing the application. After reading the same material several times, the brain starts filling in missing context. What feels obvious to the applicant may not be obvious to an officer.


A few practical habits can help.


Read only for one fact at a time


Trying to review everything at once makes errors easier to miss. Instead, read the full package once for dates only. Then read it again for addresses only. Then read it again for job titles, hours, wages, and business names.


This method is slower, but it works because it reduces noise. Each pass has one job.


Build a simple consistency chart


A chart can reveal problems that normal reading misses. It does not need to be complex. Create columns for each document and rows for the facts that must match.


For example:


Fact to verify

Employer letter

Tax record

Pay record

Website or public record

Business name

Check exact spelling

Check exact spelling

Check exact spelling

Check exact spelling

Address

Check location

Check location

Check location

Check location

Employment dates

Check dates

Check tax year

Check pay period

Check consistency

Job title

Check title

If shown, compare

If shown, compare

If shown, compare

Client or business activity

Check claim

Compare with filings

Compare with income records

Compare public information


This kind of chart forces every important fact into the open. It also makes it easier to decide whether an explanation is needed.


Review the file from IRCC’s point of view


A PFL response should not only ask, “Can I explain this?” It should ask, “Can a stranger verify this from the record?”


That difference is crucial. The applicant may know that a business moved locations, that a website was outdated, or that a client list was incomplete. But IRCC can only assess what is in the record.


If the explanation is not written down and supported, it may not help.


Use a fresh reader


A fresh reader can catch contradictions that the main preparer misses. That person does not need to know every detail of the case. In fact, limited background can help. They can flag what seems unclear, unsupported, or inconsistent.


Ask the reader to mark three things:


  • Facts that appear in more than one place but do not match

  • Claims that sound significant but lack documents

  • Documents that raise new questions


That last category is especially important. A new document can solve one problem but create another. In Garg, the applicant submitted follow-up evidence, yet the officer still found that the combined concerns remained unresolved.


Separate explanations from proof


A response should not confuse a statement with evidence. An employer letter can be useful, but if the officer already has credibility concerns, the letter may need support from independent or ordinary business records.


For example, saying “the company served more than 500 clients” is an explanation. Records showing how that number was calculated are proof. Saying “the business used another address for tax purposes” is an explanation. Tax records, registration records, lease documents, or accountant correspondence may help prove it.


The more central the fact is to the concern, the more carefully it should be supported.


The practical lesson from Garg v Canada


The PR refusal over inconsistent work evidence in Garg v. Canada shows how a file can fail even after a PFL response. The applicant did not lose because she stayed silent. She lost because the response did not resolve the officer’s concerns about the genuineness of the employment.


The employer’s claim of more than 500 clients did not sit comfortably with a website showing 18. The unfinished website remained unexplained. The address history in the response did not align with the tax records. Taken together, those issues gave IRCC a basis to exclude the employment.


The takeaway is direct: before submitting a response to IRCC, test the evidence against the concerns in the letter.


Ask two questions before filing:


  • Does the response answer every concern IRCC raised?

  • Do the attached records support each explanation?


If records differ, do not hope the difference looks minor. Explain why they differ and provide evidence where possible. A clear answer to a hard question is usually stronger than a larger package that leaves the question unanswered.


 
 
 

Comments


bottom of page