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 every one of them, lines them up, and puts the whole file through eight forensic layers. What changed, when, and what doesn't add up.

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

The eight forensic layers.

The evidence is already in the file. A forged document rarely fails one check — it fails several at once, from the raw byte structure of the PDF to the arithmetic on the page. That goes for AI-generated fakes too: a payslip invented in one shot still has to carry a real ABN, sums that reconcile and the signature of genuine payroll software. The layers don't care who — or what — made the forgery. Every file goes through all eight, and every result is reported: passed, failed, or skipped because something couldn't be read cleanly. Observable facts you can point to on the document itself. Never a model's opinion. Never a guess.

01

Revision history

Every earlier save buried inside the PDF, recovered and compared side by side.

02

Identity consistency

Payees, employers and ABNs counted across every save. A genuine document has one of each.

03

ABN ↔ employer linkage

One ABN attached to two different employers has no innocent explanation.

04

ABN checksum

Every ABN validated against the ATO's 11-digit algorithm. An altered digit rarely survives.

05

ABR register lookup

Live against the Australian Business Register: exists, active, and really that employer's number.

06

Arithmetic reconciliation

Every readable figure recomputed — payslips, bank statements, rates notices, tax returns.

07

Typography & baseline

Lookalike fonts, single retyped figures, digits sitting off the line — the fingerprints of an edit.

08

Producer software

Payroll software leaves one signature in the file. A PDF editor leaves another.

One engine, every document: the arithmetic adapts to whatever is in front of it, and everything else applies to any PDF at all — payslips, bank statements, rates notices, income statements, tax returns.

The output: a report you can stand behind

Written to be handed on — to a credit team, an auditor, or a dispute. Every layer listed with its result: passed, failed or skipped. A risk score with its reasons stated in full, save-by-save comparison tables, exhibit pages with the changed content boxed on the document image, and the file's SHA-256 fingerprint, so there is never an argument about 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

Eight forensic layers run in seconds: every saved version recovered and read, identities and ABNs compared, every figure recomputed, the typography and producer software 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