Statement review log: leave a record someone else can follow

Fill in the log as you go

The browser-local template needs no signup, email or upload. You get a blank CSV, a four-statement example and an editable log that calculates closing differences, with download sizes beside the buttons. When you print, each statement expands into fields rather than squeezing twenty columns onto one page.

Begin with the source filename and period, adding counts and balances as you check them. Download before leaving because there's no autosave. Back navigation may restore page memory, but Clear log or reload clears it, and a new page starts blank. Restore your last exported CSV to continue reliably. Its figures are snapshots, not live formulas.

This is for bank and credit-card extraction reviews, not a prescribed audit or tax form. Amounts use two decimals and one balance perspective per statement. The sources below cover US QuickBooks Desktop and US federal business records, but neither endorses the template or certifies compliance.

The template is dated October 17, 2026, and you can adapt it for your own or client work. Keep an untouched downloaded CSV for restoration, though: editing headers or protective metadata in a spreadsheet can prevent restoration.

Let the next reviewer see where you stopped

“March final” doesn't say whether you checked the fee page, counted five transactions or five spreadsheet lines, or compared only the closing total. Your colleague needs those details without having to ask you.

Reading a CSV, checking its arithmetic and reconciling the books answer different questions. Reading means a program could interpret the CSV's structure. Arithmetic tells you whether the entered balances and transaction sum agree, while bookkeeping reconciliation compares statement transactions with the books. Authenticity is a fourth question, outside all three.

Intuit's QuickBooks Desktop reconciliation help, updated August 5, 2026, lists changed, missing, duplicate or uncleared transactions and incorrect balances as causes of reconciliation differences. A clean extraction alone can't settle those ledger questions. Write “extraction review complete; books not reconciled” if that's where you stopped.

What each column is for

An authorized colleague needs enough detail to find the source, not unnecessary personal information. Identify the client or entity with an account alias and currency, not a full account number, and don't combine currencies. Use the exact PDF filename because a folder name alone doesn't identify the statement.

Enter the printed period in YYYY-MM-DD, even if it crosses months or has no transactions. First and last activity dates aren't a substitute. The page count includes every PDF page, not just those extracted.

A blank count means you don't know, not zero. “Rows expected” is the bank's printed transaction count, if supplied; manual counts belong in notes. “Rows in converted file” counts transactions rather than headings, totals or wrapped description lines. For “Rows checked”, count only transactions you actually compared, so the log doesn't claim a review you haven't done.

Opening and closing balances come from the statement, not spreadsheet totals. The transaction sum uses net signed movements, not the balance column: computed closing is opening plus transaction sum, and difference is computed minus printed closing. A balancing plug would hide the problem, so leave any nonzero result visible.

Initials and a review date tell someone who checked it and when, but don't grant automatic approval. Status describes progress, not whether the difference is zero. “OK” alone isn't enough for notes; record the evidence, corrections and next actions someone will need.

Amount fields take a decimal point, no thousands separators and at most two decimal places. CSV sums need an explicit choice of source separators because the tool won't guess what 1,234 means or resolve credit-card signs. If you're unsure which figures to copy, check the guides to dates and number formats and credit-card signs.

What a four-statement handoff looks like

Fictional Cedar Studio is a synthetic example, not customer data or a measured conversion run. All amounts are USD, with positive money in and negative money out for the operating account. January and February extraction reviews are complete, but March operating has a missing fee. March reserve has a correct total, yet its source comparison is unfinished.

January's three transactions are +800.00, -500.00 and -50.00, summing to +250.00. February's are +1,000.00, -800.00 and -50.00, summing to +150.00. Reserve has +150.00 and +5.00, summing to +155.00. Each operating closing agrees with the next opening, but that alone doesn't establish complete transaction details.

The download records two PDF pages per operating statement and one for reserve. Initials AB and date 2026-04-02 mark the operating review; CD and 2026-04-03 mark reserve. These are fictional entries, not identities the tool verified. Reserve stays in review until its interest row is compared, despite the zero difference.

The missing fee explains the 12.00 difference

The March operating example uses the same transactions as our statement CSV review guide. Its first conversion contains +1,200.00, -1,150.00, -86.45, +42.50 and -29.00. Those five rows sum to -22.95. Adding the printed opening 2,400.00 produces 2,377.05, which is 12.00 above printed closing 2,365.05.

