​

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.

​

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