> For the complete documentation index, see [llms.txt](https://docs.mosofin.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mosofin.com/start-here/quickstart.md).

# Quickstart

Connect a QuickBooks entity to MosoFin, ask a financial question in Claude, and verify the read in Activity.

MosoFin keeps the company in its own workspace, applies read-only tool policies, and returns the permitted result inside Claude.

## Before you start

You need:

* A MosoFin account.
* A QuickBooks user who can authorize the intended company.
* A Claude account with access to connectors.
* A QuickBooks company based in the United States, Australia, Canada, or the United Kingdom.

> **Country availability:** MosoFin currently supports QuickBooks companies in the United States, Australia, Canada, and the United Kingdom. If your company is based elsewhere, contact MosoFin support before starting setup.

## 1. Create the workspace

1. Sign in to MosoFin.
2. Open the workspace switcher.
3. Select **New workspace**.
4. Name the workspace for one client or company.
5. Open it and confirm the workspace name.

Each workspace can authorize up to five QuickBooks entities. Every new workspace has its own separate five-entity allowance.

## 2. Connect QuickBooks

1. Select **Data sources**.
2. Open the QuickBooks card and select **Connect**.
3. Sign in to Intuit.
4. Choose the company that matches the active workspace.
5. Approve access and return to MosoFin.
6. Confirm that QuickBooks shows a live status.

MosoFin reads QuickBooks on demand. It cannot create, update, delete, send, post, or pay through the connection.

## 3. Review tool access

1. Select **API Tools**.
2. Choose QuickBooks.
3. Confirm that the report tools needed for your first question are **Enabled** or set to **Require permission**.

Use **Disabled** for any read the workspace should never expose.

## 4. Connect Claude

1. Open Claude's connectors menu.
2. Add MosoFin.
3. Sign in to MosoFin when prompted.
4. Confirm the workspace for the task.

The selected workspace determines the authorized QuickBooks entities, agent, skills, policies, and audit history available for the request.

## 5. Ask the first question

Start with one report and explicit dates:

```
Using my selected MosoFin workspace, compare the accrual-basis profit and loss
for June 1-30, 2026 with May 1-31, 2026. Explain the three largest changes and
name the accounts supporting each explanation.
```

Review the workspace, dates, accounting basis, and supporting accounts before using the answer.

## 6. Verify the activity

1. Return to MosoFin.
2. Select **Activity**.
3. Find the tool call for the request.
4. Confirm its time, agent, tool, and task identifier.

You now have a connected workspace, governed QuickBooks reads, a working Claude connection, and an audit record.

Next, [navigate the workspace](/start-here/supported-data-formats.md) or resolve a problem in [Common issues](/troubleshooting/common-data-flow-issues.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.mosofin.com/start-here/quickstart.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.