Check your records
Statement coverage checker
Compare printed statement periods, account by account, to spot gaps and overlaps. Uncovered dates don't mean a statement is missing.
By AnyStatement
Published , 3 min read
Enter printed statement periods, not transaction dates. Keep account aliases consistent; don't use full account numbers. Check up to 300 statements against one review span for all listed accounts.
| Row | Account label | Statement start | Statement end | Source name (optional) | Action |
|---|---|---|---|---|---|
| 1 |
Manual input selected. No file was read.
Format checks: not complete.
Date coverage: not checked. Fix input errors and approve any date interpretations first.
Balances: not checked. This tool reads no transaction amounts.
The printed periods are what count
You'll need each statement's account alias and printed start and end dates, not its first and last transaction dates. Source names are optional. Enter rows directly, paste a spreadsheet table or load a UTF-8 CSV or text file. Choose the delimiter, confirm whether the first row has headings and map the columns so the fields are read correctly. Then set the source date order and review span.
The start and end dates both count. The tool sorts and combines each account's periods before comparing them with your span. So a period ending March 15 followed by one starting March 17 leaves March 16 uncovered. If both include March 15, that day overlaps. It doesn't assume one statement per calendar month.
The fictional example checks March 1 through March 31, 2026. Checking covers 30 of 31 days, leaving March 16 uncovered. Two checking documents overlap March 30 through April 5, partly outside the span, while savings covers all 31 days. The report points back to the input rows for each overlap and outside-span portion.
A gap isn't proof of a missing statement
Uncovered dates only mean your entries don't cover those days. They don't mean a statement is missing or anything is wrong: an account may have opened or closed during the year. Overlaps don't prove duplicate transactions, and full coverage doesn't prove every page or transaction is present.
The format checks catch invalid dates, reversed periods, missing account labels, unresolved columns and inconsistent CSV row widths. Findings show sorted periods, gaps within your span, overlaps across all entered periods, and portions outside the span. Whenever the overlapping statements change, a new overlap segment starts.
You'll still need to check the account list and document contents yourself, because this checks dates, not balances, bookkeeping reconciliation, statement authenticity or acceptance by a tax authority or other destination.
Before you trust the result
The limit is 300 statements against one review span and 5 MB for files and pasted text. The tool takes .csv or .txt, not PDF, XLSX or bank feeds, so paste tab-separated spreadsheet cells or save TSV as .txt. Unmapped columns stay in your input but aren't checked or included in findings.
Account aliases must match exactly, including case and spaces. Check your labels because two aliases split one account, while a shared alias wrongly combines two accounts. Accounts you haven't listed can't produce findings.
Dates need four-digit years, without weekdays or timestamps. After choosing the numeric date order, review the conversions to YYYY-MM-DD. The tool uses UTC day numbers so local timezones or daylight-saving changes don't add or remove days. It doesn't perform currency arithmetic.
Nothing is silently removed, so you remove manual rows yourself. Errors block findings downloads. Entered-period rows keep original date strings and source names, but findings reference row numbers rather than repeating source names for overlaps. If text starts with a spreadsheet formula marker, you'll need to review and approve apostrophe protection before exporting. Spreadsheet handling varies, though, so this isn't a universal safety guarantee.
What stays in your browser
Your inventory is processed in the browser tab, with no upload, server transfer or browser storage. To discard it, clear all inputs or reload: navigating away and back can retain inputs in memory. Downloading saves findings to your device.
Since the CSV includes account aliases and source names, choose labels you're comfortable putting in a workpaper. Keep reports with your records, and share them through the channel agreed with your preparer. The separate PDF converter uses a different, explicit upload workflow.
Keep the original tax records too
For US federal recordkeeping, the IRS records guidance, reviewed or updated August 3, 2026, describes supporting documents for income and expenses. Its audit records request page, reviewed or updated January 17, 2026, says to organise records by year and type of income or expense and include a transaction summary.
We checked those pages on October 17, 2026. Neither prescribes this algorithm or endorses this tool, so keep the report as a document inventory alongside original statements and other evidence. This isn't tax advice, and state and non-US rules aren't covered.