> For the complete documentation index, see [llms.txt](https://docs.kula.digital/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kula.digital/your-data-sources/quickbooks.md).

# QuickBooks

QuickBooks Online brings your **accounting** into Kula Intelligence — the general ledger, invoices, bills, expenses, suppliers and your chart of accounts — so money answers reconcile against your actual books.

## What we read — and what we don't

* **We read:** your chart of accounts, invoices, sales receipts, bills, expenses, payments, customers and suppliers — read-only.
* **We don't:** post entries, change your books, or move money. Ever.

## What you'll need

* An **admin login to QuickBooks Online** — someone who can authorise connected apps for the company file.
* About two minutes. There are no keys to create or paste — the connection is a standard **Connect with Intuit** authorisation.

## How to connect

1. In Kula, open **Connectors → QuickBooks** and click **Connect with Intuit**.
2. Sign in to Intuit and, if you have several, pick the **company file** to share.
3. Review the access summary and **authorise** — Intuit sends you straight back to Kula.
4. Kula confirms the company it reached (name, country, currency) and queues the first import.

## What to expect after connecting

* **The first import starts on the next overnight sweep**, not the moment you connect. Kula runs the sweep in your studio's own early hours, so connecting during the day can mean waiting up to about 24 hours. If you don't want to wait, open the connector's monitor page and click **Update to now** — that kicks the first import off immediately.
* The first import pulls about **24 months** of books by default; older history back to the company's start can be loaded on request.
* After that, Kula refreshes your books **nightly**, picking up everything that changed that day — new transactions, edits, voids and deletions.
* The books are only as current as your bookkeeping: Kula sees transactions once they're **posted** in QuickBooks, not while they sit in the bank feed waiting for review.

## Reconnecting

Kula renews the connection's tokens automatically while it's active. If the connection is severed — you revoke Kula's access in Intuit, or the connection sits broken for more than **100 days** — Intuit requires a fresh authorisation. Reconnecting is just the button again: **Connectors → QuickBooks → Reconnect**, sign in, authorise. The import picks up where it left off.

One thing worth knowing if a connection stays broken for a long time: Intuit only tells us about **deletions for 30 days**. Transactions you delete in QuickBooks while Kula is disconnected for longer than that stay in Kula's copy of the books. Reconnect promptly — or tell us, and we'll reload the affected period.

## FAQ

**I run more than one company file.** One Kula org holds **one** QuickBooks connection, so each company file needs its own Kula org. Ask us to set the second one up — reconnecting the same org to a different company file doesn't move the books across, it just leaves the first file's history sitting there un-refreshed.

**QuickBooks Desktop?** Not supported — Desktop has no cloud API to read from, so only QuickBooks **Online** can connect.

**Does Kula see my bank feed or payroll?** No. Bank-feed "For Review" items aren't exposed by Intuit until they're posted to the ledger, and Intuit has no public payroll API — wages appear only as the posted totals in your books.

## If it stops working

A QuickBooks error usually means the authorisation lapsed or was revoked on the Intuit side. Click **Reconnect** and re-authorise. See [Keeping your connectors healthy](/your-data-sources/operating.md).