Statement Filer

Post this quarter to Wave

Each category posts as one withdrawal on your shareholder loan account, with the expense account as its line item — the same shape as the Home Office entries already in your ledger. Personal spending is never posted.

Apply your review decisions

Open the workbook this app filed into Drive, fill in the COMMENTS column on the Review sheet with the category you want, save it, then load it back here. The app recodes those rows, rebuilds the summary and redraws every highlighted statement.

You need the same statement PDFs loaded on the Process tab first, so the highlighted files can be redrawn. If you've just done a run in this session, they're already loaded.

Remember these decisions in my rules, so the same merchants are categorized automatically next time

What's already filed

Look at a quarter without touching it. Shows which statements it covers, the category split, and anything still sitting on the Review sheet waiting for a decision from you — plus a link straight to the workbook in Drive.

Connect Google Drive to browse what's filed.

Your rules

This is the brain of the app: which merchant maps to which category, the out-of-GTA meals rule, which merchants always go to Review. Edit it here, or download it and commit it to your repo so it travels with the app.

Your merchant list is kept out of GitHub. The repo is public, so the copy of rules.json there ships with an empty merchant map. Use Import a rules file to load my-rules.json — it's stored in this browser and never uploaded. Do that once per browser you use.

One-time setup

1. Put this folder in a GitHub repo. Create a repo called statement-filer, upload every file from this folder, then go to Settings → Pages and set the source to Deploy from a branch → main → / (root). A minute later your app is live at https://<your-username>.github.io/statement-filer/.
2. Make a Google OAuth Client ID so the app can write to your Drive. Go to console.cloud.google.com → create a project → APIs & Services → enable the Google Drive API → Credentials → Create credentials → OAuth client ID → application type Web application. Under Authorized JavaScript origins add https://<your-username>.github.io. Copy the Client ID.
3. Paste the Client ID into the app using the ⚙ button, top right. It's stored in your browser only — it is not a password and it is safe to keep in a public repo, but the app doesn't put it there for you.
4. Publish the consent screen or add yourself as a test user. While the app is in "Testing" mode, only accounts listed under Audience → Test users can sign in. Add your own Gmail address there.

What it does with your Drive

The app asks for permission to see and manage your Drive files. It needs the broad scope because it has to find your existing Annual Audit … Sep folder — an app-only scope cannot see folders it didn't create. It only ever writes inside Annual Audit … Sep / Credit Card Statements /. Your statements are read inside your own browser tab and go straight to your Drive; there is no server in the middle, and nothing is stored anywhere else.

Where files land

Annual Audit 2026 Sep
└── Credit Card Statements
    └── Amex
        ├── (one untouched copy of each statement)
        └── Q3 2026
            ├── Q3 2026 Amex Transactions.xlsx
            ├── Abridged Statements/
            │   └── (transaction pages only)
            └── Expenses Summary/
                ├── Amex Q3 2026 Meals.pdf
                ├── Amex Q3 2026 Business Travel.pdf
                └── … one per category