Review the Statements archive
Use Statements to trace an imported `.qbo` file to its account, period, status, and imported bank rows.
If deleting an incorrect Statement succeeds but the archive cannot refresh, xBoox reports that deletion as completed. Refresh the page before trying to delete the Statement again.
Open Statements
From Banking, open Statements. The archive shows available information for each import, including:
- Statement Date or Period;
- Account;
- Bank Name when provided;
- File Name;
- Import Status;
- Transactions Imported;
- Uploaded At;
- available row actions.
Statements and Bank Transactions
Statements stores the import record. Bank Transactions stores the individual raw rows parsed from that statement. Posting, splitting, ignoring, restoring, and undoing happen in Bank Transactions, not in the Statements archive. The import preflight creates no archive record. If every row is already present in the selected account, xBoox reports that result without creating another Statement. One imported .qbo file creates one Statement archive record even when xBoox saves a large file in several internal batches. Transactions Imported shows the complete number of rows stored under that record. If saving is interrupted, importing the same file into the same account resumes that Statement record. It does not create another archive for the same file.
Supported source
Normal statement import supports .qbo only. A PDF is not a supported normal Bank Transactions import source, even if a current interface description refers to statement PDFs.
Delete carefully
Deleting a statement removes its archive entry and imported bank rows. It does not undo posted accounting entries or reopen completed reconciliations. Use it only to clean up an incorrect import after resolving linked Bank Transactions and reconciliation history through their correction workflows. Wait for the import to finish before considering deletion.
If Statement could not be deleted appears, none of that deletion was saved. Reload and review the statement and linked bank rows. Posted, matched or reconciled rows must be resolved through the existing correction workflows before deleting the import. Eligible deletion also clears transfer suggestions that link other bank rows to the removed rows.
If Statement import stopped appears because the statement was removed during import, the current batch was not saved. Earlier batches may already have completed and may have been removed with the statement. Reload Statements and Bank Transactions to review the current records before importing again.