QuickBooks Enterprise limits, fees, and cloud terms users learn late
The October 2025 Enterprise guide's fine print carries list caps, permission limits, a 12-month commitment, and backup duties that catch users off guard.
Pages nine through eleven of the October 2025 in-depth guide for QuickBooks Desktop Enterprise hold the disclosures most buyers never reach. Intuit puts the list ceilings, the permission boundaries, the seat increments, the subscription terms, and one easily missed backup duty in plain sight there, pages deep in the back matter. We went through them, and the details change how you should plan a purchase.
A million names is a ceiling, not a target
Enterprise accepts up to one million names across customers, vendors, and employees. It accepts another million items spanning inventory, non-inventory, and service types. The concession sits in the same paragraph: performance is likely to degrade as either list approaches those thresholds.
The number is a licensed maximum, not a comfort zone. Firms that merge files, import years of history, or run high-volume distribution can drift toward the cap without anyone watching. Nothing in the guide promises a warning before the slowdown arrives, so growth monitoring is a maintenance task, not an optional one.
Record-level permissions cover three centers only
The software does offer record-level permissions, which is a finer control than a plain user role. The scope is narrow, and the guide is blunt about it. The feature covers the Customer, Employee, and Vendor Centers, and no other areas are named. A firm hoping to restrict a single bank account, a class, or a specific item by the same mechanism will not find it there.
Seats scale one user at a time
Licenses are sold in single-user increments, from one user up to ten, or up to forty, with fees at each step. That granularity matters when headcount sits between the usual tiers.
Cloud access is monthly billing on an annual promise
The cloud access service is a monthly subscription, charged automatically each month until you cancel. The desktop software inside the bundle is an annual subscription, and the twelve-month clock starts at enrollment, not at first use. Choosing the monthly payment plan spreads the annual cost across twelve installments. It does not convert the arrangement into a month-to-month service.
Cancel inside the first sixty days and the money-back guarantee applies. Cancel after that window and before month twelve, and a termination fee takes its place. The fee equals the monthly payments still remaining on the term. The guide’s own arithmetic: a firm six months into its subscription owes six months of the then-current monthly fee.
Cancellation is handled by phone ahead of the monthly renewal date, with refunds running through the end of the current billing period. The guide also reminds cloud customers that access depends on a reliable internet connection, subject to maintenance windows and events outside the vendor’s control.
Backups run nightly, and the verification duty is yours
Hosting and support for the cloud bundle run through Rightworks, and a valid license code is required to open a support case. Backups are taken nightly using snapshot technology and replicated to a protected offsite facility. Retention runs on a rolling ninety-day cycle, and there is no size cap on a customer’s backup.
The line that surprises people sits one sentence later. Customers are responsible for verifying the integrity of their hosted data at least every ninety days. A nightly backup protects against server failure. It does not prove the latest copy opens, reconciles, and holds everything you expect. That check belongs to you, on a schedule you set and keep.
The practical takeaway
Read the subscription terms before enrolling, not after the sixty-day window closes. Track list growth as routine file maintenance, because slowdown near the ceiling is documented behavior rather than a defect. Put the ninety-day data verification on the calendar as a recurring task, because the obligation is written into the service terms.
If you need restrictions on records outside the three covered centers, plan for workflow controls rather than the permission feature itself. None of these limits appear in the sales pitch. All of them appear in the guide, pages from the front, where the binding terms live.