Skip to content

Supported documents

Which PDFs, images, screenshots, and claim documents VerifyReceipt can inspect

Insurers should not have to guess whether the workflow covers their files. This page shows the document classes, image types, and review situations the platform is built to handle before payout.

PDF, JPEG, PNG, and TIFFBorn-digital PDFs, scans, screenshots, and phone photosReceipts, invoices, quotes, and supporting claim packets

What buyers ask first

Does it cover the files our team actually sees?

1

More than one kind of PDF

Native PDFs, scans, flattened exports, mixed text-on-image files, and stitched claim packets behave differently and should be treated that way.

2

Images are part of the workflow too

Screenshots, phone photos, and image-based receipts can still be useful evidence, but not with the same trust model as a clean original.

3

The point is clarity for the reviewer

The platform should tell the team what kind of surface they are looking at before asking them to rely on it.

File type

PDF

Born-digital invoices, scanned PDFs, flattened exports, mixed text-on-image PDFs, and multi-page claim packets.

File type

JPEG / JPG

Phone photos of receipts, clinic bills, repair paperwork, damage photos, and screenshot-style claim evidence.

File type

PNG

Screenshots, exported web confirmations, mobile-captured documents, and image-only receipts routed through the image-analysis path.

File type

TIFF

High-resolution scans and older workflow exports used in claims operations and document archives.

Document surfaces

The workflow is built for more than one kind of PDF

Claims files arrive as native PDFs, scans, screenshots, flattened exports, and image-based uploads. The point is not to force every file into one lane. It is to identify what kind of surface the reviewer is dealing with before relying on it.

Born-digital PDFs with embedded text and metadata
Scanned or flattened PDFs that behave more like images than native documents
Mixed PDFs with both rendered images and selective digital text overlays
Screenshots of confirmations, receipts, or portal views
Phone photos of receipts, invoices, or supporting claim paperwork

Document family

Receipts and expense proof

Low-value documents create high operational risk when they are duplicated, edited, or weakly supported.

  • Hotel folios and accommodation receipts
  • Pharmacy receipts and over-the-counter medical proof
  • Meal, taxi, and disruption expense receipts
  • Rental and transport receipts submitted for reimbursement

Document family

Invoices and bills

Higher-value invoices often drive payout decisions and deserve more than manual spot checking.

  • Medical invoices from clinics, hospitals, and specialists
  • Repair quotes, towing invoices, and parts bills
  • Builder invoices, make-safe invoices, and restoration paperwork
  • Provider invoices and treatment expenses across longer-running claims

Document family

Supporting claim documents

Claims files rarely contain one clean invoice. They contain mixed documents that need to be read together.

  • Specialist referrals and medical certificates
  • Repair estimates, scope documents, and appraisals
  • Supporting screenshots, exported confirmations, and claim attachments
  • Claim photos and image-based evidence paired with invoices or receipts

What happens when the file looks wrong

The system should make the problem obvious, not mysterious

If the same PDF appears again, the platform can flag the replay and link the earlier submission.
If a near-duplicate document appears with only a date, amount, or claim reference changed, the reviewer can compare the two side by side.
If a PDF or image carries flattening cues, suspicious regions, or screenshot laundering patterns, the case can be routed with reviewer guidance instead of a generic score.
If dates, totals, currencies, provider names, or line items do not fit the claim cleanly, the system can explain what to inspect before payout.