Statement review log

What goes in each statement row

After adding a statement, choose Edit to enter its printed opening and closing balances. Then count converted transactions and record how many rows you compared with the PDF. Leave a count blank if you don't know it yet.

The difference is opening balance plus transaction sum minus printed closing. Take the fictional March example: 2,400.00 plus -22.95 gives 2,377.05, compared with a printed closing balance of 2,365.05. That leaves 12.00. Restoring the missing -12.00 source fee changes the sum to -34.95 and the difference to 0.00.

You can type the transaction sum or load a converted CSV. For a CSV, confirm its columns, number separators and balance perspective, then review the old and new values before choosing Apply. Only this statement's sum and converted count change. The source and previous values go into notes, but review status stays unchanged.

A zero difference isn't a sign-off

The log uses exact integer cents rather than floating-point money. It flags invalid dates or counts, mismatched expected and converted counts, and nonzero closing differences. Reading a CSV is separate from passing the selected amount-format checks. If amounts remain unresolved, there's no complete sum to show, so the log won't present a partial one as complete.

Even a zero difference doesn't prove every row is right. The log doesn't read PDFs, verify your row count, compare transactions with your bookkeeping ledger, authenticate statements or test an accounting importer. Reviewer initials and status are entries you supply, not an electronic signature or independent approval.

You don't have to finish the review before exporting. CSV and printable exports keep all entered values, incomplete checks, warnings and nonzero differences. For sign-off practice, see the review-log method and four-statement handoff example.

What the log can accept

Each statement needs one currency, included in the account label. Enter log amounts with a decimal point, no grouping and at most two decimal places; other currency precisions and exchange-rate conversion aren't supported. Dates use YYYY-MM-DD. If you type a sum, it isn't independently checked against transaction rows.

The optional CSV input accepts UTF-8 CSV or text up to 5 MB, with either one signed amount column or two split columns. For credit cards, the signs must describe the same balance perspective as the printed balances. Before using a computed sum, fix CR/DR suffixes, subtotals, repeated headers or malformed rows in a separate working copy. The original file is never edited.

The template is this tool's working format, not an accounting import format, and computed values are snapshots rather than spreadsheet formulas. To recalculate after edits, restore an unchanged export with its header and protection metadata intact. If you fill in a downloaded blank CSV elsewhere, you'll need to return here for calculations or do them yourself. Import identifiers into spreadsheets as text so leading zeros and long references survive. Keep the untouched CSV too, so you can restore it here without losing data.

Save before you leave

File contents, filenames and form entries stay in browser memory for processing. This tool doesn't upload them, save them to browser storage, send them to analytics or put them in URLs. Download saves the requested CSV to your device, while the printable view creates a local browser-window copy. Close that window when you're finished.

There's no autosave or server copy, so download before leaving and check that the file arrived before choosing I saved this version. Back navigation may restore page memory, but Clear log or reload clears this page, and a new page starts blank. The leave-page warning is attached only while the log differs from its saved version, and browsers don't always show it. Printing doesn't mark the editable log as saved. Your browser, downloads folder, backups and printer have their own retention behavior.

Where the template's rules come from

The template is dated October 17, 2026. You can use and adapt the blank or fictional filled CSV for your own or client work. It follows the comma, quote and line-break conventions in RFC 4180, rather than a universal bank schema.

Exported text gets a protective apostrophe where needed because spreadsheets can read text as formulas. OWASP's CSV injection guidance, checked October 17, 2026, explains this risk and why re-saving may remove that protection. There's no universal spreadsheet-safety guarantee, so don't enable formulas or external content from untrusted notes.