> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.monite.com/v2024-01-31/accounting/integration/index/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.monite.com/_mcp/server.

# Accounting integration

## Overview

Many SMEs use various accounting solutions to store and prepare their financial data for submission to tax authorities. With Monite, you can connect your users' data to their preferred accounting software and pull necessary financial data for import into your interface, as well as push data in case they need to do any post-accounting work outside of your application.

### Supported accounting systems

Each [entity](../../entities/index) can connect to one of the following accounting systems:

* QuickBooks Online
* Xero

New supported accounting systems will be added in future releases of our platform. If you have any specific requests, please contact our [Support team](../../intro/support).

### Requirements and considerations \[#requirements]

* All Monite partners that intend to support accounting integration must create developer accounts in the accounting platforms they intend to support.
* Each entity that wants to connect to an external accounting system (like Xero or QuickBooks) must have an account with that system before attempting to create an accounting connection with the Monite API.

## Set up the integration \[#setup]

See [Set up accounting integration](./setup).

## How the integration works \[#how-it-works]

The first step required to enable accounting integration for an entity is to establish a connection to an entity's accounting software and ask an entity user to authorize the connection. Once the connection has been established, the entity's financial data will be synchronized automatically between Monite's and the entity's accounting software. After the initial synchronization, Monite will automatically trigger synchronizations between both systems every hour.

> **Info**
>
> Monite does not push older invoices or bills to the entity's accounting software during the initial synchronization. Therefore, only invoices and bills eligible for pushing **after** the accounting synchronization will be pushed to the accounting software.

## What data is synchronized

In our accounting integration, we support two key actions for handling synchronized data:

#### Pull for matching

This feature pulls external data into our system for comparison or matching with existing records. No new records are created within the Monite platform; the purpose is solely to match the pulled data with corresponding data that already exists in our system.

#### Pull for creation

This feature not only pulls external data but also creates new entries in the Monite system for any unmatched records. If the pulled data does not have a corresponding match, a new record is automatically created in our platform.

Currently, Monite pulls and pushes the following data from and to accounting systems. Data is synchronized every hour.

<table>
  <thead>
    <tr>
      <th rowspan="2">
        Data
      </th>

      <th colspan="3">
        Pull
      </th>

      <th rowspan="2">
        Pushed
      </th>
    </tr>

    <tr>
      <th>
        for access
      </th>

      <th>
        for matching
      </th>

      <th>
        for creation
      </th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>
        [Ledger accounts](./ledger-accounts)
      </td>

      <td>
        :heavy_check_mark:
      </td>

      <td />

      <td />

      <td>
        References to ledger accounts in invoice line items, and products
      </td>
    </tr>

    <tr>
      <td>
        [Counterparts](../../common/counterparts/index)
      </td>

      <td />

      <td>
        :heavy_check_mark:
      </td>

      <td />

      <td>
        :heavy_check_mark:
      </td>
    </tr>

    <tr>
      <td>
        [Products](../../accounts-receivable/products)
      </td>

      <td />

      <td>
        :heavy_check_mark:
      </td>

      <td>
        :heavy_check_mark:
      </td>

      <td>
        :heavy_check_mark:
      </td>
    </tr>

    <tr>
      <td>
        Tax rates
      </td>

      <td>
        :heavy_check_mark:
      </td>

      <td>
        :heavy_check_mark:
      </td>

      <td />

      <td />
    </tr>

    <tr>
      <td>
        Accounts receivable: 

        [invoices](../../accounts-receivable/invoices/index)
      </td>

      <td>
        :heavy_check_mark:
      </td>

      <td />

      <td />

      <td>
        :heavy_check_mark:
      </td>
    </tr>

    <tr>
      <td>
        Accounts receivable: 

        [credit notes](../../accounts-receivable/credit-notes)
      </td>

      <td />

      <td />

      <td />

      <td>
        :heavy_check_mark:
      </td>
    </tr>

    <tr>
      <td>
        Accounts receivable: invoice 

        [payment records](../../common/payment-records)
      </td>

      <td />

      <td />

      <td />

      <td>
        :heavy_check_mark:
      </td>
    </tr>

    <tr>
      <td>
        Accounts payable: 

        [bills](/accounts-payable/payables/collect)
      </td>

      <td>
        :heavy_check_mark:
      </td>

      <td />

      <td />

      <td>
        :heavy_check_mark:
      </td>
    </tr>
  </tbody>
</table>

Entities can also pull records from the accounting system on demand by calling [`POST /accounting_connections/{connection_id}/sync`](../../api/accounting-connections/post-accounting-connections-id-sync).

## How data is synchronized

#### Pulling

### Pulling

This section describes how data is pulled from an accounting system.

#### Ledger accounts

Ledger accounts are pulled only for mapping to products. Monite does not create any new items during this process.

