# Pleo integration

Connect Pleo with an API key and import accounting entries with receipts into Expenses.

Connect **Pleo** so Cortena imports accounting entries and their receipts into **Expenses** for matching and your expense workflow.

**Who this is for:** Finance admins who use Pleo for cards and employee spend and want those entries in Cortena. This connection is import-only.

Pleo and expense management must be enabled for the workspace. If **Pleo** is not in the integrations list, ask Cortena to turn it on.

Related: [Expense workflow](https://help.cortena.ai/guides/workflows/expense-workflow) and [Spendesk integration](https://help.cortena.ai/guides/integrations/spendesk).

## 1. Create a Pleo API key

1. In Pleo, open **Settings → API keys** and create a standalone API key.
2. Grant **read** access to accounting entries. Cortena uses that access to sync.
3. Copy the key. You will paste it once. Cortena stores it encrypted and does not show it again.

If the key is organisation-wide, also copy the **company ID** (a UUID) for the company you want to sync.

## 2. Connect Pleo in Cortena

1. Open **Settings → Integrations → Expenses → Pleo**.
2. Paste the key into **Pleo API key**.
3. If you use an organisation-level key, fill in **Pleo company ID**. Leave it empty for a company key.
4. Under **Sync expenses from**, choose how far back the first sync should go. Set this before the first successful sync.
5. Save, then click **Sync now** (or wait for the scheduled sync).

| **Sync expenses from** | What is included |
| --- | --- |
| **From today** | Entries from today onward |
| **Current month (from the 1st)** | This calendar month |
| **Last month (from the 1st)** | From the 1st of last month |
| **Last 3 months (from the 1st)** | From the 1st of the month three months ago |
| **All entries** | No start window |

After the first successful sync, the window is locked. **Disconnect from Pleo** to choose a new start window, then connect again.

## 3. What Cortena imports

Sync pulls Pleo **accounting entries** and their receipt files into **Expenses**. That includes card purchases, out-of-pocket spend, bill invoices, mileage, and per diem when Pleo has an accounting entry for them.

Card purchases that are already completed in Pleo are marked **paid** in Cortena so bank matching does not treat them as still open.

A sync toast reports how many entries were processed and how many were skipped. **Last sync** on the settings page shows when the last run finished.

Already imported entries are not duplicated on later syncs.

## 4. What this connection does not do

- It does not write bookkeeping status back to Pleo.
- It does not push categories, tags, or cost centers into Pleo.
- It does not export from Cortena into Pleo.

Use Cortena for review, matching, and your accounting export. Keep Pleo as the source of the card and receipt.

## Quick reference

| Task | Where |
| --- | --- |
| Create the key | Pleo **Settings → API keys** (accounting entries, read) |
| Connect | **Settings → Integrations → Expenses → Pleo** |
| Limit the first import | **Sync expenses from** |
| Import now | **Sync now** |
| Change the start window later | **Disconnect from Pleo**, then connect again |