Skip to main content
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
For more on webhooks and event-driven notifications, see Event-Driven Notifications (Webhooks).

​
What Comes Next?

  • Review your ERP/Accounting system capabilities and determine which deployment approach fits best
  • Familiarise yourself with Accounting Integrations and the integration lifecycle
  • Ensure team members responsible for the integration understand OAuth 2.0 flows and token handling
  • Set up a Staging environment for testing before Production deployment