← James M. Owens
Runs in your browser · nothing is uploaded

Project 01Assurance tooling

Bank
Reconciliation

Match a bank statement to the cash book and work through the differences.

I used a fictional student club for the sample reconciliation. One cheque cleared the bank for $56.40, but the club recorded $65.40. Try the sample to see how the tool spots the difference and proposes an entry. You can also load your own CSV files.

Inputs
Bank statement CSV and cash-book (GL cash account) CSV
Matching
Cheque number → amount + date window → cheque-number discrepancy → manual
Outputs
Two-sided reconciliation statement, classified reconciling items, proposed adjusting entries, CSV export
Sample data
Forest City Seniors Connect (fictional club), March 2026
Privacy
Static page, no server. Parsing and matching run in your browser; nothing is sent anywhere.

Bank statement and cash book

Paste a CSV export into each box, drop a file, or load the sample. Columns are detected from the header row (dates, descriptions, withdrawals and deposits, or a single signed amount). Cash-book entries dated before the statement period are treated as items brought forward from the last reconciliation.

Bank statement · what the bank says0 lines
Drop a .csv here or Template

Recognised headers: date, description, withdrawal/debit, deposit/credit, or amount (deposits positive), optional balance.

Cash book · what the books say0 lines
Drop a .csv here or Template

Recognised headers: date, ref/cheque, description, party/payee, category, receipt/debit, payment/credit, or amount (receipts positive).

Reconciliation settingsDerived from the statement when possible

What a bank reconciliation proves

The cash account in the general ledger and the bank's statement should describe the same money, but they never agree on a given day. Cheques the club has written haven't all been cashed. A deposit made after the branch closed shows up tomorrow. The bank charged a fee nobody has recorded yet. A reconciliation lists every one of those differences, and when the two adjusted balances agree, you have evidence that both records are complete and that nothing is missing or invented. It's one of the first controls an auditor tests, and it's the first thing I'd want in place as a treasurer.

Two sides, two kinds of difference

The statement is built in two columns. On the bank side, start from the balance per the statement and adjust for things the books know about but the bank doesn't yet: add deposits in transit, deduct outstanding cheques. These are timing differences, and the books need no entry. On the book side, start from the balance per the cash book and adjust for things the bank knows about but the books don't: interest earned, service charges, NSF cheques that bounced, and errors in the books. Each of these needs a journal entry, which is why the tool proposes them.

If the two adjusted balances don't agree, the difference is the size of the problem you haven't found yet. The tool shows it rather than forcing it to zero. A "plug" to make a reconciliation balance is exactly what the control exists to prevent.

Why cheque numbers come first

Descriptions are unreliable: the bank says POS PURCHASE FRESHMART #114 and the books say "Refreshments, St. Patrick's social." Amounts alone are ambiguous when two reimbursements happen to be $36.00. A cheque number is a unique identifier that both records share, so it is the strongest key. Only after cheque matches are exhausted does the engine fall back to exact amount within a date window (default seven days, because a cheque written on the 27th may clear in the next month), choosing the closest date when there are several candidates.

The transposition rule

When a cheque number matches but the amounts differ, one side has an error. If the difference divides evenly by nine, the tool flags a probable transposition: $65.40 written for $56.40 is off by exactly $9.00, and swapping any two digits always produces a difference divisible by nine. The sample data plants one of these on cheque 1046. If one amount is exactly ten or a hundred times the other ($50.00 recorded as $5.00), the decimal point slid instead. Neither rule proves anything, but both say where to look first.

Items that deserve a second look

  • NSF cheques. A deposit that bounced reduces cash and reinstates the receivable from whoever wrote it. The bank usually adds a fee on top, which is a separate expense.
  • Stale-dated cheques. Anything outstanding for more than six months has probably been lost. It should be investigated and, if appropriate, cancelled and reissued rather than left on the list forever.
  • Unexplained bank debits. A withdrawal the books don't know about is either an unrecorded payment or something worse. It goes to a suspense account until identified, never straight to an expense.
  • Brought-forward items that never clear. The tool treats cash-book entries dated before the period as last month's outstanding items. If one still hasn't cleared, it stays on the list and is flagged by age.

The control around the tool

Ideally, someone other than the person making payments reviews the reconciliation. For a small club, a second executive can get the statement directly from the bank, check the adjustments and sign off. They can also check the next statement to see whether outstanding cheques cleared.

The tool reads CSV files and matches the entries in your browser. It keeps amounts in cents to avoid rounding errors. You can review the suggested matches before exporting the reconciliation.

Stack
HTML, CSS, vanilla JavaScript
Dependencies
None (fonts from Google Fonts)
Data handling
Entirely client-side; nothing leaves the page
Limits
Single account and period per run; no persistence between visits by design
Sample
Forest City Seniors Connect, a fictional student club. All names, vendors and figures are invented.