“The file does not contain any account information”
Beyond the transactions, an OFX file states which account they belong to. Importers use that to route the data, and a file without it has nowhere to be filed — hence a rejection that says nothing about the transactions themselves, which are usually fine.
Symptoms
An error about missing or invalid account information The import runs but never offers an account to import into The file was produced by a converter rather than downloaded from the bank
What actually causes it
The converter omitted the account block
Tools that turn CSV into OFX often write the transaction list without a BANKACCTFROM aggregate containing BANKID and ACCTID, because they were never told the account number.
The bank exported a generic file
Some export options produce a transaction list intended for spreadsheets rather than a complete OFX document.
The account block was damaged by editing
Hand-editing a file to fix something else can remove or unbalance the account aggregate.
How to fix it
- Drop the file into the fixer below to confirm the transaction data is intact and to repair any structural problems it finds.
- Open the file in a text editor and look for BANKACCTFROM with BANKID and ACCTID inside it — that is the block importers require.
- If it is absent, prefer downloading a proper OFX/QFX from the bank over patching, because the account and routing numbers must be genuine to route correctly.
- If your bank offers no OFX at all, CSV import with manual account selection avoids the whole problem.
Related import problems
Skip the manual edit — fix it automatically
The fixer validates structure and transactions; it deliberately does not invent account or bank identifiers, because a wrong one files your money in the wrong ledger. Free, no signup, no upload.
Open the fixer