> 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/zoho-books/best-practices.md).

# Best Practices

## Recommended setup

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><strong>Use one data flow per reporting purpose</strong></td><td>Rather than pulling every entity into one data flow, create separate flows for AR reporting (Invoices + Customer payments), AP reporting (Bills + Purchase orders), and expense tracking. This makes troubleshooting easier and keeps destinations clean.</td></tr><tr><td><strong>Join Invoices with Customer payments</strong></td><td>Use the Join transformation to match invoices with their corresponding payments by customer. This gives you a true picture of outstanding balances rather than relying on the balance field alone.</td></tr><tr><td><strong>Append data from multiple organizations</strong></td><td>If your business runs multiple Zoho Books organizations, create a separate source connection for each and use the Append transformation to consolidate them into a single report.</td></tr><tr><td><strong>Send financial summaries to AI destinations</strong></td><td>Route Expenses or Invoices data to ChatGPT, Claude, or Gemini to generate plain-language summaries, flag anomalies, or answer ad hoc questions about your financials.</td></tr></tbody></table>

## Data refresh and scheduling

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><strong>Sync transactional entities daily</strong></td><td>Invoices, Bills, Expenses, and Customer payments change frequently. Daily syncs keep your reports accurate for AR/AP tracking and cash flow monitoring.</td></tr><tr><td><strong>Sync reference data less often</strong></td><td>Entities like Taxes, Items, Organizations, and Users change rarely. A weekly sync — or syncing on-demand when you make changes — is more than enough.</td></tr><tr><td><strong>Set a conservative start date on first run</strong></td><td>Pulling multiple years of Transactions or Invoices on the first run can be slow and may hit API rate limits. Start with 3–6 months back, confirm the data looks right, then extend the range if needed.</td></tr></tbody></table>

## Common pitfalls

{% hint style="danger" %}
Don't aggregate invoice or bill totals across currencies without accounting for exchange rates. Zoho Books stores amounts in transaction currency — summing them directly will produce incorrect totals if your organization transacts in multiple currencies.
{% endhint %}

{% columns %}
{% column %}
**Do**

* Use the `status` field to filter Invoices and Bills (e.g., show only Overdue or Open)
* Use a specific Organization ID per connection to avoid mixing data across orgs
* Verify your data flow runs successfully before setting a schedule
* Pull the Transactions entity when you need a complete ledger view
  {% endcolumn %}

{% column %}
**Don't**

* Use a low-permission user's API key if you need access to Banking or Journals
* Set your start date to the beginning of your account history on the first run — start recent
* Combine invoice totals and bill totals in the same column without labeling them — use the Append transformation with a source label
* Assume Transactions and Invoices counts will match — they reflect different levels of the ledger
  {% endcolumn %}
  {% endcolumns %}


---

# 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.coupler.io/sources/category/finance-and-accounting/zoho-books/best-practices.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.