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

# Integrations

> How Monk connects to your ERP, payment processor, and accounting stack

# Integrations

Monk connects to the systems you already use to keep customer, invoice, payment,
and credit-memo data aligned. Each integration is built on the same core
principles: direct API connectivity, incremental sync, multi-entity support where
the provider exposes it, and configurable scoping and account mapping.

<CardGroup cols={2}>
  <Card title="Rillet" icon="building-columns" href="/integrations/rillet">
    Modern accounting/ERP with multi-subsidiary support
  </Card>

  <Card title="Stripe" icon="credit-card" href="/integrations/stripe">
    Payment processing and subscription billing
  </Card>

  <Card title="NetSuite" icon="building" href="/integrations/netsuite">
    Oracle NetSuite ERP and OneWorld subsidiaries
  </Card>

  <Card title="QuickBooks" icon="book" href="/integrations/quickbooks">
    QuickBooks Online accounting
  </Card>

  <Card title="Campfire" icon="campfire" href="/integrations/campfire">
    Revenue and contract management platform
  </Card>

  <Card title="Dynamics 365" icon="microsoft" href="/integrations/dynamics-365">
    Microsoft Dynamics 365 Business Central and Finance & Operations
  </Card>

  <Card title="Xero" icon="cloud" href="/integrations/xero">
    Xero cloud accounting
  </Card>

  <Card title="Sage Intacct" icon="chart-line" href="/integrations/sage-intacct">
    Sage Intacct cloud financial management
  </Card>

  <Card title="SAP S/4HANA" icon="server" href="/integrations/sap-s4hana">
    SAP S/4HANA Cloud, Public Edition
  </Card>

  <Card title="JD Edwards" icon="database" href="/integrations/jd-edwards">
    Oracle JD Edwards EnterpriseOne
  </Card>

  <Card title="Acumatica" icon="gears" href="/integrations/acumatica">
    Acumatica Cloud ERP
  </Card>

  <Card title="Maxio & SaaSOptics" icon="right-left" href="/integrations/maxio-saasoptics">
    Billing history migration from Maxio or SaaSOptics
  </Card>
</CardGroup>

## How we think about integrations

### Authentication

Every integration uses the provider's standard, secure authentication:

* **OAuth 2.0** for cloud accounting and payment platforms that support it
  (NetSuite, QuickBooks, Stripe, Dynamics 365, Xero, Sage Intacct, Acumatica).
* **API keys** for providers where that is the canonical access model
  (Rillet, Campfire, SAP S/4HANA, Maxio, SaaSOptics).
* **Service-account credentials** for self-hosted systems (JD Edwards).
* Credentials are encrypted at rest and refreshed automatically where a refresh
  flow exists. Monk never stores your provider password.

### Entity mapping

Monk keeps a canonical set of AR entities in sync with each provider. The exact
object names differ by system, but the concepts are the same:

| Monk entity       | Examples of provider-side names               |
| ----------------- | --------------------------------------------- |
| Customers         | Customers, vendors, accounts                  |
| Invoices          | Invoices, sales invoices, receivables         |
| Invoice lines     | Invoice lines, sales invoice lines, items     |
| Payments          | Payments, customer payments, invoice payments |
| Credit memos      | Credit memos, adjustments, credit notes       |
| Products / items  | Items, products, SKUs                         |
| Chart of accounts | Accounts, GL accounts, cash accounts          |

Each provider page below lists the provider-specific object names that Monk
syncs.

### Multi-entity and currency

* **Multi-entity:** Monk can operate across subsidiaries, companies, or legal
  entities. One Monk org typically maps to one legal entity (subsidiary,
  company, or data area), and you can connect multiple Monk orgs to the same
  provider tenant.
* **Multi-currency:** Invoice and payment amounts are stored with their original
  transaction currency and exchange rate. Functional currency is respected for
  reporting and reconciliation.

### Parent-child relationships

Monk preserves parent/child relationships when the provider exposes them:

* Customer hierarchies (parent/child customers, sub-customers).
* Subsidiary/company roll-ups.
* Invoice-to-payment and invoice-to-credit-memo application links.

### Custom configuration and scoping

You can scope what syncs and how:

* **Subsidiary/company selection:** pick which legal entity a Monk org connects
  to, where the connector supports it.
* **Date cutover:** choose how far back historical invoices and payments are
  imported.
* **Payment sync and account mapping:** enable or disable payment synchronization
  and select the GL or bank account used for provider-side payment transactions.

### Sync behavior

* Incremental sync based on provider timestamps or change-data-capture feeds.
* Automatic retry with exponential backoff for transient errors.
* Clear connection health states so you know when to reconnect.

## Supported integrations

| Integration  | Category            | Authentication  |
| ------------ | ------------------- | --------------- |
| Rillet       | ERP                 | API key         |
| Stripe       | Payments / billing  | OAuth           |
| NetSuite     | ERP                 | OAuth 2.0       |
| QuickBooks   | Accounting          | OAuth 2.0       |
| Campfire     | Revenue platform    | API key         |
| Dynamics 365 | ERP                 | OAuth 2.0       |
| Xero         | Accounting          | OAuth 2.0       |
| Sage Intacct | ERP                 | OAuth 2.0       |
| SAP S/4HANA  | ERP                 | API key         |
| JD Edwards   | ERP                 | Service account |
| Acumatica    | ERP                 | OAuth 2.0       |
| Maxio        | Billing (migration) | API key         |
| SaaSOptics   | Billing (migration) | API token       |