A practice pays for a stack of software and services it can no longer list from memory, and every item in that stack bills by email. Those invoices land in the same mailbox as the client work, they lose to it every time, and for most of the year that is the correct outcome. The trouble is that a few of the messages in the pile are not invoices at all. They are decisions with a date on them, and they look exactly like the rest.
- Most software invoices are receipts. The card was charged before the message arrived, so nothing in the pile needs paying, and the job is capture rather than payment.
- The one message carrying a choice is the renewal or price notice. It turns up weeks before the invoice, wearing the same template as the newsletters, and ignoring it is a purchase.
- Nobody in the firm can list what the firm pays for. The mailbox is the only place the whole stack is visible, and deriving the list from it takes an afternoon, once.
- A lapse never surfaces on the day it happens. It surfaces as a locked account or a declined card in the week you can least afford either.
Three kinds of message in one pile
Everything in this class arrives looking the same: a sender you half recognise, a subject line with a number in it, usually an attachment. Sorted properly there are three kinds, and they want three different things from you.
Most of it is a receipt. The subscription renewed, the card was charged, and the email is the confirmation. There is nothing to approve and nothing to pay. What the message contains is a document you will need in ten months, held by a firm that will not think about it again for nine of them.
A smaller part is a genuine payable with a date on it. The landlord, the professional indemnity premium, the licensing body, the CPE provider, the IT retainer, the shredding contract, the printer who did the year’s folders. These behave like ordinary bills and they are the easiest of the three, because a due date is a thing a practice already knows how to hold.
The third kind is the one this whole subject turns on, and it is a notice rather than an invoice. Your plan renews on the fourteenth. Your price is changing. Your card ends in a fortnight. A seat was added. The terms have been updated. None of these asks for money today and none of them can be filed, because each one contains a decision that expires.
In most businesses getting that third kind wrong is an irritation. In a practice, three or four items in the stack are the only route by which something gets filed on a date nobody can move, and the day they stop working is chosen by a vendor’s billing system rather than by you.
The message that buys it again
Elsewhere in a practice, silence is ambiguous and mostly means nothing at all. That is worked through properly in quarterly estimate reminders, where nothing coming back is the normal outcome and proves neither one thing nor the other.
Here silence has exactly one meaning. It means yes, again, for another year, at whatever the new price is.
That inversion is what makes the renewal notice the most consequential message in the pile and the one most reliably skimmed. Four things conspire.
It looks like marketing, because it comes from the same sender and the same template as the product announcements, and because half of it genuinely is marketing. The part that matters is one line in the middle.
It arrives at the wrong moment. Whether you get thirty days, seven days or nothing at all depends on the vendor and on where you are, so the sensible position is to treat a notice as a courtesy rather than an entitlement and to hold the date yourself. Tax software makes this worse than most: the offer for next season lands while you are still finishing the current one, and the discount for deciding early expires in the month you have the least room to think.
It carries the price increase, and it is the only place that increase appears before it is charged. A card statement in November tells you it happened. The notice in September was the offer to discuss it.
And the decision it asks for needs an input nobody has: what the thing actually got used for over the past year. Which is why the honest answer to most renewal notices, read on the day they arrive, is that you cannot decide yet.
So do not decide on the day. The working rule is to date the notice to the last week in which acting is still possible, and let it come back then, with the annual read described below already done. A message whose value is zero today and high in five weeks is the exact case that snoozing was built for, and it is one of the few places in a practice where pushing something away is the responsible move rather than the avoidant one.
Two smaller notes on notices. A price rise is negotiable far more often than firms assume, and the notice is the only moment at which asking costs you nothing, because after the charge you are requesting a refund rather than discussing a rate. And a terms update is worth thirty seconds if the vendor holds client documents, because that is the one category where a change to what a supplier may do with what it stores is a question for the firm rather than for the person paying the bill.
Nobody has the list
Ask any partner what the practice pays for and you will get six items. Ask the person who reconciles the card and you will get most of them, in the order they appear on a statement, with three that nobody can identify. The real number in a small firm is commonly somewhere between twenty and forty recurring lines.
This is not carelessness. The stack was assembled over a decade, by different people, on different cards, for reasons that were good at the time. Several items were free when they started. Two were bought for a single client who has since left. One is a duplicate of another, bought because the first one was in somebody else’s name.
What a practice actually pays for, in shape rather than in brand names: the tax preparation software and whatever it charges per return or per filing; a portal for delivering returns and collecting signatures; document management or a cloud drive; e-signature, sometimes billed by the envelope; a research subscription; practice management or workflow; the payroll engine; bookkeeping subscriptions, occasionally one per client ledger; time and billing; a payment processor; email and file storage; the phone system; a website and a domain; professional indemnity; the licensing body and any state registrations; CPE; the backup service nobody has ever tested a restore from.
Every one of those bills by email, including the ones paid by card and the ones paid by direct debit. Which means the mailbox holds the only complete copy of the list, and holds it in the worst possible form: scattered across a year, filed under the minute each vendor’s billing run happened to fire.
Deriving the list is a two-hour job and it is done once. Twelve months of card and bank statements down one side, a mailbox search for recurring senders down the other. The statements tell you what left the account. The mailbox tells you what it was for, which the statements cannot, because a card line reading PLATFORM SVCS LLC identifies nothing. Neither source works alone, and the mailbox half is the one that survives the person who set everything up leaving the firm.
What goes on the list is seven columns and one of them does the real work. The vendor, what it is for, the renewal date, the notice window, whose name the account is in, which card pays for it, and whether it is recharged to a client. Then the column firms leave off: one sentence saying what stops if this lapses. That is what turns a schedule of expenses into a schedule of risks, and it is the only version anyone reads twice.
Do it in a quiet month, along with everything else the firm decides in advance rather than under pressure. Inbox zero during busy season makes the general case for moving that kind of work out of the weeks that cannot hold it, and this list is a good candidate, because it is entirely made of things that will not complain if they are skipped.
The seats you added in January
Per-seat pricing and seasonal staffing do not get on, and the mailbox is where the argument is recorded.
You take on three preparers in January, so you add three seats. In May the preparers go. The seats stay, because removing a seat is a small errand with no deadline attached to it, and because the confirmation of the addition arrived by email while the reminder to reverse it was never written anywhere. Next January you add three more, from a base that is now three higher than it should be. The ratchet only turns one way, and it turns once a year.
Pay-per-return blocks behave the same way at a different rhythm. A block gets bought in advance at a sensible price, runs out in the middle of March, and is topped up at speed by whoever was at the desk when the software refused, on whatever terms were in front of them. Nobody afterwards compares blocks bought against returns filed, so the firm never finds out whether the per-return cost it quotes itself is anything like the one it pays.
The fix is not a billing discipline. It is the same discipline this collection applies to a client request, turned around and pointed at the firm. When you ask a client for something, the date you will chase it on is fixed in the same breath as the asking, rather than whenever it dawns on somebody that nothing came. Running the firm inbox derives both of those dates properly. Applied here it comes to one line: write down the removal date on the day you create the seat, and put it somewhere that will come looking for you in May.
There is a second reason to keep those confirmations, and it is not about money. The seat additions are frequently the only record of who was given access to what. A seasonal preparer who left in April and still has a login to the tax preparation software is a live problem, and the email confirming the seat was created is often the only place in the firm that knows the login exists.
Whose name the account is in
Vendors do not bill firms. They bill whoever created the account, and everything that follows from that is a routing problem the practice has to solve on its own.
The account for the research subscription is in the name of a preparer who left three years ago, so the renewal notice goes to an address that bounces or, worse, to one that still delivers into a mailbox nobody opens. The card is in a partner’s own name. The password reset for the billing login goes to a personal address that person no longer uses. The invoice itself carries an individual rather than the practice, which is a small problem for the expense claim and a larger one if anybody ever looks properly.
The failure this produces is the same every time and it is the most expensive thing in this article. A card expires. The charge declines. The vendor emails the account holder, politely, three times, over three weeks. Nobody reads any of them. The software locks the day before a filing deadline, and the firm spends an afternoon on hold trying to prove it is entitled to an account nobody in the room owns.
Three things prevent it, and none of them is a purchase.
Name one address as the firm’s billing record. Which address, and who is accountable for reading it, is a decision the collection has already made once in a broader form, and the reasoning is in running the firm inbox. The answer here is the same: the mechanism matters far less than the fact that the sentence exists in writing.
Then change it at the vendor rather than forwarding into it. A forwarding rule gets you a copy of the invoice and leaves the vendor still holding the dead address, which means the password reset, the security notice and the final warning all go somewhere nobody is standing. That distinction is invisible until the day it is the whole problem.
And put the card’s expiry month on the list from the section above, alongside the renewal dates, because a card expiring is a scheduled event that presents itself as a surprise.
One more thing belongs here even though it is not really about email. If your firm has a checklist for somebody leaving, it almost certainly covers the mailbox and the building keys. Vendor accounts sit outside it in most practices, which leaves the firm both paying for and reachable through a person who no longer works there.
The ones you buy for a client
A slice of the stack is not the firm’s cost at all. Signature envelopes bought for one engagement. A payroll subscription in a client’s name that you pay and recharge. A hosted ledger seat. A filing or registration fee paid on a client’s behalf. A per-return charge that belongs to exactly one return.
Each of those invoices is two documents at once: a cost to the practice and an input to a client’s bill. If it stays in the mailbox it only ever becomes the first.
That makes this the quietest failure in the collection, and it is worth being precise about why. Everywhere else in a practice, a missing thing announces itself. A document that has not arrived holds up a return. An unsigned letter stops work. A query with no answer sits on somebody’s desk. Here nothing stops. An unrecharged disbursement produces no gap, no stalled job and no client asking where it got to, so a firm can absorb the same cost every quarter for years and never once encounter the fact.
The rule that holds it is unforgiving and short: the invoice is attributed to a client on the day it arrives, or it is not attributed at all. Ten months later, nobody can say which engagement forty signature envelopes were for, and the honest thing to do at that point is stop trying.
There is a slower cost underneath the obvious one. Disbursements that never get billed teach the firm that a client is cheaper to serve than they are, and that misreading turns up later in a fee conversation where it does real damage.
Client supplier invoices are a separate job with the same word in the middle of it. When a client’s own bills arrive in your mailbox for coding, or when a bookkeeper is forwarding purchase invoices in for the ledger, that is bookkeeping traffic rather than the firm’s payables, and it belongs to a calmer inbox for bookkeepers.
The invoice that is not real
A practice is a deliberate target rather than an accidental one. It moves money, the people who authorise payments are few and busy, and behind them sit clients whose money the firm can sometimes be persuaded to move. Invoice mail is the natural way in, because it is the one category everybody processes with their attention somewhere else.
Three shapes account for nearly all of it.
The invoice for something you do not have. Domain renewals, directory listings, registration or filing services, trademark watch notices, a final demand for a subscription that never existed. These work for exactly one reason: nobody in the firm can say from memory whether the practice has that service. Which is the same gap the list closes, and the best argument for spending the afternoon on it.
The real supplier with new bank details. Well written, correctly branded, often sitting inside a genuine thread, and occasionally sent from the supplier’s actual mailbox after it has been broken into. This one is expensive and it does not look wrong, because most of the time nothing about it is wrong except the account number.
The sign-in page wearing an invoice’s clothes. Your payment failed, your account will be suspended, click here to update your card. It works best in the fortnight when everyone in the building is moving quickly and the fear of losing access to the tax software is real.
Three checks handle all three, and none of them requires anybody to become good at spotting forgeries.
A change to where money goes is confirmed by voice, on a number the firm already held, before anything is paid. Not a number in the message, not a reply to the thread, and not once you have looked at it hard and decided it is fine. Every time, including the times it obviously is.
An invoice you do not recognise goes against the list rather than against somebody’s memory. If it is not on the list, nobody pays it while they find out.
A message saying your payment failed is checked by going to the vendor yourself and looking at the account. The link in the message is never the route, even when the message turns out to have been genuine.
The last one is about the firm rather than the mail. Whoever pays the invoices should not be the only person who ever sees them. A second pair of eyes on anything that changes where money goes is not a control framework and does not need a policy document. It is one sentence about how the firm behaves, and it is the difference between a bad afternoon and a very bad year.
Capture on the day or not at all
What has to be kept is the invoice, and the invoice is often not what was emailed to you.
A large share of software vendors send a notification rather than a document. Your payment was successful, view your invoice, with a link into a billing portal. The link expires, or it needs a login that the bookkeeper does not have and would not be given, and the message that remains in the archive is proof that something was paid without saying what for. Where input tax is reclaimable, the notification does not support the claim and the document does. So the capture is the download, taken while the link is alive and while somebody still knows which vendor it belongs to.
The reason to do it on the day is that the alternative is reconstruction, and reconstruction here is unusually hard. The card line says PLATFORM SVCS. The vendor’s trading name is not its legal name. The subscription was renamed when the product was acquired. Ten months later this is an afternoon of forensic work on an amount too small to justify it, which is why it usually ends in a guess.
There is a sharper version of that point, and it is the one worth taking away. A practice closes years for a living. The one year that gets closed carelessly is its own, because there is no client on the other end of it asking how it is going, and no deadline that anybody outside the building is watching. The client version of that job is the year-end close. This is the one nobody chases you for.
Coding on arrival takes seconds and answers three questions while they are still cheap: which client, if any, which category, and which period it covers. That last one catches the annual charge paid in month one and belonging across twelve, which is the single most common misstatement in a small firm’s own accounts.
And keep the mail. The rest of this collection keeps the archive because it is evidence of what was asked and when. Here it is evidence of a price you agreed to, a term you accepted, a notice you were or were not sent, and a bank account that was correct in March. All four are things you may one day have to show, and none of them exists anywhere else.
Where does Point fit?
A lever-arch file and a wall calendar handled all of this for a very long time, and a firm keeping an honest list still needs nothing more. Software moves only the remembering and the capture. Which subscription earns its money, whose bank details those really are, what the seat count ought to be in June: none of those move anywhere.
The ranking deserves saying first, because it is what Point is best known for, and of every job in this collection it helps this one least. A supplier invoice sitting below a client’s answer about a loan account is correctly ordered. On the worst morning of the year you want the client, and a tool that pushed the invoice up over them would be wrong. Why importance and urgency are two separate measurements is that argument in full, and what the weighing actually measures is a subject of its own. What this class needs is not to be promoted. It needs to lose safely, which is a different capability.
A standing request in plain words is the closest fit there is. Ask to be told when anything arrives from a named vendor, or when a renewal or a price change comes in, and you hear once, when it lands, rather than watching a pile you have every reason to skim. For a stack of twenty renewal dates you cannot hold in your head, that is close to the whole discipline.
Where a message puts something on you, it turns into a dated item with nobody retyping it anywhere, and a renewal notice is exactly that shape: a decision with a date on it, four paragraphs down, under a subject line that reads like an announcement. How a task gets lifted out of a message covers the mechanism. Things you have set aside come back on the day you chose rather than the day they occur to you, which is the entire renewal rule, given that the notice is worth nothing on the morning it arrives and a good deal in the last week you can still act.
Capture is well served. Attachments stop living inside conversations and collect into a single dated list, each of them still tied to the mail it came in on, which is the shape a year of invoices wanted all along. Search reads what you meant rather than the words you typed, so last March’s portal invoice is findable without remembering the vendor’s legal name. A document will also answer a question about itself and point at the line the answer was read from, which on an invoice is usually the two facts you wanted: the period it covers, and the number of seats being charged for.
On the ones that are not real, Point holds risky mail at the door and sets it aside before it reaches you, so it is something you decide about rather than react to, and mail from a sender it does not recognise is held back rather than read into anything. Take that for exactly what it is: a judgement about a message, not knowledge of your supplier’s bank account. The phone call to a number you already had is still the control, and nothing in any mail product replaces it.
A reply arrives already written in your own voice, so the note taking a seat off in May, or the message asking a vendor to correct the billing address, arrives needing a correction instead of a start, and on the day a renewal is better settled by phone, finding a time everyone can make is handled without the thread. How far it takes any of that alone is set for each kind of action rather than once for everything, and every one of them ships at review, meaning the work is prepared and then waits. The dial is the proper treatment. Filing and coding an incoming receipt is among the first things worth raising, being frequent, short and hard to get badly wrong. Anything that authorises a payment, or answers a message about where money is sent, is the last, and should have a person reading it every single time. What Point does shows up in a log with times against it, and the log is where you take an action back, with the one exception no mail software escapes: a message already delivered to somebody else’s server has gone.
Connecting is a sign-in to the Google or Microsoft account the practice is already on, which matters more here than it sounds: the billing address held on file by forty vendors never has to change. If you also run a second business alongside the practice, each business you operate is kept apart from the other, which is the boundary you want on the day the same vendor bills both of them.
What Point has no version of is accounts payable. It holds no vendor list, it has never seen your card, it cannot cancel a subscription, it does not know what your contract says, it pays nothing and it posts nothing to a ledger. It has no opinion about whether a renewal is worth the money, which is the only question in this article that actually matters. The full inventory sits on the benefits page, Point for accountants arranges the same capabilities around a practice, and the questions to put to any vendor before an account is connected are in is an AI email client safe for client data.
Common questions
Should the firm send software invoices to a separate email address?
A dedicated billing address is worth having, but only if it is the address the vendors themselves hold and somebody is named to read it. An address that mail is merely forwarded into solves the wrong half of the problem: you get a copy of the invoice while the vendor still has a dead address for the password reset, the security notice and the warning before the account locks. So change the record at each vendor rather than adding a rule, and write down who reads the resulting mailbox. A billing address with nobody accountable for it is where renewals go to happen unobserved.
How do we stop subscriptions renewing without anyone deciding?
Hold the dates yourself rather than relying on being told, because whether a notice arrives at all, and how far ahead, varies by vendor and by where you are. Build the list once from twelve months of card statements read against the mailbox, and put the renewal date and the notice window on every line. Then treat the notice when it comes as a dated decision rather than as something to read on arrival, because on the day it arrives you do not yet have the one input the decision needs, which is what the thing got used for over the year. Set it to come back in the last week you can still act, and do the usage read before that week rather than in it.
What should a firm keep from a software invoice?
The invoice document itself, not the email saying a payment succeeded. A great many vendors send only a notification with a link into a billing portal, and that link expires or needs a login your bookkeeper does not have. Where input tax is reclaimable, the notification will not support the claim. Download it while the link is live, and code it the same day to a client if it is recharged, a category, and the period it actually covers, because a card line reading PLATFORM SVCS LLC identifies nothing ten months later and the annual charge paid in month one belongs across twelve.
How do we spot a fake invoice or a change-of-bank-details email?
Do not try to spot them, because the convincing ones are convincing and some are sent from a supplier’s genuine mailbox after it has been broken into. Use three habits instead. Any change to where money goes is confirmed by voice on a number the firm already held, never a number in the message and never by replying, every time and including when it obviously looks fine. Any invoice for something nobody recognises is checked against the firm’s list of what it actually pays for, and is not paid while that is happening. Anything saying a payment failed is checked by going to the vendor’s site yourself rather than through the link. And whoever pays the invoices should not be the only person who ever sees them.
Is any of this different for an accounting practice than for any other small business?
Four things are. Several items in a practice’s stack are the only route by which something gets filed on a date nobody can move, so a lapse is not an inconvenience but a missed deadline. Per-seat and per-return pricing collides with seasonal staffing, which makes the cost ratchet upward once a year. Part of the stack is bought for named clients and is a billing input as well as a cost, which nothing else in the firm will notice going missing. And a practice is a deliberate fraud target rather than an accidental one. The parts that are simply true of running any small business, and they are real, belong with running a one-person business from your inbox instead.
The short version
Supplier and software invoices are mostly receipts for money that has already gone, so the job is capture rather than payment, and the mail is right to sit below the client work. What hides in the pile is the renewal or price notice, which is the only message here carrying a decision, and where doing nothing means buying it again at the new price. Derive the list once from a year of card statements read against the mailbox, and put a renewal date, a notice window, an account holder and one sentence on what stops if it lapses against every line. Date the seat you add in January to come off in May. Change the billing address at the vendor rather than forwarding into it, so the password reset and the final warning land somewhere somebody is standing. Attribute anything bought for a client on the day it arrives, because nothing will ever remind you. Confirm every change of bank details by voice on a number you already had. And capture the document rather than the notification, coded and dated, on the day, because the year nobody chases you about is your own. Every other recurring job in a practice is treated one at a time alongside this one, and anyone at the point of comparing products is better served by AI email for accountants.