This API is intended for developer partners and third-party service providers whose users make purchases with Pleo cards. Accounting Enrichment is currently available to selected partners and customers. To get access, contact Pleo Support. Key Concepts
What is an Accounting Entry?
An accounting entry is Pleo’s representation of a spend transaction enriched with details such as receipts, tags, and notes.
What is the Receipt Inbox?
The Receipt Inbox is the spender’s inbox in the Pleo mobile app. Receipts that could not be matched to an accounting entry are placed there for the spender to manually match.
Authentication
Authentication uses Pleo’s OAuth flow with the accounting-entries:write scope.
You can authenticate as an organisation or a company. For organisations with a multi-entity setup, you must use a company-level token to ensure enrichment requests target the correct company’s accounting entries.
How It Works
The integration sends an enrichment request to Pleo containing transaction details and enrichment data. Pleo uses the transaction details to identify the matching accounting entry and enriches it with the provided receipt and, optionally, tags.
See the Enrichment Workflow Quick Guide to get started.
Request Parameters
Transaction Details
Transaction details are used by Pleo to identify the correct accounting entry. All details are passed as query parameters.
| Parameter | Required | Description |
|---|
amount | Yes | Transaction amount in minor units (e.g. cents) |
currency | Yes | ISO 4217 currency code |
card_last_four_digits | Yes | Last four digits of the Pleo card used |
merchant_name | Yes | Name of the merchant |
performed_at | No | Timestamp of transaction authorisation |
settled_at | No | Timestamp of settlement |
email | No | Email address of the Pleo user who made the purchase |
Provide at least one date parameter (performed_at or settled_at). The more details provided, the higher the likelihood of a successful match.
Enrichment Data
Enrichment data is passed in the request body.
| Field | Required | Description |
|---|
receipts | Yes | One or more Base64-encoded receipt files. Supported formats: PDF, PNG, JPEG, HEIC |
tags | No | List of Pleo Tag UUIDs. See Tags API |
Receipt Statuses
Pleo returns a receipt status with every enrichment response.
| Status | HTTP | Description |
|---|
UPLOADED | 201 | Match found; receipt attached to the accounting entry |
ACCEPTED | 202 | Request accepted; Pleo will retry matching asynchronously |
ADDED_TO_RECEIPT_INBOX | 200 | No match found; receipt stored in the Receipt Inbox |
UNRESOLVED | 404 | Request could not be processed; receipt was not attached to any accounting entry |
Supported Features
v2 supports:
- Multiple receipts per request
- Asynchronous matching via the
ACCEPTED status
