Three protections keep client invoices and email recoverable after ransomware: locking final invoices, holding client email, and keeping a separate copy of both.
Key takeaways
- Lock issued invoices in your billing system, and limit unlock rights to a few named people.
- Confirm that an In-Place Hold, Litigation Hold, or retention policy covers every mailbox that handles client email.
- Keep a copy of invoices and mail in storage that everyday logins cannot change.
- Run a restore test on each copy, and write down the date and who ran it.
Why client invoices and email are the target
A small accounting firm keeps two kinds of records that matter more than almost anything else on its systems. The first is invoices: the documents that show what a client was billed, when, and whether it paid. The second is client email. It is where clients send tax documents, ask questions, approve work, and give instructions that nobody has written down anywhere else.
When ransomware reaches a firm's network, these are the records that hurt most to lose. They also tend to sit in systems with the widest access, which makes them an easy place for an attack to spread.
Ransomware aims to lock people out of their data and make recovery expensive or slow. For a firm with a few partners and a handful of staff, the damage is practical. Billing stops because nobody can open the invoice tool. Client questions pile up because the shared mailbox is encrypted or missing messages. A partner cannot answer a client who asks what was sent last spring, because the only copy sat on a laptop that is now quarantined. The firm keeps going, but every week costs more than it should.
The groups behind these attacks do not have to build every tool themselves. The CISA advisory on LockBit notes that several of the group's tools remained available for outside operators: "LockBit 2.0, LockBit 3.0, LockBit Green, and LockBit Linux-ESXi Locker are still available for affiliates’ use on LockBit’s panel." ( CISA advisory) In plain terms, a criminal can pick up ready-made software and run an attack. The threat does not depend on one group staying in business.
The same advisory's country notes show how far that reach went. For Australia, "The earliest documented occurrence of LockBit 3.0 was in early August 2022." Over one year, "From April 1, 2022, to March 31, 2023, LockBit made up 18% of total reported Australian ransomware incidents." ( CISA advisory)
Canada shows the same pattern from an earlier date: "The first recorded instance of LockBit activity in Canada was in March 2020." New Zealand's reporting service saw the group in volume: "In 2022, CERT NZ received 15 reports of LockBit ransomware, representing 23% of 2022 ransomware reports." ( CISA advisory)
For a firm, the lesson is that brands change and the attacker's reach does not. The more useful question is what would be lost if any group got in.
That is why this post is about records, not attackers. You cannot fully control whether someone gets into your network. You can control whether, after an attack, the invoices and client email are still there, readable, and trustworthy. That depends on protections put in place in advance, because the systems you would use to configure them on the day of an alarm may already be compromised.
This post covers three protections. The first is locking invoices once they are final. The second is holding client email so that deleted or edited messages leave a copy behind. The third is keeping a separate copy of both, stored where a compromised login cannot reach it. For each, I describe what it does, what it does not do, and what to check. None of them replaces a sound security program, a proper backup plan, or a response plan. Together, they reduce the chance that an attack becomes a permanent loss.
Lock invoices once they are final
Invoices show what was billed and when, so they need to hold still once a client has them. A draft that gets edited is normal. The trouble starts when an invoice the client already received changes quietly. The amount shifts, a line disappears, or the date moves. The cause might be a staff member fixing a typo, a shared login used carelessly, or an attacker. From the client's side, all of these erode trust. From the firm's side, they make any later dispute harder to settle.
Zoho Books offers record locking for this reason. The Zoho Books help page describes its feature this way: "Record Locking allows you to lock the records (items, quotes, sales orders, invoices, credit notes, and custom module transactions) in your organization." ( Zoho Books help) The same page says the feature is "useful for protecting important information and preventing accidental changes." ( Zoho Books help)
The key phrase is accidental changes. A lock guards against edits made through the product in the ordinary way. It is not a backup, and it offers little real barrier against someone who controls an account with the rights to unlock.
Once you find the setting in your own billing system, check the following before you rely on it.
- Which record types it covers. Confirm that issued invoices and credit notes are included, not only items or quotes. Check whether estimates lock while invoices stay open.
- Who can unlock. If nearly everyone can unlock a finalized invoice, the lock stops careless clicks but does little against a login used by someone with that permission. Limit unlock rights to a few named people, and review the list when someone leaves.
- What the rules allow. The setting asks you to choose whether to "Restrict All Actions, Restrict Selected Actions, or Allow Selected Actions." ( Zoho Books help) A firm that wants strict control will restrict everything and allow only the few actions it needs. Decide on purpose and write the choice down rather than accepting the defaults.
- How changes are recorded. Find out whether the system keeps an audit trail of edits, deletions, and unlocks, who can see it, and how long it is kept. Assign one named person to read it, because a trail nobody reads is of little use.
Check whether the lock covers drafts as well as issued invoices. If a draft holds something important, such as an agreed rate, record that agreement in a document with its own version history.
Compare the three protections side by side
The three protections do different jobs, apply to different systems, and fail in different ways. Treating them as interchangeable leaves gaps. The table shows where each one fits.
| Protection | Where it applies | What it guards against | What it does not do |
|---|---|---|---|
| Record locking in the billing product, such as Zoho Books | Issued invoices, credit notes, and other records inside the billing system | Accidental or unwanted edits made through the product | Stop anyone who can unlock records; does not create a copy outside the product |
| Mailbox holds in Exchange Online | Client correspondence in Microsoft 365 mailboxes | Accidental or malicious deletion, and earlier versions of edited messages once the protection is switched on | Does not keep copies where the hold was never switched on; not a filing system |
| A separate copy of invoices and mail, kept offline or in protected storage | Exported invoices and a mail archive held apart from the live systems | Changes or deletions in the live systems, if the copy cannot be reached or overwritten from them | Work by themselves; a copy you have never restored from is only an assumption |
Read the table as a set. Locking keeps the billing record honest in normal operation. Mailbox holds keep client email recoverable when messages are removed or changed. The separate copy is the one that still works if the live systems are compromised, which is why it matters most when the other two fail. The next two sections take the email hold and the separate copy in turn.
Hold client email so deletions leave a trace
Client email is harder to protect. Many people write to it, messages get deleted casually, and in many firms it is the only record of client instructions. Deleting messages is a normal part of managing an inbox. That is exactly why a deletion made by an attacker, or through a compromised account, can look ordinary. An email hold keeps copies of messages even after they are deleted or edited.
If your firm uses Microsoft 365, Exchange Online has a Recoverable Items folder for this purpose. Microsoft's documentation says that "to protect from accidental or malicious deletion and to facilitate discovery efforts commonly undertaken before or during litigation or investigations, Exchange Online uses the Recoverable Items folder." ( Microsoft Learn) The detail that matters most is what the folder keeps and when. Microsoft states that "if In-Place Hold, Litigation Hold, or a Microsoft 365 or Office 365 retention policy is enabled, this subfolder contains the original copy of the item; and also, if the item is modified multiple times, a copy of the item before modification is saved." ( Microsoft Learn)
Read together, those statements set the rule. Copies are kept when a hold or retention policy is enabled. Turn that into a checklist for your own tenant.
- Confirm the current state. Find out whether an In-Place Hold, Litigation Hold, or retention policy is on for the mailboxes that handle client correspondence. Get the answer from your IT provider in writing.
- Cover staff mailboxes, not only partner mailboxes. Staff inboxes often hold the most recent client instructions and the replies that were actually sent. A hold that covers partners but misses bookkeepers protects the wrong messages.
- Protect who can change the hold. Removing a hold should require a limited administrator role, not an everyday account. If an attacker takes over an ordinary login, they should not be able to switch off protection. Keep administrator accounts few, each with strong, separate credentials.
- Test a restore. Delete a test message in a test mailbox and recover it through the folder the platform provides. Do this after the hold is applied and after any major change to the mail system. A protection never tested is a belief, not a control.
- Record the scope. Write down which mailbox groups are covered, so the list can be checked when someone joins or leaves. For the staff side of this, see employee data retention tools for staff who leave.
Holds keep copies; they do not organize them. Keep your normal filing system, with client folders, naming conventions, and a clear place for signed documents. A person still has to find the right message quickly when a client calls, and the two work together.
Be clear with your IT provider about what the hold does not cover. Email holds protect messages in the mail system. They do not protect files saved to a laptop desktop, documents in a personal cloud folder, or spreadsheets someone emailed to themselves and then deleted. Ask about those gaps before an incident exposes them.
Keep a copy the live systems cannot change
The first two protections live inside systems ransomware targets. If an attacker gains an account with enough rights, they may reach both. The third protection is a separate copy of invoices and client email, kept where a logged-in account cannot easily change or delete it. This is the layer meant to hold up when the live systems are the problem.
The method depends on your setup and budget, but the principle is the same: separate the copy from the account that makes everyday changes. Three approaches fit small firms well.
- An offline or removable drive, connected only while the copy job runs. It cannot be reached over the network while unplugged, which is its main value. Someone must still own the job and its schedule.
- A backup service with immutable storage, which keeps copies unaltered for a set period. Ask exactly what immutability guarantees, who can override it, and how the retention period is set. Marketing language and actual controls can differ.
- A separate account with copy-only rights. The account running the job should not edit invoices or send client email, and it should not be able to delete the copies it creates.
Set the copy schedule by how much loss the firm could accept. A firm that could tolerate losing a day of invoices may not tolerate losing a week of client instructions. Write the answer down for each record type, then set the schedule to match it.
Test the copy the same way you test the holds. Pick a small set, such as one client's invoices for one period, and restore it to a machine not connected to the main network. Open the files, check the amounts against the originals, and confirm the attachments open. Record the date and who ran the test. The first problem with the copy should not surface during a real incident.
Finally, keep a written record of where the copies are, how to restore them, and who to call. People under attack cannot be relied on to remember steps. A one-page instruction sheet stored somewhere other than the systems that may be locked is among the most useful things a small firm can prepare.
Setting them up in order
These protections are not equally hard to set up. Start with the easiest and most obvious gaps, then work toward the copy that needs the most planning.
Begin with mailbox holds if you use Microsoft 365, since the question is answered by a few settings and a written confirmation from your provider. Next, review the billing system's locking options and decide which record types to lock and who can unlock them. Then design the separate copy, choose a method, set a schedule, and run the first restore test.
Assign one named person to own the list. In a small firm, that is often the operations lead, who already knows where records live and which people use which systems. The partner approves choices, and the operations lead keeps the checklist current when staff change, a system is added, or a test fails. A list without an owner goes stale quickly. A related guide on handoffs is Accounting Client Intake Checklist for a Clear Handoff.
Review the list on a regular schedule and after any change to billing, mail, or staff. Ask three questions. Are holds still on for every mailbox that matters? Are locks still on for the record types that matter? When did the last restore test happen, and did it succeed? Any no or unknown answer goes to the top of the list.
None of this makes the firm immune to ransomware, and none of it replaces strong authentication, timely patching, and staff training. Those belong on the same list. What these protections change is the outcome. When an attack happens, the firm still has its invoices, its client email, and a tested way to bring them back. That can turn a crisis that stops the business into a serious but recoverable disruption, which is worth setting up before anything goes wrong.
Next step today: check whether a hold is on for the mailbox that receives client email, and whether issued invoices are locked. Write both answers down and give them to the person who owns the list.
Related guides: Client decisions to confirm before acting: 4 to record · Account deletion for firm records: 3 checks before removal · ACH invoice fees: 4 facts to check before a client pays.
Frequently asked questions
Does record locking stop ransomware?
No. Locking guards against accidental or unwanted edits made through the billing product, and it offers little real barrier against someone who controls an account with the rights to unlock.
Is a mailbox hold a backup?
Not on its own. A hold keeps copies of messages inside the mail system, and it does not cover files saved to a laptop or a personal cloud folder.
Why keep a separate copy if the other protections exist?
Because the first two protections live inside systems ransomware targets, and an attacker with enough rights may reach both.