Automations

Organize Bank Statements by Account and Period

Six accounts, twelve months, two years. Every file downloaded from every bank is called something like eStmt_0831.pdf, and the reconciliation needs the one from March on the account ending 4471.

The short answer

Bank statements are the case where filenames are actively misleading: every bank names its downloads the same way, so six accounts produce six identical-looking files per month. A workflow uses the Read Details from File step to pull the institution, the last four digits of the account and the statement period off the first page, the Rename step to write those into the filename, and the Move step to file by account and year. Because every file now leads with its period, an account folder reads as an unbroken run of months, and a gap in that run is a fact rather than a possibility.

Steps this uses

File UploadedEmail AttachmentOn a ScheduleRead Details from FileCheck File DetailsRenameMoveSend a Message

Before and after

What actually changes

As they arrive

  • eStmt_0831.pdf
  • eStmt_0930.pdf
  • 20260831.pdf
  • statement (2).pdf

After the workflow

  • First National ...4471/2026/2026-08-statement.pdf
  • First National ...4471/2026/2026-09-statement.pdf
  • First National ...9902/2026/2026-08-statement.pdf
  • Lighthouse Credit Union ...3310/2026/2026-08-statement.pdf

Four downloads with near-identical names, separated by the institution and account printed inside each one.

Setting it up

Described once, then it runs

This is the sentence. Send it to the builder and the steps below appear on a canvas, wired and named, for you to change before anything runs.

When a bank statement arrives, read the institution, the last four digits of the account and the statement period off the first page, rename it by that period, and file it under the account and year.

01

Account first, then year

Reconciliation is per account, so the account is the folder. The institution and the last four digits together are what make it unambiguous — a business with two accounts at the same bank is the normal case, not the edge case.

02

Name by statement period

Not the download date, not the closing date if they differ. The period is what a reconciliation is done against, and putting it first in ISO form means a folder sorts into a timeline.

03

Read the first page

The institution, the masked account number and the period are all printed on a statement's first page. The Read Details from File step takes them from there, which is why identical filenames stop mattering.

04

Let a gap announce itself

Statements come monthly, so a missing month is a fact rather than a possibility. Once every file is named by its period the folder sorts into a timeline, and the gap is visible in the listing — which is the kind of thing otherwise found during an audit.

Why bank filenames are worse than useless

A meaningless filename is a nuisance. A filename that looks meaningful and is ambiguous is a trap: eStmt_0831.pdf tells you the month and hides the account, so six files from six accounts appear to be six months of one. Sorting a download folder by name groups statements from unrelated accounts together, which is exactly the mistake that survives into a reconciliation.

A missing month is the finding

Most document organization has no notion of completeness — you cannot know what was never sent. Statements are the exception, because they arrive monthly by definition. That makes the absence of a month a hard fact worth surfacing, and it is usually the thing an auditor finds first. Naming by period is the whole of the trick: it turns a folder into a sequence, and a sequence shows its own gaps.

What it does not do

It names and files. It does not reconcile, categorise transactions, import into a ledger, read the transactions inside a statement, or alert you that a month is missing — the gap is visible in the folder, not pushed to you. Bookkeeping software does that, generally from a bank feed rather than a PDF. This is about the source documents you have to keep and produce, which is a separate obligation from the bookkeeping itself.

FAQ

Common questions

How should bank statements be organized?

By account, then year, with each file named by its statement period in ISO form — 2026-08-statement.pdf. The account folder should name the institution and the last four digits, since a business with two accounts at the same bank is completely ordinary and the masked number is what tells them apart.

Why not just keep the bank's filename?

Because every bank names downloads the same way regardless of account, so files from different accounts look identical and sort together. That is worse than a meaningless name: it looks informative and is ambiguous, which is how statements from two accounts end up treated as one series.

Can it tell me if a statement is missing?

It makes one obvious rather than alerting you to it. Statements arrive monthly, so a gap in the sequence is a fact rather than a guess — but what surfaces it is the naming. Once every file leads with its period, an account folder reads as an unbroken run of months and a missing one stands out in the listing, which is typically what an audit finds first.

Does this import transactions into my accounting software?

No. It organizes the statement documents themselves. Transaction import normally comes from a bank feed rather than a PDF, and lives in your bookkeeping software. Keeping and producing the statements is a separate obligation, and that is the one this handles.

Six accounts, one timeline each.

Named by the account and period printed inside, not by what the bank called the download.

Build this workflow

5 GB free · No credit card required