PDF security blog

The File-Integrity Step in Admissions Document Review

HTPBE Team··10 min read
The File-Integrity Step in Admissions Document Review

This article is a snapshot – content was accurate as of November 2026 (code examples tested against the API as of October 2026). The product evolves actively; specific counts, examples, and detection rules may have changed since publication – see the changelog for the current state.

An admissions officer opening an application sees a transcript, a degree certificate and a bank letter, all as PDFs. They look right. The grades are plausible, the crest is in the corner, the balance clears the threshold. What the officer cannot see from the page is whether the file in front of them is still the one the institution or the bank produced, or a copy someone edited on the way to the upload form.

This article is for university admissions and compliance teams, and for the education agents and immigration advisers who assemble application bundles. It covers one narrow step in admissions document review – a PDF file check for evidence of modification – and where it sits beside the credential checks you already run.

What is the file-integrity step?

Short answer: it is a check on the PDF file itself, run at intake, that asks one question: was this file changed after it was created? HTPBE? answers it with structural PDF analysis. It reads how the file was built and saved, not the text, grades or figures on the page, and returns one of three verdicts: intact, modified or inconclusive.

The step does not replace credential verification. Confirming that an institution awarded a degree, that a transcript matches its records or that funds are held in an account remains the job of the issuing institution, the bank, or an official verification service. The file check runs before and alongside those steps: each file gets a quick file-level result, and the issuer-side checks still run on every document as they always have.

Which admissions documents arrive as PDFs?

Most admissions documents now arrive as PDFs, and each route puts the file in different hands first:

  • Academic transcripts. Some institutions send electronic transcripts directly; many applicants download one from a student portal or scan a paper copy, so the applicant usually holds the file before you do.
  • Degree certificates and diplomas. Often scanned or photographed from a paper original, sometimes issued as a PDF. The checks HTPBE? runs on this document type are described on the diploma tamper-detection page.
  • Proof-of-funds documents. Bank statements and bank letters supporting a student visa application or a deposit. For how UKVI treats bank statements on the immigration side, see what UKVI actually checks; this article does not repeat those rules.
  • Agent-forwarded bundles. An education agent or adviser collects documents from the student and forwards them, sometimes merged into one PDF. One more party has handled every file. A merged bundle is itself a changed file, so it will not come back intact even when every document in it is unaltered. Where you can, check each document as the student supplied it, before merging, and treat a verdict on the bundle as a routing signal about the bundle, not about any single document.

What a reviewer sees, and what the file shows

A reviewer reads the page, and that catches a lot: a grading scale that does not match the institution, a name spelled two ways. Manual review, helped by OCR where your team uses it, is good at spotting content inconsistencies.

What that review cannot see is the file’s history. A PDF records how it was put together and saved, and an edit made after the document was created can leave evidence in that structure even when the page looks unaltered. That is the layer HTPBE? reads. A transcript can read perfectly and still carry evidence of a later edit. The reverse question – whether what the page says is true – is one the file check cannot answer, because it does not read the content.

Which check answers which question?

Admissions review already combines several checks. The file-integrity step fills one gap:

QuestionWho answers itWhat it does not answer
Was this PDF changed after it was created?File-integrity check (HTPBE?)Whether the institution issued it
Did the institution issue this document to this student?The issuing institution or an official verification serviceWhether the file you hold was later edited
Does the content meet our entry and eligibility rules?Admissions and compliance reviewWhether the figures on the page are real

The second row stays primary. HTPBE? never confirms that an institution issued a document, never checks grades and never confirms that funds exist. The broader picture of how forged diploma and certificate PDFs show up across sectors is on the certificate tamper-detection page.

What each verdict means at the admissions gate

Write what each result does into the review procedure before the first file goes through. Every API result carries a usage_caution field stating that it is not safe for automated adverse decisions. A verdict describes the file, not the applicant, and it should never be the sole basis for refusing an offer or withdrawing one.

VerdictWhat it meansWhat the review step does
intactNo modification was detected in the fileContinue with credential and eligibility review as normal. It is not a confirmation of the document.
modifiedThe file itself carries evidence that it was changed after it was createdRoute to a reviewer with the result and its named markers attached. Ask for an issuer-sent copy.
inconclusiveHTPBE? cannot confirm the file as an untouched original – a reason for manual review, not proof of fraudNot a rejection. Use the issuer channel you would use anyway, and review the content as you normally would.

