The bank export is rejected
The destination says the file is invalid without identifying the broken header, XML structure, or required metadata.
Bank file import checks
Bank file won't import? Find out why.
Check OFX, QFX, QBO, CAMT.053, MT940, and BAI2 files for free before retrying an import. See likely blockers and next steps; repair is available only for selected OFX, QFX, and QBO issues.
No signup required Private file checking OFX, QFX, QBO, CAMT.053, MT940 & BAI2
Import failures
Does this sound familiar?
Bank-file failures often hide behind vague import errors. Check the file to see what may be wrong.
Transactions are missing
A malformed date, amount, account block, or duplicate transaction identifier can make part of a statement disappear.
The next import creates duplicates
Unstable or reused FITID values can make the same transactions look new—or cause legitimate transactions to be skipped.
The account will not map
QuickBooks and Quicken may reject a readable file when institution, account, or destination-specific markers do not match.
CAMT.053 works in one system, not another
Namespace versions, balances, dates, references, and destination mappings can differ even when the XML is well formed.
A DATEV workflow breaks downstream
The supported source bank file, a conversion step, or the DATEV import profile may be responsible. Native DATEV files are not parsed here.
A controlled diagnostic pass
How it works
Check your file for free
Upload or paste an OFX, QFX, QBO, CAMT.053, MT940, or BAI2 file. No account is needed to check it.
See what may block the import
Review likely problems, practical next steps, and whether this file has a supported repair.
Choose your next step
Correct or regenerate the source file, or choose a repair for an eligible OFX, QFX, or QBO file. A repaired download is offered only after verification confirms improvement.
Current supported scope
What CorrectBankFile diagnoses
Structural diagnosis helps identify likely blockers. It is not exhaustive schema validation, accounting advice, or a guarantee that every destination will accept the file.
OFX SGML and XML structure
Headers, root structure, encoding declarations, and recognizable OFX-family content.
Account and institution metadata
Account blocks, account types, bank identifiers, and QBO/QFX destination markers.
Dates, amounts, and transaction IDs
Malformed timestamps, suspicious amount values, missing IDs, and duplicate FITID values.
Bounded CAMT.053 structure
Namespace version, statements, accounts, balances, entries, dates, currencies, and references.
MT940 bank statement structure
Core statement tags, balances, transaction lines, dates, currencies, and bounded profile-aware diagnostics.
BAI2 bank statement structure
Core record hierarchy, continuations, counts, trailers, currencies, and bounded control-total diagnostics.
Sensitive finance data
Privacy deserves more than a footnote
Bank files may contain account identifiers, balances, transactions, payees, and memo text. CorrectBankFile processes the submitted file for the diagnostic request and avoids storing raw financial payloads by default.
Developer and integration questions
Evaluating a bank-file integration?
The public product is the web checker. General-purpose API keys, public schemas, and self-service developer access are not currently offered, but the integration overview explains the current position.