To access the ledger accounts pulled from the accounting system, use [`GET /ledger_accounts`](../../api/ledger-accounts/get-ledger-accounts).

#### Counterparts

Counterparts from the accounting system are matched with the existing counterparts in Monite, but no new counterparts are created in Monite if there is no match.

Counterparts are matched based on their names and each part of the billing address (country, city, street name, and so on).
All counterpart types - both organizations and individuals - are pulled as organizations.

If there is no match, entities can manually create counterparts in Monite to match the counterpart details in their accounting system.

#### Products

All products are pulled from the accounting system on the first connection. Data is pulled, and IDs are matched based on their names alone. If a product does not exist in Monite, Monite will create a new product in our database and link it to the corresponding product from your accounting system.

Every time a new product is created in the accounting system, Monite checks if there is a match for this product in Monite.
If the product is not found, Monite pulls the product's data and automatically creates the product internally.

> **Limitations**
>
> * Products with a negative price or no price are not pulled.
> * A products is not pulled from accounting if two or more products with the same name exist in Monite.
>
> These errors are included in results from [`GET /accounting_sync_records?object_type=product`](../../api/accounting-synchronized-records/get-accounting-synced-records).

#### Tax rates

Tax rates are pulled only for mapping purposes. Monite does not create any new items during this process; therefore, no action is taken if no match is found.

To access the tax rates pulled from the accounting system, use [`GET /accounting_tax_rates`](../../api/accounting-tax-rates/get-accounting-tax-rates).

> **Info**
>
> **Handling multiple matches**
>
> If a product's name matches with multiple products on either system, Monite does not attempt to match any of the results. The resulting error will be returned in your `sync_object`.

#### Accounts payable: invoices (bills)

Payables are pulled only for access purposes, they are neither matched nor created.

To get the list of payables (bills) from the accounting system, use [`GET /accounting/payables`](../../api/accounting-data-pull/get-accounting-payables).

#### Accounts receivable: invoices

Invoices are pulled only for access purposes, they are neither matched nor created.

To get the list of invoices from the accounting system, use [`GET /accounting/receivables`](../../api/accounting-data-pull/get-accounting-receivables).

#### Pushing

### Pushing

This section describes how data is pushed to an accounting system.

#### Ledger accounts

Ledger accounts are not pushed into the accounting system.

#### Accounts payable: invoices (bills)

Only payables in the ‘issued’ and ‘canceled’ statuses are pushed. Before pushing, bills are validated to confirm the presence of references for `tax_rate_ref_id`, `ledger_account_id`, and `line_items`. Issuance of bills without this validation is prohibited.

#### Accounts receivable: invoices

Monite does not push any of the entity's older invoices during the initial synchronization. After synchronization, invoices in Monite are only pushed to the entity's accounting system when they are moved to the `issued` status.

The receivable line items include the `accounting_tax_rate_id` field, which allows overriding the default tax rate when pushing invoices to the accounting system. Valid tax rate IDs can be retrieved using the `GET /accounting_tax_rates` endpoint.

#### Accounts receivable: credit notes

Credit notes are pushed without a document number. Users can backfill credit note numbers in the accounting system manually.

The pushed credit notes do not get associated with the corresponding invoices in the accounting system. As a result, invoices in the accounting system will not be automatically canceled when a corresponding credit note is pushed.

#### Payment records

Only payment records associated with accounts receivable invoices are pushed into the accounting system.
Payment records for payables (bills) are not pushed.

Before payment record can be pushed, the entity must specify the [ledger account](./ledger-accounts) to attach them to.
Use the entity setting [<code>accounting.<wbr />ledger\_account\_ids.<wbr />payments</code>](../../api/entities/patch-entities-id-settings#request.body.accounting) to specify the target ledger account. For more information, see [Assign a ledger account to payment records](./ledger-accounts#payment-records).

#### Counterparts

Monite pushes counterparts into the accounting system when:

* A new counterpart is created in Monite.
* An invoice issued to that counterpart is pushed into the accounting system.

When pushing counterparts, Monite first tries to find a matching counterpart with the same name in the accounting system.
If no match is found, Monite creates new counterparts in the accounting system.

If a counterpart in Monite has both `is_customer` and `is_vendor` set to `true`, it's pushed twice: we create a *customer* in the accounting system and also create a *vendor* with the same details but with the `_VENDOR` suffix in the name.

Once counterparts are matched, there is no regular check for data changes in either system.

After every synchronization, you can track its status and any errors returned by calling [`GET /accounting_synched_records/{synced_record_id}`](../../api/accounting-synchronized-records/get-accounting-synced-records-id). For more information, see [Check synchronization logs](./manage#check-synchronization-logs).

> Enable your users to synchronize accounts payable and receivable data with popular accounting solutions.