A year-end close is one ordinary month-end plus about a dozen jobs that come round once a year. Nearly all of the email comes out of that second half. The routine part runs on records you already hold. The annual part waits on somebody outside the firm, and a few of those answers stop being available on the last day of the year.
- A close’s mailbox tracks how many annual judgments the accounts contain. That’s a different number from the size of the business.
- If a third party recorded it, you can still get it in March. If only the business could have observed it, the year end was the last day it existed. What replaces it is an estimate somebody has to stand behind.
- This is the one job in the year whose date the firm invents. So the message carrying that date names the thing downstream that has a real one.
- A query list is two lists in one envelope. What the client answers from memory, and what they have to go and find. Send them together and it comes back two thirds done.
One month-end and a dozen annual jobs
Split a close in half. The two halves behave like different jobs.
One half is the twelfth month-end. Bank and card accounts reconciled, the feed cleared down, payables and receivables cut at the date, payroll agreed to the ledger, the suspense account emptied. All of it runs on records that already exist, and most of those already sit in your own systems. Every line of it is yours to finish in-house. It’s work, and on a well-kept set of books it’s a predictable amount of work.
The other half is the annual set, and it’s a list of positions rather than a list of tasks. Depreciation, and whether the assets on the register are still in use or went to the dump in June. Accruals and prepayments. Stock or work in progress at the date. The balance on the owner’s loan or current account, and what the movements on it actually were. A customer who stopped answering in the spring, and whether that debt is ever going to be paid. The private-use proportion on a vehicle, a phone, a room in a house. Opening balances agreeing to last year’s final figures rather than to last year’s draft. And then whatever this business did once and won’t do again: took a loan, bought a van, started renting a unit, wrote something off, changed how it gets paid.
Every one of those is a question for somebody outside your office. That’s why the annual half produces nearly all of the mail. Reconciling a bank account is silent. Deciding whether a debt is bad costs a message, a wait, a chase and a reply, and it costs that whether the business turns over a lot or very little.
Two things follow. The first is worth saying to whoever plans the firm’s January.
Size a close by the count of annual judgments, because that’s what the mail and the waiting are made of. Transaction volume is the wrong ruler. Picture a one-vehicle trade with a room at home, a director’s loan, some stock in a storage unit, and personal spending running through the business account. That generates more year-end email than a company ten times larger with two bank accounts, no inventory and a bookkeeper. Volume counting the wrong thing is a general property of a practice mailbox, set out in running the firm inbox. The year-end version is sharper than most, because the two numbers can point in opposite directions.
The second is about habit. Monthly work has a rhythm, and the rhythm carries it. Once-a-year work rests on whoever happens to remember it, and it lives in the mailbox rather than in the ledger for as long as it stays open. Most firms keep a close checklist, and it solves half of that: every item is enumerated, and every item stays enumerated. The other half stays open. The items on a checklist are questions addressed to named people, and a checklist carries the question alone. The addressee and the date it needs are somewhere else.
All of this holds whatever the close is for. It may end in a compiled financial statement, in a management pack, in a set of financial statements, or in a trial balance handed to whoever prepares the return. Those differ downstream, in what gets produced and who signs it. The mail in front of them is the same mail.
The inputs that cannot be got later
Almost everything a practice waits for can be got late, at some cost. A bank statement can be requested again. A loan balance can be confirmed. A supplier sends a copy invoice. A payroll bureau reruns a report. A merchant service exports a settlement history. It’s slow, and sometimes it takes a phone call and a password reset. The document is somewhere, and you can get it.
A small number of year-end inputs work differently, and the line between the two groups fits in one sentence. If a third party recorded it, you can still have it in March. If only the business could have observed it, the year end was the last day it existed.
The second group is short, and it’s always the same. A count of what was on the shelves at the close. Work in progress on a job half finished. An odometer reading. Cash in the drawer. Which tools were in the van, and which had been written off months earlier without anyone saying so. Materials on site. Any of those can be reconstructed in February. The reconstruction costs considerably more than the observation would have, it rests on movements that themselves have to be evidenced, and the answer it gives is worse. What you end up with is an estimate called a count.
So the most valuable message of the whole close leaves in November. It’s an instruction to do something on a particular day. It wants three things: what to record, which day to record it on, and how to send it in. That’s the whole message. A photograph of a tally sheet taken on the shop floor beats a spreadsheet that arrives in March. Say so in the message, and you remove the main reason people put it off.
It also wants the right addressee, and that’s rarely the person who signed the engagement. The count is done by whoever is standing in the stockroom. The odometer is read by whoever drives the van. Send the instruction to the owner and hope it gets passed on, and you add a link to the chain and a week to the timing. The general form of that mistake lives in one PBC list, not five copies of it, along with what to do about a line on a list your client has to get from somebody else.
Two more notes on the November message, because it does more than one job.
It’s the last point at which some things can still be acted on rather than merely recorded. Which things those are is a question about the client’s affairs rather than their mail, so it belongs elsewhere. What belongs here is the timing. A message that arrives in February arrives too late, and the difference between the two dates is the whole of the value.
Where the input has already been missed, say so out loud rather than absorbing it. The accounts carry an estimate. The client should know which figure is estimated and on what basis. The fact belongs in a note against that client for next year, where next January will find it. A firm taking on a new client in January inherits this problem in full. The honest version of that first conversation says plainly that parts of this year will be estimated, because the year has already ended.
The one date nobody outside the firm set
Every other deadline in a practice arrives from somewhere else. Filing dates, payment dates, the day a form has to reach the person named on it. They belong to somebody outside the firm, and that’s what gives them force.
A close date is one the firm chooses. Year-end financial statements may carry a filing date, and it usually sits months beyond the date you’re actually working to. So the date on your calendar stays an internal one. This is the only substantial job in the practice’s year that works this way, and it explains a failure firms tend to read as a client problem.
An internal date carries no consequence, and clients can tell. “We would like to have your year end wrapped up by the end of January” is a preference. Preferences get answered at the rate preferences are answered, which is after everything carrying a real date. The firm ends up mildly aggrieved about a message that only ever asked.
So find the first thing downstream that does have a date, and carry that date in the message instead of your own. There’s usually one. A return that waits on the books being closed. A payroll year end. A pack a lender wants, a covenant tested at a date, a facility up for renewal. A grant claim, a valuation, a sale, an investor doing their own diligence. Whichever it is, it’s the client’s date rather than the firm’s. It carries a cost they already understand, and it turns a request about your workflow into a sentence about their year.
Where the next real date genuinely sits months out, say so rather than papering over it. A close that drifts costs three things, and a penalty is none of them. A year of numbers nobody can make a decision from. Questions asked about a period so distant that the answers get worse. And a larger bill when the work finally gets done at speed. A client told that plainly may still choose to be late, which is their business, and that’s a decision rather than a drift.
The internal date changes one more thing, and this is where it earns its place in the mailbox. It changes what a chase can honestly threaten. A chase escalates by changing the channel, the person or the consequence, and the consequence has to be one you’ll actually apply. That ladder is set out in managing client document requests. On a close, the true consequence is almost always a scheduling fact. If the records reach us after the ninth, this moves behind the returns and gets done in March. That’s easy to say, easy to mean, and it works because it’s true. A client who has dealt with you for three years already knows an invented deadline is soft. Working out what your own side still needs after the papers land, and why that sum gets shorter every week of the season, is inbox zero during busy season.
What a query list is two of
Every close produces the same thing: a list of transactions the ledger can’t explain, exported by the software as dates, amounts, payees and an empty column. Forty lines, or eighty, or two hundred. It’s the most familiar object in the whole job, and it’s handled worse than anything else in the practice, because it goes out exactly as it came off the screen.
Four things improve it, and the first happens before anything is sent.
Cut the list inside the firm. A real share of any query list can be settled in-house: the same payee was coded the same way last year, the merchant is unambiguous, or the amount is small enough that any answer leaves every number where it is. That triage is your work rather than theirs. It takes a fraction of the time the correspondence would take, and it’s the single largest reduction available. What leaves the office is the part only the client can settle.
Then split what remains, because the list is two lists wearing one heading. Some lines are memory questions: what was the payment to the building supply store on the third of August for. A client answers that in three minutes, standing in a parking lot, from a phone. Other lines are paperwork questions: we need the invoice behind it. That’s an errand with a drawer at the end of it, done on an evening that has to be found. Put both in one message and you get the ordinary result. The easy half comes back on Tuesday, the rest sits, and a follow-up goes out asking for everything again. Send the memory half as a message they can answer by hitting reply. Let the paperwork half join the documents you’re already waiting on, where the asking is a craft of its own and works the same however small the items are.
Third, propose rather than ask, wherever you safely can. Eighty blanks is a form, and a form gets put off. Eighty statements, each ending with an invitation to correct it, is something a person reads through in one sitting. On the routine lines your proposal is usually right. “We have treated this as repairs to the unit unless you tell us otherwise” costs the client a glance. A blank column costs them a decision.
That has a limit, and it matters. Two kinds of line want a plain question instead. The ones where being wrong would change what is claimed. And the ones where the answer is a judgment about the owner’s own affairs rather than a matter of coding. Ask those plainly, and accept that they take longer.
Fourth, order the list by what it changes rather than by date. A ledger export comes out in date order, and date order is the one ordering that says nothing about which lines matter. Three or four lines usually decide the figures. The rest is tidiness. Say which ones those are, at the top, in the words their own bank statement uses rather than the words your ledger uses. A client who knows which four questions are the real ones answers those four first. That’s exactly the outcome you want, and a two-hundred-row spreadsheet rarely produces it.
One class of line belongs somewhere else entirely. A payment to a family member. Personal spending running regularly through the business account. Cash with no counterpart. A round-sum transfer to an account that’s new to you. Those look like list items, and they’re conversations, with consequences on both sides and a record that outlives the engagement. Take them out before the list goes, and handle them as what they are. The same goes for the query that turns out to be an advice question in disguise. Left in, it gets answered in the eightieth row of a spreadsheet by whoever is doing the typing.
Finally, send the list as a list. Hold each line as it occurs to you, and let them go together. A client who gets eleven separate small questions over two weeks has a different week from a client who gets one message on a Tuesday, and the difference in how fast they answer is larger than it has any right to be. Why a batch beats a drip, and what it does to the count of things you’ve added to a job, is one PBC list, not five copies of it.
December goes on arriving in January
A close draws a line through a date. The mailbox carries both sides of that line for about six weeks, in identical envelopes.
The traffic in the second and third weeks of January is a mixture. Invoices dated in December that were posted in January. A card statement whose period straddles the year end. A utility bill covering a quarter that ends in February. An expense claim from somebody who has finally found the receipts. A supplier’s year-end statement. A bank charge applied on the last day and visible on the third. A payroll run paid in January for work done in December. And underneath all of it, the ordinary business of the new year, which has been running the whole time.
Which side of the line any of it falls on is your call. Period allocation is your judgment, and it rests on a basis the client has no reason to understand. Ask them whether an invoice is for last year and they’ll answer with when they paid it. That’s the only date they have a feeling about, and it’s the date most likely to point the wrong way.
So ask about the event. When was the work done. When did the goods arrive. What dates does the bill cover. People answer events accurately, and periods are guesswork to them. It’s the same reason the useful January question about paperwork asks what happened rather than what exists.
Second, decide in advance what happens to anything that arrives after you’ve closed. Make it a rule rather than a case-by-case act of goodwill. There are three answers: reopen the period, put it in the new year, or hold it as an adjustment because it’s large enough to matter. Every firm has a threshold, and most keep it in their heads, so the version the client gets depends on the mood of whoever answers. The mailbox part is narrow. Tell the client the rule at the moment the year closes, three weeks before they’d otherwise be sitting on an invoice wondering whether it’s worth bothering you with.
Third, a client with access to their own books posts into a period you’ve finished, and they post quietly. Where the software allows the period to be locked, lock it. That’s a control. Everything else here is a hope. Where the software leaves it open, your signal is the client mentioning it in passing, which is one of several reasons the year should end with a message rather than with silence.
A client who’s also on extension has two tax years open at once. That’s a related problem with an answer of its own, including the discipline of naming the year in the messages themselves, and it’s tax extensions and the six months of quiet after them. What’s specific to a close is narrower. Here the open question is which side of a cut a transaction falls on, and that’s a decision only your side can make.
Approval, and what silence is not
A close ends by sending somebody a set of numbers. Somebody else produced them, most of them are beyond checking from where the client sits, and they’re being asked to agree.
The usual version attaches the pack and asks whether there are any questions. It’s a request with no action in it, and the ordinary reply is silence, or three words. Neither one is approval. Here’s what actually happened. A busy person opened a large attachment on a phone, saw that the figures were the accountant’s work, and had no way to tell which parts were theirs to confirm.
The repair is to separate the confirmation from the presentation. The pack is presentation. The confirmation is a short list of the things only the client knows, and on which you’ve taken a position. Put it at the top of the message, where it gets read.
The balance on the loan or current account with the owner, and whether the movements are what they believe them to be. The value put on stock or work in progress. Whether a named debt is going to be paid. The split between business and private use on the vehicle, the phone, the room. And every figure you estimated because the input had expired, named as an estimate, with the basis in half a sentence.
Three to six lines, each answerable with a yes or a correction. Then the pack underneath for whoever wants it. A client who replies that the loan account looks right and the stock figure is too high has told you something. A client who replies that it all looks fine to a forty-page attachment has told you nothing at all. The difference lies entirely in what they were asked.
Say what happens if nothing comes back, once, with a date, and then honor it. On a close that sentence is unusually easy to write honestly. What happens next is that the thing behind the approval waits, and that’s a fact rather than a lever.
Where the close ends in something that has to be signed and filed rather than merely agreed, chasing and filing a signature is a job with its own shape. It’s engagement letters and the signature you are still waiting on. What belongs here is one line. A signature is a different act from an approval, and asking for both in one message tends to produce neither.
The message that ends the year
Most closes stop rather than end. The last thing the client hears is a reply to their answer about a query. Then the file goes quiet, and both sides assume the other has finished.
There’s a message worth writing at that point, and it’s short. The year is closed as at this date. Here’s what was adjusted, in a sentence each, and what it changed. Here’s what was estimated, and why. Here’s what remains open, if anything does. Here’s what to do with anything you come across afterwards. And here’s who’s holding the work now.
It buys four things, and three of them stay invisible until the day you need them.
It stops the year moving. A client who’s been told the period is closed, and told plainly to send anything they find rather than judging whether it matters, sends it. A client who’s heard nothing posts it themselves, or sits on it until March.
It’s the record. In eighteen months somebody notices that a figure in the software disagrees with the accounts. The question arrives in a mailbox, and the answer is either in a message with a date on it or in a reconstruction.
It’s the handoff. A close finishes and something downstream starts, often with a different person: another team in the firm, the client’s tax preparer, a lender’s analyst, the client’s own bookkeeper picking up the new year. That handoff is an email between two people, each quietly believing the other is holding the client, and it’s the gap two weeks disappear into. What it owes is small and entirely specific: the date the books were closed, what carries an estimate, what is still open, and who the client should now be writing to. On that last point, expect people to carry on as they were. People reply to the address that last wrote to them. That’s the reasonable thing to do, and it’s a habit that outlasts any instruction, so the arrangement has to hold on its own. Naming the address that holds the record for a client is running the firm inbox. Where the other party is the client’s own bookkeeper, that relationship has a rhythm of its own in working with a client’s bookkeeper.
And it writes next year. The annual judgments this particular business actually has. The queries its books produce every single year, which are remarkably stable. The count, its date, and the name of the person who does it. Record those once as facts about the client, and next January finds them waiting. They become November’s message instead of February’s surprise, and carrying forward the annotations rather than the rows is the part of a rollforward that’s worth the effort.
Where does Point fit?
Everything above is a way of working, and it predates software. Firms closed years on paper for a very long time, and the careful ones closed them well. A tool moves where the effort falls: the remembering, the waiting, the matching and the wording of a first draft. The positions themselves stay exactly where they were.
Point reads the mailbox before you do. Each message gets weighed on how much it matters and how soon, rather than on when it turned up. So on a January morning, a client’s answer about the loan account sits above the delivery of receipts that landed alongside it. What that weighing measures is a subject of its own. Every thread carries a one-line summary, and on a close that’s usually the whole question you had: whether something came, and what period it covers.
Three capabilities carry most of the load here.
A standing request in plain words covers the input you’re genuinely waiting on. Ask to be told when a named client’s count sheet arrives, or the signed approval. You hear once, on the day, and the checking stops. Against the November instruction, set weeks before anything is due to happen, that’s close to the whole discipline. Leave the watch, and stop thinking about it.
Requests you send are held as things you’re owed, and they come back on the date you chose. Where the reply has already arrived, the follow-up flags itself as likely dealt with and waits for your word, so nobody chases an approval the morning after it was given. And an ask sitting three paragraphs into somebody else’s message becomes a dated item on its own. That’s exactly the shape of the sentence about buying a van in September, turning up in the middle of a reply about something else.
Attachments come out of their threads and gather into one list, dated, each still joined to the message that brought it. A question put to a document comes back with a pointer to the page it was read from. That matters more on a close than elsewhere. January’s post is largely paperwork arriving bare, and the fastest route from a supplier statement to a period allocation is asking what dates it covers and being shown where.
Replies come back drafted the way you write. The query message, the approval request and the message that closes the year all start as something you correct rather than something you compose. And Point runs the scheduling back and forth itself, for the day a query list becomes twenty minutes on the phone.
Each kind of action carries its own setting for how far Point takes it alone, and all of them ship at review. The work gets prepared, and then it waits for you. The dial explains that setting properly. Acknowledging a delivery is the first kind worth raising. The message asking a client to confirm a stock value wants somebody reading it before it goes, every year. Every action lands in a log with a time against it, and the log is where you undo one. The limit is the one every mail product shares: once a message has reached the recipient, it has gone.
Point signs in to the Gmail or Microsoft account the practice already runs. The address on your letterhead stays the same, and so does the archive behind it.
The ledger stays yours. Point has never seen your trial balance, holds no close checklist, and has no view on what is material. Which side of the cut a transaction falls on, and which annual judgments this particular business contains, are yours to decide. Those are the job, and they stay where they are. Everything Point does is listed on the benefits page, and Point for accountants arranges the same list around a firm’s year. Whether a tool ought to be reading mail carrying a client’s records is a question that comes before any of it, and what a firm should satisfy itself about first is where it gets settled.
Common questions
When should year-end emails actually start?
Earlier than most practices send them, and the reason is timing rather than politeness. A small set of inputs stop existing at the year end. The message asking for them has to arrive while the year is still running, which in practice means November. It reads as an instruction to record something on a particular day, addressed to whoever will physically do it. Everything else in the close keeps until January, and that’s worth knowing, because it lets the November message stay short enough to be acted on.
How do we get a client to answer sixty queries?
By sending fewer than sixty. Settle inside the firm every line that last year’s coding, an unambiguous payee or a trivial amount already answers, which is usually a substantial share of the list. Split what’s left into what they can answer from memory and what they have to go and find. Send those as two different things, because a list holding both gets postponed to an evening nobody has. Then propose an answer wherever a correction is the worst outcome, so the client is reading rather than filling in. And say at the top which three or four lines actually decide the figures. What comes back is a faster answer, and a better one.
A client sends an invoice dated in December after we have closed. What now?
Answer it against a rule rather than a mood, because the same question arrives from eleven clients. Reopen, carry it into the new year, or hold it as an adjustment if it’s above your threshold. Every firm has a position, and most keep it to themselves. Say it once, in the message that closes the year, along with an instruction to send anything they find rather than deciding for themselves whether it matters. And when you ask about the item, ask when the work was done or the goods arrived, never whether it’s for last year, because the client answers that one with the date they paid.
Is silence on a set of draft accounts an approval?
No, and a reply saying it all looks fine is the same answer in more words. Both are the predictable response to being sent something unreadable and asked an open question. The fix is in the asking. Put three to six specific confirmations at the top of the message. Each one is a thing only the client knows, and on which you’ve taken a position: the owner’s loan balance, the stock value, whether a named debt is collectable, the private-use split, and anything you estimated. Those get answered on a phone in a minute, and an answer to them is worth something. A pack that asks nothing back produces silence in every firm that sends one.
Should the close run in the accounting software rather than in email?
Partly, and it’s worth using what the software does well. Most ledger packages can hold a query against a transaction and let the client answer it in place, which removes the transcription and keeps the answer next to the thing it explains. The rest of the close lives outside the ledger, and the rest is most of it. The instruction to count something on a particular day. The conversation about a debt. The estimate you had to make, and the reason for it. The approval. The handoff to whoever picks the work up next. Those arrive and depart as mail whatever else you run. So a firm that moves its queries into the software usually finds the volume of year-end email roughly unchanged, with the queries out of it. A useful split rather than a replacement, and it’s the same shape as the answer about portals in managing client document requests.
The short version
A year-end close is one ordinary month-end plus a dozen once-a-year judgments, and the judgments produce nearly all the mail. So plan the close against how many of them the business has, rather than against how big it is. A few inputs can’t be obtained late at any price. If only the business could have observed it, the year end was the last day. That puts the highest-value message of the whole job in November, addressed to the person holding the tally sheet rather than to the person who signed the engagement. The date you’re working to is one the firm invented, so carry the client’s own downstream date in the message instead, and let the honest consequence be a scheduling fact rather than an invented penalty. Cut your query list inside the office before it leaves. Split what remains into memory questions and paperwork questions. Propose answers where it’s safe to, and say which few lines decide the numbers. Expect December to keep arriving through January, ask about events rather than about periods, and write down in advance what happens to something that turns up after the cut. Ask for specific confirmations rather than sending a pack and hoping. Then end the year with a message that says it’s closed, what was estimated, what’s open and who holds it now, because a close that merely stops is a close that reopens. Every other repeating job in a practice is taken on its own terms elsewhere in this collection. For choosing a tool at all, there’s AI email for accountants.