Cross-Document Verification: Checks That Catch Bad Files

Cross-document verification means taking one fact (a name, an address, an income figure, an institution and transit number, a business number, a date) and checking that every document in the file, and every public record you can reach, says the same thing about it. Most incomplete or inconsistent files are not forged. They hold a pay stub from one employer, a bank statement under a slightly different name and a utility bill that is five months old. Each document looks fine alone. The file does not.

This article is for informational purposes only and does not constitute legal, financial, or regulatory advice. Regulatory references are accurate as of October 2026 and cover Canada at the federal level unless stated otherwise; provincial rules vary. Consult a qualified professional for your situation.

What does cross-document verification compare?

It compares a field on one document with the same field on another document or a public record, then routes any difference to a person with a defined next step. It is a consistency control, not an authenticity test: two documents can agree with each other and both be wrong.

FINTRAC guidance on methods to verify the identity of persons and entities recognizes prescribed methods such as the government-issued photo ID method, the credit file method and the dual-process method, which relies on two independent sources, so a second source is built into the regulatory approach (FINTRAC, Methods to verify the identity of persons and entities). The obligations come from the Proceeds of Crime (Money Laundering) and Terrorist Financing Act (PCMLTFA). Landlords, staffing agencies and lenders that are not reporting entities are outside those rules, but the logic carries over: an error or a lie has to survive two documents from independent issuers.

For the wider method, see our document verification guide. For why extracting text is not enough, read cross-document validation beyond OCR.

The seven cross-checks, field by field

Seven comparisons cover most of what goes wrong in an applicant file. Each has a source field, a comparison field, a typical mismatch and a reviewer action.

Dates run through all seven. A document issued after the application date, a pay stub from before the offer letter, or an ID that expires before the decision date are cross-checks in their own right.

How does the income triangle work in practice?

The income triangle compares a pay stub, a bank statement and a tax document, because each comes from a different party: the employer, the bank and the Canada Revenue Agency (CRA).

Take an illustrative case. A pay stub shows net pay of $2,314.60 for the period ending September 30, paid on October 3. The bank statement shows a deposit of $2,314.60 on October 3 from "NORTHWAY LOGISTICS INC". The stub reads "Northway Logistics Inc." Amount, date and payer line up, and the punctuation is harmless. Now change one thing: the statement shows $2,980.00 from the same payer. That gap is a bonus the stub does not show, a second job, or an edited document. The reviewer does not decide which. The reviewer asks for the next pay period and an offer letter, and records the reason.

Three rules keep this check useful:

• Compare net pay to the deposit, not gross pay.
• Match amount first, then date (allow a few days either side), then payer name.
• Compare at least two pay periods. One match proves little; a pattern proves a lot.

The third corner is a tax document the applicant did not prepare. For employees, the T4 comes from the employer and the Notice of Assessment from the CRA; for self-employed applicants, compare the NOA with the bank deposits over a full year, since pay stubs do not exist (CRA). For rental files, our guide to income verification on rental applications applies the same logic.

Where do name, address and bank-detail mismatches hide?

They hide in formatting differences that look like fraud but usually are not, and in real differences that look like formatting.

Names: variants versus different people

A name mismatch is benign when surname and date of birth agree and the difference is a nickname, a dropped middle name, a hyphen or a missing accent. It needs a question when the surname differs, which happens after marriage, divorce or a legal name change. It needs escalation when first name and surname both differ and no change document exists. In Quebec and in bilingual files, accented characters (é, è, ç) are routinely dropped by one system and kept by another; treat that as cosmetic.

Addresses: one-line differences

Addresses fail more often on form than substance: "Unit 3, 14 Main St." against "3-14 Main Street". Normalize abbreviations and the unit-dash convention, then compare postal code and street number. A different postal code on a document dated after a move is expected; the same code with a different street number is not.

Bank details: the account holder is the real field

Canadian accounts are identified by institution number, transit number and account number rather than an IBAN, so there is no standard checksum to lean on. The field that matters is the account holder name. A void cheque in a third party's name is a valid document and a failed check.

How do you cross-check a corporate file against the registry?

You compare legal name, corporation number, status, registered office and directors on the contract or invoice with the public record. Federally incorporated companies are listed with Corporations Canada; provincially incorporated companies appear in the provincial registry, so first establish which jurisdiction the company was formed in.

Four comparisons do the work:

1. Legal name on the contract against the registry entry for that exact name.
2. Status: active, dissolved or amalgamated on the date of signature.
3. Registered office against the address on the letterhead.
4. Signer against the listed directors and officers.

A registry lookup proves that a corporation exists in that jurisdiction with that status on that day; it does not prove that the document in front of you is genuine or that the person signing has authority. For entities that are reporting entities under the PCMLTFA, FINTRAC also expects beneficial ownership information to be collected and confirmed with reasonable measures, which a registry extract alone will not supply. Ask the client for ownership details and keep the record.

What does a mismatch look like, and what does the reviewer do?

A mismatch falls into one of three classes, and each has a fixed response. Without that, the same discrepancy is accepted by one reviewer and rejected by another.

A file is complete when each of the seven checks has a result, not when each document is present. A missing statement and a failed comparison are different states and should be reported as different states.

Questions people ask about mismatched files

People who handle applicant files in professional communities tend to ask the same things. These two come up most.

"The name on the pay stub is slightly different from the driver's licence. Do I have to reject it?" No. Check surname and date of birth first. If both match, treat it as a variant and record the rule you applied. Escalate only when surname or date of birth differ without a supporting document.

"The bank deposits are lower than the pay stub shows. Is it fake?" Not necessarily. Pay can be split across two accounts, reduced by an advance or deposited late. Ask for the next pay period and a second stub. It becomes unexplained only if the gap persists with no explanation.

Automating the comparisons

A validation tool should extract the same fields from each document, normalize them and show a field-by-field comparison with a reason for each difference. Whether a mismatch is acceptable stays a policy decision for your team. The comparison should only use fields you need: the Social Insurance Number in particular should be collected only where a law requires it. The federal private-sector privacy law is PIPEDA, and Quebec's Law 25 adds its own requirements for files that involve Quebec residents. CheckFile compares fields, dates and register data across a file and flags differences for review; it does not certify that any document is authentic. To see how this works on a financing file, read about our solution for financing and leasing, check pricing or review our approach to security and data handling.

Frequently Asked Questions

What is cross-document verification?

It is the comparison of the same field (such as name, address or income) across several documents and public records in one file. Differences are classified and sent to a reviewer with a defined next step.

Which documents should be compared first?

Start with the government photo ID, the proof of address and the income documents. Name, date of birth and address on these three catch the largest share of inconsistent files, and they are the cheapest to compare.

Does cross-document verification detect forged documents?

Not by itself. It finds inconsistencies between documents. A well-made forgery that agrees with the rest of the file would pass, which is why an issuer check or a registry lookup is added where one exists.

How many months of bank statements should be matched to pay stubs?

At least two pay periods. One can match by coincidence or fail for an innocent reason; two show whether the pattern holds.

What should the reviewer record?

The check, the fields compared, the result, the rule applied and any document requested. That record is what you show an auditor or FINTRAC examiner if the decision is questioned.