> ## Documentation Index
> Fetch the complete documentation index at: https://control-dev.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Integrations overview

> Connect accounting, CRM, billing, and operational systems to Control.

export const ControlAppLink = ({path, breadcrumb, children}) => {
  const link = <a href={`https://app.control.dev${path}`} target="_blank" rel="noopener noreferrer" aria-label={breadcrumb ? `Open ${breadcrumb} in Control` : undefined}>
      {children}
    </a>;
  return breadcrumb ? <Tooltip tip={breadcrumb}>{link}</Tooltip> : link;
};

An integration belongs to an entity and imports data from one source system. A single entity can have several data sources, for example accounting plus CRM and billing.

## Connect a data source

1. Open <ControlAppLink path="/entities-data-sources/overview"><strong>Entities & sources</strong></ControlAppLink>.
2. Open the entity or choose **Add data source**.
3. Select the source system.
4. Complete OAuth or enter the requested credentials.
5. Verify the connection and wait for the first sync.

<Note>
  Credential fields are encrypted. After saving, secret fields appear empty because Control does not read the saved
  secret back into the browser.
</Note>

### Native integrations vs. Via Nango

**Add data source** groups accounting systems into two sections:

* **Native integrations** — connectors maintained by Control. Data starts importing on the standard schedule after
  the first sync. Rows are tagged **Native**.
* **More accounting systems (Via Nango)** — a searchable catalog of additional providers. Connecting captures
  credentials only. Data import starts after Control activates the provider pipeline for you. Rows are tagged
  **Via Nango**. See [Additional accounting systems (via Nango)](/product-docs/integrations/nango-accounting).

## Sync history

Open the <ControlAppLink path="/entities-data-sources/sync-history"><strong>Sync history</strong></ControlAppLink> tab to see recent integration runs and their status.

## Closed accounting periods

Where supported, accounting integrations report their latest period-lock state. Use [Closed periods](/product-docs/integrations/closed-periods)
to identify actuals that may still change and to record a separate manual close decision in Control when needed.

## Credential methods

| Method                    | What you do                                                                    |
| ------------------------- | ------------------------------------------------------------------------------ |
| OAuth                     | Choose Connect, authorize Control in the provider, and return to Control.      |
| Provider token or key     | Create a restricted credential in the provider and paste it into Control.      |
| Provider-specific consent | Approve Control's app, then provide the resulting agreement or employee token. |

## Accounting data coverage

The table describes the source objects Control imports. **Included** means the object is loaded by the standard
connection. **Optional** means it also depends on a Control integration setting, provider module, or source-system
permission. A dash means Control does not currently import that object as a standalone dataset.

| Integration                                                 | GL entries                     | Chart of accounts | Dimensions / projects     | Sales / receivables         | Purchases / payables                | Payment / bank data               | Payroll / employees    |
| ----------------------------------------------------------- | ------------------------------ | ----------------- | ------------------------- | --------------------------- | ----------------------------------- | --------------------------------- | ---------------------- |
| [Procountor](/product-docs/integrations/procountor)         | Included                       | Included          | Included                  | Optional invoices           | Optional invoices                   | Optional invoice payments         | Optional               |
| [Netvisor](/product-docs/integrations/netvisor)             | Included                       | Included          | Included                  | Optional sales invoices     | Optional purchase invoices          | Optional sales payments           | —                      |
| [Fortnox](/product-docs/integrations/fortnox)               | Included                       | Included          | Cost centers and projects | Sales invoices              | Supplier invoices                   | Customer and supplier payments    | —                      |
| [Visma eEkonomi](/product-docs/integrations/visma-eekonomi) | Vouchers                       | Included          | Projects                  | Customers                   | Suppliers                           | —                                 | —                      |
| [Xero](/product-docs/integrations/xero)                     | Journals                       | Included          | Tracking categories       | Invoices and credit notes   | Invoices and credit notes           | Invoice status and paid amounts   | —                      |
| [QuickBooks](/product-docs/integrations/quickbooks)         | GL reports and journal entries | Included          | Classes and departments   | Invoices and sales receipts | Bills, purchases, vendor credits    | Payments, deposits, and transfers | —                      |
| [e-conomic](/product-docs/integrations/economic)            | Journal and posted entries     | Included          | Optional dimensions       | Booked sales invoices       | —                                   | —                                 | —                      |
| [Tripletex](/product-docs/integrations/tripletex)           | Postings and vouchers          | Included          | Departments and projects  | Sales invoices              | Supplier invoices                   | Bank statements and transactions  | Optional by permission |
| [Xledger](/product-docs/integrations/xledger)               | —                              | —                 | Projects                  | AR transactions             | AP transactions and purchase orders | Outstanding AR/AP balances        | —                      |

<Note>
  Invoice rows can contain customer, supplier, payment-status, or dimension details even when the provider does not
  expose those records as a separate dataset. Available history and fields can also depend on the provider plan and the
  rights granted to the integration user.
</Note>

## Billing data coverage

| Integration                                 | Objects imported                                                                                                                                                                                        |
| ------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [Stripe](/product-docs/integrations/stripe) | Customers, subscriptions, invoices and line items, charges, payment intents and methods, products, prices, credit notes, refunds, balance transactions, coupons, promotion codes, and tax configuration |

## Available setup guides

* **Accounting:** [Procountor](/product-docs/integrations/procountor), [Netvisor](/product-docs/integrations/netvisor), [Fortnox](/product-docs/integrations/fortnox), [Visma eEkonomi](/product-docs/integrations/visma-eekonomi), [Xero](/product-docs/integrations/xero), [QuickBooks](/product-docs/integrations/quickbooks), [e-conomic](/product-docs/integrations/economic), [Tripletex](/product-docs/integrations/tripletex), and [Xledger](/product-docs/integrations/xledger)
* **Billing:** [Stripe](/product-docs/integrations/stripe)
* **Other accounting systems:** [Additional accounting systems (via Nango)](/product-docs/integrations/nango-accounting) for providers without a native connector yet

## After connecting

The first successful sync imports the available source records. Accounting integrations that provide a chart of accounts
or dimensions also create or update those records in Control. Continue with [Account mappings](/product-docs/configuration/account-mappings)
and [Dimension mappings](/product-docs/configuration/dimension-mappings).

<Note>
  **How long does the first sync take?** Smaller datasets with tens of thousands of general ledger (GL) rows typically
  finish in minutes. Larger datasets can take several hours. Control must fetch the complete GL history before the
  Balance Sheet can match the source system because Balance Sheet balances are cumulative across accounting periods.
</Note>

## Troubleshooting checklist

* Confirm the credential belongs to the intended company or agreement.
* Confirm the source-system user has access to the required data.
* For restricted keys, confirm read access covers the required resources.
* Verify the integration is enabled in Control.
* Check whether the provider requires a paid API or integrations module.
* If a token was rotated or revoked, update the saved credential and verify again.