Loupe · Document fraud detection Live
Document fraud detection: Find the figure someone changed on a payslip or bank statement, before you rely on it.
In short Loupe checks the payslips, bank statements, invoices and letters people send you. When something has been changed, it marks the place on the page and says what’s wrong in a sentence your team can read back to the applicant. Then someone on your team decides what happens next.
£1 a document, pay as you go · in our cloud or entirely on your own machines
Sam on the lettings team gets the pack, with each spot marked.
What Loupe found in D. Reyes’s rental application
His letting agent sent us four documents in one ZIP. Both summer payslips came back clean. These are the reasons Loupe gave for the other two.
-
October payslip
Net pay is £400 more than pay less deductions
The slip says 3,237.60, but the lines above it come to 2,837.60. Someone who changes a payslip often keeps the sums right, so Loupe also checks that every balance moves the way its transactions say it should.
-
October payslip
The net pay figure is in a different typeface from the rest of the slip
At a glance it looks right. Next to the figures around it, the digits are a slightly different shape and sit a fraction higher on the line.
-
October statement
Page 2 was scanned apart from pages 1 and 3
Pages 1 and 3 share the same paper, light and grain. Page 2 doesn’t, which usually means it was swapped in from another month, or printed and scanned again.
-
October statement
It was saved again in a PDF editor two days after the bank issued it
Banks don’t edit a statement once they’ve sent it, so this is worth asking the applicant about.
Other reasons Loupe gives
- Payslip
This looks to have been made whole by an AI tool, and its payroll number can’t exist.
- Utility bill
The supplier’s logo was pasted in from a different image.
- Payslip
A white box covers text that is still in the file. Underneath it reads 2,837.60.
- Employer letter
The letter was changed after it was digitally signed.
- Photo of a payslip
The photo was edited in image software before it was sent.
- Bank statement
The sort code and account number fail their check digits.
- Two payslips
They give different National Insurance numbers for the same person.
- Invoice
This invoice was sent before, with another application under a different name.
Sam on the lettings team decides what happens next
Loupe never turns anyone down. Sam sees the payslip with the figure marked and the reasons beside it, and chooses to clear it, ask Mr Reyes for more, or confirm fraud. Whatever Sam decides is kept with the result, along with the reason, so it’s there if an auditor or a complaint asks about it months later. You choose which results go to a person, and most teams send everything that doesn’t look genuine.
How documents reach Loupe
- Drop in a whole application as a folder or a ZIP. Each document gets a result, and so does the application, so two documents that can’t both be right are caught.
- Send them from your own systems through our API. You hear the moment each result is ready, and later what your team decided and why.
- Share a folder with us and each file is checked as it arrives.
- Pick results up in Desk if your team works its cases there. Each one lands on the case it belongs to.
- Attach the evidence pack to your own case file: one PDF per check, with the marked pages and the reasons.
If documents can’t leave your building, Loupe runs on your own servers
It makes the same checks with no connection to us. Point it at a folder or a ZIP and it writes a result beside each document. If you’d like it to check reference numbers against the registers, you can switch that on, and then only the numbers are sent to us.
What people ask us
Will Loupe reject an applicant?
No. It tells you what it found and where. Whether a document is accepted is always your team’s decision, and you can set which results go to a person.
Which documents does it work on?
Payslips, bank statements, invoices, utility bills, letters and similar documents, as PDFs, scans, phone photos, Word or Excel files, or emails with their attachments. If it can’t read a document properly it says so rather than guessing.
Can it tell when a document was made with AI?
Yes. A document generated whole has no edit to find, so Loupe looks for what a real issuer would never produce: the marks an image generator leaves, the labels AI tools write into their files, and reference numbers that can’t exist.
How long does a check take?
Most packs come back while the applicant is still on the phone. Large scanned bundles take a little longer, and you’re told the moment each result is ready.
Can it run without sending documents to you?
Yes. The offline version runs on your own servers with no connection to us and makes the same checks. Looking numbers up with the registers needs the internet, so it stays off unless you switch it on, and then only the numbers come to us, never the documents.
What happens to the documents we send?
We check them and do nothing else with them. Loupe learns only from documents we make ourselves. Yours are held apart from every other organisation’s, nothing is deleted while it’s waiting for someone to look at it, and anything marked as altered is kept for good. Every view and decision is logged against the person who made it.
Does it work with Nib and Desk?
Yes, and it works without them too. Nib checks whether the signature on a document belongs to the person, and in Desk each result lands on the case it belongs to.
How much does it cost?
£1 a document, pay as you go, however many pages it has. A document Loupe couldn’t read isn’t charged.
Bring a few documents you weren’t sure about, and we’ll go through them with you.
It’s £1 for each document checked, and nothing for one we can’t read.