> For the complete documentation index, see [llms.txt](https://docs.coupler.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coupler.io/sources/category/finance-and-accounting/quickbooks.md).

# QuickBooks

QuickBooks Online is Intuit's cloud-based accounting platform used by small and mid-sized businesses to manage invoices, expenses, payroll, and financial reporting. By connecting QuickBooks to Coupler.io, you can automatically export your accounting data to spreadsheets, BI tools, or databases — no manual CSV downloads required.

Coupler.io offers **two QuickBooks data sources** that cover different use cases:

| Data source            | What it does                                                                                              |
| ---------------------- | --------------------------------------------------------------------------------------------------------- |
| **QuickBooks**         | Pulls raw entity data — invoices, customers, bills, payments, vendors, and 25+ other data categories      |
| **QuickBooks Reports** | Pulls pre-built financial reports — P\&L, Balance Sheet, General Ledger, Transaction List, and 20+ others |

## Why connect QuickBooks to Coupler.io?

* **Automate financial reporting** — Schedule regular data refreshes so your spreadsheets and dashboards always reflect the latest accounting data.
* **Build custom dashboards** — Export P\&L, Balance Sheet, or transaction data to Looker Studio, Power BI, or Google Sheets for visualization beyond what QuickBooks offers natively.
* **Combine with other sources** — Merge QuickBooks data with CRM, e-commerce, or advertising data for a full picture of business performance.
* **Flexible destinations** — Export to AI tools, Google Sheets, Excel, BigQuery, Looker Studio, Power BI, or other supported destinations.

## Prerequisites

Before connecting, make sure you have:

* A **QuickBooks Online** account (Simple Start, Essentials, Plus, or Advanced)
* Admin or Accountant access to the company file you want to pull data from
* A Coupler.io account

{% hint style="warning" %}
Coupler.io connects to the **QuickBooks Online** API only. **QuickBooks Desktop** is not supported. If you use QuickBooks Desktop, you would need to migrate to QuickBooks Online first.
{% endhint %}

## Quick start

{% hint style="success" %}
Start with a **Profit and Loss Summary** report for **This Fiscal Year**, with Display columns by **Month**. This gives you a monthly revenue and expense breakdown that you can immediately visualize in Looker Studio or Google Sheets. Run it once to verify the connection, then set up a daily or weekly auto-refresh schedule.
{% endhint %}

## How to connect

Both QuickBooks data sources use **OAuth authentication** — you sign in with your Intuit account directly.

{% stepper %}
{% step %}
In Coupler.io, create a new **data flow** and select **QuickBooks** (for entity data) or **QuickBooks Reports** (for financial reports) as the source.
{% endstep %}

{% step %}
Click **Connect** and sign in with your Intuit/QuickBooks account.
{% endstep %}

{% step %}
Grant Coupler.io permission to **view your QuickBooks data**. Click **Allow**.
{% endstep %}

{% step %}
**For QuickBooks (entities):** Select a **data entity** (e.g., Invoice, Customer, Bill).
{% endstep %}

{% step %}
**For QuickBooks Reports:** Select a **report name** (e.g., Profit and Loss Summary, General Ledger Detail). Set the **report period**.
{% endstep %}

{% step %}
Choose your **destination** and run the import.
{% endstep %}
{% endstepper %}

## QuickBooks data overview

Coupler.io provides two separate QuickBooks data sources, each designed for different use cases. **QuickBooks** gives you raw entity data (invoices, customers, bills, etc.), while **QuickBooks Reports** gives you pre-built financial reports (P\&L, Balance Sheet, General Ledger, etc.).

## QuickBooks (Entity Data)

This source pulls structured records directly from your QuickBooks Online account. Select one entity per data flow.

#### Available entities

| Entity            | Description                       | Typical use case                      |
| ----------------- | --------------------------------- | ------------------------------------- |
| **Invoice**       | Customer invoices with line items | Revenue tracking, accounts receivable |
| **Customer**      | Customer records and contact info | Customer lists, contact management    |
| **Bill**          | Vendor bills (accounts payable)   | Expense tracking, AP aging            |
| **Payment**       | Customer payments received        | Cash flow tracking                    |
| **Vendor**        | Vendor/supplier records           | Vendor management, AP reporting       |
| **Employee**      | Employee records                  | Payroll, HR reporting                 |
| **Estimate**      | Quotes and estimates              | Sales pipeline tracking               |
| **Purchase**      | Purchases and expenses            | Expense analysis                      |
| **PurchaseOrder** | Purchase orders                   | Procurement tracking                  |
| **SalesReceipt**  | Point-of-sale receipts            | Retail and cash sales                 |
| **CreditMemo**    | Credit memos issued               | Refund and credit tracking            |
| **Deposit**       | Bank deposits                     | Cash flow, deposit reconciliation     |
| **Transfer**      | Bank-to-bank transfers            | Cash management                       |
| **JournalEntry**  | Manual journal entries            | Adjustments, accruals                 |
| **Account**       | Chart of accounts                 | Account structure and balances        |
| **Item**          | Products and services             | Inventory, catalog management         |
| **Budget**        | Budget records                    | Budget vs. actual analysis            |
| **TimeActivity**  | Time tracking entries             | Billable hours, payroll hours         |

Additional entities: Attachable, BillPayment, Class, CompanyInfo, Department, ExchangeRate, JournalCode, PaymentMethod, Preferences, RefundReceipt, TaxAgency, TaxCode, TaxRate, Term, VendorCredit.

#### Entity parameters

| Parameter    | Purpose                                                                    | Example                 |
| ------------ | -------------------------------------------------------------------------- | ----------------------- |
| **Where**    | Filter records using QuickBooks query syntax                               | `TxnDate>='2025-01-01'` |
| **Order**    | Sort results by a field (ascending by default; append DESC for descending) | `EmailAddress DESC`     |
| **Split by** | Split multi-line values (e.g., invoice line items) into separate rows      | `Line`                  |

{% hint style="info" %}
The Where parameter accepts standard date strings in `YYYY-MM-DD` format. See the [Where parameter guide](https://docs.coupler.io/sources/category/finance-and-accounting/quickbooks/where.md) for full syntax and field-by-field examples.
{% endhint %}

## QuickBooks Reports (Financial Reports)

This source pulls formatted financial reports from QuickBooks Online. Each report has its own set of columns and query parameters.

#### Summary reports

| Report                          | What it shows                               | Key parameters                             |
| ------------------------------- | ------------------------------------------- | ------------------------------------------ |
| **Profit and Loss Summary**     | Revenue and expenses by account             | `accounting_method`, `class`, `department` |
| **Balance Sheet**               | Assets, liabilities, and equity snapshot    | `accounting_method`, `adjusted_gain_loss`  |
| **Cash Flow**                   | Cash inflows and outflows                   | `class`, `department`, `customer`          |
| **Trial Balance**               | Debit/credit balances for all accounts      | `accounting_method`                        |
| **Expenses by Vendor**          | Expense totals grouped by vendor            | `accounting_method`, `class`               |
| **Sales by Customer**           | Sales totals grouped by customer            | `accounting_method`, `class`               |
| **Sales by Product**            | Sales totals grouped by product/service     | `accounting_method`, `department`          |
| **Sales by Class Summary**      | Sales totals grouped by class               | `accounting_method`                        |
| **Sales by Department**         | Sales totals grouped by department/location | `accounting_method`                        |
| **Tax Summary**                 | Tax collected and owed                      | —                                          |
| **Inventory Valuation Summary** | Inventory quantities and values             | —                                          |

#### Detail reports

| Report                           | What it shows                                    | Key columns                            |
| -------------------------------- | ------------------------------------------------ | -------------------------------------- |
| **Profit and Loss Detail**       | Individual transactions behind P\&L line items   | Date, Type, Name, Amount, Balance      |
| **General Ledger Detail**        | All transactions by account with running balance | Date, Account, Debit, Credit, Balance  |
| **Transaction List**             | All transactions in a flat list                  | Date, Type, Account, Amount            |
| **Transaction List by Customer** | Transactions grouped by customer                 | Date, Type, Customer, Amount           |
| **Transaction List by Vendor**   | Transactions grouped by vendor                   | Date, Type, Vendor/Supplier, Amount    |
| **Transaction List with Splits** | Transactions showing all split lines             | Date, Account, Amount, Product/Service |
| **Journal Report**               | Journal entries with debit/credit detail         | Date, Account, Debit, Credit           |

#### Aging and balance reports

| Report                        | What it shows                                 |
| ----------------------------- | --------------------------------------------- |
| **AP Aging Detail / Summary** | Outstanding vendor bills by aging period      |
| **AR Aging Detail / Summary** | Outstanding customer invoices by aging period |
| **Customer Balance / Detail** | Customer balances and underlying transactions |
| **Vendor Balance / Detail**   | Vendor balances and underlying transactions   |
| **Customer Income**           | Income by customer                            |
| **Account List Detail**       | Chart of accounts with balances               |

#### Report configuration options

| Option                 | Purpose                                                                      | Available for                        |
| ---------------------- | ---------------------------------------------------------------------------- | ------------------------------------ |
| **Report period**      | Preset time range (This Month, Last Fiscal Year, Custom, etc.)               | All reports                          |
| **Start/End date**     | Custom date range (when Report period = Custom)                              | All reports                          |
| **Display columns by** | Group data into columns by time period or dimension                          | Summary reports, Transaction Lists   |
| **Report structure**   | Choose between QuickBooks-style (hierarchical) or Flat structure             | Detail reports, some summary reports |
| **Query parameters**   | Additional filters (accounting\_method, class, department, customer, vendor) | Varies by report                     |
| **Columns**            | Select specific columns to include                                           | Detail reports                       |

## Common metric combinations

| Goal                      | Source                          | Configuration                                     |
| ------------------------- | ------------------------------- | ------------------------------------------------- |
| Monthly P\&L dashboard    | QuickBooks Reports              | Profit and Loss Summary, Display columns by Month |
| Accounts receivable aging | QuickBooks Reports              | AR Aging Detail with customer and term filters    |
| Invoice line-item export  | QuickBooks                      | Invoice entity, Split by = `Line`                 |
| Filtered vendor expenses  | QuickBooks Reports              | Expenses by Vendor, filter by class or department |
| Budget vs. actual         | QuickBooks + QuickBooks Reports | Budget entity + Profit and Loss Summary           |

## Use cases by role

{% tabs %}
{% tab title="Finance / Accounting" %}
Automate P\&L, Balance Sheet, and General Ledger exports to Google Sheets or BigQuery. Combine with budgets for variance analysis. Use the `accounting_method` parameter to ensure consistent Cash or Accrual reporting across all data flows.
{% endtab %}

{% tab title="Business Owners" %}
Build monthly revenue and expense dashboards in Looker Studio or Power BI without waiting for accountant reports. Start with Profit and Loss Summary by Month and AR/AP Aging Summary for a real-time snapshot of your business health.
{% endtab %}

{% tab title="Operations" %}
Track AP/AR aging, vendor balances, and purchase orders to manage cash flow proactively. Use the Customer Balance Detail and Vendor Balance Detail reports to stay on top of outstanding receivables and payables.
{% endtab %}

{% tab title="Bookkeepers" %}
Export transaction lists and journal entries for audit preparation and reconciliation. The General Ledger Detail and Transaction List with Splits reports give you the granular, row-level data needed for month-end close and audit trails.
{% endtab %}
{% endtabs %}

## Platform-specific notes

* **QuickBooks Online only** — Coupler.io connects to the QuickBooks Online API. QuickBooks Desktop is not supported.
* **Accounting method** — Reports default to the accounting method set in your QuickBooks company preferences. To override, use the `accounting_method` query parameter with value `Cash` or `Accrual`.
* **400,000-cell limit** — The QuickBooks Reports API has a hard limit of 400,000 cells (rows × columns) per report. If your report exceeds this, QuickBooks truncates the data. Narrow your date range or filters to stay under the limit.
* **Budget entity limitations** — The Budget entity returns budget metadata (name, type, dates) but budget line-item details (monthly amounts by account) are returned in a nested format that requires additional processing.
* **Inactive records** — By default, the QuickBooks entity source returns only active records. To include inactive records (e.g., inactive vendors), add `Active IN (false, true)` to the Where parameter.
* **Class and Department filtering** — To filter reports by Class or Department, you must use the `class` or `department` query parameters with the entity IDs (not names). Find these IDs by first exporting the Class or Department entity.
* **Date fields** — Both the Where parameter (entities) and the Start/End date fields (reports) accept dates in `YYYY-MM-DD` format. Use the date picker for report Start/End dates.

## QuickBooks common issues

### Connection Issues

<details>

<summary>401 Authorization Error — "AuthorizationFault"</summary>

The OAuth token has expired or been revoked. QuickBooks tokens expire periodically, and any changes to your Intuit account credentials can also invalidate them.

**Fix:**

1. Go to your Coupler.io data flow settings.
2. Click the source connection and select **Reconnect**.
3. Sign in again with your Intuit/QuickBooks credentials and re-authorize.

If the Reconnect option doesn't appear, remove the existing QuickBooks connection from **Settings → Connections** and create a new one.

</details>

<details>

<summary>QuickBooks Desktop is not supported</summary>

Coupler.io connects to the QuickBooks Online API only. If you have QuickBooks Desktop (including Desktop Enterprise), the integration will not work.

**Fix:** You would need to migrate your data to QuickBooks Online, or use a third-party sync tool that bridges QuickBooks Desktop to an online-accessible format.

</details>

<details>

<summary>Connection works but data flow fails on subsequent runs</summary>

This usually means the OAuth token refreshed successfully but QuickBooks returned an API error. Check the error details in the data flow run history.

**Fix:** Open the data flow, click on the failed run, and expand the error details. Common causes include changed permissions, a deleted entity, or API rate limits.

</details>

### Missing Data

<details>

<summary>Only active records are returned (missing inactive vendors, customers, etc.)</summary>

By default, QuickBooks API queries return only active records. Inactive vendors, customers, or items won't appear unless you explicitly request them.

**Fix:** Add `Active IN (false, true)` to the **Where** parameter to include both active and inactive records.

</details>

<details>

<summary>Budget entity returns metadata but no line-item amounts</summary>

The QuickBooks Budget entity returns budget-level metadata (name, fiscal year, type) but the detailed line items (monthly amounts per account) come in a nested format that isn't broken out into columns automatically.

**Fix:** There is currently no built-in way to fully flatten budget line items in Coupler.io. As a workaround, export the Budget entity and process the nested fields in your destination using formulas or a transformation step.

</details>

<details>

<summary>P&#x26;L report returns data for wrong date range</summary>

Some users set a custom report period (e.g., starting January 2021) but only receive data from a more recent period.

**Fix:** Make sure you select **Custom** as the Report period and then enter both the **Start date** and **End date** explicitly. Also check that your QuickBooks company file actually contains data for the requested period.

</details>

<details>

<summary>Invoice or transaction data is missing line-item detail</summary>

When exporting invoices or other entities with multiple line items, each record may appear as a single row with aggregated data.

**Fix:** Set the **Split by** parameter to `Line`. This splits multi-line documents into separate rows — one row per line item.

</details>

### Permission Errors

<details>

<summary>"Access denied" or missing entities</summary>

Some QuickBooks entities require specific subscription tiers or features to be enabled (e.g., Classes require QuickBooks Plus or Advanced, Budget requires Plus or Advanced).

**Fix:** Verify your QuickBooks Online subscription tier supports the entity you're trying to export. Also ensure the connected account has Admin or Accountant-level access.

</details>

### Data Discrepancies

<details>

<summary>Reports show Cash basis instead of Accrual (or vice versa)</summary>

QuickBooks Reports default to the accounting method set in your company preferences. If you're getting Cash-basis data when you expect Accrual, the report is inheriting the default.

**Fix:** Add the query parameter `accounting_method: Accrual` (or `Cash`) in the **Query parameters** field. This overrides the company default for that specific report.

</details>

<details>

<summary>Report totals don't match QuickBooks Online</summary>

Small differences between Coupler.io exports and the QuickBooks UI can occur when the report covers a different date range, uses a different accounting method, or includes/excludes certain transaction types.

**Fix:**

1. Confirm the **report period** and **start/end dates** match exactly.
2. Check the **accounting\_method** parameter.
3. Verify **Display columns by** is set the same way (Total vs. Month can affect how subtotals appear).
4. For multicurrency accounts, check whether the report includes or excludes currency conversion adjustments (`adjusted_gain_loss` parameter).

</details>

<details>

<summary>General Ledger doesn't show split transaction detail</summary>

The General Ledger Detail report may show "Split" in the Split column instead of the actual accounts involved when a transaction is split across multiple accounts.

**Fix:** Use the **Transaction List with Splits** report instead. This report outputs each split as a separate row, showing the actual GL account or class for each portion of the transaction.

</details>

<details>

<summary>Line items are concatenated in one column and row</summary>

When exporting Invoices, Bills, or other entities with multiple line items with the **Split by** parameter empty, you will get one row per invoice, bill (or whichever entity is selected), and will have the line items concatenated together like so:

<figure><img src="https://1055512216-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOFxU2LUkJMCfvbE2re5C%2Fuploads%2FdAz5LNK2OJV3gxsSGfTS%2Fimage.png?alt=media&amp;token=df63654e-767a-4c39-bad8-a6d0640630b2" alt=""><figcaption></figcaption></figure>

To unnest or flatten this to give you one row per line item, set the **Split by** parameter to `Line` :

<figure><img src="https://1055512216-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOFxU2LUkJMCfvbE2re5C%2Fuploads%2FCa20e27XHh1skmujeiED%2Fimage.png?alt=media&amp;token=0a62b5f0-cfa1-4205-8d63-bc389ae9a1d3" alt=""><figcaption></figcaption></figure>

<figure><img src="https://1055512216-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOFxU2LUkJMCfvbE2re5C%2Fuploads%2FPfkMk3jiSne0aeCtVoCe%2Fimage.png?alt=media&amp;token=197b2f89-6685-4cb5-b208-1fe6e99ea83a" alt=""><figcaption></figcaption></figure>

</details>

### Rate Limits and API Errors

<details>

<summary>400,000-cell limit error — report data is truncated</summary>

The QuickBooks Reports API enforces a hard limit of 400,000 cells (rows × columns). When a report exceeds this, QuickBooks truncates the response or injects an error message like "Unable to generate report."

**Fix:**

* Narrow the date range (e.g., pull monthly instead of yearly).
* Reduce the number of columns selected.
* Filter by class, department, or customer to reduce the data volume.
* Split the report across multiple data flows with non-overlapping date ranges.

</details>

{% hint style="danger" %}
The 400,000-cell limit is a QuickBooks API limitation, not a Coupler.io limitation. There is no way to increase it. If your General Ledger or Transaction List consistently hits this limit, you must split your exports into smaller time ranges.
{% endhint %}

<details>

<summary>Data type mismatch errors when exporting to BigQuery</summary>

BigQuery requires consistent data types within a column. If QuickBooks returns mixed types (e.g., a "Num" column that contains both integers and strings like "JL07"), the import fails.

**Fix:** Use the **Columns** selector in Coupler.io to exclude problematic columns, or use a transformation step to standardize the data types before export.

</details>

<details>

<summary>Power BI error: "Key should not be null or empty"</summary>

This occurs when a column in the exported data has a blank or "Untitled" header. Power BI cannot parse columns without proper names.

**Fix:**

1. Open the data flow in Coupler.io.
2. Go to the **Transform** step.
3. Rename any blank or "Untitled" column headers.
4. Re-run the data flow and refresh the Power BI connection.

</details>

## QuickBooks FAQ

<details>

<summary>What's the difference between QuickBooks and QuickBooks Reports in Coupler.io?</summary>

**QuickBooks** pulls raw entity data — individual records like invoices, customers, bills, vendors, and 25+ other data categories. Each record is a row with all its fields.

**QuickBooks Reports** pulls pre-built financial reports — Profit and Loss, Balance Sheet, General Ledger, and 20+ others. These are the same reports you see in QuickBooks Online, formatted with totals, subtotals, and groupings.

Use **QuickBooks** when you need granular transactional data. Use **QuickBooks Reports** when you need summarized financial data for dashboards or analysis.

</details>

<details>

<summary>Does Coupler.io work with QuickBooks Desktop?</summary>

No. Coupler.io connects to the **QuickBooks Online** API only. QuickBooks Desktop (including Desktop Enterprise and Desktop Pro) is not supported. To use Coupler.io, you would need to migrate to QuickBooks Online.

</details>

<details>

<summary>Can I pull custom reports from QuickBooks?</summary>

No. Coupler.io can only pull the predefined report types available through the QuickBooks API (Profit and Loss Summary, Balance Sheet, General Ledger Detail, Transaction List, etc.). Custom reports that you create inside the QuickBooks UI are not accessible via the API.

As a workaround, use the closest predefined report and apply **query parameters** (filter by class, department, customer, vendor, date range) to approximate your custom report.

</details>

<details>

<summary>How do I filter reports by Class?</summary>

Add `class: <class_id>` in the **Query parameters** field. You need to use the Class ID (a number), not the class name.

To find the Class ID, create a separate data flow using the **QuickBooks** source with the **Class** entity. This will export all classes with their IDs. Then use that ID in your report query parameter.

For multiple classes, separate the IDs with commas: `class: 12345,67890` (no spaces between values).

</details>

<details>

<summary>How do I switch a report from Cash to Accrual accounting?</summary>

Add the query parameter `accounting_method: Accrual` (or `accounting_method: Cash`) in the **Query parameters** section of your data flow. This overrides the default accounting method set in your QuickBooks company preferences.

This parameter is available on most financial reports including Profit and Loss, Balance Sheet, Customer Balance, and Expenses by Vendor.

</details>

<details>

<summary>How do I include inactive vendors or customers?</summary>

By default, QuickBooks only returns active records. To include inactive ones, add `Active IN (false, true)` to the **Where** parameter in your data flow settings.

This works for Vendor, Customer, Item, Account, Employee, and other entities that have an Active field.

</details>

<details>

<summary>How do I export invoice line items as separate rows?</summary>

Set the **Split by** parameter to `Line` in your data flow settings. This tells Coupler.io to split multi-line documents (invoices, bills, sales receipts) into separate rows — one row per line item.

Without this setting, each invoice appears as a single row with aggregated totals.

</details>

<details>

<summary>Why is my report data truncated or incomplete?</summary>

The QuickBooks Reports API has a hard limit of **400,000 cells** (rows × columns). If your report exceeds this, the data is silently truncated.

To fix this, narrow the date range, select fewer columns, or filter by class/department/customer. If your General Ledger or Transaction List frequently hits this limit, split the export into monthly data flows.

</details>

<details>

<summary>How do I use the Where parameter to filter by date?</summary>

Use the `TxnDate` field with comparison operators. Examples:

* `TxnDate>='2025-01-01'` — transactions from January 1, 2025 onward
* `TxnDate>='2025-01-01' AND TxnDate<'2025-02-01'` — January 2025 only
* `MetaData.CreateTime >= '2025-01-24'` — records created in the last 30 days (update the date as needed)

</details>

<details>

<summary>Why doesn't the OR operator work in the Where parameter?</summary>

The QuickBooks query language does **not support the OR operator**. Only `AND` is supported for combining multiple conditions. If you need OR-like behavior, you would need to create separate data flows for each condition and combine the results in your destination.

Alternatively, the `IN` operator can match multiple values for a single field: `Id IN ('30','80')`.

</details>

<details>

<summary>Can I display columns by both Class and Month at the same time?</summary>

No. The **Display columns by** option supports only one dimension at a time. You can group by Month or by Class, but not both simultaneously. This is a QuickBooks API limitation.

As a workaround, create two separate data flows — one grouped by Month and one grouped by Class — and combine them in your destination.

</details>

<details>

<summary>What QuickBooks Online subscription do I need?</summary>

Coupler.io works with all QuickBooks Online tiers: Simple Start, Essentials, Plus, and Advanced. However, some features and entities require higher tiers:

* **Classes** and **Locations** require Plus or Advanced
* **Budgets** require Plus or Advanced
* **Custom fields** require certain plan tiers

If you try to export an entity or use a report parameter that isn't available on your plan, QuickBooks may return an error or empty data.

</details>

{% hint style="info" %}
For detailed query parameter syntax and field-by-field reference for each entity, see the [Where parameter guide](https://docs.coupler.io/sources/category/finance-and-accounting/quickbooks/where.md). For report-specific query parameters, see the [Reports parameters guide](https://docs.coupler.io/sources/category/finance-and-accounting/quickbooks/parameters.md).
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.coupler.io/sources/category/finance-and-accounting/quickbooks.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