Page 2 of the fictional PDF has transaction 6: a -12.00 monthly service fee. Restore it with its source date and description, rather than a generic -12.00 adjustment that merely forces the total to work.

A correction note could read: “Review copy v1 omitted monthly fee, PDF page 2, transaction 6. Added source-backed -12.00 fee to v2; sum changed from -22.95 to -34.95. All six source rows rechecked; closing difference now 0.00.” Include the correction date and reviewer, and only write that last sentence after comparing all rows.

The download stops at “difference found”: the correction is identified, not applied. Knowing the likely fix isn't the same as making and checking it. Keep the earlier snapshot if your process needs to show how you closed the exception.

Record each check for what it tells you

1. Once you've listed the PDFs and printed periods, the coverage checker can check for missing or overlapping statement periods, not gaps between transaction dates.
2. Compare converted rows with their sources, using the balance checker for added running-balance diagnostics if those balances are available. Record the check and keep its exception report so the log has supporting evidence.
3. Before merging files, investigate overlaps with the overlapping CSV guide. Matching amounts alone aren't grounds to delete a transaction.
4. Record import preparation separately because a QuickBooks CSV check or Xero CSV check checks format, not source accuracy. You still need an actual import preview and later ledger reconciliation.

Loading a transaction CSV previews the old and new sum and count before applying them, then appends those values and the CSV filename to notes. It doesn't embed the file, check transaction dates or change status. Keep that CSV with the log so someone else can reproduce the sum.

Sign off only on the work you did

The status follows the work: “not started” once you've listed a statement, “in review” while checks remain, and “difference found” for an unresolved exception. “Resolved” means you've finished your stated review and addressed exceptions. These are template conventions, not industry certifications.

The recipient needs the exact PDF and reviewed file version, enough detail to repeat the arithmetic and find corrections, and an honest count of rows compared. They also need to know who owns each next action. To preserve the first reviewer's initials, date a second review in notes instead: “CD, 2026-04-03: repeated March closing check and inspected restored fee in v2; no additional source comparison performed.”

Changing a balance to remove a flag leaves the problem behind. Intuit's Desktop guidance warns that reconciliation adjustments don't fix underlying errors. Our balanced-statement explanation shows why offsetting mistakes can also leave zero difference.

Keep the files, not just their names

A filename isn't a backup or attachment, so keep the original PDF, untouched conversion, reviewed version and log together under your existing access and retention controls. When correcting reviewed data, save a new version rather than annotating your only original.

For US business records, the IRS recordkeeping page, checked October 17, 2026, distinguishes books from supporting documents: substantiating an expense may need several documents. The log can't replace receipts, invoices or other required context. This article sets no retention period; follow the rules for your records and engagement.

The CSV export quotes embedded commas, quotes and line breaks as described in RFC 4180. Formula-like notes get a protective apostrophe and round-trip metadata. OWASP warns that saving and reopening in a spreadsheet can remove protection, so don't enable formulas or external content from untrusted notes. Keep the original export for restoration. Aliases and identifiers need importing as text because CSV can't enforce column types. Microsoft documents how Excel can remove leading zeros or truncate long identifiers. The original CSV preserves them for restoration here.

Before leaving, download the log, check it arrived and acknowledge it in the tool. Don't rely on leave-page warnings: they're a backup, not autosave, and MDN documents that these warnings are unreliable on mobile. Downloads and printouts stay under your own controls, and local print windows should be closed when you're finished.

If only PDFs remain, check for a bank-native export or prepare rows manually first. AnyStatement can extract reviewable data with source-linked rows if you need that separate conversion step. Keep the original PDF and check the rows whichever route you choose.

What we checked, and what we didn't

On October 17, 2026, we opened the linked Intuit, IRS, RFC, OWASP and MDN sources and independently checked all four fictional statements and the missing-fee correction with Python Decimal. The sums are January 250.00, February 150.00, incomplete March -22.95 and reserve 155.00. Corrected March sums to -34.95 with zero closing difference.

We tested the browser tool with fictional CSVs: 10,000 rows, malformed records, ambiguous separators, exact large amounts and formula-like notes. Downloads restored commas, quotes, line breaks, Unicode and leading-zero identifiers. We inspected a PDF of the print view and saw no requests during CSV processing. This involved no real customer statements, live bookkeeping imports, professional audit approval or authenticity checks. Spreadsheet save/reopen behavior and physical printing weren't tested across products or devices.