Skip to main content
This page provides a high-level overview of custom Accounting Integrations between Pleo and external ERP or Accounting 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.
If your system is supported out of the box, you may prefer a pre-built integration.

​
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 + Tax Code API
Level 4✅✅✅✅Export API + Tags API + Tax Code API + Vendors API + Accounts API
How to choose a level:
  • Level 1
    Enables exporting expenses and attachments. Suitable for basic accounting workflows.
  • Level 2 (recommended minimum)
    Adds tags to support automated workflows and accounting dimensions.
  • Level 3
    Includes tax codes and categories, enabling more accurate and compliant bookkeeping.
  • Level 4
    The full integration model, supporting master data synchronisation and highly automated accounting flows.

​
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 This Page Does Not Cover

This page intentionally does not describe:
  • Export job sequencing
  • Data mapping rules
  • Bookkeeping behaviour
  • Error handling logic
These are covered in the dedicated implementation guides.

​
What Comes Next?

Depending on what you are building, continue with: