Document intake
The file is saved server-side for a statement-only review job, retained for 24 hours after upload, and then pruned with its review artifacts. You can delete a completed review sooner through the review controls or API.
Screen uploaded bank statements for suspicious signals, document-type mismatch, inconsistent totals, missing statement fields, visible IBAN issues, and other review evidence. Login is required for file upload.
The file is saved server-side for a statement-only review job, retained for 24 hours after upload, and then pruned with its review artifacts. You can delete a completed review sooner through the review controls or API.
IBANs and supported domestic routing identifiers are checked independently from the AI review.
The agent returns parseable JSON for score, evidence, inconsistencies, and next steps.
Every completed review can be downloaded as structured JSON for case files, QA evidence, or API integration. Teams get predictable monthly capacity without turning a risk score into an automatic approval decision.
View multipart API and polling contractThe validator focuses on practical risk triage: does the upload look like a real bank statement, are core fields present, do visible numbers and dates make sense, and do supported account identifiers validate?
No automated tool can prove authenticity from an uploaded file alone. IBANgen returns a risk score and evidence to support review.
The report can flag document-type mismatch, missing bank-statement fields, weak transaction structure, inconsistent amounts, invalid identifiers where present, and other visible review signals. Absence of IBAN alone is not a risk for non-IBAN jurisdictions.
Screenshots can be reviewed, but original PDFs downloaded from a bank portal usually provide stronger evidence for review.
Upload a statement to generate the report.