> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dualentry.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Kintsugi Sales Tax Integration: Read-Only Setup

> Connect DualEntry to Kintsugi with a read-only sync that exports your transactions, items, and customers for sales tax monitoring and reporting.

# Kintsugi sales tax integration: read-only setup

Connect DualEntry to [Kintsugi](https://help.trykintsugi.com/en-US/trykintsugi/article/WkCNXFlc-dualentry-readonly-integration-guide), a sales tax automation provider, so your DualEntry transactions, items, and customer records sync into Kintsugi for sales tax calculation, reporting, and compliance monitoring. This is a read-only integration: data flows one way, from DualEntry into Kintsugi, and requires no changes to your existing accounting workflows. You authorize the sync with a DualEntry API key that you generate in DualEntry and paste into Kintsugi, and you set up the connection from the Kintsugi side.

## Prerequisites

Confirm the following before connecting Kintsugi to DualEntry:

* A DualEntry account where you can generate an API key. The key must carry the **Admin** role, so you need administrator access or help from an administrator.
* A Kintsugi account. You can create one during setup if you do not have one yet.
* The companies (legal entities) you tax exist in DualEntry. By default, Kintsugi imports every company in your DualEntry account.
* Complete customer addresses on the records you expect to tax. Kintsugi validates addresses after import and flags incomplete ones, so accurate addresses reduce the cleanup work in the final step.

<Info>
  This integration is read-only. DualEntry is the source of record, and Kintsugi imports a copy of your data for monitoring. Kintsugi does not write any data back into DualEntry.
</Info>

## How the read-only integration works

The Kintsugi integration is a one-way data sync that exports DualEntry records into Kintsugi for sales tax analysis. Understanding the direction of the flow clarifies where each task happens and what Kintsugi can and cannot do.

DualEntry holds your ledger, transactions, items, and customers. Kintsugi connects to DualEntry's Public API with the API key you provide and pulls a copy of that data. After the initial import, Kintsugi continues to import new transactions on an ongoing basis and monitors your sales tax exposure worldwide.

Three properties define the connection:

* **One-way sync.** Records move from DualEntry into Kintsugi only. Nothing Kintsugi calculates or stores flows back into your DualEntry ledger.
* **API key authorization.** A single DualEntry API key with the Admin role authorizes the import. You generate it in DualEntry and paste it into Kintsugi; you do not exchange credentials in the other direction.
* **All companies by default.** Kintsugi pulls in every company in your DualEntry account unless you scope the connection differently during setup.

Because the integration is read-only, Kintsugi uses your DualEntry data for tax monitoring, reporting, and compliance. It does not yet calculate tax and post it onto your DualEntry transactions. See [Current limitations](#current-limitations) for what the read-only mode excludes.

## Step 1: Generate a DualEntry API key

Create the API key in DualEntry that Kintsugi will use to read your data. Kintsugi requires a key with the Admin role.

1. In DualEntry, go to **Settings > Developer Access**.
2. Choose the **+** (plus) button to create a new API key.
3. Give the key a recognizable **name**, such as `Kintsugi`.
4. Under **Role**, select **Admin**.
5. Choose **Create API Key**.
6. Copy the API key immediately and store it somewhere safe. DualEntry shows the key only once at creation time and cannot display it again after you close the dialog.
7. Choose **Done** to close the dialog.

<Warning>
  The API key is shown only once. If you lose it before pasting it into Kintsugi, you cannot retrieve it. Generate a new key in **Settings > Developer Access** instead. For more on how DualEntry keys work, see the [Authentication guide](../../developers/guides/authentication).
</Warning>

## Step 2: Connect DualEntry to Kintsugi

Add DualEntry as a data source in Kintsugi using the API key from the previous step. You complete this step inside Kintsugi, not DualEntry.

1. Log in to your Kintsugi account, or follow the on-screen prompts to create one.
2. From the Kintsugi menu, go to **Data Sources**.
3. Choose **Browse Integration**.
4. Find **DualEntry** and choose **Connect**. A modal window opens with three fields.
5. Set **Environment** to **Production** or **Development**. For most users, choose **Production**.
6. In **API Key**, paste the key you copied from DualEntry.
7. Leave **Companies** at its default to import all companies in your DualEntry account, or scope it as needed.
8. Choose **Save**.

After you save, Kintsugi immediately begins importing your DualEntry data, including items, invoices, and customer records, so it can start monitoring your sales tax exposure.

## Step 3: Check the integration status

Confirm the import is running and watch for it to finish. Kintsugi reports the connection state on its integrations screen.

1. In Kintsugi, navigate to **Data Sources > Manage Integrations**.
2. Find **DualEntry** in the list. While the initial import runs, the status shows **Syncing**.
3. Wait for the import to complete. Depending on the volume of data, syncing can take a while. When it finishes, the status updates to **Read-Only**.

A status of **Read-Only** confirms the integration is connected and that Kintsugi is mirroring your DualEntry data in read-only mode.

## Step 4: Verify the imported data

Review the imported records in Kintsugi after the sync completes to confirm everything came over correctly. Check three record types on your Kintsugi dashboard.

* **Transactions.** Confirm that your DualEntry invoices and transactions appear on the Kintsugi dashboard.
* **Customers.** Confirm that your customer list imported correctly.
* **Products.** Review your items and check that categories and subcategories are assigned. Products are not all taxed at the same rate, so accurate categorization matters for correct tax monitoring.

If anything looks missing or incomplete, Kintsugi surfaces it as a pending task, which you resolve in the next step.

## Step 5: Resolve pending tasks

After the initial import, Kintsugi may surface pending tasks so it can calculate your tax exposure accurately. The two most common task types are product categorization and address validation.

### Product categorization

Kintsugi Intelligence, the AI engine within Kintsugi, automatically identifies a category and subcategory for each product it imports from DualEntry. Review and confirm these assignments, since taxability depends on the category. You can approve them two ways:

* **Approve individually.** Review each product one at a time and confirm its category.
* **Bulk approve.** Approve all suggested categories at once from the dashboard.

### Address validation

If any imported customer addresses are invalid or incomplete, Kintsugi flags them and suggests corrected addresses. Accurate addresses determine the correct taxing jurisdiction. You can resolve flagged addresses two ways:

* **Bulk update.** Accept all suggested corrections at once.
* **Approve individually.** Review and confirm each correction separately.

Once these tasks are cleared, setup is complete. Kintsugi continues to import your transactions regularly and monitors your sales tax exposure worldwide.

## What syncs

The integration moves data one way, from DualEntry into Kintsugi, during an initial import and on an ongoing basis afterward. The table below lists each record type and its direction.

| DualEntry data          | Kintsugi use                                | Direction             | Frequency                    |
| ----------------------- | ------------------------------------------- | --------------------- | ---------------------------- |
| Transactions (invoices) | Sales tax exposure monitoring and reporting | DualEntry to Kintsugi | Initial import, then ongoing |
| Customers               | Customer list and address validation        | DualEntry to Kintsugi | Initial import, then ongoing |
| Items (products)        | Product categorization for taxability       | DualEntry to Kintsugi | Initial import, then ongoing |

DualEntry receives nothing back from Kintsugi in this integration. Kintsugi reads your data and performs its analysis on its own side.

## Current limitations

A few aspects of the read-only integration are worth knowing before you rely on it.

* **Tax engine not yet available.** The integration currently supports read-only data sync and reporting only. Kintsugi does not yet calculate sales tax and post it onto your DualEntry transactions. To calculate tax inside DualEntry today, use the [native Tax Management engine](../core-financials/tax-management/index) or the [Avalara AvaTax integration](./avalara).
* **One-way, read-only sync.** Data flows from DualEntry into Kintsugi only. Kintsugi never writes to your DualEntry ledger, so master data in each system is maintained independently.
* **Admin API key required.** The connection needs a DualEntry API key with the Admin role. A key with a lesser role cannot complete the import.
* **All companies by default.** Kintsugi imports every company in your DualEntry account unless you scope the **Companies** field during setup.

## Troubleshoot the integration

When the sync stalls or data looks wrong in Kintsugi, the most common causes are below.

| Symptom                         | Cause                                                        | Resolution                                                                                                                |
| ------------------------------- | ------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------- |
| Status stays on **Syncing**     | A large data volume takes time to import.                    | Wait for the import to finish; the status changes to **Read-Only** when complete.                                         |
| Connection fails after **Save** | The API key is wrong, or the wrong environment was selected. | Verify the key and re-check **Production** vs **Development**, then reconnect from **Data Sources > Browse Integration**. |
| API key lost before pasting     | DualEntry shows the key only once at creation.               | Generate a new key in DualEntry under **Settings > Developer Access** and reconnect in Kintsugi.                          |
| Products flagged as pending     | Kintsugi categories are not yet confirmed.                   | Approve the suggested categories individually or in bulk from the Kintsugi dashboard.                                     |
| Customer addresses flagged      | An imported address is invalid or incomplete.                | Accept Kintsugi's suggested corrections individually or in bulk, and complete the address in DualEntry.                   |

## Result

After completing these steps, your DualEntry transactions, customers, and items sync into Kintsugi in read-only mode, and Kintsugi monitors your sales tax exposure and prepares reporting from that data. To calculate tax inside DualEntry while the Kintsugi tax engine is unavailable, see the [Avalara AvaTax integration](./avalara) and DualEntry's [native Tax Management](../core-financials/tax-management/index). For how DualEntry API keys are issued and used, see the [Authentication guide](../../developers/guides/authentication). To connect more systems, return to [Integrations](./index).