PDF version forensics · AU payroll & lending

Every document tells a story.
Some tell several.

Editing a PDF takes minutes. Hiding the edit is much harder — the earlier versions are often still saved inside the file. Indagar recovers them, lines them up, and re-checks every figure, name and ABN against the rest. What changed, when, and what doesn't add up.

DECISION SUPPORT FOR A HUMAN REVIEWER — NEVER A DETERMINATION OF INTENT
What it checks

The evidence is already in the file.

A doctored document usually keeps its own receipts: an earlier save under someone else's name, an ABN that fails its checksum, a total that only balances because one figure was typed over it. None of this relies on a hunch — every check below is an observable fact about the file, and when something can't be read cleanly, Indagar skips the check rather than guess.

01

Hidden versions, recovered

Each time a PDF is edited and re-saved, the previous version can stay buried inside the file. Indagar digs every saved state back out and lays them side by side — so you can watch a name, an employer or a net pay change from one save to the next.

02

One file, many identities

The classic template job: one real payslip, re-saved again and again with a different person's details each time. Indagar counts the payees, employers and ABNs across every save. A genuine payslip has one of each.

03

ABNs put to the test

Every ABN in the file is run through the ATO checksum, flagged if it's attached to two different employers, and can be checked live against the Australian Business Register — does it exist, is it active, is it really that employer's number? A failed checksum is a fact, not a suspicion.

04

Arithmetic that must hold

Net pay has to equal gross minus tax. Super has to sit at the legislated rate for the pay date. Year-to-date figures only ever move forward, and a bank statement's transactions have to land exactly on its closing balance. Rates notices and tax returns get their own sums. A figure typed over rarely survives being recomputed.

05

The fingerprints of an edit

A payslip that says it came from Xero shouldn't have been produced by a PDF editor. A font nobody else on the page uses, a digit sitting slightly off its line, producer software that changed between saves — small tells, plainly recorded.

06

A report you can stand behind

Every check — passed, failed or skipped — in one evidence report: a risk score with its reasons, save-by-save comparison tables, exhibit pages with the changed content boxed on the document image, and the file's SHA-256 so there's never a question of which document was examined.

How it works

Drop a file. Read the story. Decide.

Nothing to install, no templates to set up, no training run. Indagar works on the PDFs you already receive — payslips, bank statements, rates notices, income statements and tax returns.

Drop in a document

Drag a client PDF into the browser. Analysis starts on the spot and takes seconds — not a queue, not an overnight batch.

The engine investigates

Every saved version is recovered and read, identities and ABNs are compared, every figure is recomputed, the typography and producer software are examined.

You make the call

A risk score with every reason laid out in plain English, and a report you can attach to the file. Indagar tells you what it found — never what to conclude. The decision stays yours.

Privacy by design

Client documents stay with you.

Analysis runs in your browser

The entire analysis happens on your own device. The document is never uploaded, never stored and never seen by us — there is no server copy to leak, because there is no server copy. Two optional checks send only the bare minimum when you switch them on: AI field-reading sends a rendered image of page one, and the ABN lookup sends the eleven digits of the ABN. Nothing else ever leaves the machine.

NOTHING STORED · NOTHING SHARED · SHA-256 EVIDENCE TRAIL IN EVERY REPORT