It's filing week. A preparer working from home needs the same company file as a colleague sitting at a client's office, but the current copy is on a PC in the back room. Someone has to send a backup, confirm which version is current, and hope nobody posts another adjustment before it arrives.
Moving that file online removes the handoff. Building a dependable cloud based accounting firm takes more: the applications must work together, staff must have appropriate access, and someone must prove the firm can recover when a device disappears or a server fails.
A cloud-based accounting firm runs its accounting applications and client records on hosted infrastructure that authorized staff and clients reach over the internet. The practice may use browser-based software, hosted desktop applications, or a combination of both.
The important change is where the working environment lives. Instead of relying on an office PC to hold the current books, the firm gives people controlled access to centrally maintained records.
In the office-bound model, updates often travel between people as attachments, USB files, or manually created backups. Each handoff creates a question: is this the copy everyone should be using? Hosting changes that arrangement, but it doesn't remove the need for review, version control, or clear ownership.
Think of the hosted environment as a shared workshop with labeled tools. The preparer, reviewer, and administrator can reach the tools their jobs require, rather than keeping separate toolboxes locked in their cars.
That doesn't mean everyone gets unrestricted access to everything. A client might need reports for their business, while a preparer needs transaction entry and a partner needs approval rights. Shared infrastructure and restricted access belong together.
Cloud platforms are already established in accounting: in its 2025 survey of 250 professionals, Xero's State of the Industry report found that 85% of U.S. accounting and bookkeeping firms reported using cloud platforms.
A browser ledger can handle bookkeeping without addressing the rest of the firm's work. Tax preparation, supporting documents, spreadsheets, practice management, and specialist add-ons may still sit elsewhere.
For example, a preparer may open the books online but need an office computer to reach the tax return and supporting schedules. That's a partial cloud arrangement, not necessarily a bad one, but the office computer remains a dependency.
Practical rule: Follow an engagement from client upload to final review. Any step that requires a particular office machine belongs on your migration checklist.
A cloud-based practice can still have an office and meet clients in person. Its defining feature isn't an empty building; it's the ability to complete authorized work without depending on a particular desk.
That distinction matters during deadlines. A slow desktop is inconvenient. Losing access to the working papers, tax application, or current books can prevent the firm from finishing the engagement.
How each piece of a cloud-based accounting firm runs
| Piece | What is hosted | Who uses it | Change versus the office server |
|---|---|---|---|
| Books and payroll | QuickBooks, Sage, or Peachtree on a hosted server | Bookkeepers and clients | One live company file instead of emailed copies |
| Tax preparation | Drake, Lacerte, ProSeries, or CCH | Preparers during season | No USB handoff of the return file |
| Client documents | Document system next to the apps | Reviewers and admins | One repository instead of scattered drives |
| Remote access | Remote desktop from a supported device | Partners and seasonal staff | Work continues if the office is closed |
| Collaboration | Shared sessions and permissions | Accountant and client together | Authorized users see saved changes without exchanging copies |
| Access control | Role permissions and multi-factor sign-in | Firm admin | Joiner and leaver access is deliberate |
| Backups | Copies isolated from the live server | Whoever owns continuity | A tested restore, not only an uptime claim |
Start with books and payroll. The bookkeeper needs the correct company file, the correct application edition, and any payroll components required to finish the job. Hosting the ledger without its integrations can leave the workflow incomplete.
Tax preparation adds a separate dependency. Preparers need the right tax application, return files, prior-period information, and working folders. Confirm licensing and simultaneous-user requirements rather than assuming that installing software on a server grants everyone permission to use it.
Documents belong beside the applications operationally, even if they use a separate storage service. Reviewers need a predictable place for statements, signed forms, and supporting schedules. Administrators need naming conventions and retention rules, not another folder that staff must remember to search.
Remote access is the doorway, not the whole system. A laptop needs a supported connection method, a usable internet connection, and an appropriate device configuration. Closing the office shouldn't close the practice, but a lost connection can still interrupt an individual's session.
Collaboration means people can work against current records within the application's supported multi-user behavior. It doesn't mean they should share a login or edit the same return simultaneously when the software doesn't support it.
Access administration and backup ownership are distinct jobs. The administrator decides who can reach the environment; the continuity owner establishes how the firm will resume work after disruption. Assign names to those responsibilities before migration.
Partial adoption is common. In 2024, 43% of respondents at nearly 500 U.S. accounting firms said less than 75% of their applications and data had migrated to the cloud, according to coverage of Rightworks' Accounting Firm Technology Survey.
A firm can therefore have an online ledger while still emailing tax files or storing engagement documents on local drives. Mark every row in the table that your practice still handles that way.
Use that inventory when planning IT support for accounting firms. A server migration isn't complete merely because staff can sign in; they need to finish real work without an undocumented workaround.
A hosted workday should feel familiar inside the accounting software. The difference is that the application runs remotely while the employee's device provides the screen, keyboard, and connection.
The preparer signs into a remote desktop. They authenticate to the hosted environment rather than opening a company file stored on their laptop. A named account connects the session to a specific person.
The accounting application opens on the server. The preparer launches QuickBooks or Sage and selects the authorized company file. In a properly restricted setup, the working file remains on the host rather than downloading to the kitchen-table laptop.
The reviewer opens the engagement with appropriate permissions. They see posted entries without waiting for a backup attachment. Their account should allow the review actions they need without automatically granting administrator rights.
Supporting documents stay in the designated repository. The preparer saves statements and working papers where the reviewer expects them. A client portal for accountants can provide the intake route, while the firm defines how accepted documents enter the engagement folder.
The preparer saves work and signs out. The records remain in the hosted environment. Preventing local copies also requires deliberate controls over downloads, redirected drives, clipboard use, and printing; ending a session alone doesn't erase files someone exported.
The workflow below shows the central idea: the employee changes location, but the working environment remains hosted.
A browser-based ledger is an application delivered through a web browser. A remote desktop gives the employee access to a hosted desktop environment where compatible desktop applications can run.
That distinction matters when the practice relies on Windows tax software, specialist utilities, or established desktop accounting products. Moving those applications to hosted infrastructure isn't the same decision as replacing them with browser-native software.
Say a small practice brings in a seasonal preparer working from another state. The preparer can use the hosted accounting and tax environment, subject to licensing and permissions, without the firm setting up another office server.
The arrangement still needs a realistic test. Opening an application proves less than preparing a return, importing a spreadsheet, attaching supporting documents, and producing the final output.
Test the awkward parts of the workday, not just the login screen.
Checks, scanners, local printers, PDF tools, and add-ons deserve attention before the deadline rush. A printer may need redirection into the remote session; a scanner may need a supported capture workflow; an integration may require a particular installation location.
The useful end state is practical: current records are available, reviewers don't request evening backup emails, and a new employee can begin after their account and workspace are approved rather than after someone rebuilds an office PC.
A padlock icon indicates something about a connection. It doesn't tell a partner whether a former employee can still open payroll records or whether an administrator's changes are reviewed.
SOC 2's control framework addresses security, availability, processing integrity, confidentiality, and privacy through an independent CPA examination of a service organization's controls. It isn't a generic security badge: the examined services, testing period, and reported exceptions matter.
Use concrete questions when reviewing cybersecurity for accountants.
For partners learning the terminology, Matil's guide to SOC 2 compliance offers additional context for that conversation. Processing integrity deserves particular attention because payroll, bookkeeping, and tax workflows must finish accurately and without unauthorized alteration.
Central hosting doesn't prevent employees from pasting client information into an outside AI tool. Maintain an approved-tool list and written rules covering permitted data, prompt retention, model training, administrator controls, and human review of outputs.
A secure environment still needs a recovery plan. Preventing unauthorized activity and resuming work after failure are different responsibilities.
Hosting applications isn't the same as being able to recover them. Rightworks found that 49% of accounting firms hosted at least three-quarters of their data and applications in the cloud, while only 44% could remotely wipe a lost or stolen device, according to its accounting-firm cybersecurity findings.
Define recovery targets before comparing availability promises. Recovery point objective, or RPO, is the maximum amount of recent work the firm can tolerate losing; recovery time objective, or RTO, is the maximum acceptable interruption.
NIST's cloud-computing guidance recommends evaluating availability, backup, recovery, and disaster-recovery provisions against continuity needs. Write your targets in hours where useful, then make the contract and restoration procedure support them.
Failures a cloud-based accounting firm should plan to survive
| Event | Why uptime is not enough | Recovery check |
|---|---|---|
| Ransomware on the host | Applications may be encrypted along with live data | Backups isolated from production logins and restored in a test |
| Lost or stolen laptop | Closing a session doesn't remove cached or exported files | Remote wipe plus multi-factor sign-in on the next login |
| Accidental delete before a deadline | The file share can remain online despite missing records | A recoverable copy recent enough to meet the firm's RPO |
| Regional outage | An uptime percentage doesn't relocate the workload | Documented failover and an achievable RTO |
| Employee leaves mid-engagement | An active login can still reach client files | Same-day removal and review of what they opened |
A meaningful backup and recovery plan restores the application, data, permissions, and dependencies needed to complete an engagement. Restore into a non-production environment and have a preparer open the file and perform a representative task.
Recovery test: Record when restoration starts, when staff can resume useful work, and which entries aren't present.
Match backup frequency and retention to the RPO. Match restoration capability, support response hours, and escalation procedures to the RTO, including when deadlines fall outside normal office hours.
The same hosted model can support very different working arrangements. These scenarios illustrate how the pieces fit; they aren't customer case studies or promises of results.
Consider a small tax practice that uses Drake or Lacerte alongside QuickBooks. A seasonal preparer in another city needs the tax application, company records, and supporting schedules, but doesn't need access to every client engagement.
The partners place the required working materials in the hosted environment and assign the preparer an appropriate role. The reviewer can inspect the return and supporting entries without coordinating a file transfer.
The useful change isn't remote employment. The practice has made the preparation and review process independent of a particular office workstation.
A bookkeeping shop serving several small businesses needs convenient navigation without mixing client access. The bookkeeper moves between authorized company files within the remote environment, while each client receives access only to their own permitted information.
Instead of sending a backup at the end of the week, the bookkeeper publishes approved reports through the agreed delivery process. The client knows where to retrieve them, and the bookkeeper doesn't have to determine which attachment the client opened.
Separation still matters. A shared server isn't permission to use a shared client folder or let one business browse another business's records.
A nonprofit treasurer and outside accountant may both need the books during month-end, while board members need approved financial reports. Hosted access can remove reliance on the treasurer's PC without giving the board transaction-editing rights.
The accountant posts adjustments, the treasurer completes the review, and board members receive the approved reporting package. Responsibility for approval remains with the people doing the work, not with the hosting service.
In a 2025 survey of 100 UK accountants, accessibility was the most frequently cited cloud benefit at 48%, followed by productivity and time savings at 44%, according to Wolters Kluwer's UK cloud-accounting report.
Those are UK survey findings, not a guarantee for another practice. They support evaluating cloud arrangements around practical access and working efficiency rather than treating migration as an achievement by itself.
In each scenario, the useful improvement depends on bringing the necessary working materials into a coherent process. An online ledger won't resolve a review bottleneck if the supporting documents remain on an unavailable office computer.
Choose a host by testing the work your practice must finish. A polished demonstration doesn't establish that your tax application, company file, scanner, and review process will function together.
Use a short acceptance checklist when choosing a cloud provider.
Cloudvara is one candidate to evaluate. We offer remote desktop hosting for QuickBooks, Sage, and tax applications, with QuickBooks hosting on a fully managed, dedicated server.
We've been an Intuit QuickBooks Hosting Partner since 2012, and our servers are located in SSAE16 compliant facilities. Facility attestations and hosting-partner credentials don't replace reviewing the controls and commitments relevant to your deployment.
Use a vendor trial, where available, to test an active company file and a representative tax workflow before moving the remaining office workload. Include a restore exercise, peripheral testing, and removal of a test user's access.
Keep the acceptance record in writing, including confirmed trial terms and unresolved limitations. Judge the pilot against the firm's recovery objectives and ability to finish engagements, not a generic uptime claim.
Cloudvara offers hosted access to accounting, tax, and document applications so your team can work in a centralized environment without depending on the office server. Visit Cloudvara to discuss your application inventory and plan a trial that tests real work, access removal, and recovery before a full migration.