> ## Documentation Index
> Fetch the complete documentation index at: https://zenofirm.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Ledger connections and runtime

> How the same Zenofirm workflow reaches QuickBooks Online and QuickBooks Desktop.

Connections translate Zenofirm's provider-neutral plans into the native
operations of each accounting system.

| Ledger                 | Connection runs                                            | Status                                                    |
| ---------------------- | ---------------------------------------------------------- | --------------------------------------------------------- |
| **QuickBooks Online**  | In the hosted firm workspace through Intuit OAuth          | First hosted connection, in development                   |
| **QuickBooks Desktop** | Locally on the Windows workstation beside the company file | Available today; connection to the firm workspace follows |

## One capability, different runtime

Hosted connections can reach internet-facing ledger APIs from the firm
workspace. QuickBooks Desktop exposes only a local Windows interface, so its
connection runs on the workstation. In both cases, Zenofirm prepares a plan,
puts the proposed work through review, applies approved changes through the
ledger's native interface, and records what happened.

## The ledger stays authoritative

Zenofirm reads, resolves, validates, and writes through the connection. It does
not import the client's books into a second general ledger. Any cached read
model names its source and when it was last synchronized.

## Provider differences stay visible

Transaction kinds, taxes, tracking dimensions, voiding, and deletion do not
mean exactly the same thing across providers. The shared plan contract carries
the governed workflow; each connection owns its provider-specific mapping and
reversal rules.