# A Weekly Bookkeeping Routine for Client Books

- Author: AutoBankConvert (https://www.autobankconvert.com)
- Published: 2024-12-11
- Updated: 2024-12-11
- Category: Bookkeeping workflows
- Canonical: https://www.autobankconvert.com/blog/weekly-bookkeeping-routine

> A weekly bookkeeping routine for client books: what to convert, categorize and review each week so month end becomes a short check instead of a scramble.
A weekly bookkeeping routine is a fixed set of jobs you run on every client's books once a week: take in whatever statements arrived, convert and code them, send the week's questions and check that nothing is stuck. Done weekly, month end shrinks to reconciling, reviewing and signing off work that is already mostly finished.

## What belongs in a weekly bookkeeping routine for client books?

A weekly bookkeeping routine holds the jobs that get harder the longer they wait: intake, coding, client questions and a short status check. Those four jobs decay. Statements pile up, payees blur, clients forget what a charge was for. Anything that only makes sense once a month is complete stays out of the week.

### The four weekly jobs

- **Intake.** Log every statement, receipt batch and client message that came in since last week, and file each against the right client.
- **Conversion and coding.** Turn new statements into rows, let the client's rules assign accounts, and code what the rules could not.
- **Questions.** Send each client one message with this week's unknowns, instead of a long list on day ten of the close.
- **Status check.** Look at every client once, even the quiet ones, and note what is missing or waiting.

### What the routine is not

A weekly routine is not a weekly close. You are not proving the month each Friday, and you are not producing reports for owners every week unless the engagement calls for it. The routine keeps the inputs current so the close has less to do. If you find yourself reconciling every account to a half-finished month, the routine has grown past its job.

A good test is to ask, for each task, "Would this be harder next week?" If yes, it belongs in the routine. If the answer is "No, it just has to be done before sign-off," it can wait for month end.

## Weekly intake of client statements that close on different days

Weekly intake of client statements works because banks do not close every account on the last day of the month. A checking account may cycle on the 15th and a card on the 22nd. Across a client list, some statement lands nearly every week, and a weekly pass picks each one up soon after it arrives.

### Map each account's cycle date

For each client, write down every account and the day its statement period ends. Put that list next to your intake log. When you sit down each week, you know which statements should have arrived since last time, so a missing one is spotted within days instead of at month end. Card accounts in particular tend to close mid-month, which also spreads the work out.

### Log first, convert second

Start the intake job by logging, not processing. Note which client, which account, which period and when the file arrived. A short log tells you three things at a glance: what is here, what is late and what is a duplicate of a file you already have. Then convert in one batch. Batching a week of mixed statements at once is faster than handling each file the moment it lands, and it keeps your attention on one kind of work at a time.

AutoBankConvert takes a folder of statements from several banks and clients in one upload and keeps each client's results apart, so a week's intake can go through as a single batch. Its balance check flags any statement whose opening balance plus transactions does not reach the closing balance, which tells you on the same day that a page or a line is missing.

### Handling files clients send by email

Clients send statements as attachments, phone photos and forwarded bank emails. Each of those is a client record that has to be stored and deleted as carefully as the books themselves. Treat your inbox as a holding area, move files to the client's folder during intake, and clear them from email afterward. The guide to [what client confidentiality covers for a bookkeeper](/blog/client-confidentiality-in-bookkeeping) sets out the duty behind that habit.

## Coding the week's transactions while the client still remembers them

Coding transactions weekly means assigning each new statement line to an account within days of it arriving, while the payee and purpose are fresh. A client asked about a charge from last Tuesday usually knows the answer. Asked about the same charge six weeks later, they guess, or ignore the question.

### Let rules take the routine lines

Most lines on a client statement repeat: rent, payroll, software, utilities, the same suppliers. Those should be coded by rules written once per client. Your weekly coding time then goes to the remainder: new vendors, unusual amounts, transfers and anything a rule was unsure about. Each time you code a new vendor, ask whether a rule should cover it next time. Over a few weeks, the weekly remainder shrinks.

### Send one question message per client

Collect every unknown line from the week into one message per client. List the date, the amount and the description as the bank printed it, and ask a specific question, such as "Was this a supplies purchase or personal?" One short weekly message gets better answers than a long monthly list, because the client can reply from memory in a few minutes.

### Park, do not guess

When a line cannot be coded yet, move it to a holding account you clear before month end, and note the question it is waiting on. Guessing creates errors that look finished. A parked line looks unfinished, which is what it is, and it stays visible until someone answers.

## How long should a weekly bookkeeping session take per client?

A weekly bookkeeping session for a typical small client should take minutes, not hours. The time depends on how many new lines arrived and how many the rules could code. A client with one checking account and a card needs more time in a week when a statement arrives than in a week when nothing does.

### Measure, then budget

Rather than trusting a rule of thumb, time a month of weekly sessions for each client. Record the minutes and the number of lines handled. After four weeks you will have a per-client figure that reflects their volume, their mess and how good their rules are. Use that figure to plan your week, and revisit it when a client grows or changes banks.

### Signs a session is too long

- The same vendor needs manual coding every week. Write a rule.
- You spend the session chasing missing statements. Fix intake with the client, not your calendar.
- Questions from last week are still open. Escalate once, then park the lines.
- You are rebuilding prior months. That is not routine work. A client whose books are wrong underneath needs the separate project laid out in the [bookkeeping cleanup checklist for books that are wrong](/blog/bookkeeping-cleanup-checklist).

### When the client is months behind

A client who arrives with a backlog cannot start a weekly routine on day one. Bring the books current first, as a defined project, then switch to the weekly rhythm. The steps for that project are in [catch up bookkeeping with bank statements](/blog/catch-up-bookkeeping-with-bank-statements), which works through months in order and proves each one against its statement.

## A five-day weekly bookkeeping calendar for a client list

A five-day weekly bookkeeping calendar gives each job its own day so that the whole client list moves together. Intake happens early in the week, conversion and coding follow, questions go out midweek so answers can come back, and Friday is a short check across every client. The days below are an example to adapt.

| Day | Job | What "done" looks like |
| --- | --- | --- |
| Monday | Intake for all clients | Every file that arrived since last Monday is logged against client, account and period |
| Tuesday | Convert and code | New statements converted in one batch, balance checks passed or flagged, rule-coded lines accepted |
| Wednesday | Manual coding and questions | Remaining lines coded or parked, one question message sent per client |
| Thursday | Answers and fixes | Client replies applied, flagged statements chased or re-requested |
| Friday | Status check | One line per client: what is current, what is missing, what waits on whom |

### Why the order matters

Each day depends on the one before. You cannot code what has not been converted, and you cannot ask good questions until coding has shown what is unknown. Sending questions on Wednesday gives clients two working days to reply before Friday. If replies come later, they roll into next week's Thursday rather than disrupting a close.

### The Friday status line

The Friday check is the part most worth protecting. For each client, write one line: statements current through which date, open questions and anything blocked. An example line might read "Client B: checking current to the 15th, card statement for the 22nd not yet in, two questions open." A week of these lines tells you where month end will slow down before it starts.

### Fitting a small practice

A solo bookkeeper with a handful of clients might fold the week into two sessions, Monday for intake through coding and Thursday for answers and the status check. The order stays the same. Only the number of sittings changes.

## Weekly bookkeeping tasks to hold back for the month end close

Some bookkeeping tasks should not move into the weekly routine, because doing them on a partial month wastes time or gives a false result. Reconciliation, adjusting entries, report review and sign-off all need a complete period. Run them once, at month end, on finished inputs.

### Reconciliation to a closing balance

Reconciling an account means proving that the books agree with the statement's closing balance. A statement that has not closed yet has no closing balance to agree with. Reconciling to an online running balance mid-month can be useful as a spot check, but it is not a substitute for the month-end reconciliation, and doing it every week doubles the effort.

### Adjustments and accruals

Entries such as depreciation, prepaid expense releases or accrued payroll are monthly by nature. Posting them weekly invites partial amounts and reversals. Leave them on the month end list.

### Reports and owner reviews

Owners who want a weekly cash figure can get one from the bank balance. A profit and loss built from three weeks of coding misleads more than it helps. Send reports when the month is closed.

### Quarterly items

Sales tax returns, payroll filings and estimated tax payments run on their own calendars. The weekly routine keeps the inputs ready, but the filing work belongs to the [quarter end bookkeeping checklist for client books](/blog/quarter-end-bookkeeping-checklist), which pulls three closed months together.

Kept to these limits, a weekly routine turns month end into a check of work already done. If your weekly batches are where the hours go, [AutoBankConvert](/get-started) is built to take a pile of client statements in one upload and return coded rows ready for review.