Finance
A monthly close that stops drifting into week two
The close is a chase, not a calculation. A worker runs the chase: who owes what item, who has gone quiet, and what is blocking the two things that always block.
What the worker does
In Polaris, a monthly close checklist is a task list with an AI worker assigned to keep it moving. The worker builds the checklist from the previous month, assigns each item to its named owner, chases people who have not delivered, and posts a daily status comment naming what is outstanding and who it is waiting on. The controller decides when the period is actually closed.
- Connections
- Slack · Google Drive · Gmail
- Cadence
- Daily during close week
- Lives in
- A close workstream, Focus lane pinned
Close does not slip because the maths is hard
Ask a controller why the close ran long and you will not hear about accruals. You will hear that the marketing lead never sent the agency invoice, that the payroll file landed on day four, and that nobody noticed one bank line was unreconciled until day six.
Close is a coordination problem wearing an accounting costume. It has twenty to sixty items, eight owners, and one person doing the chasing while also doing their own items.
That chasing is the part to hand over. The worker knows what the list was last month, who owned each line, and who has not answered. It posts the same status every morning so the blockers surface on day two instead of day six.
Running a close in Polaris
- 1
Make the close its own workstream
A workstream is any container of work. Give the close one, with lanes for the stages you actually use. Lanes are shared between list and board view, so the controller can work in a list while everyone else looks at the board.
- 2
Pin the deadline items to Focus
Focus is a time-based lane across Today, This week and Next 30 days, pinned first in every view. The three items that always run late belong there, not buried in a list of forty.
- 3
Assign the chase to a worker
Assignment works the same for a worker as for a person. Give it the close workstream, Slack for the chasing and Google Drive for where the supporting files live.
- 4
Write the acceptance criteria for the daily status
For example: every open item named with its owner and days outstanding; every item that moved since yesterday listed; anything blocked stated with what would unblock it. The worker ticks these as it goes.
- 5
Read the morning comment, unblock, then close
The worker posts, you act. When the last item is done, a human closes the task. The machine never marks the close complete.
What moves and what does not
The worker changes the tempo of the close. It does not change who is responsible for it.
Handed to the worker
- Rebuilding this month's checklist from last month's
- Assigning each item to the owner it had before
- Chasing in Slack, on a schedule, without getting embarrassed about it
- Reporting status every morning in the same shape
- Collecting supporting files into the close folder
Stays with the controller
- Any accrual, estimate or cut-off judgment
- Reviewing reconciliations
- Deciding an item can be waived this month
- Signing off the period
- Closing and rating the task
The shape of the job
Sizes vary by team. These are the dimensions worth measuring on your own close before and after.
3
Focus horizons
Today, This week, Next 30 days
1
Status comment per day
Same shape every morning, so drift is visible
$0
Cost of the workspace
You pay only for the hours the worker delivers
Questions people ask
+Will the worker chase our CEO for a missing receipt?
It chases whoever is named as the owner of that item, in Slack, on the cadence you set. If you want a different escalation path for certain people, write it in the SKILL.md and the worker follows it.
+Can it rebuild the checklist from last month automatically?
Yes, because last month's close lives in the same workspace as a set of tasks with owners and outcomes. That is the practical argument for keeping the close in the same tool as everything else rather than in a spreadsheet nobody can query.
+What happens if nobody reads the morning comment?
The task stays open, which is the point. Deliveries are comments on tasks, so an unread status is visible as an open item with an assignee rather than a message that scrolled past in a channel.
+Do we need every finance person to have a paid seat?
There are no seats. Polaris is free for unlimited people, tasks, workstreams and docs. The only thing billed is delivered work from AI workers, at roughly $2 per human-equivalent hour, itemized on the work log.
Related
Finance work with an AI worker on the roster
The chasing, sorting and assembling that fills a finance week, prepared by a worker you brief once and review every time.
Budget reports written for the people who did the spending
Plan against actuals is easy to produce and hard to read. A worker writes the variance up in sentences a department head will actually act on.
Invoice tracking that produces a chase list, not a dashboard
A worker matches Stripe payments to what you invoiced, ages the gap, and drafts the reminder for each account. You decide who actually gets chased.
The weekly review, written before the meeting starts
A meeting that begins with everyone reading the same document is a different meeting.
Hire an AI bookkeeper
It does the sorting, chasing and drafting that eats a finance afternoon, and it stops at the line where a qualified person has to sign.
Focus lane
A commitment for a horizon, not a filter over everything you have.
Workstream
A strand of work that keeps going, rather than a project that ends.
Connect Slack to Polaris
Six scopes, no access to direct messages, and a bot that only reads the channels somebody invited it into.