Integrations overview

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

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 .
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.

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

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).

Sync history

Open the 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 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	Included	Included	Included	Optional invoices	Optional invoices	Optional invoice payments	Optional
Netvisor	Included	Included	Included	Optional sales invoices	Optional purchase invoices	Optional sales payments	—
Fortnox	Included	Included	Cost centers and projects	Sales invoices	Supplier invoices	Customer and supplier payments	—
Visma eEkonomi	Vouchers	Included	Projects	Customers	Suppliers	—	—
Xero	Journals	Included	Tracking categories	Invoices and credit notes	Invoices and credit notes	Invoice status and paid amounts	—
QuickBooks	GL reports and journal entries	Included	Classes and departments	Invoices and sales receipts	Bills, purchases, vendor credits	Payments, deposits, and transfers	—
e-conomic	Journal and posted entries	Included	Optional dimensions	Booked sales invoices	—	—	—
Tripletex	Postings and vouchers	Included	Departments and projects	Sales invoices	Supplier invoices	Bank statements and transactions	Optional by permission
Xledger	—	—	Projects	AR transactions	AP transactions and purchase orders	Outstanding AR/AP balances	—

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.

Billing data coverage

Integration	Objects imported
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, Netvisor, Fortnox, Visma eEkonomi, Xero, QuickBooks, e-conomic, Tripletex, and Xledger
• Billing: Stripe
• Other accounting systems: Additional accounting systems (via Nango) 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 and Dimension mappings.

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.

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.