Integrations

Integration Overview

View as Markdown

Tabs integrates with your existing stack so finance teams don’t re-enter data across systems. Understanding how data flows helps you configure integrations correctly during implementation.

Data flow

The typical Tabs integration path:

  1. CRM (HubSpot or Salesforce) syncs customers and closed-won contract documents into Tabs
  2. Tabs processes contracts, generates billing terms, invoices, and revenue schedules
  3. ERP receives customers, sent invoices, payments, credit memos, and revenue journal entries from Tabs
  4. Stripe and Plaid connect for payment collection and cash application
  5. Tax providers calculate sales tax on eligible invoices

Customers from CRM often arrive in Tabs before contracts — you’ll see labels like Created by HUBSPOT in the app. Contract sync then links each deal to the existing customer record.

Integration categories

CRM (HubSpot, Salesforce)

CRM integrations sync:

  • Customers — companies created and updated before contracts are linked
  • Contracts — PDFs from closed-won deals or configured opportunities

Setup requires provisioning sandbox and production accounts for Tabs to configure the connection. Contact your implementation manager or customer success team to get started.

See Customer Ingestion and Contract Ingestion.

E-signature (DocuSign, PandaDoc)

Signed contracts can flow into Tabs automatically when e-signature platforms are configured to email a PDF copy to Tabs on completion. A link alone is not sufficient — the PDF attachment is required.

See Contract Ingestion for email ingest requirements and e-signature platform configuration.

ERP

Tabs connects directly to QuickBooks Online, NetSuite, Sage Intacct, and Rillet. Other ERPs may be supported via CSV or API — contact support for options.

ERP integrations sync customers, invoices, payments, credit memos, items, chart of accounts, and revenue journal entries. See ERP & Account Mapping for connect instructions and sync details.

Payments (Stripe, Plaid)

  • Stripe — customer portal payments, autocharge, card and ACH processing
  • Plaid — bank transaction sync for cash application and invoice matching

See Payments & Integrations, Set Up Stripe, and Set Up Plaid.

Tax (Anrok, Avalara, Sphere)

Tax providers calculate sales tax on invoices at send time. For QuickBooks, a sales tax integration item maps tax line items to your chart of accounts.

See Invoices & Integrations and Set Up Tax.

Setup models

IntegrationSetup approach
QuickBooks OnlineSelf-serve — connect via Settings → Integrations → QuickBooks Online
StripeSelf-serve — OAuth connect via Settings → Integrations → Stripe
PlaidSelf-serve — bank connect via Settings → Integrations → Plaid
NetSuiteSelf-serve — OAuth 2.0 connect via Settings → Integrations → NetSuite
HubSpot / SalesforceImplementation-led — sandbox and production CRM accounts required
DocuSign / PandaDocAdmin configuration in your e-sign platform

Contact your implementation manager for complex NetSuite configurations. If you connect a sandbox environment, ensure it has been synced with production within the last few months to maintain data consistency.

Notifications

When contracts are ingested via email, CRM sync, or e-signature platforms, Tabs can notify your team in Slack when documents are received and processed. Contact support if a document was sent but has not appeared in Tabs.

Programmatic access

Beyond native integrations, Tabs exposes a REST API for building custom workflows:

  • Tabs Integrators API — create customers, contracts, billing terms, and pull invoices, payments, and reports. See Develop With the Tabs API.
  • Usage Events API — ingest metered usage data for usage-based billing
  • Tabs MCP Connector — query billing, revenue, and contract data from AI assistants via the Model Context Protocol

See Develop with the Tabs API for rate limit details.