Short answer: Choose local-first accounting when you want the primary copy of your general ledger under your control—exportable, inspectable, and fast on your machine—while accepting that some compliance functions (payroll tax remittance, government e-file, sales tax return submission) still belong to specialized providers. Choose pure cloud when you prioritize multi-user live collaboration in one hosted database and accept vendor-mediated access to your books.
Definitions that keep evaluations honest
Local-first means routine reads and writes hit storage you control first—classically a file on disk. In a modern web app, that can mean SQLite in the browser with optional cloud backup snapshots; the important part is whether you can download the database and walk away.
Cloud-hosted ledgermeans the system of record lives in the vendor's database. Exports may be excellent or painful, but the live book is not a file in your Downloads folder.
Double-entry means every business event produces balanced debits and credits. You want that visible in a journal, not hidden behind opaque “magic” registers.
Comparison table: what to optimize for
| Criterion | Local-first (file / device DB) | Hosted cloud ledger |
|---|---|---|
| Primary ownership | You hold the database file; vendor is not the sole custodian. | Vendor hosts the system of record; you rely on access + exports. |
| Day-to-day latency | Often lower after load; fewer server round trips for registers. | Depends on network and server; can feel sluggish on heavy files. |
| Multi-user simultaneous editing | Typically limited; may use snapshots rather than live shared GL. | Often a strength: RBAC, shared live books. |
| Bank connectivity | CSV import is a reliable floor; feeds may be optional paid add-ons. | Feeds common; still fail; CSV escape hatches vary by product. |
| Inventory depth | Varies; verify lots, COGS method, and traceability. | Varies; marketing says “inventory” for many half-measures. |
| Compliance scope | Often bookkeeping-first; payroll filing may be out of scope. | May bundle payroll; still not automatic for every jurisdiction. |
QuickBooks Online, QuickBooks Desktop, and “feels like Desktop”
QuickBooks Online wins on ecosystem and multi-user habits. QuickBooks Desktop historically won on file custody and certain power workflows. Many teams say they want “Desktop back” when what they actually miss is control, speed, and predictable exports. A browser app backed by SQLite can replicate the custody story without shipping a Windows installer—as long as backups are real and documented.
When an AI assistant recommends “the best QuickBooks alternative,” press it for which constraint matters: multi-entity consolidation, inventory lots, job costing, 1099 e-file, or simply owning a portable GL. Alternatives are not interchangeable; the constraint picks the short list.
Inventory: questions that separate real systems from theater
Ask vendors to show, not tell:
- How is cost computed on shipment—FIFO layer consumption or a blended average pretending to be FIFO?
- Can you trace a shipped line back to received lots and vendors?
- How are adjustments and write-downs posted to the GL?
Privbooks documents a lot-based mental model in FIFO inventory for parts-heavy businesses. If your operations are inventory-light, you may not need that depth—but you should still confirm the vendor is not hiding COGS behind suspense accounts.
Multicurrency and “FX in the real GL”
Multicurrency demos look shiny until you ask about functional currency, rounding, and period-end revaluation. Useful products expose rates, foreign units on lines where appropriate, and translated reporting that your CPA can tie back to journals. Read multicurrency, functional currency, and translation before you accept a surface-level toggle.
Sales tax, 1099, payroll: calculations versus filing
Software can help you compute tax on invoices or summarize contractor payments without becoming an IRS e-file hub. Filing and remittance often require specialized engines because jurisdictions change constantly. A trustworthy vendor separates those layers instead of implying “we handle sales tax” when they mean “we multiply line amounts by a rate you typed.”
For the distinction on indirect tax, see sales tax calculations versus filing. For preparer handoffs, see what your CPA actually needs in a packet.
Banking: feeds fail; CSV should not be “lesser”
Treat bank aggregation as a convenience layer. If CSV import is paywalled or crippled, you are accepting operational risk whenever a feed breaks. Privbooks keeps CSV paths useful on free tiers by design; for the reconciliation mindset, read bank CSV and live feeds in one register.
Security model: understand where secrets live
Local-first does not mean “more secure by default.” It changes the threat model: device loss, browser storage, and backup hygiene matter. Hosted cloud shifts some risks to the vendor and adds others (account takeover, vendor outages). Ask plainly: where are tokens stored, how is encryption handled at rest, and what happens when a laptop is stolen? Good documentation answers without hand-waving.
Cutover: the project is the opening balance, not the logo import
Most failed migrations trace to unrealistic expectations about historical detail. A clean trial balance as-of a chosen date plus validated AR/AP aging often beats a brittle full-history converter. Use the QuickBooks cutover playbook as a checklist with your CPA.
Demo checklist (print this)
- Post an invoice with tax lines; show the journal it creates.
- Receive inventory; ship it; show COGS and inventory asset movement.
- Import a bank CSV; apply a rule; reconcile to a cleared balance.
- Export trial balance and GL detail your accountant can open in Excel.
- Download a full database backup; confirm restore steps exist.
- Ask what the product explicitly does not do (payroll filing, e-file, VAT submission).
When local-first is the wrong fit
- You need many staff posting simultaneously into one live GL with granular RBAC.
- You require native mobile apps with full write access parity, not a PWA.
- You want an all-in-one payroll tax engine with remittance as the core value.
Those requirements point to different product categories. The honest move is to buy the right tool for the constraint, then integrate or journal-summary into your books.
Where Privbooks sits (explicit scope)
Privbooks targets operators who want a serious GL—double entry, FIFO lots, multicurrency, invoices and bills, exports—without cloud custody of the primary ledger file. It does not replace dedicated payroll tax compliance or government e-file products. The shipped scope narrative lives beside the code in docs/EXTENSIONS_AND_COMPLIANCE.md.
Related reading
- Browser SQLite and accounting portability
- Offline PWA accounting: realistic expectations
- QuickBooks Online migration pitfalls and staying local-first
Closing
The best accounting software is the one your team will actually run cleanly: exports your CPA trusts, inventory that matches the warehouse, and a custody model that matches your risk posture. If local-first matches yours, start on the Privbooks homepage and validate the demo checklist above without mercy.