A CRA Notice of Assessment is the most-trusted income proof in Canada – and the most-edited
Mortgage brokers and B-lenders treat the NOA as authoritative – it’s the official CRA verdict on the borrower’s declared income. Express Entry candidates submit it as proof of Canadian work history. Whenever an applicant needs a higher figure, the temptation is the same: download the real NOA from CRA My Account, edit the line that matters, re-export. The page renders identically. The file structure does not.
HTPBE? analyzes the structural layer of the PDF file – the layer that records every edit, even invisible ones. We don’t inspect holograms, phone photos, or ID biometrics. If your fraud problem is a digitally altered or fabricated NOA, we’re the most specific tool for it.
When HTPBE? returns INCONCLUSIVE on a Notice of Assessment, that is a reason to escalate to manual review, not proof of fraud – it means HTPBE? cannot confirm the file as an untouched original.
The problem
Modern document fraud is invisible to visual review
A growing class of document fraud opens a genuine PDF, edits a balance, a date, or a beneficiary, and re-saves it. Visually nothing changes – the document passes pixel-level review, layout review, and KYC.
Structural PDF analysis reads the layers rendering engines never expose: revision history, object structure, signature coverage maps. That is where edits leave fingerprints they cannot wipe.
Common tampering patterns
- Modified balances or totals after export
- Swapped IBAN or beneficiary on invoices
- Post-signature edits on contracts
- Backdated issue and modification dates
- Fabricated documents from consumer PDF tools
What this looks like
How fake and tampered NOA PDFs actually look
Three real fraud mechanics we catch at the structural PDF layer.
Real NOA edited and re-saved with a higher Total income
The applicant downloads the genuine NOA from CRA My Account, opens it in any PDF editor or spreadsheet, edits Line 15000 (Total income) or Line 26000 (Taxable income), exports as PDF. The edit typically leaves traces of the editor in the file. Visual layout preserved; the file structure is not.
NOA fabricated in Word from a screenshot of the CRA layout
A Word document built using the NOA layout copied from CRA documentation, populated with desired figures, exported as PDF. However closely it copies the CRA layout, the file does not come back INTACT: with nothing indicating later editing it returns INCONCLUSIVE and should go to manual review; with evidence of editing or fabrication, MODIFIED.
Tax year backdated to fill an income gap
A real NOA from one tax year gets edited to show a different year – covering a gap when the applicant was not earning Canadian income. Visual page looks legitimate; HTPBE? flags the post-issuance edit and the file’s dates that disagree.
The scale
Why your existing checks miss this
CRA Auto-fill My Return checks via consent. Borrowers who edited the file rarely consent.
Both layers matter. The CRA call only works if the borrower lets you make it.
CRA Auto-fill My Return and similar consent-based tooling can check NOA figures directly with CRA – when the borrower agrees to grant access. Borrowers who edited the file rarely do. OSFI B-20 guidelines push lenders to check income, but that check is downstream and slow. IRCC immigration officers see NOAs in PDF form without consent-based CRA access at all. HTPBE? catches the NOA PDF the borrower or applicant uploaded at the moment of intake – standalone, no CRA API, no consent required.
What HTPBE? checks
Detection capabilities
Deterministic structural signals. No probabilistic scores, no model training.
Desktop-built NOAs go to review
An NOA saved as PDF from Word, Excel or LibreOffice does not come back INTACT, however closely it copies the CRA layout. With no sign of later editing it returns INCONCLUSIVE for manual review; with evidence of editing or fabrication, MODIFIED.
The file decides, not the look
Whatever tool produced it, an NOA comes back MODIFIED when the file itself carries evidence of editing or fabrication. Matching the CRA page pixel for pixel doesn’t change that – HTPBE? looks at the file, not the page.
Post-issuance edit detection
Editing a CRA notice after issuance – in a PDF editor, or by rebuilding it in other software – leaves structural evidence behind. HTPBE? flags it as MODIFIED.
Character overlay on the original
Changing a figure on an existing notice leaves a structural trace. HTPBE? flags it without reading the page – it never looks at what the figures say.
Dates that disagree
A ‘freshly issued’ NOA whose own dates show it was changed months later is a high-confidence flag for post-issuance editing.
Reworked documents
HTPBE? detects documents reworked after their original creation and documents assembled from pages of different sources.
Share with engineering
Wire this into your intake pipeline in under a day
Two API calls – one POST to submit the PDF, one GET to retrieve the verdict. Forward this page to your engineering team; the full API reference, quotas, and copy-paste examples in cURL, JavaScript, Python, PHP, Go, and Ruby are one click away.
Pricing
Self-serve plans, no sales call
All plans include the same forensic checks. Pick the quota that matches your monthly document volume.
manualStarter
30 credits/mo
Manual spot-checks and integration testing
most commonGrowth
350 credits/mo
Active document processing pipelines
high volumePro
1,500 credits/mo
High-volume automation and API integrations
Enterprise (unlimited, on-premise available) — see full pricing
API key on signup. Free test environment on every plan. No card required.
Customer Stories
Teams that stopped document fraud
Compliance, finance, and risk teams use HTPBE? to catch manipulated PDFs before they become costly mistakes.
Caught an invoice where the total had been changed by less than a thousand dollars. Without this I would have approved it without a second look.
Sarah M.
AP Manager
United States
We had three applicants in the same week with bank statements that looked completely fine. Two of them were flagged as modified. You simply cannot see this by reading the document — it is in the file structure.
Lars V.
Risk Analyst, Online Lending
Netherlands
Salary slips were coming with altered figures. We identified two problematic files before the placement was finalised.
Priya K.
HR Operations Lead
India
Since we started checking documents this way, we stopped two applications early in the process that would have been very difficult to reverse later.
Julien R.
Fraud Analyst, Fintech
France
Some applicants were sending PDFs that looked authentic but had been edited in ways not visible to the eye. We now ask for checked originals when something is flagged. Already saved us from a few bad decisions.
Marta S.
Compliance Coordinator
Spain
One invoice was caught because there was a mismatch between the document dates and structure. That particular case would have cost us significantly.
Tariq A.
Finance Manager
United Arab Emirates
FAQ
Frequently asked questions
Do I need to call CRA or use Auto-fill My Return to check NOAs?
Can it catch NOAs fabricated from scratch in Word?
inconclusive – not intact – however closely it copies the CRA layout, and should go to manual review. The verdict is modified when the file itself carries evidence of editing or fabrication.How is this different from Equifax or TransUnion fraud detection?
What about NOAs used in Express Entry or PR applications?
What does an INCONCLUSIVE verdict mean for a Notice of Assessment?
Secure your workflow
Create your account – check PDFs on the web or with an API key, both ready on signup.
No sales call. Cancel any time.