Why "Fake or Real" Is the Wrong Question in Document Verification

Many document verification tools promise a simple answer: real or fake, pass or fail, green or red. It is an attractive promise. It is also the source of some of the hardest problems a compliance team will ever have to explain.

A verdict hides its reasoning. When an applicant is declined because a system marked their payslip as fake, the organisation is left defending a conclusion it cannot fully explain. When a forged statement passes because nothing was flagged, there is no record of what was actually checked.

Documents change for ordinary reasons. Files are re-saved, scanned, compressed, exported from accounting software or corrected by an employer. A signal that a file was modified is a reason to look closer. It is not proof that anyone acted dishonestly. Equally, finding no signals is not proof that a document is genuine. Some alterations leave no trace.

That is why we designed Truvasse around a different question: what does this evidence actually show? Truvasse examines submitted digital evidence for supported forensic indicators of modification, inconsistency and provenance issues. Each finding is explained in plain language, with the method used, where it was found and the innocent explanations that may apply.

The reviewer then does what software cannot do well: weigh the context, ask the applicant to explain or replace a document, and make a decision. That decision, and the reason for it, become part of a defensible record.

Regulators, auditors and courts rarely ask whether a tool said yes or no. They ask what you received, what you checked, what you found and who decided. A review process built on evidence rather than verdicts can answer every one of those questions.