Skip to main content
This page provides a high-level overview of custom Accounting Integrations between Pleo and external Accounting Systems (AS) or Enterprise Resource Planning (ERP) systems. It explains what accounting integrations are, which integration levels are available, and where to go next depending on your implementation needs.

​
What Is an Accounting Integration?

An Accounting Integration allows an ERP or Accounting System to receive accounting-ready data from Pleo using Pleo APIs. These integrations are typically used when:
  • No pre-built integration exists
  • Custom bookkeeping logic is required
  • Advanced automation or synchronisation is needed
  • The ERP system requires a bespoke deployment model
Accounting Integrations are export-driven and focus on moving expenses, attachments, and related accounting data from Pleo into an external system in a predictable and auditable way.

​
Integration Levels

Accounting Integrations can be implemented at different levels, depending on which APIs are used and how much automation is required.
LevelExportTagsCategoriesVendorsCorresponding APIs
Level 1✅Export API
Level 2✅✅Export API + Tags API
Level 3✅✅✅Export API + Tags API + Accounts API + Tax Code API
Level 4✅✅✅✅Export API + Tags API + Accounts API + Tax Code API + Vendors API
How to choose a level:
  • Level 1
    Enables exporting expenses and attachments. Suitable for basic accounting workflows.
  • Level 2 (recommended minimum)
    Adds Tags Sync, which syncs Accounting Dimensions from the Accounting System into Pleo as Tags. Users assign tags when they submit an expense; bookkeepers can assign or update them further before export.
  • Level 3
    Adds Chart of Accounts Sync and Tax Code Sync. Chart of Accounts are synced from the Accounting System into Pleo and mapped to expense categories; users assign a category when they submit an expense and bookkeepers can assign or update it before export. Accounts can optionally carry a taxCodeExternalId as a reference to a tax code in the Accounting System. Tax codes are synced separately via the Tax Code API.
  • Level 4
    Adds Vendor Sync, which is bi-directional. Vendors are synced from the Accounting System into Pleo. The integration can also listen for new vendors via the v1.vendor.created webhook and update the Accounting System with the details.

​
Deployment Overview

Accounting Integrations can be deployed in different ways depending on the target ERP or Accounting System. At a high level, integrations are deployed either:
  • As a module / on-premises, hosted inside the ERP environment
  • On a cloud platform, hosted externally and connected through OAuth 2.0
Each deployment model affects how users authenticate, where configuration lives, and how authorisation is handled.

​
Authentication & Authorisation

All Accounting Integrations use OAuth 2.0 to securely access Pleo APIs.
  • Users authorise access from within Pleo
  • Tokens are issued and managed by the integration
  • Scopes determine which APIs and data can be accessed
Authentication behaviour varies slightly depending on deployment model, but OAuth 2.0 remains the single authorisation mechanism.

​
What Comes Next?

Start by getting access to the staging environment and setting up authentication, then build up through the integration levels in order. 1. Get access 2. Level 1: Export Integration 3. Level 2: Tags Sync 4. Level 3: Chart of Accounts and Tax Code Sync 5. Level 4: Vendor Sync