Three vendor caps should be checked before any bulk client update: Gmail's daily limits on sending and receiving mail and on recipients, Microsoft 365's 10,000 tenant maximum for compliance policies, and Zoho Books' limit of 25 bulk actions on inventory adjustments at a time. The two numbers to remember are 25, which sets the batch size for Zoho's bulk actions, and 10,000, which sets the total for Microsoft compliance policies.
Chief takeaways
- Gmail caps both the number of emails you can send or receive per day and the number of recipients you can add, so split large sends.
- Work and school Gmail accounts follow their own sending limits, so confirm which account type each sender uses.
- Microsoft 365 counts compliance policies against a 10,000 tenant maximum, and MRM retention policies sit outside that count.
- Zoho Books allows bulk actions on only 25 inventory adjustments at a time, so plan updates in batches.
Gmail's daily send and recipient caps
Gmail sets two separate ceilings that matter for bulk client messages. The first is volume. Google's help page says Gmail "limits the number of emails you can send or get per day," which means received mail counts alongside sent mail. A firm that sends a reminder campaign on a busy day can reach that daily ceiling before the day ends, and client replies arriving in the same account draw on the same capacity. The second ceiling is audience size. Gmail also limits "the number of people you can add as recipients." A single send to a long client list can fail even when the daily total still has room.
Google gives the purpose of both limits in the same sentence: "To help prevent spam and keep accounts safe." That reason should shape how you plan. A sudden burst of near-identical messages to hundreds of addresses resembles the pattern spam filters are designed to catch, so treat the limits as a pacing guide rather than a target to approach. Split large lists into smaller groups, and spread sends across several days rather than one morning. Keep a simple log of how many messages went out each day and to how many recipients, so the operations lead can see when a campaign is nearing the line.
Two checks make this practical. Before any send, count the recipients and confirm the list fits the recipient cap. Then count what has already gone out from that account that day, including the messages it has received, so the total is never a surprise. Build both numbers into the procedure for every bulk client message, because the limit is enforced whether or not the team has noticed how close it is.
Why work-account Gmail users may face different limits
Google's help page includes a note that changes the picture for many small firms: "If you use your Gmail account through your work, school, or other organization, learn about Gmail sending limits through work or school." That sentence tells you the general limits described in the previous section do not automatically govern every account. An account provided through an employer or other organization follows its own sending rules, and those rules can differ from the ones that apply to a personal Gmail address.
Accounting firms often send client mail from a business domain rather than a personal login, which makes this difference easy to overlook. Suppose a partner sends from a personal Gmail address while the operations lead runs the bulk campaign from a shared firm account. The two senders may not share the same daily or recipient ceilings, and the inbox of each looks identical. A bulk procedure that assumes one set of numbers for every sender can therefore fail for the account that matters most.
The fix is a short inventory. List every mailbox that might send to clients, and mark each one as personal or organization-provided. Use the general limits only as a starting point for personal accounts. For any organization-provided account, apply the sending rules that the organization's account carries, and do not assume that a figure you saw once applies across the firm. Keep the inventory attached to the bulk-message procedure, so whoever runs the send knows which account and which rules apply before the first message goes out.
Side-by-side: Gmail, Microsoft 365 and Zoho batch limits
Each of the three vendors caps something different, and the difference determines how you check it. The table below lines up the measures row by row so you can see the unit, timing and figure for each cap.
| Vendor and cap | What it limits | Time or scope | Stated figure |
|---|---|---|---|
| Gmail, daily volume (source) | Emails sent and received | Per day | Set by Gmail |
| Gmail, recipients (source) | People added as recipients | Not specified in source | Set by Gmail |
| Microsoft 365, compliance policies ( source) | Compliance policies in the organization | Tenant-wide | 10,000 maximum |
| Microsoft 365, enrollment age ( source) | Limits applied to the organization | Length of enrollment | Varies with enrollment length |
| Zoho Books, bulk actions ( source) | Inventory adjustments in one run | Each batch | 25 at a time |
Read the table by its unit column. The Gmail caps are daily limits and a recipient count, so they must be rechecked on every send day. The Microsoft compliance figure is a standing ceiling for the whole tenant, so the ceiling stays fixed while only the count of counted compliance policies changes as policies are added or removed. The Zoho cap is a batch size, which means a larger job is simply split into runs of 25.
Microsoft's own page adds a caveat that belongs in the comparison: "The limits applied to a Microsoft 365 organization may differ depending on how long the organization has been enrolled in the service." Two firms with the same plan can therefore sit under different limits, so the figure you read in documentation is only a reference point until you confirm it for your tenant. The Zoho cap applies to inventory adjustments, not client records, so it is useful here as a model of batch discipline rather than as a limit on client updates.
Hold rules that can block a bulk edit in Microsoft 365
Microsoft's page names the kinds of holds that sit alongside ordinary policies: "Holds include Microsoft 365 retention policies and retention label policies, Microsoft Purview eDiscovery case holds, and In-Place Holds." Holds are a separate control layer from the compliance policy count discussed below, and they are the item most likely to surprise an operations lead who expects a bulk change to run cleanly. Before a bulk update touches mailbox content, confirm which holds apply to the affected accounts.
The table lists the four hold types named in the source, with a plain description of what to confirm for each one.
| Hold type | Named in the source as | What to confirm before a bulk change |
|---|---|---|
| Retention policy | Microsoft 365 retention policies | Which mailboxes or sites the policy covers |
| Retention label policy | Retention label policies | Which labels are published to the affected users |
| eDiscovery case hold | Microsoft Purview eDiscovery case holds | Whether any active case covers the client mailboxes |
| In-Place Hold | In-Place Holds | Whether the mailbox has an in-place hold set |
Work through the list in the order the table gives it. Retention policies and label policies are the ones most firms configure once and then forget, so start there. An eDiscovery case hold usually comes from a legal or compliance request, which means the operations team may not know it exists unless they ask. Confirm whether each affected mailbox has an In-Place Hold set rather than trusting a single firm-wide setting.
Record the answers in the same bulk-change checklist used for the Gmail caps. A hold confirmed before the change saves a stalled run, and a hold discovered afterward may force the team to stop or reverse part of the change.
The 10,000 tenant compliance policy ceiling
Microsoft caps compliance policies at a set maximum for each tenant. The tenant is the Microsoft 365 organization as a whole, so the ceiling covers every team and mailbox in the firm together, not one department. Microsoft's page states that the policies counted toward the maximum include policies for several named controls, among them Microsoft Purview Data Loss Prevention, Microsoft Purview Information Barriers and sensitivity labels.
The table below shows how each named policy family sits relative to the maximum, using the source's own categories.
| Policy family | Position relative to the 10,000 maximum | Basis in the source |
|---|---|---|
| Data Loss Prevention policies | Listed among policies counted toward the maximum | Microsoft Purview Data Loss Prevention |
| Information Barriers | Listed among policies counted toward the maximum | Microsoft Purview Information Barriers |
| Sensitivity labels | Listed among policies counted toward the maximum | Sensitivity labels |
| MRM retention policies | Excluded from the maximum | Exchange retention policies from messaging records management |
The practical effect for a bulk client update is that a firm which adds many data-protection or labeling policies in the same period draws down the same ceiling. A firm that has grown its policy set over several years may find headroom is smaller than it appears, especially when a single bulk project asks for several new policies at once. Count every existing compliance policy that counts toward the maximum before any change that adds to them, and record the total with the date of the count.
The ceiling is a hard total, so plan for it the way you plan for the Gmail daily cap: count first, then act.
Why MRM retention policies sit outside that ceiling
Microsoft's page makes a specific exclusion that affects how you count: "Exchange retention policies from messaging records management (MRM) are excluded from this 10,000 maximum." Those policies are therefore left out of the total that the ceiling measures, and they do not reduce the headroom available for compliance policies. A partner who counts every retention setting in the tenant as if it consumed the same budget will overestimate how close the firm is to the limit.
The distinction requires two separate tallies. Keep one count for the compliance policies that count toward the 10,000 maximum, which is the figure that must stay at or below 10,000. Keep a second count for MRM retention policies, which is useful for understanding the mailbox configuration but is not measured against the maximum. When you present the numbers to a partner, label each tally with its source and its date, so the two totals are never merged by accident.
The exclusion also explains why a firm's count can change quickly after a single configuration project. Adding a batch of compliance policies moves the first tally, while adding MRM retention policies leaves it unchanged. Before planning a bulk client update, read both tallies, and then decide whether the update needs any new compliance policy at all. If it does not, the ceiling is not a constraint on the job, and the update can proceed on the other checks in this post.
Zoho's 25-item bulk action cap, applied by batch
Zoho Books' help page on inventory adjustments sets a firm boundary: "Note: You can perform bulk actions on a maximum of 25 inventory adjustments at a time." The cap applies to a single bulk action, so a larger job has to be split into several runs. Whatever number of records you need to change, the batch size stays at 25.
The page is about inventory adjustments, not client records, so it does not tell you what limit applies to your own software or your client files. Its value for a small firm is the discipline it models. Before a bulk change begins, divide the total number of records by 25, round up, and number each batch. Run one batch at a time, and record which batch finished and what it changed.
Numbered batches matter most when a run stops partway through. If the team knows that batch 3 finished and batch 4 did not, they can resume without re-editing records that already changed, and they can check the finished batch against the source list. Without batch numbers, a stalled job leaves the operations lead guessing which client records were touched.
Set the batch size before the work starts, not while it runs. Write the number of batches on the project plan, assign an owner to each one, and check the count against the original list. A short, fixed batch plan turns a large, risky edit into a series of small steps that can each be verified.
Quantity changes that happen without a transaction
Zoho's page makes a point that applies well beyond inventory: "Sometimes, the quantity or value of your items could change without creating any sales or purchases transactions." In other words, a record can change even though no invoice, bill, or sale appears to explain the change.
For a bulk update, this means a review that only looks at transactions will miss some changes. A team that checks only the documents it created may assume a record is correct when its stored value has drifted. Before a bulk job, compare the current value of each record with the most recent documents that support it, and note any mismatch before you edit anything.
The same logic applies to client files. The same precaution applies to client files: a record can change with no document behind it, so capture a baseline before you edit. A bulk edit that overwrites these fields without a baseline can erase the only record of what was there before.
Capture a snapshot of the affected fields before the change, and keep the snapshot with the batch plan. When a record differs from its last supporting document, write down the reason before you correct it. That note turns an unexplained difference into an auditable entry.
Quantity Adjustment as a correction path
Zoho's help page states how it handles changes that have no matching transaction: "In Zoho Books, these scenarios are accommodated using Quantity Adjustment." The page presents this mechanism as one way Zoho Books deals with those situations, and that is the point to take from it.
The practical advice is consistency. When a quantity or value changes without a transaction, record the correction through the adjustment mechanism the software provides, rather than typing a new figure directly into a record. A direct overwrite leaves no clear trail, and two people correcting the same kind of error in different ways makes the history hard to read.
Standardize the procedure in writing. Name the adjustment route, state who may use it, and require a reason for each entry. The page does not describe every alternative, so the firm's procedure should say what staff should do when a change does not fit the adjustment pattern, and it should ask someone to review those cases before the batch proceeds.
This approach also helps with the batch cap. Adjustments made through one route can be grouped into batches of 25, so the same numbering system used for the rest of the bulk job covers these corrections too.
A worked example: ten units at one rate
Zoho's help page offers a simple scenario to anchor the process: "Let's say you purchase 10 mobile phones at a certain rate." The example is short, but it shows how the batch cap and the adjustment route fit together.
Start with the purchase record. It shows ten units, and the example leaves the rate open as "a certain rate," so the team should copy the rate from the actual purchase document rather than from memory. Next, compare the count in the system with the ten units on the purchase. If they match, nothing needs correcting.
If the count later differs, the example points toward the right fix. The change should go through Quantity Adjustment rather than through an edit to the original purchase. The numbers in this scenario also fit the batch rule. Ten adjustments sit well inside the 25-item run limit, so the whole correction can run as one batch.
| Step | Figure from the example | Check before editing |
|---|---|---|
| Units purchased | 10 phones | Matches the purchase record |
| Batch cap | 25 adjustments in each run | Ten adjustments fit in one run |
| Rate | "A certain rate" (not stated) | Copy the rate from the purchase document |
The example does not give a rate, so the procedure should not invent one. It shows the sequence instead: verify the purchase, compare the count, correct through the adjustment route, and keep the change within the batch size.
Which one should you pick?
Not every bulk job needs all three checks. The right first check depends on what you are changing and which tool you are using. Gmail's page is the place to start for client messages, and it adds an important qualifier: "If you use your Gmail account through your work, school, or other organization, learn about Gmail sending limits through work or school." The sending account type determines which rules you are working under, so confirm it before anything else.
For compliance changes in Microsoft 365, the relevant check is the tenant ceiling and how long the organization has been enrolled. Microsoft notes that "the limits applied to a Microsoft 365 organization may differ depending on how long the organization has been enrolled in the service." Two firms on the same plan may therefore not face identical limits, so look up your own tenant's figures before planning.
For inventory corrections in Zoho Books, the first check is the batch size. Bulk actions run on a maximum of 25 inventory adjustments at a time, so the job plan should be built around that figure.
| If your bulk job is... | Check first | Why |
|---|---|---|
| Sending client messages from Gmail | Account type, then daily and recipient limits | Work and school accounts follow their own rules |
| Adding compliance policies in Microsoft 365 | The 10,000 tenant maximum and enrollment history | Limits may differ by enrollment length |
| Correcting inventory records in Zoho Books | The 25-item batch cap | Bulk actions are capped at 25 at a time |
Pick the row that matches the job, run its check, and only then start the batch.
Related guides: 3 Teams chat limits before sending client files · ACH invoice fees: 4 facts to check before a client pays · Bank reconciliation: 8 checks before client sign-off.
Reader questions
Do Gmail's daily limits apply only to sent mail? No. Google's help page says Gmail "limits the number of emails you can send or get per day," so received mail counts toward the daily total as well. Gmail Help
Does a work or school Gmail account follow the same numbers as a personal one? Not necessarily. Google directs users of organization-provided accounts to learn about "Gmail sending limits through work or school," which means those accounts follow their own rules. Gmail Help
Do MRM retention policies count toward Microsoft's 10,000 maximum? No. Microsoft states that "Exchange retention policies from messaging records management (MRM) are excluded from this 10,000 maximum." Microsoft Learn
Is 25 the limit for every bulk action in Zoho Books? The page specifically limits bulk actions on inventory adjustments to 25 at a time, so the figure should be read as applying to that feature. inventory adjustments help
Can inventory change without any sales or purchase record? Yes. The page says the quantity or value of items "could change without creating any sales or purchases transactions." inventory adjustments help
Are the limits the same for every firm? Not necessarily. Microsoft says the limits "may differ depending on how long the organization has been enrolled in the service," so check your own tenant. Microsoft Learn
Which Zoho feature handles changes with no matching transaction? The help page says these scenarios "are accommodated using Quantity Adjustment." inventory adjustments help
Does an eDiscovery or In-Place Hold appear in the list of holds? Yes. Microsoft's page names "Microsoft Purview eDiscovery case holds, and In-Place Holds" alongside retention and retention label policies. Microsoft Learn
Not legal or tax advice.