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

# Accounting Integration Deployment Decisions

export const NoteCallout = ({title, children, icon = "💡"}) => <div style={{
  backgroundColor: 'var(--recommended-bg)',
  borderLeft: '4px solid #3beaf6',
  borderRadius: '10px',
  padding: '18px 22px',
  marginBottom: '20px',
  boxShadow: '1px 1px 3px rgba(0,0,0,0.06)'
}}>
    <div style={{
  display: 'flex',
  alignItems: 'flex-start',
  gap: '14px'
}}>
      <span style={{
  fontSize: '22px',
  lineHeight: '1',
  flexShrink: 0
}}>
        {icon}
      </span>
      <div>
        {title && <div style={{
  fontSize: '16px',
  fontWeight: 600,
  color: 'var(--recommended-title)',
  marginBottom: '6px'
}}>
            {title}
          </div>}
        <div style={{
  fontSize: '14px',
  lineHeight: 1.65
}}>
          {children}
        </div>
      </div>
    </div>
  </div>;

export const RememberCallout = ({title, children, icon = "🪢"}) => <div style={{
  backgroundColor: 'var(--recommended-bg)',
  borderLeft: '4px solid #f63b92',
  borderRadius: '10px',
  padding: '18px 22px',
  marginBottom: '20px',
  boxShadow: '1px 1px 3px rgba(0,0,0,0.06)'
}}>
    <div style={{
  display: 'flex',
  alignItems: 'flex-start',
  gap: '14px'
}}>
      <span style={{
  fontSize: '22px',
  lineHeight: '1',
  flexShrink: 0
}}>
        {icon}
      </span>
      <div>
        {title && <div style={{
  fontSize: '16px',
  fontWeight: 600,
  color: 'var(--recommended-title)',
  marginBottom: '6px'
}}>
            {title}
          </div>}
        <div style={{
  fontSize: '14px',
  lineHeight: 1.65
}}>
          {children}
        </div>
      </div>
    </div>
  </div>;

This page explains **how Accounting integrations can be deployed**, including options for different ERP/accounting systems and integration partners. It highlights **OAuth 2.0 authorisation**, data flow, examples, and best practices for stable, secure operation.

## Overview

Accounting integrations transfer **accounting-ready data** from Pleo to external systems using **API-triggered export jobs**. Deployment depends on your ERP/accounting system capabilities and whether the integration is partner-hosted or run in-house.

All deployments rely on **OAuth 2.0** for secure authorisation when accessing Pleo data.

## Deployment Options

### Module / On-Premises

Some ERP/accounting systems allow the integration to run **within their own environment**. Examples include **NetSuite** and **SAP B1**.

**Benefits include:**

* Higher stability and tighter connectivity
* Ability to leverage the ERP/AS platform tech stack for configuration
* Typically requires a single **OAuth 2.0 authorisation step** to access Pleo data

**Notes:**

* Not all ERP/accounting systems support this deployment
* May require additional licensing, platform setup, or technical approval
* Suitable for organisations that prefer in-house control over integration execution
* Check with your partner manager or customer success team to confirm availability and any additional costs

### Cloud Platform

The integration runs on a **cloud platform or partner-hosted middleware**, such as integrations deployed by **Pandium**.

**Key workflow:**

1. A bookkeeper or automation in the Pleo Web App initiates an **export job**.
2. Immutable, accounting-ready **JSON records** are produced.
3. Your integration consumes the records programmatically via API, authenticated using **OAuth 2.0**.

**Benefits include:**

* Centralised management by partners or middleware providers
* Works well for complex multi-system workflows
* Enables near real-time responsiveness using **webhook notifications** or polling

**Notes:**

* Integration logic can be decoupled from the ERP/AS platform
* Webhooks notify the integration of new export jobs (`v1.export.job-created`) or master data changes (`v1.vendor.created`)
* Ensure partner agreements are in place for any partner-hosted deployments

## Considerations for Both Deployment Types

* Ensure OAuth 2.0 tokens are stored and refreshed securely
* Follow API rate limits and error handling guidelines
* Traceability and auditing of export jobs are critical
* Test in **Staging** before promoting to **Production**

<NoteCallout title="Event-Driven Notifications">
  For more on webhooks and event-driven notifications, see [Event-Driven Notifications (Webhooks)](/reference/webhooks/overview-webhooks).
</NoteCallout>

***

## What Comes Next?

* Review your ERP/Accounting system capabilities and determine which deployment approach fits best
* Familiarise yourself with [Accounting Integrations](/docs/current/getting-started/accounting-integrations-overview) and the [**Exports Lifecycle**](/docs/current/platform/exports/lifecycle)
* Ensure team members responsible for the integration understand [OAuth 2.0](/docs/current/integration-design/auth/oauth/integration-design-auth-oauth-overview) flows and token handling
* Set up a [**Staging Environment**](/docs/current/guides/environment-access/staging-oauth-workflow) for testing before Production deployment

***

## Related Reading

* [Export Integration Workflow Guide](/docs/current/guides/export-integration-workflow-guide)
* [How To Connect Pleo to a Pre-Built ERP or Accounting System](/docs/current/how-tos/how-to-connect-pleo-to-pre-built-as-systems)

***