Voided checks are the easiest document in a loan file to fake — and the one underwriters check the least. This guide breaks down exactly what to look for on the MICR line, the routing number, and the account holder details before you fund a bad file.
- Cross-check the MICR line against the printed routing and account numbers — mismatches show up in roughly 1 in 20 voided checks submitted with MCA and working capital applications.
- A routing number that fails ABA validation is an automatic decline, not a follow-up question.
- ClearStaq flags voided check inconsistencies as one of its 27+ fraud signals in under 5 seconds per document.
- Reused check images across multiple applications are the single biggest tell in 2026 — run image hash checks before funding.
- Buy verdict: pair manual MICR review with automated cross-referencing against submitted bank statements before wiring funds.
Why this matters
A voided check exists to confirm one thing: the applicant controls the bank account they claim to control. When that check is doctored, altered, or pulled from someone else's file, the entire underwriting decision rests on a lie.
MCA brokers and lenders who skip this step end up wiring funds into accounts that don't match the business on the application. By the time the first payment bounces, the funds are gone. Check fraud detection software built for this exact failure point catches the mismatch before approval, not after default.
Voided check fraud isn't rare in 2026 — it's cheap to produce. Templates circulate on forums, and a doctored check takes under 10 minutes to generate with basic editing software. That's exactly why manual review alone misses it.
What you'll need
- The submitted voided check (original file, not a screenshot or re-scan)
- The applicant's bank statements for the same account, minimum 3 months
- Access to an ABA routing number lookup or a parsing tool that validates automatically
- The business's EIN and legal entity name from the loan application
- A document viewer that shows image metadata (EXIF/creation date)
- 10-15 minutes per file for manual review, or under 5 seconds with automated parsing
The steps
1. Validate the MICR line against the printed numbers
The MICR (magnetic ink character recognition) line at the bottom of the check should match the printed routing number, account number, and check number exactly. Fraudsters often edit the printed numbers but forget the MICR line still reads the original account — or vice versa.
Zoom to at least 300% and compare digit by digit. A single-digit mismatch between MICR and print is a hard stop, not a clarification request. Common mistake: reviewers eyeball the numbers at normal zoom and miss a transposed digit in the account number.
2. Run the routing number through ABA validation
Every valid routing number passes a checksum formula defined by the American Bankers Association. A routing number that fails this checksum was either typed incorrectly or fabricated — there's no third option. Cross-reference the resulting bank name against what's printed on the check; a routing number for a credit union in Ohio paired with a check header for a bank in Florida is a fabricated document.
Expected outcome: routing number resolves to the exact bank name printed on the check. Common mistake: skipping this because the check looks real — visual design tells you nothing about the encoded routing data.
3. Match the account holder name to the entity on file
The name printed on the voided check must match the legal business name or authorized signer listed in the loan application, not a DBA, not a personal name, not a similarly-spelled variant. A voided check under an individual's name submitted for a business loan application is a red flag for undisclosed ownership or a straw borrower.
Cross-check the EIN against IRS records where available. Businesses that recently changed names or restructured should have documentation explaining the mismatch — absence of that paper trail is itself a signal.
4. Cross-reference the account number against submitted bank statements
The account number on the voided check must match the account number on the bank statements submitted in the same file. This step catches the most common fraud pattern: applicants submit legitimate statements from one account and a voided check from a different one they actually control, hiding a second account with weaker cash flow.
Parsing tools that read fake bank statements alongside voided checks catch this automatically by comparing account numbers across every document in the file within the same pass.
5. Check font and print consistency
Legitimate checks are printed by a single print run with uniform font weight, spacing, and ink density across every character. Doctored checks show subtle font shifts — a slightly different typeface on the account number, uneven kerning, or ink that looks digitally overlaid rather than printed.
Open the image at full resolution and scan character by character along the bottom line. Expected outcome: identical font, spacing, and ink tone across the entire line. Common mistake: reviewing a compressed PDF where font artifacts get smoothed out — always request the original file format.
6. Check image metadata for manipulation
Open the file's metadata (EXIF for images, document properties for PDFs) and check the creation and modification timestamps. A voided check edited in image software shows a modification date that doesn't match the original scan or photo date — sometimes months apart.
This step also flags checks edited in tools like Photoshop or GIMP, which embed software signatures in the metadata even after the visible edits are cleaned up.
7. Run duplicate detection against prior submissions
The same voided check image gets reused across multiple loan applications — sometimes from the same broker shopping a deal to five lenders, sometimes from an outright fraud ring recycling a stolen account. Hash the image file and compare it against previously reviewed submissions.
A voided check that matches a hash from an unrelated application filed weeks earlier under a different business name is not a coincidence. This is one of the fastest wins in 2026 fraud review because it requires zero human judgment — the match is binary.
Troubleshooting
Applicant says the account is new and no printed check exists yet. Request a bank letter on official letterhead confirming the account number and routing number instead of accepting a blank or handwritten voided check.
MICR line is present but the account number field is blank. Treat this as incomplete, not verified — a partial MICR read means the file needs a fresh submission, not an approximation.
Business name doesn't match but applicant claims a recent rebrand. Require the EIN update letter or amended articles of organization before accepting the explanation; verbal claims of rebranding are the most common cover story for account mismatches.
Check image resolution is too low to verify font or MICR detail. Reject the submission and request a higher-resolution scan or the original PDF — never approve based on an unreadable document, regardless of how minor the flag seems.
Routing number is valid but resolves to a bank the applicant has never mentioned. This usually means the account belongs to someone other than the applicant. Flag for manual review and request bank statements confirming ownership of that specific account.
Multiple applications share the same voided check hash. Escalate immediately — this pattern shows up in structuring patterns tied to coordinated fraud rings, not isolated applicant error.
Tools and resources
- ABA routing number validator (checksum lookup)
- Document viewer with EXIF/metadata support
- Image hashing tool for duplicate detection across a file archive
- A parser that cross-references voided checks against bank statements and tax documents in the same pass, catching mismatches in seconds instead of a manual 10-15 minute review per file
- IRS EIN verification for entity name confirmation
What to do next
Manual voided check review catches obvious fraud but misses reused images and metadata tampering unless you're checking every file by hand. Teams that automate bank statement review alongside voided check validation cut per-file review time from 15 minutes to under 5 seconds, and catch cross-document mismatches a human reviewer would need three separate systems to find.
FAQ
What is the fastest way to detect a fraudulent voided check?
Cross-check the MICR line against the printed account and routing numbers, then validate the routing number against ABA checksum data. A mismatch on either check is an automatic decline in 2026 underwriting workflows, not a request for clarification.
Can a voided check pass fraud checks but still be tied to fraud?
Yes. A technically valid check can still belong to an account the applicant does not control if the account number does not match the submitted bank statements. Always cross-reference the account number across every document in the file.
How much does voided check fraud cost lenders in 2026?
Exact loss figures vary by lender and loan size, but a single funded deal into a mismatched account results in total principal loss with no recourse, since the funds land in an account the borrower does not control.
Is a blank or handwritten voided check a red flag?
Yes, unless paired with an official bank letter confirming the account and routing numbers. Handwritten voided checks with no printed MICR line should never be accepted as standalone verification.
How do you check if a routing number is real?
Run it through an ABA checksum validator, which confirms the number follows the required mathematical formula. A routing number that fails this check is either mistyped or fabricated.
Do fraud detection tools catch reused voided check images?
Yes, when the tool hashes submitted images and compares them against a database of prior submissions. A matching hash across unrelated applications is one of the clearest fraud signals available in 2026.
What is the difference between a font mismatch and a print quality issue?
A font mismatch shows different typefaces, spacing, or ink density within the same line of text, which indicates editing. A print quality issue affects the entire document uniformly and does not isolate to specific characters.
Should underwriters manually review every voided check?
Manual review works at low volume but misses metadata tampering and duplicate images at scale. Automated parsing that checks MICR, routing validation, and image hashing in one pass catches what manual review consistently misses.
One last thing
The check that looks the most legitimate is often the most dangerous one — fraud rings polish the visual details because they know reviewers scan for obvious red flags first. The MICR line and the metadata do not lie the way a printed layout can; that is where the real signal lives.
Related guides
ClearStaq Team
Content Team
The ClearStaq team builds AI-powered tools for bank statement parsing, fraud detection, and income verification.
