Over the past 18 months, we have seen a measurable shift in the quality of fraudulent documents submitted through our customers' pipelines. Documents that would have required professional graphic design skills to fake two years ago are now being produced by non-technical fraudsters using freely available AI tools. The volume has also increased: AI-generated document fraud is up 400% since January 2024.
Invoice fraud is the most common entry point. Invoices are the highest-volume document type in most accounts payable and expense workflows, which makes them the highest-value target. As the FBI IC3 advisory on Business Email Compromise highlights, a convincing fake invoice is now one of the most accessible fraud vectors in corporate finance.
What changed
The arrival of capable AI image editing models - and more recently, document-specific generation models - has fundamentally changed the cost structure of invoice fraud. Previously, creating a convincing fake required either access to the original digital file, graphic design skills, or a willingness to pay someone who had both. Today, a fraudster with a smartphone and a legitimate invoice as a reference can produce a convincing fake in under 10 minutes.
The fake starts as a real invoice, so its text stays consistent
A reference invoice and free tools are all it takes. No step needs design skill or the original digital file.
- 1.Start from a legitimate invoice as the reference image
- 2.Inpaint the target fields: amount, date, vendor name or bank details
- 3.Render the new text in the original font, weight and spacing
- 4.Rebuild the metadata with plausible creation and modification times
Valid amount, real vendor name, unique invoice number: nothing is left for a text rule to catch.
The specific capabilities that matter are: inpainting (editing a specific region of an image while preserving the surrounding context), text rendering (generating text that matches the font, weight, and spacing of the original), and metadata reconstruction (producing a file with plausible creation and modification timestamps).
How the AI forgery shift changed key fraud metrics between 2022 and 2026.
Why this matters for finance teams
The fraud detection stack at most companies was built for an older threat model. Rule-based systems - flag duplicates, check amounts against policy limits, validate vendor names - catch opportunistic fraud. They fail against AI-generated documents because the document is indistinguishable from a legitimate one at the text level.
Attempts are up 400%. Traditional detection still sits at 22-41%.
The fraudster's cost to produce a convincing fake has dropped to zero. The defender's text-level checks have not moved.
- 22-41%defender's detection rate using traditional tools
This creates an asymmetry: the fraudster's cost to produce a convincing fake has dropped to zero, while the defender's detection rate using traditional tools remains at 22–41%. The ACFE Report to the Nations documents how the expected value of fraud has increased dramatically. This is reflected in the volume: we see more attempts, not fewer, as the economic calculus has shifted.
What pre-OCR detection does differently
Hesper AI operates before your OCR pipeline reads the document. We analyze the raw pixel data - detecting generation artifacts, editing artifacts, compression inconsistencies, and font rendering anomalies that are the byproduct of AI-based document manipulation.
- Generation artifacts left by diffusion models in synthetically created documents - subtle statistical patterns in pixel distributions that real documents do not exhibit
- Editing artifacts from inpainting and clone stamp operations - compression discontinuities at region boundaries
- Compression inconsistencies in regions that have been modified - JPEG re-encoding creates characteristic artefact patterns
- Font rendering anomalies that indicate character replacement - sub-pixel rendering differences between original and inserted text
The output is a fraud score from 0 to 100, a verdict (LIKELY_FRAUD / INCONCLUSIVE / LIKELY_GENUINE), and an array of findings with pixel coordinates, severity ratings, and human-readable descriptions. The structured output routes directly into your existing review queue.
The pixel check runs before OCR, and clean invoices flow on unchanged
Read left to right: the raw image is scored, the score routes it, and a reviewer gets the exact region to inspect.
- 01Pixel analysisGeneration, editing and compression artifacts read from raw pixels
- 02Font checkInserted characters compared with the original text rendering
- 03Score and verdictFraud score 0-100: likely fraud, inconclusive or likely genuine
- 04FindingsPixel coordinates, severity and a plain description for each
- Exact region to inspect
- Clean: on to OCR, unchanged
What to do about it
The architectural fix
Add a fraud detection API call before your OCR step. Each document is analysed in seconds - not hours - and the entire class of AI-generated fraud that your existing rules cannot see is caught automatically. Most teams integrate in an afternoon against any document workflow - AP automation, expense management, or loan origination.
- Before passing each invoice to your OCR pipeline, send the raw image to the Hesper API
- Receive fraud score (0–100), verdict, and findings array inline
- If score exceeds your threshold (typically 65–75 for invoice workflows), route to focused review queue
- Pass the findings and coordinates to reviewers so they know exactly where to look
- If clean, continue to your existing OCR and approval flow unchanged
Invoice fraud is one piece of a larger problem. For the full picture, see our 2026 document fraud statistics report. If your AP team processes vendor invoices at scale, our post on accounts payable fraud and document forensics covers the specific schemes and detection patterns.
Key takeaways
- AI-generated invoice fraud is up 400% since January 2024, driven by free tools requiring no technical skill.
- AI-generated invoices pass OCR validation in ~95% of cases - text-based checks cannot catch them.
- The manipulation is detectable only at the pixel level: generation artifacts, compression inconsistencies, font rendering anomalies.
- A pre-OCR API call completing in seconds catches what rules-based and OCR systems miss entirely.
- Most teams can integrate a pre-OCR fraud layer into their existing pipeline in an afternoon.