It's 8 p.m. two days before a filing deadline and a preparer can't reach the office server. The return is on a desktop at work, the workpapers are in someone else's email, and nobody's sure which version is final. That breakdown is why firms look at cloud computing for accountants, not for novelty. I would treat the move as a control and continuity decision first, and a convenience decision second.
A desktop install is like keeping client files in a cabinet in your own office. Cloud computing is like renting space in a secured records facility that staff can reach from any desk, with rules about who holds keys, who logs entry, and who fixes the building. You gain reach, but you don't stop owning the contents or the responsibility for them.
The shared definition comes from the U.S. National Institute of Standards and Technology. The NIST final definition published on September 28, 2011 describes cloud computing as on-demand network access to a shared pool of configurable resources, including networks, servers, storage, applications, and services. That wording matters because it separates hosting from storing a file online.
NIST named on-demand self-service, broad network access, resource pooling, rapid elasticity, and measured service. For a firm, that means staff sign in over a network, capacity can grow for busy season without a hardware purchase, several customers share underlying infrastructure, and use can be metered. If a vendor can't explain which of those apply to your setup, you're buying a label, not a defined service.
The three service models translate cleanly to accounting work:
For most small and mid-sized firms, the practical case is the third one with management on top. A managed hosted server runs QuickBooks or tax software centrally, so remote staff open the same company file instead of passing copies around. That model preserves familiar desktop workflows while shifting patching, hardware care, and backup routines to the host under contract.
| Criterion | On-premises | Cloud-hosted |
|---|---|---|
| Where data lives | Office server or each PC | Provider data center, reached over the internet |
| Who maintains hardware | Your IT person or vendor | Provider, under a managed service agreement |
| Remote access | VPN or remote desktop, patched by your team | Browser or remote desktop from any device |
| Software updates | Installed manually by staff | Applied by the vendor or managed host |
| Backups | Whatever your team schedules and tests | Usually automated; confirm restore testing |
| Capacity in tax season | Buy hardware for the peak | Add resources without new hardware |
| Cost pattern | Large upfront purchase, then upkeep | Recurring subscription or hosting fee |
| Main single point of failure | Office power and internet | Internet link and provider uptime |
Practical rule: count how many applications staff need outside the office during the year, because that count decides how much cloud makes sense.
If the answer is one ledger used by two people in one room, a local setup may still be defensible. If it's tax, documents, payroll, and email across homes and client sites, you're already operating distributed work on infrastructure built for a single office. The mismatch, not fashion, is the case for change.
Say a senior accountant is reviewing a client's return from a hotel two days before filing, while a junior preparer edits the same workpapers from home. Both need the current file, not yesterday's attachment. That single evening shows the first benefits in the order staff feel them.
Remote review works when everyone opens the same hosted file from any device.
Accessibility comes first. Reviews don't wait for someone to drive to the office, copy a file, or describe a screen by phone. Partners can clear a return, a preparer can fix it, and an admin can check status without three separate copies forming.
Collaboration is next. Several preparers work in one client file with a visible audit trail, which replaces emailed spreadsheets named final, final2, and final revised. You still need discipline about who locks, edits, and signs off, but you stop spending deadline hours reconciling versions.
Backups stop depending on memory. Hosted environments usually run automated, off-site backups, so a failed laptop doesn't mean lost workpapers. That isn't the same as a tested restore, and I'd verify restoration separately, but it removes the weakest step, which is hoping someone rotated a drive.
Security maintenance gets lighter, not automatic. Vendor-managed patching and encryption reduce the work your team carries, because the host updates servers you no longer touch. Your firm still configures who can sign in, which clients they see, and how they share files. A patched server with loose permissions is still exposed.
Firms pairing hosted access with newer review tools can also look at resources such as AI2Fin for accounting professionals to understand where automation fits after the underlying files are centralized. Don't automate on top of scattered storage. Centralize first, then improve the workflow.
A short walkthrough helps staff picture the hosted desktop before a pilot.
Run a one-week pilot before you commit:
If those three numbers don't improve, the platform isn't solving your actual problem.
Treat the table below as a map from each daily workflow to the tool that usually hosts it. Read it in the order a month-end or filing cycle runs, because sequencing matters more than moving everything at once. Each row has one concrete check, and skipping that check is where migrations fail.
| Workflow | Typical hosted tool | What changes | Check before go-live |
|---|---|---|---|
| Bookkeeping and general ledger | Hosted QuickBooks company file or online ledger | Several staff post from any location | File size and user licence count |
| Tax preparation | Drake, Lacerte, ProSeries or CCH ProSystem fx on a hosted desktop | Preparers work from a hosted desktop | Licence allows hosted use; printing and e-file work |
| Client document exchange | Document management system or secure client portal | Clients upload to one folder | Retention rules and access logs |
| Payroll | Payroll platform or hosted payroll module | Approvals move online | Who can change bank details |
| E-signature and engagement letters | E-signature tool | Signed copies stored with the client file | Audit trail retained with each signature |
| Email and collaboration | Hosted Microsoft 365 or similar | Shared calendars and co-authoring | Archiving and legal-hold settings |
Bookkeeping anchors the move. A hosted QuickBooks company file or an online ledger lets several staff post entries from different locations without a single office PC acting as gatekeeper. Before go-live, check company file size and licence count together, because a large file with too few seats creates queues on day one. Test opening, posting, and reporting at the busiest hour you'll face.
Tax preparation needs licence proof, not assumptions. Desktop suites such as Drake, Lacerte, ProSeries, and CCH ProSystem fx often run well on a hosted desktop, but you must confirm the licence allows hosted use. Then test the unglamorous steps staff rely on, printing to local printers, scanning source documents, and e-filing from the host. A return that calculates correctly but won't print or transmit isn't migrated.
Client document exchange should replace email attachments with a secure portal or document management system where clients upload to one folder. If you're evaluating that piece, compare your requirements against client portal software built for accountants and confirm retention rules and access logs before clients receive invitations. Logs matter when a client says a document was sent and your team needs to prove when it arrived and who opened it.
Payroll approvals move online easily, which is exactly why bank detail changes need a hard control. Name who can change bank details, require a second approval, and log every change. For e-signature and engagement letters, store the audit trail with the signed copy in the client file, not in a separate inbox. Email and collaboration tools such as hosted Microsoft 365 need archiving and legal-hold settings checked before mailboxes move, not after a dispute starts.
Connections between these tools decide whether staff re-key data or review it. The CloudOrbis guide to accounting integration is useful context when you're mapping how ledger, payroll, and document systems should exchange data instead of creating separate islands.
Move client document exchange and read-only archives first, then the ledger, and leave the tax suite to a planned cutover outside the filing peak.
That order gives staff an early win with low risk. It also keeps your highest deadline system stable until printing, e-file, and restore tests pass.
Cloud savings depend on which costs you avoid, so compare line items rather than headline prices. A hosting quote looks expensive next to a server you already own, until you add replacement, labour, backup storage, and downtime. Build the comparison with your invoices on the table.
| Cost line | On-premises | Cloud-hosted | What to confirm |
|---|---|---|---|
| Hardware purchase and replacement | Every 3-5 years | Included in hosting fee | Provider's hardware refresh cycle |
| Power, cooling and server space | Ongoing in the office | Mostly included in hosting fee | Whether the hosting fee covers power, cooling and rack space |
| IT labour for patching and backups | Internal hours or contractor | Mostly provider-managed | Hours your staff still own |
| Software licences | Per seat or per install | Per seat or per hosted server | Whether desktop licences may be used on hosting |
| Backup storage | Local drives plus an off-site copy | Usually bundled | Retention period and restore-test support |
| Migration (one-time) | Not applicable | Data conversion, setup and training | Fixed quote in writing |
| Exit or data export | Not applicable | Possible fees | Export format and fee schedule |
On-premises hardware often needs replacing every three to five years, and firms tend to remember the purchase price while forgetting setup weekends. IT labour is the quieter line. Patching, backup checks, user setup, and printer fixes consume internal hours or contractor invoices whether anyone labels them as server costs or not.
Use this only as an illustrative calculation, then replace every figure with quotes from your own providers. Say on-premises running costs total 18,000 per year once you include hardware reserves, power, licences, backup storage, and support labour. Say cloud hosting costs 12,000 per year, and one-time migration costs 6,000.
The arithmetic is plain:
That result doesn't prove cloud is cheaper for your firm. It proves whether a quote pays back before the contract becomes hard to exit. If payback stretches beyond the term you're willing to sign, renegotiate scope or stay put.
Downtime during a deadline is a real cost even though it rarely appears on an invoice. Staff idle time, expedited support, and client explanations all carry value, so estimate one lost filing day and include it as a separate sensitivity line. Don't bury it in the base case to make the answer look better.
For a structured comparison of your own numbers, work through cloud versus on-premise costs line by line with both vendors present. Ask each provider for a fixed migration quote and the export terms in writing. If export format, timing, or fees are vague, treat that as a cost you haven't been shown yet.
Moving to the cloud doesn't make a firm secure automatically. Controls have to be designed, assigned, and documented, because the host can't decide which preparer should see which client. I would work through this checklist in order and keep evidence for each item.
The infographic below summarizes the control set staff should recognize on sight.
The IRS Security Summit guidance recommends multifactor authentication for systems containing taxpayer information, including tax software, cloud storage, and email, and it also recommends encryption and regular backups. Passwords alone fail against phishing and reuse, while a second factor means a stolen password by itself is less likely to open the door.
Two measures turn backup talk into a standard. Recovery point objective means how many hours of entries you could lose and need to re-key. Recovery time objective means how long the firm can work without the system before deadlines slip. Set both per application, because payroll and archived returns don't need the same answer.
Document all of this in your written information-security program, and use cloud security best practices as a cross-check when you review settings. A policy nobody tests is only a description of intent.
List the client data you hold, including taxpayer identifiers, bank details, payroll records, and personal contact data. Then confirm the provider's processing terms, breach-notification timing, data-location commitments, and deletion at contract end. Firms with EU or UK clients should check GDPR processor terms and data-transfer safeguards, and tax preparers should map their written program to the FTC Safeguards Rule.
A clean SOC 2 report is evidence, not proof that your firm is secure. SOC 2 is an independent examination of a provider's controls against the AICPA Trust Services Criteria of security, availability, processing integrity, confidentiality, and privacy, as described in Microsoft's SOC 2 offering documentation. It tells you about the provider's environment. It says nothing about whether you configured users correctly.
Know which type you're holding. Type 1 checks whether controls were designed suitably at one point in time. Type 2 checks whether controls were designed and operated effectively over a specified period. For a host holding live tax and payroll data, Type 2 is the report that matters.
Start with the system description to see what environment the report describes. Check the audit period next, because stale evidence doesn't cover recent changes. Then read the scope list carefully and ask whether it includes the backup system, the identity platform, support processes, and the application you'll use. If a component is excluded, the report provides no evidence for that component.
Continue to the complementary user-entity controls. Those are your jobs, typically user provisioning, permission reviews, endpoint protection, and retention settings. Read exceptions and management responses together, since an exception with a credible fix differs from one nobody addressed. Finish with subservice organizations, such as a data-center operator, and confirm how their controls are monitored.
Watch for three red flags:
A provider can pass its examination while your firm still fails its own obligations. Both sides of the control list have to work.
Turn reading into action. Map general ledger, tax preparation, document exchange, and payroll to the provider's stated controls, compare availability commitments with your recovery objectives, and confirm encryption and logging practices. File the report, your mapping, and the management responses in the vendor-risk file. If you need the underlying terminology first, review what SOC compliance means before the meeting, then bring specific scope questions, not a request for a logo.
A daily backup does not equal recoverability. Backup preserves data. Disaster recovery restores the working environment, including users, permissions, licences, bank feeds, printers, and integrations. A firm can recover every file and still lose half a filing day rebuilding access around them.
Plan for the failures that happen most often first. Rightworks reporting on accounting firm cybersecurity notes that only 44% of firms can remotely wipe a lost or stolen device, and just 43% have endpoint detection and response on every device. A separate 2026 professional survey described there found internet outages were the leading cause of significant downtime, followed by cloud-hosting outages. Your likeliest deadline problem is connectivity or a device, not a dramatic data center fire.
| Failure type | First action | Within the hour |
|---|---|---|
| Internet outage | Switch to a mobile hotspot | Open the offline copy of critical records and pause uploads |
| Host or cloud outage | Check the provider status channel | Escalate to the named contact and pause new entries until service returns |
| Lost or stolen device | Remotely wipe the device | Revoke its sessions and issue a replacement |
| Locked identity | Use stored recovery codes | Bring in a second administrator to restore access |
| Ransomware or data corruption | Isolate the affected machines | Restore from the separated backup and log the recovery time |
Assign a named owner to each action before tax season. During an incident, staff shouldn't debate who has hotspot credentials, who can wipe a laptop, or who calls the host. Print the table, store recovery codes offline under control, and keep one spare configured laptop ready for a preparer whose device fails.
A complete continuity model covers identity recovery, device replacement, offline access to critical records, tested restoration, backup retention, vendor escalation, and contingency internet access. For the broader planning structure behind those steps, Computer Daddy's business continuity guide offers useful context on assigning responsibilities before an incident forces improvisation. Adapt it to filing deadlines, because your tolerance for downtime changes by date.
Choose backup arrangements that support restoration of applications and permissions, not just file copies, and compare options through cloud backup solutions for business against your recovery targets. Set a recovery time and recovery point for each application, then test them once a quarter by restoring into a clean environment. Log the actual time. If the test misses the target, change the plan or change the target in writing, but don't leave both standing.
Start with the question: which applications move, connect, replace, or stay put, and how few hosting environments you can run without creating a fragmented stack. Vendor-native cloud products can be the wrong answer when legacy desktop tax software still carries your filing season.
The mixed pattern is normal. In a 2026 CPAFMA Digitally Driven Firm Survey, 23% of firms still maintained networks in-house and 60% used a managed service provider. A deliberate mix beats a rushed conversion. Keep the number of environments small, and treat integration as a selection criterion rather than a later wish.
The diagram below shows the sorting logic before the detailed scoring begins.
Legacy desktop tax software, document systems, CRM, and Microsoft applications may need a controlled hosted environment while workflows modernize around them. In our model, we create a workgroup server and install the applications a customer requires, so data can be accessed remotely by any number of users from any computer with internet access, and customers keep using the desktop versions of software they already own. We have been an Intuit QuickBooks Hosting Partner since 2012, which matters if QuickBooks sits at the center of your stack.
Do one thing this week. Complete the inventory and the scoring. Until that sheet exists, every vendor conversation is opinion and every quote covers a different scope.
If your scoring points to hosting QuickBooks, tax software, or document applications you already own, Cloudvara can build a managed workgroup server around those tools so staff work remotely without you maintaining office hardware. Review the hosting options, confirm application compatibility, and plan a pilot that includes a timed restore before your next filing peak.
