Example · Finance
Have you ever seen last month's numbers too late to change this month?
The close eats working days 1 to 8. By the tenth, the month those numbers describe is long gone.
Who it's for
- Your controller or bookkeeper rebuilds the month in a rush after it ends.
- Bank, card and payment lines are matched by hand.
- The management pack lands around the tenth, or later.
When we'd say skip it
Books already close in two days? Keep your process. Chart of accounts in a mess? Fix that first. A faster close on messy books only delivers wrong numbers sooner.
Where the close jams
- Transactions in
- Matched
- Reconciled
- Accruals
- Adjustments
- Pack built
- Commentary
Matching waits until the month ends. A break found on day three happened weeks earlier.
Receipts get chased all over again. The pack is built by hand, and the commentary gets an hour.
In a distributor, it's inventory and freight accruals. In construction, it's the work-in-progress schedule. In an accounting practice, it's every client's books at once.
We'd build a daily books check.
It reconciles the month while it happens, not after it ends.
The close turns into a review
- Bank and card lines are matched every morning, not on day three.
- A break surfaces the day it happens, with its likely cause.
- Missing receipts and approvals are chased quietly all month.
- The pack builds itself, so your controller writes the commentary.
What it's worth: the days your close takes now
Count the working days from month end to a finished pack. Multiply by the people on it, and by their hourly cost.
Then ask one question. What would you do with the numbers on day 3 instead of day 12?
Sample output · daily books check · yesterday
312 lines in, 15 for a person
| Item | Count | For a person |
|---|---|---|
| Bank and card lines matched and coded | 297 | 0 |
| Coding suggested, waiting for review | 11 | 11 |
| Possible duplicate vendor payments | 2 | 2 |
| Deposits with no invoice | 2 | 2 |
| Receipts missing this month | 9 | reminders drafted |
Your controller posts every entry. Nothing posts by itself.
How it runs, every step
Open the full run
When it runs
Every morning, for the previous day's activity.
What it reads
Your accounting system, such as QuickBooks, Sage Intacct or NetSuite. Bank and card feeds. Your expense tool and payables inbox. Each source is confirmed in the first conversation.
The six steps
- Pulls the previous day's bank, card and payment lines.
- Matches each line to an invoice, bill or receipt.
- Suggests coding for the rest, from your past choices.
- Flags breaks: duplicates, gaps and amounts that don't tie.
- Drafts reminders for missing receipts and approvals.
- Builds the pack schedules from your own reports.
Where a person decides
Your controller approves each suggested match and each coding choice before it posts.
What it never does
It never posts a journal entry on its own. It never moves money. It never changes a closed period.
Three things we'd need from you
Read access to your books and bank feeds. Your close checklist. Three past management packs.
Neighbours it often comes with
- Invoice matching, so bills arrive already checked against the order.
- Timesheet to cash, so billing is finished before the month ends.
- A source-to-revenue report, so spend is tied to what it brought in.
You become the owner who steers by this month's numbers.
Last month's numbers arrive while this month can still change.
Yours won't look exactly like this. A first conversation is where we work out what it should look like.
Next step
Count it with us first.
One conversation, about an hour, with one of our co-founders. It's free and needs no access.
Every message is read by a person, with a reply most often inside one working day.