Pleo
Card spend, out-of-pocket expenses, and receipts from Pleo — coded, VAT-aware, and posted to your ledger without a manual export.
Overview
European card spend arrives with VAT attached, a receipt that may or may not be there yet, and a category someone still has to translate into a GL account. Pleo handles the spending. DualEntry handles the accounting. The connector in between does the translation.
Every Pleo card transaction, reversal, and out-of-pocket expense flows into DualEntry already coded — merchant, amount, currency, cardholder, VAT, and cost center intact. Purchases debit the mapped expense account and credit your Pleo card-payable account. Reversals post against the same accounts. Receipt status and the original Pleo transaction ID ride along on every entry, so the audit trail points straight back to the source.
The flow is inbound only. Pleo stays the source of truth for spend, DualEntry stays the source of truth for the books, and DualEntry never pushes your chart of accounts or journal entries back into Pleo.
This integration is delivered as a managed connector hosted by APIWorx rather than a tile inside DualEntry. Authorization and mapping are handled in the APIWorx portal.
Card transactions (purchases)
Card transaction reversals
Out-of-pocket employee expenses
Receipt status
Expense categories (mapped to GL accounts)
Cost centers and teams
VAT amounts and rates
Cardholders and employees
Data synced
The integration syncs the following data types:
Key Features
- Coded on arrival
Each Pleo expense category maps once to a DualEntry GL account and reuses that mapping on every transaction. Cost centers, departments, and projects come through as dimensions. - VAT carried through
The VAT amount and rate travel with the transaction to the matching DualEntry tax treatment, so European spend lands with tax already broken out. - A receipt policy you choose
Post and flag transactions missing a receipt, or hold them until a receipt is attached in Pleo. Nothing reaches the ledger without documentation unless you want it to. - Reversals and edits follow through
Recategorizations, edits, and reversals made in Pleo post as corresponding adjustments in DualEntry instead of leaving the original entry wrong. - Audit trail back to source
Receipt-attached status and the Pleo transaction ID are written onto every posted entry. - Near real time or batched
Webhooks drive near-real-time syncing where Pleo exposes them; a configurable batch schedule covers everything else. - Nothing fails silently
Unmapped categories route to a default holding account and are flagged. Currency and tax mismatches raise an exception rather than posting misaligned figures. Failed postings retry automatically and are logged with the Pleo transaction ID. - Managed connector
Delivered and hosted by APIWorx. Authorize Pleo and DualEntry once from the APIWorx portal; no connector tile is required inside DualEntry.
FAQ
Yes. Pleo is delivered as a managed connector built and hosted by APIWorx rather than as a native tile inside DualEntry. You authorize your Pleo organization and your DualEntry company once from the APIWorx portal, and mapping is maintained there. Both authorizations require admin access.
It removes the manual step between company spend and the general ledger. Card transactions, reversals, and out-of-pocket expenses post automatically with the GL account, cost center, VAT, and cardholder already applied — and the Pleo transaction ID and receipt status stay attached for audit. Finance stops re-keying card statements and closes faster.
No. The integration is one-way: data flows from Pleo into DualEntry. DualEntry does not push your chart of accounts or journal entries back to Pleo. Pleo remains the source of truth for spend, and DualEntry remains the source of truth for the books.
That is a policy you choose during setup. In post-and-flag mode the transaction posts to DualEntry and is flagged as missing a receipt. In hold-pending-receipt mode it is held and does not post until a receipt is attached in Pleo — which means nothing reaches the ledger without documentation, but held spend is also absent from period reports until the receipt arrives. Choose hold-pending-receipt only if your close process can tolerate that.
Both event-driven and scheduled syncing are supported. Webhooks drive near-real-time syncs where Pleo exposes them, and a configurable batch schedule covers everything else — for example a daily export of the prior day's settled transactions. You select the mode during setup.
Nothing fails silently. Unmapped expense categories route to a default holding account and are flagged for coding. Currency or VAT mismatches raise an exception rather than posting misaligned figures. Failed postings are logged with the Pleo transaction ID and retried automatically per the configured retry policy, with persistent failures flagged for manual review. Connector logs are retained for troubleshooting and audit.
.avif)