Accounting first
Charts, journal entries, registers, bank activity, reconciliation, and reports stay connected.
About LedgerHQ
Built around the books accounting firms actually manage.
LedgerHQ is a hosted bookkeeping service from Tax Planner Pro, LLC, based in Bonita Springs, Florida. The product stays focused on the accounting records, bank activity, review, reconciliation, reporting, and supervised AI work firms need to keep company books current.
Firm managed
The operating model starts with a firm supervising separate company books.
Narrow by design
LedgerHQ avoids claiming unsupported broad-suite modules simply to make the feature list longer.
01
Why LedgerHQ exists
Accounting firms often perform the same bookkeeping loop across many companies: bring in activity, classify it, resolve exceptions, post to the ledger, reconcile to statements, answer questions, and deliver financial reports.
LedgerHQ is built to make that loop inspectable and increasingly agent-ready without severing the daily workflow from the accounting records that make it trustworthy.
- Company-by-company accounting scope
- Bank activity connected to the ledger
- Reconciliation tied to statement evidence
- Reports tied back to posted records
02
A focused product boundary
The visible product direction is intentionally narrower than an all-in-one business suite. LedgerHQ concentrates on firm and company workspaces, charts, journal entries, registers, Plaid-connected activity, bank reconciliation, reports, minimal company-owner interactions, and supported API and agent access.
That focus helps the product say no clearly. A feature should deepen the bookkeeping workflow, not revive old promises around payroll, inventory, CRM, projects, generic provider imports, or broad self-hosting.
- Firm and company workspaces
- Core accounting and banking
- Requests and supporting evidence
- REST, OpenAPI, MCP, and Tally
03
AI belongs inside the controls
Tally is designed as the AI bookkeeper inside LedgerHQ, not as a separate chatbot that can bypass the books. It can inspect and act on supported context only through the firm's allowed scope and LedgerHQ's guarded workflows.
That means an AI answer is not treated as proof. Actions, approvals, records, and activity provide the evidence that a task actually moved.
- Scope before context
- Tools before book changes
- Confirmation for sensitive work
- Records and activity as proof
How the workflow moves
A visible sequence, not a black box.
The exact action depends on permissions, company context, and the evidence available. The workflow stays inspectable from intake through review.
- 1Start with a focused accounting problem a firm repeatedly handles.
- 2Build it on the same ledger and organization boundaries as the rest of the product.
- 3Expose the supported workflow to people, API users, and approved agents where appropriate.
- 4Document the real boundary and keep the resulting work reviewable.
Human control
LedgerHQ's product direction favors explicit company scope, role-based access, guarded mutations, and reviewable accounting outcomes.
Product boundary
This page intentionally does not publish unapproved founder biographies, customer metrics, funding claims, or third-party certifications.
Questions
What firms usually ask.
Who operates LedgerHQ?
LedgerHQ is a subsidiary service of Tax Planner Pro, LLC, based in Bonita Springs, Florida.
Is LedgerHQ open-source or self-hosted?
LedgerHQ is presented as a hosted bookkeeping service at ledgerhq.pro. The marketing site does not promise a public self-hosting or open-source product.
Why does LedgerHQ focus on accounting firms?
The firm-managed model creates a clear need for multi-company scope, repeat workflows, staff permissions, exception review, and supervised agent work.