Organizing bank records for litigation means four things: an index of every account and month received, Bates numbers that tie each page to the production, a transaction database built from those pages, and gap checks that prove nothing is missing. Done first, it lets the whole team cite the same records and trust that the set is complete.
Why organizing bank records for litigation comes before any analysis
Organization comes first because every later finding depends on knowing exactly which records the team has. If a month is missing, a page is duplicated or two versions of a statement circulate, the analysis will be wrong in a way nobody notices until an opposing expert does. An hour spent on the index saves days of rework.
The usual failure is not dramatic. A paralegal saves a production into a shared folder. An associate pulls a few statements for a deposition outline. An expert receives a second copy from the client. Three months later, two people are quoting different balances for the same account and month, and nobody can say which is right.
Organizing the records fixes that by giving every page one identity, one location and one status. It also makes the gaps visible early, while there is still time to ask the other side or the bank for what is missing. Discovering in the last week before an expert report is due that eight months of a key account were never produced is a common and avoidable crisis.
Give the index one owner. A single person, often a senior paralegal or the expert's lead analyst, adds new productions, updates statuses and records requests. Everyone else reads from it. When two people edit the same index in parallel, it soon stops matching the folder it describes, and the team is back to arguing about which copy is current.
Building a bank records index by account and month
A bank records index is a table with one row for each account and month, showing whether the statement was received, where it sits in the production and whether it passed the completeness checks. The index is the team's map. Anyone can see at a glance what exists, what is missing and what needs attention.
The example below shows the layout. Accounts, ranges and results are illustrative.
| Account | Month | Bates range | Pages | Foots | Opens at prior close | Status |
|---|---|---|---|---|---|---|
| Operating 4401 | 2024-01 | DEF-002210 to DEF-002215 | 6 of 6 | Yes | Yes | Complete |
| Operating 4401 | 2024-02 | DEF-002216 to DEF-002220 | 5 of 6 | No | Yes | Page 4 missing |
| Operating 4401 | 2024-03 | Not produced | Requested 2026-05-12 | |||
| Operating 4401 | 2024-04 | DEF-002221 to DEF-002226 | 6 of 6 | Yes | No | Prior month missing |
| Savings 0078 | 2024-01 | SUB-000044 to SUB-000045 | 2 of 2 | Yes | Yes | Complete |
Build the index from the full expected range, not from what arrived. List every month from the start of the relevant period to the end for every known account, then fill in what was produced. Blank rows are the requests that still need to go out.
Add a row for every new account as it is discovered. A transfer to an unknown account number in one statement is a reason to add that account to the index with every month marked "not produced."
How should Bates numbers map to bank statement pages?
Each bank statement page should carry one Bates number, and that number should follow the page into every schedule, exhibit and note. A Bates number is a unique identifier stamped on each page of a production. Mapping it to the statement and the transactions on that page lets anyone check a figure against its source in seconds.
Keep three rules:
- One number per page, never reused. If a page is produced twice, both copies keep their own numbers, and the index notes that they are duplicates.
- Record the range per statement in the index, so a statement can be pulled by its numbers.
- Carry the page number into the database, so every transaction line points to the page it came from.
When records come from more than one source, such as the opposing party, a subpoena to the bank and the client, keep the source prefix visible. A statement produced by the defendant and the same statement received from the bank are two pieces of evidence. If they differ, that difference may matter more than anything on them.
Do not renumber productions to make them tidy. The numbers the other side stamped are the ones the court will see.
A litigation transaction database built from bank statements
A litigation transaction database is one table holding every transaction from every statement in the index, in the same columns for every account. Raw fields copied from the statement stay unchanged. Review fields, added by the team, sit in separate columns. Each row carries the Bates number of the page it came from.
Columns that keep it usable
- Raw: account, statement month, Bates page, posting date, description as printed, debit, credit, printed running balance, check number.
- Review: normalized payee, category, linked transaction (for transfers), reviewer initials, note, flag.
The split matters in litigation. If an opposing expert challenges a category, the raw line is untouched and the category can be changed without disturbing the evidence. If someone asks what the bank printed, the answer is in the raw columns exactly as the page shows it.
Matching to other records
Bank lines often need to be matched to something outside the bank: invoices, ledger entries, payroll records. A deposit that should equal the sum of three invoices is a common test in commercial disputes, and matching bank deposits to invoices covers how to handle combined deposits, partial payments and fees taken before the money arrives. Record each match in the review columns, with the invoice number, so the link can be checked.
Which gap checks prove a bank production is complete?
Four gap checks prove a production is complete: each statement foots, each statement opens at the prior month's closing balance, every page in each "page x of y" count is present, and check numbers run without unexplained breaks. A statement that passes all four is very unlikely to be missing a line.
- Footing. Opening balance plus deposits minus withdrawals must equal the closing balance printed on the statement.
- Continuity. Each month's opening balance must equal the prior month's closing balance. A break means a missing statement, or a statement that was altered.
- Page counts. Most statements print "page 3 of 6." Compare the pages received with the count.
- Check sequence. Gaps in check numbers can be voided checks or checks that have not cleared, but each gap should have an explanation.
Record each result in the index. PreciseBankFlow runs the footing check on each statement, flags gaps in check sequences and gives every extracted field a confidence score, so the team knows which lines to compare against the page before relying on them.
A failed check is a finding in itself. Note the failure, the date it was found and what was requested to resolve it.
Bank productions that arrive as scans, spreadsheets or duplicates
Productions rarely arrive as clean bank PDFs. Scanned paper, bank-generated spreadsheets, screenshots and multiple copies of the same statement are all common. Each format can be organized, but the original must be kept as received and its Bates numbers preserved, with any converted version clearly marked as derived.
Scans
Scanned statements must be read optically before their data can be used, which introduces the chance of a misread digit. The footing check catches most misreads in amounts, because a wrong digit breaks the balance. Dates and check numbers need a sample check against the image.
Spreadsheets from the bank
A bank's transaction export is useful but is not a statement. It may omit fees, pending items or running balances. Treat it as a separate source, compare it to the statements for the same months, and note any difference.
Duplicates
When the same statement arrives twice, compare the copies line by line before discarding either from the analysis. Duplicates from different sources that do not match are evidence. Duplicates that do match should be linked in the index, with one designated as the working copy.
Turning organized bank records into trial exhibits
Organized records turn into exhibits with little extra work, because every total in the database can already be traced to a Bates page. Summary exhibits are built by filtering and totaling the database. The underlying pages are listed by their numbers, ready for the other side to examine.
Federal practice expects this. Federal Rule of Evidence 1006 at Cornell's Legal Information Institute allows a summary, chart or calculation to prove the content of voluminous writings that cannot be conveniently examined in court, and requires the originals or duplicates to be made available to other parties. An index and database built as described here meet that requirement almost by construction.
Building the summary itself, and the foundation needed to admit it, is covered in the summary exhibit of bank records for court.
Good organization also changes the bill. Much of a forensic accountant's time in a bank-records case goes into collecting, sorting and checking statements before analysis starts. A team that hands over an index, a Bates-mapped production and a list of known gaps can shorten that stage considerably. The other factors that drive the fee are covered in forensic accountant cost and what drives it.