Pleo
Upload monthly Pleo exports to land card spend, supplier invoices, and wallet activity in SaaSFlow.
The Pleo integration imports your monthly spend from Pleo as a single ZIP/CSV export. It's a file-based integration — there's no OAuth flow.
What gets imported
Each row of the Pleo export becomes one transaction on the Pleo wallet account. SaaSFlow handles the seven row kinds Pleo emits:
| Row kind | What it is |
|---|---|
| Card Purchase | Card spend on the Pleo wallet. |
| Invoice | Supplier invoice (accrual side). |
| Invoice Payment | Payment of a supplier invoice; inherits VAT and categorization from the matching Invoice row. |
| Wallet Load | Top-up from your bank account; auto-linked to the matching bank transfer. |
| Cashback | Pleo cashback credits. |
| Pleo Invoice | Pleo's own service fees. |
| Reimbursement | Employee reimbursement claim. |
Connect
Add the integration
Settings → Integrations → Add integration. Pick Pleo. SaaSFlow creates the Pleo wallet account.
Upload the export
From the integration's detail page, click Upload Pleo export and select your monthly Pleo export (ZIP or CSV). You can select multiple months at once.
Pick a P&L mapping column
On the first upload, SaaSFlow asks which CSV column to use for P&L categorization. Chart of Accounts - Code is the typical choice. Optionally pick a label column (e.g. Chart of Accounts - Name) so the mapping picker shows readable names instead of bare codes.
Map values to categories
For every unique value of the chosen column, pick a SaaSFlow category. The mapping is saved, so future uploads only prompt you for new values.
Diffs are keyed by Pleo's stable Expense ID UUID. Re-uploading a month preserves categorizations, notes, and assignees you added by hand.
Vendors
Pleo's export has no merchant id, only the merchant text on each row. SaaSFlow turns that text into vendors so Pleo spend shows up in vendor reports and can carry vendor defaults:
- Invoice payments get a vendor named after the supplier record in Pleo.
- Card purchases get a vendor named after the cleaned merchant text on the card statement, including merchants that appear only once.
- Reimbursement payouts get a vendor per employee, named as on the payout. The claim rows behind a payout (out-of-pocket receipts, mileage, per diem) name no merchant that could be matched, so the employee is the counterparty.
- Per-charge ids and acquirer prefixes are stripped before matching, so
MSFT * E0300YP98IandMSFT * E0100YIXVMland on one vendor. A merchant whose text already matches an existing vendor by name or website is attached to that vendor instead of creating a second one.
Each vendor remembers the Pleo spellings it was matched from. If the same merchant still ends up as two vendors, merge them on the Vendors page; later uploads resolve both spellings to the merged vendor.
Defaults and service periods
The P&L mapping from your chosen column decides the category. A vendor's default categorization fills in for rows whose mapping value is empty in Pleo. For an employee vendor it categorizes payouts that arrive with the main export before the reimbursements export supplies the exact split; that upload then replaces the default. A vendor's default date rule applies to every row of that vendor, even when the mapping supplied the category. Pleo has no field for a service period, so this is where an annual license gets spread: set the vendor's date rule to 12 months from the transaction date and every charge from that vendor is recognised over the year.
Starting balance
If your first upload doesn't go back to the month the wallet was opened, the account is missing the balance that existed before your first imported export. Set it once:
- Open the Pleo wallet account in SaaSFlow.
- Click Set initial balance in the Transactions section.
- Look up the wallet balance in Pleo on the suggested date (the day before your earliest imported transaction), enter it, and confirm.
SaaSFlow books the amount as a single balance transaction that re-uploads never touch. To correct it later, pick Edit initial balance… from the account's ⋯ menu.
If you later upload a month older than the initial balance, the account warns you to update it: the balance now belongs to an earlier date.
Re-uploading
Uploading a month that was already imported replaces the previous import for that month. Re-uploads inherit your earlier mappings automatically.
To edit saved mappings later, open the integration and click Manage P&L mappings.
Disconnecting
Settings → Integrations → ⋯ → Remove. SaaSFlow offers to convert the Pleo wallet account into a regular account so its transaction history is preserved.