Integrations
Reads your books. Writes back carefully.
Bookkite connects to the ledger you already use — QuickBooks Online, Xero, or a bank feed — and watches overnight. No migration, no second source of truth, no credentials stored in Bookkite.
- Read-only by default
- All writes require your approval ceiling
- Every write logged
- Immutable, exportable audit trail
- No credentials stored
- OAuth tokens scoped to read + tagged write
Supported sources
Three connections. One overnight watch.
Reads
Transactions, chart of accounts labels, vendor list
Writes
Reconciliation journal entries, categorisation tags — all reversible, all logged
Never
Creates payees, modifies chart of accounts, initiates payments without your approval ceiling
Reads
Bank transactions, contacts, invoices
Writes
Reconciliation matches, categorisation tags
Never
Deletes records, modifies the chart of accounts, initiates transfers
Reads
Transaction stream only (via Plaid, Mercury, Wise)
Writes
Nothing back to the bank — feed data drives the nightly reconciliation in QBO/Xero
Never
Initiates outbound transactions
What Bookkite reads vs. writes
Propose first. Log always. Never act alone.
Every write is a reconciliation match or category tag that is reversible, written to the immutable log, and visible in the morning brief.
| Source | Reads | Writes | Never |
|---|---|---|---|
| QuickBooks Online | Transactions, chart of accounts labels, vendor list | Reconciliation journal entries, categorisation tags — all reversible, all logged | Creates payees, modifies chart of accounts, initiates payments without your approval ceiling |
| Xero | Bank transactions, contacts, invoices | Reconciliation matches, categorisation tags | Deletes records, modifies the chart of accounts, initiates transfers |
| US/CA bank feeds | Transaction stream only (via Plaid, Mercury, Wise) | Nothing back to the bank — feed data drives the nightly reconciliation in QBO/Xero | Initiates outbound transactions |
Read-only by default
Your accountant’s window is always read-only.
The /share/:token link your accountant uses gives a filtered, time-scoped view of the action log — no write surface, no login required on their side, no permission sprawl. Bookkite proposes; you approve; the log records both.
Every reconciliation write lands in the immutable log before it touches your ledger.
Token-gated share links expose the log read-only — no edit surface, no login, no client state.
You set the dollar ceiling. Above it, Bookkite queues and waits. Nothing auto-pays.
For the owner
Your ledger stays where it is; Bookkite layers on top and hands you three paragraphs by morning.
See how the morning brief worksFor their accountant or CPA
CPAs and fractional CFOs get the same audit trail the owner sees — no second login, no admin rights, no permission sprawl.
Read how we work with accountants →Request an integration