Create a year and account inventory
Inventory every account used during the year with owner or entity, currency, institution, opening or closing status, and statement frequency. Note changes and closures so an absent final statement becomes detectable.
File by the covered statement period, not the download date. A January issue may close a December cycle and, depending on the recordkeeping method, belong with the prior year's activity.
Give every expected account-period combination an inventory row containing institution, masked account, dates, issued filename, receipt status, pages, supporting-record status, reconciliation outcome, and scheduled retention review. This exposes missing months and distinguishes received from reviewed files, even when folders appear complete but contain duplicates or unreconciled periods.
Maintain an inventory with one row for every expected account and period. Include the bank, masked identifier, coverage dates, original file name, arrival state, pages, reconciliation result, linked-evidence state, and next retention check. The inventory should distinguish missing, received, reviewed, and superseded files. A folder can look complete while one account is missing February, another statement is duplicated, and several files have never been reconciled. Coverage is demonstrated by the inventory, not by the number of files in the directory.
Use filenames that identify the source
Use a filename pattern that identifies year, period end, institution, masked account, and document type. Exclude full account numbers and unstable labels such as final or latest.
Preserve the issued file unchanged. Converted workbooks, annotations, reconciliation schedules, and tax workpapers should remain separate and carry clear versions or statuses.
A useful filename identifies the institution, year, period end, document type, and account mask, for example 2026-03-31-examplebank-4821-statement.pdf. Omit full account numbers because filenames surface in indexes, sync logs, screenshots, and email subjects. Reserve labels such as final for controlled statuses and version converted or annotated files separately from the issued original.
Track completeness and review state
Track every expected statement through separate received, verified, reconciled, evidence-complete, and reviewed states. Downloaded does not mean reconciled or suitable for tax reporting.
The manifest should record filename, period, account, any checksum, review state, unresolved issues, and retention basis. Those fields make omissions and unexpected changes easier to identify.
Use a status vocabulary that distinguishes source presence from review completion. Received means the file arrived; verified means account, period, page count, and readability were checked; reconciled means the period passed its balance and ledger controls; supported means required related records are linked. A file can be received but unreadable, or verified but still unreconciled. Store the status and reviewer date in the inventory rather than encoding it only in filenames, which can become misleading when work is reopened or corrected.
Recommended archive layers
Separate source evidence, working material, and completed records so an edit can never replace the issued file.
Originals
Store issued statements without modification under filenames based consistently on their covered periods.
Working records
Keep extracts, reviewer notes, evidence packets, and open-item registers in the working layer.
Completed controls
Connect reconciliations, category summaries, and review approvals to the relevant period.
Retention manifest
Maintain account inventory, file register, backup state, retention basis, review date, and disposal history.
Protect retention and disposal
Schedule retention review according to the relevant tax, property, employment, legal, insurance, or contractual need. Passing a generic number of years is not, by itself, deletion authority.
Protect archives and backups with encryption and restricted access, test restoration, and securely dispose of authorized paper and digital records. Keep a deletion record naming the applicable retention rule.
Perform year-close testing from the inventory: confirm each expected period appears once, source files open, page counts are plausible, reconciliations have statuses, evidence links work, and permissions match retention. Log gaps and duplicates before making the archive copy, then encrypt and back up according to sensitivity and schedule retention review rather than preserving every working file indefinitely.
Run a year-close test before archiving. Confirm every expected period is present once, source files open, page counts are plausible, statement periods do not overlap unexpectedly, evidence links resolve, and access permissions match the retention plan. Record exceptions before creating the archive copy. Keep converted spreadsheets and annotated working files separate from issued originals, and schedule the next retention review. Deleting by folder age alone can remove records still needed for property, legal, employment, insurance, contractual, or current jurisdictional purposes.