Your practice pays for a stack of software and services longer than anyone can list from memory, and every item in it 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’s the right outcome. A few of the messages in that pile 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 everything in the pile is already paid and the job is capture rather than payment.
- One message in the pile carries a choice: the renewal or price notice. It turns up weeks before the invoice, in the same template as the newsletters. Ignoring it is a purchase.
- Ask anyone in the firm what the firm pays for and the list comes up short. The mailbox is the only place the whole stack is visible, and deriving the list from it takes an afternoon, once.
- A lapse surfaces weeks after it happens. It arrives as a locked account or a declined card, in the week you can least afford either.
Three kinds of message in one pile
It all arrives looking the same. A sender you half recognize, a subject line with a number in it, usually an attachment. Sort it and 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 confirms it. It’s settled before you see it. What the message holds is a document you’ll need in ten months, kept by a firm that thinks about it again in the tenth.
A smaller part is a real 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. They’re the easiest of the three, because your practice already knows how to hold a due date.
The third kind is a notice, and it’s the one this whole subject turns on. Your plan renews on the fourteenth. Your price is changing. Your card ends in two weeks. A seat was added. The terms have been updated. Each one asks for a decision rather than for money, and a decision expires, so filing it loses it.
In most businesses, missing that third kind 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. The day they stop working is picked by a vendor’s billing system.
The message that buys it again
Elsewhere in your practice, silence is ambiguous. That’s worked through properly in quarterly estimate reminders, where a client saying nothing back is the normal outcome and proves little either way.
Here silence has exactly one meaning. It means yes, again, for another year, at whatever the new price is.
That’s what makes the renewal notice the message in the pile that matters most, and the one most reliably skimmed. Four things make it easy to miss.
It looks like marketing. It comes from the same sender and the same template as the product announcements, and half of it genuinely is marketing. The part that matters is one line in the middle.
It arrives at the wrong moment. You might get thirty days, seven days, or none at all, depending on the vendor and on where you are. So treat a notice as a courtesy and hold the date yourself. Tax software is the sharpest case. The offer for next season lands while you’re 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’s the only place that increase shows up before it’s 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 yet: what the thing actually got used for over the past year. So on the day a renewal notice arrives, the honest answer to most of them is that you’ll decide later.
You’re allowed to leave it. The working rule is one line. Date the notice to the last week you can still act, and let it come back then, with the annual read described below already done. A message worth nothing today and a good deal in five weeks is exactly what snoozing was built for. It’s one of the few places in a practice where pushing something away is the responsible move.
Two smaller notes on notices. A price rise is negotiable far more often than firms assume, and the notice is the moment when asking is free, because after the charge you’re requesting a refund rather than discussing a rate. And a terms update is worth thirty seconds when the vendor holds client documents. 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’ll get six items. Ask whoever reconciles the card and you’ll 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 runs between twenty and forty recurring lines.
This is how a stack ends up, and it happens to careful firms. It 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 duplicates another, bought because the first one sat in somebody else’s name.
Here’s 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. So the mailbox holds the only complete copy of the list. It holds it 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 you do it 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, because a card line reading PLATFORM SVCS LLC identifies nothing on its own. You need both halves, and the mailbox half is the one that survives the person who set everything up leaving the firm.
The list is seven columns wide, and one column does the real work. The vendor, what it’s for, the renewal date, the notice window, whose name the account is in, which card pays for it, and whether it’s recharged to a client. Then the column firms leave off: one sentence saying what stops if this lapses. That’s what turns a schedule of expenses into a schedule of risks, and it’s the version anyone reads twice.
Do it in a quiet month, 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 can’t hold it. This list is a good candidate, because every line on it stays quiet when it’s skipped.
The seats you added in January
Per-seat pricing and seasonal staffing pull against each other, 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. Removing a seat is a small errand with an open deadline, and the confirmation of the addition arrived by email while the reminder to reverse it lived nowhere. Next January you add three more, from a base that’s now three higher than it should be. The ratchet turns one way, and it turns once a year.
Pay-per-return blocks do the same thing on a different rhythm. A block gets bought in advance at a sensible price. It runs out in the middle of March, and it’s topped up at speed by whoever was at the desk when the software refused, on whatever terms were in front of them. Afterwards the blocks bought and the returns filed stay in separate places, so the per-return cost the firm quotes itself drifts away from the one it pays.
The fix 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, you fix the date you’ll chase it on in the same breath as the asking. Running the firm inbox derives both of those dates properly. Applied here it comes to one line. Write the removal date down on the day you create the seat, and put it somewhere that comes looking for you in May.
Keep those confirmations for a second reason, and this one is about access. The seat additions are frequently the only record of who was given access to what. A seasonal preparer who left in April and still holds a login to the tax preparation software is a live problem. 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
A vendor bills whoever created the account. Everything downstream of that is a routing problem the practice solves on its own.
The account for the research subscription is in the name of a preparer who left three years ago. 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 gave up years ago. 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 runs the same way every time, and it’s 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. The mail lands where nobody is standing. The software locks the day before a filing deadline, and the firm spends an afternoon on hold trying to prove it’s entitled to an account nobody in the room owns.
Three habits hold it off, and all three are free.
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. What matters is that the sentence exists in writing.
Then change the record at the vendor. A forwarding rule gets you a copy of the invoice, and it leaves the vendor still holding the dead address. The password reset, the security notice and the final warning all go there. That difference stays invisible until the day it’s the whole problem.
And put the card’s expiry month on the list from the section above, alongside the renewal dates. A card expiring is a scheduled event that presents itself as a surprise.
One more thing belongs here, and it reaches past email. Your firm’s checklist for somebody leaving almost certainly covers the mailbox and the building keys. In most practices, vendor accounts sit outside it. That leaves the firm paying through, and reachable through, a person who has moved on.
The ones you buy for a client
A slice of the stack belongs to a client. 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. Left in the mailbox, it stays the first one only.
That makes this the quietest failure in the collection, and it’s worth being precise about why. Everywhere else in a practice, a missing thing announces itself. A document still in transit holds up a return. An unsigned letter stops work. A query sits on somebody’s desk waiting for an answer. Here the work carries straight on. An unrecharged disbursement leaves the job running, the client quiet and the quarter closed, so a firm can absorb the same cost every quarter for years and meet the fact once, late, if at all.
The rule that holds it is short. The invoice is attributed to a client on the day it arrives, because that’s the only day the answer is in the room. Ten months later, which engagement forty signature envelopes were for is gone, and the honest move at that point is to stop looking.
There’s a slower cost underneath the obvious one. Unbilled disbursements teach the firm that a client is cheaper to serve than they are. 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. A client’s own bills arriving in your mailbox for coding, or a bookkeeper forwarding purchase invoices in for the ledger, is bookkeeping traffic rather than the firm’s payables. That work belongs to a calmer inbox for bookkeepers.
The invoice that is not real
A practice is a deliberate target. It moves money, the people who authorize 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. It’s the one category everybody processes with their attention somewhere else.
Three shapes account for nearly all of it.
The invoice for a service you’ve never had. 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. From memory, nobody in the firm can say whether the practice holds that service. The list closes that same gap, which is 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 reads as ordinary, because most of the time everything about it is right 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 two weeks 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 they run on habit rather than on an eye for 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 don’t recognize goes against the list rather than against somebody’s memory. If the list stays silent, the invoice waits while somebody finds out.
A message saying your payment failed is checked by going to the vendor yourself and opening the account. You take your own route in, 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 have a second pair of eyes on anything that changes where money goes. That’s one sentence about how the firm behaves, written down. It’s the difference between a bad afternoon and a very bad year.
Capture on the day or not at all
What you keep is the invoice document itself. The mail often carries a pointer to it instead.
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 wants a login the bookkeeper has no route to. What’s left in the archive shows that something was paid and stays quiet about what for. Where input tax is reclaimable, the claim rests on the document. So the capture is the download, taken while the link is alive and while somebody still knows which vendor it belongs to.
Do it on the day, because the other route is reconstruction, and reconstruction here is unusually hard. The card line says PLATFORM SVCS. The vendor’s trading name differs from its legal name. The subscription was renamed when the product was acquired. Ten months later that’s an afternoon of forensic work on an amount too small to justify it, so it usually ends in a guess.
There’s a sharper version of that point, and it’s the one worth taking away. A practice closes years for a living. The one year that gets closed carelessly is its own, because the other end of it is empty. No client asks how it’s going, and no deadline 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 it answers three questions while they’re still cheap. Which client, if any. Which category. 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 as evidence of what was asked and when. Here it’s 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 the mail is the only place they live.
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 does fine on them. Software moves the remembering and the capture. The judgments stay with you. Which subscription earns its money, whose bank details those really are, what the seat count ought to be in June.
The ranking deserves saying first, because it’s 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 wants is to lose safely, which is a different capability from being promoted.
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. You hear once, when it lands, and the pile stays where it is. For a stack of twenty renewal dates you can’t hold in your head, that’s close to the whole discipline.
Where a message puts something on you, it becomes a dated item, and you retype nothing. 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’ve set aside come back on the day you chose, which is the entire renewal rule, given that the notice is worth little on the morning it arrives and a good deal in the last week you can still act.
Capture is well served. Attachments 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 turns up under a description instead of the vendor’s legal name. A document will also answer a question about itself and point at the line the answer was read from. On an invoice that’s usually the two facts you wanted. The period it covers, and the number of seats being charged for.
On the ones that are fake, Point holds risky mail at the door and sets it aside before it reaches you, so it’s something you decide about rather than react to, and mail from an unfamiliar sender waits there too. Take that for exactly what it is. It’s a judgment about a message, and your supplier’s bank account sits outside it. The phone call to a number you already had is still the control, and it stays the control whatever mail product you run.
A reply arrives already written in your own voice. 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. On the day a renewal is better settled by phone, finding a time everyone can make is handled without the thread. How far Point 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. The work is prepared, and then it waits for you. 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 authorizes a payment, or answers a message about where money is sent, is the last, and a person reads 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. One exception holds across every mail product: 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 stays exactly as it is. 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.
Accounts payable sits outside Point. Point holds no vendor list, has never seen your card, and posts nothing to a ledger. Cancelling a subscription, reading what your contract says, and paying a bill all stay with you and your own systems. Whether a renewal is worth the money is yours to decide, and it’s 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, on two conditions. The vendors themselves hold that address, and somebody is named to read it. An address that mail is merely forwarded into gets you a copy of the invoice, while the vendor keeps the 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 somebody accountable for it is the one where renewals get seen.
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. On the day it arrives you’re still missing 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, rather than 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 wants a login your bookkeeper has no route to. Where input tax is reclaimable, the claim rests on the document. Download it while the link is live. Code it the same day to a client if it’s recharged, a category, and the period it actually covers. 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?
Spotting them is the wrong job, and you’re off the hook for it. 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. Confirm any change to where money goes by voice, on a number the firm already held rather than one in the message, and by a call rather than a reply, every time and including when it obviously looks fine. Check any invoice for something nobody recognizes against the firm’s list of what it actually pays for, and hold payment while that happens. Check anything saying a payment failed by going to the vendor’s site yourself rather than through the link. And whoever pays the invoices should have a second person seeing 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 costs you a 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, and it’s the one thing in the firm that goes missing quietly. And a practice is a deliberate fraud target rather than an accidental one. The parts that are simply true of running any small business are real too, and they belong with running a one-person business from your inbox.
The short version
Supplier and software invoices are mostly receipts for money that has already gone. 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. It’s the one message here carrying a decision, and silence on it buys the thing again at the new price. Derive the list once from a year of card statements read against the mailbox. 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 that’s the only day the answer is in the room. 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.