Deleting Statements, Files, and Accounts: What Happens Downstream

Deleting a statement removes the statement period itself, every transaction that was extracted from it, and every match or story membership that was applied to any of those transactions. The transactions are destroyed, not merely unassigned — you cannot reassign them to another statement or account. If those transactions were matched to check images, the matches are broken. If they were confirmed as part of a transfer match, that match is dissolved. Any categorization, notes, or custom fields applied to the individual transactions are also removed.

Deleting a deposit slip deliberately deletes every check image attached to it. This is not accidental cascade — Valid8's delete mechanism is designed to walk the parent-child chain recursively and remove every descendant of a deposit slip, up to 10 levels deep. If you delete a deposit slip, every Front (individual check image) that was grouped under it is deleted along with it. You cannot delete the deposit slip and keep its check images; there is no detach-first option.

Deleting an account removes every statement period tied to that account, every transaction in those periods, and every match involving those transactions. If the account participated in transfer matches with other accounts, those matches are broken. Account deletion also removes any custom fields, visualizations, or settings specific to that account. The account's file uploads (the original PDFs and CSVs) remain in the ALL FILES list, but they are no longer assigned to anything — re-creating an account with the same name does not automatically reconnect those files.

Deleting an uploaded file from the ALL FILES list — whether a statement PDF, a check image PDF, or a transaction CSV — does not automatically delete the data that was already extracted from it. However, depending on the file type, you may lose the ability to reprocess or re-extract it. For bank statements that have already been processed and assigned, deleting the source file leaves the extracted data intact but removes the original document. For check images, the extracted check items remain, but the underlying image file is gone.

If you delete a file in order to replace it with a corrected version, re-uploading can be blocked by duplicate detection. For files processed through Valid8's standard extraction pipelines — most bank statements and check images — duplicate detection is permanent and file-based. Deleting the extracted data inside Valid8 does not clear the duplicate record, so uploading the exact same file again will be rejected with a message that it has already been uploaded.

Your options in this situation are:

1. Make a trivial change to the file — add a blank page, re-save it from a different PDF tool, append a cover sheet — so that it is no longer byte-identical to the original. THIS WILL INCUR VPU COST.
2. Contact support to reimport.

Not every role can delete every object type, and the role requirements are strict:

• Deleting a statement or a check item (including a deposit slip) requires Engagement Owner on that specific engagement. Engagement User cannot delete statements or check items at all, regardless of the item's status.
• Deleting an account also requires Engagement Owner.