inconclusive is routine. Scanned and photographed pages can never be confirmed intact, and many perfectly ordinary transcripts and diplomas reach admissions as scans. The result says nothing about the applicant. For inconclusive, usage_caution.recommended_action is request_from_issuer: in admissions that means the channel your team already uses, such as asking the institution to send the transcript directly or confirming the award through an official verification service.

modified is not a finding of fraud. It says the file carries evidence that it was changed after it was created. It does not say who changed it, why, or whether the content is now wrong, and a changed file is not, on its own, proof that anyone acted dishonestly. The result lists named markers describing what was found, so the reviewer sees the reason, not just the verdict. Word the request to the applicant neutrally: you need an issuer-sent copy of this document. Give them the chance to explain before any decision.

Check your procedure against your own legal and regulatory obligations on adverse decisions before you rely on it.

Where the step sits in intake

At a university. The natural point is where documents are uploaded to the applicant portal or pulled into the admissions system, so a reviewer opening the application sees the verdict next to the document. Credential checks still run on every file; a modified or inconclusive result adds an issuer-sent-copy request to that review.

At an education agency or immigration practice. Agents and advisers sit one step earlier. Checking each file as a student hands it over means evidence of a change can surface before your organisation puts its name to a submission. For the immigration-adviser side, including visa and sponsor documents beyond admissions, see the immigration document tamper-detection page.

The same step appears in employment screening. The right-to-work and I-9 article covers it for HR teams, and the diploma check for HR and ATS pipelines covers the API integration side.

Handling student data. Transcripts and bank letters carry personal data. Files uploaded through the web may be retained after analysis to improve detection, without being linked to your account. Files submitted through the API are fetched, analysed once and discarded; only the result is kept. With the on-premise deployment, documents stay inside your own infrastructure. For web and API checks, the result is kept for up to three years and includes the filename. Results are private by default, but a public link you enable shows the filename too, so use neutral filenames rather than a student’s name. The privacy policy sets out the details.

What the file check does not tell you

Outside the file check: the institution, the grades, the funds and the applicant. HTPBE? does not read the content of the document, does not contact the institution or the bank, and does not confirm that a degree was awarded or that money is in an account.

The other limits:

  • Content that was false from the start. The check looks for evidence that a file was changed after it was created, and content that was false from the start carries no evidence of a later edit. The check does not read content, so it cannot judge whether what the document says is true. intact means no modification was detected, not that the document is genuine.
  • Scans and photographs. An inconclusive result on them is routine and is not a mark against the applicant.
  • Signatures. Where a file carries a digital signature, the check does not test the certificate, the certificate chain or the signer’s identity.

Frequently asked questions

Does an intact result confirm the university issued the transcript?

No. HTPBE? checks the PDF file, not the institution, the grades or the student. An intact result means no modification was detected in the file, not that the document is genuine. Whether the institution issued the transcript, and whether the grades on it are right, are questions for the issuing institution or an official verification service, which stays the primary check.

Is an inconclusive result on a scanned transcript a red flag?

No. An inconclusive result means HTPBE? cannot confirm the file as an untouched original – a reason for manual review, not proof of fraud. Scanned and photographed pages can never be confirmed intact, so at the admissions gate this result is routine. The next step is the issuer channel your team would use anyway, such as asking the institution to send the document directly.

Can we reject an applicant because a file came back modified?

Not on that result alone. Every API result carries a usage_caution field stating it is not safe for automated adverse decisions. A modified result says the file carries evidence that it was changed after it was created; it does not say who changed it, why, or whether the content is wrong. Route the case to a reviewer, give the applicant a chance to explain or provide an issuer-sent copy, and let your normal admissions and credential checks decide.

Check a sample file

Start with a file or two your team has already reviewed, and compare the verdicts with what you know about each one. The certificate tamper-detection page shows what HTPBE? checks on diplomas and transcripts. To run a check, upload a PDF on the home page or send a file URL through the API. Files uploaded through the web may be retained after analysis, and API submissions are discarded once analysed, so for applicant documents use the API or a file you are free to share.

Share this article

Found this article helpful? Share it with others to spread knowledge about PDF security and fraud detection.

https://htpbe.tech/blog/admissions-document-review-file-integrity-step

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.