> ## Documentation Index
> Fetch the complete documentation index at: https://usepike.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Pleo

> How to connect Pleo to Pike and import card and out-of-pocket expenses onto projects in real time.

The Pleo integration imports Pleo card and out-of-pocket expenses into Pike in real time and puts each one on its project through a Pleo tag group that Pike keeps filled with active project names.

## Connect Pleo

1. Go to **Workspace settings** → **Integrations** → **Pleo**.
2. Click **Add integration**.
3. Authorize Pike in the Pleo popup.

Only workspace admins can connect or disconnect Pleo.

## Import data

On the integration page, click **Import data**. The stepper runs entities in dependency order, so Pike reads expense categories before the expenses that use them. It skips entities whose **Read** toggle is off, names them, and links to sync settings.

## What syncs

| Pleo | Pike expense |
| - | - |
| Amount and currency | Amount and currency |
| Date | Date |
| Merchant | Merchant |
| Pleo category | Expense category |
| Receipt | Receipt link |
| Note | Note |
| Tag in the "Pike project" tag group | Project |

### Projects

Pike creates a Pleo tag group named "Pike project" and keeps it filled with active project names. The tag chosen in Pleo sets the project in Pike.

### Source of truth

Once a record is linked, Pleo owns the linked fields and Pike reads them back. Pike-only fields, such as project links, internal notes, allocations, and cost profiles, stay in Pike and are never overwritten.

### Schedule

Changes in Pleo reach Pike in real time through Pleo webhooks. **Import data** and **Refresh** always run on demand.

## Sync settings

While Pleo is connected, the **What syncs with Pleo** card sits under the top button row on the integration page. Each entity has a **Read** toggle (Pleo to Pike). Toggles save immediately.

| Entity | Read | Send |
| - | - | - |
| Expenses | Yes | Not available |

New connections start with **Read** on for everything.

## Synced records

Every synced record shows the Pleo marker, "Last synced {time}" or "Not synced yet", and a **Refresh** action. **Refresh** shows only while **Read** is on for that entity.

### Sync issues

Records that fail to sync appear in the **Sync issues** list on the integration page, with the record, the reason, and a **Retry** action. The integration never deletes Pike data on its own. A record removed in Pleo is marked "Removed in Pleo" in Pike, never deleted.

## Disconnect

Disconnecting Pleo stops syncing and keeps all imported data. Linked records keep their history.

## Permissions

Synced data respects Pike roles and private projects. A private project's tasks never sync out to anyone who cannot see the project in Pike.

## Limits

* The sync is one way, from Pleo to Pike.
* Accounting export stays in Pleo.

## Related

* [Pleo integration overview](https://usepike.com/integrations/pleo): What syncs, how agencies use it, and FAQs.
* [Expensify](https://usepike.com/docs/integrations/expensify.md): Expenses from approved reports every hour.
* [Log → Expenses](https://usepike.com/docs/sidebar/log.md#expenses): Review, assign, and approve expenses.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.