Skip to main content
The Pleo integration makes company card spend available in client work. Ask what a team spent on a client last month, which expenses are missing a receipt, or how travel spend compares across teams, and Hebno answers from Pleo with each expense cited. When a request implies a change, such as tagging an expense to a client or adding a note for the bookkeeper, Hebno shows a confirmation card and writes to Pleo only after you confirm.

​
At a glance

​
Before you start

You need:
  • An owner or admin role in Hebno.
  • A Pleo user with the Owner or Admin role in your Pleo company, to create the API key.
  • A Pleo API key for Hebno. In Pleo, open Settings → Integrations → API keys, create a key named Hebno and choose the access below. Copy the key straight away, because Pleo shows it once.
  • Tag groups set up in Pleo under Settings → Tags if you want to tag expenses to clients or projects.

​
Permissions

Give the API key the narrowest access that covers what Hebno needs.
Leave write access off the key if you want a read-only connection. Pleo returns a permission error for any write the key does not allow.

​
Connect Pleo

1

Allow the integration

Open Admin → Connectors → Catalogue, find Pleo under Finance, and set it to Allow.
2

Connect the organisation

Select Connect, paste the API key and select Test connection. Hebno shows your Pleo company name and lists the areas the key can read and write.
3

Choose teams and data areas

Under Who can use it, choose All teams or pick teams. Under Data areas, choose what members can see. See Data areas.
4

Set access

Access is Read only by default. Choose Read and write to let members propose expense notes and tags.
The card shows Connected with the Pleo company name. Members can link their own Pleo account so they see their own expenses and notes are added in their name.
  1. In Hebno, open Settings → Connections, find Pleo and select Link your account.
  2. Enter the email address you use in Pleo and select Link. Hebno matches it to your Pleo employee record.
When your account is linked, you see your own expenses even if your team is not in the Spend data area, and notes you confirm show your name.

​
Data areas

Data areas control what members of the allowed teams can see through the organisation connection. They apply on top of the access on the API key.
Admin connector panel showing who can use it, access and data areas

An organisation connection with team access and data areas. Financial figures default to owners and admins.

To share client spend with delivery leads, open the Pleo card in Admin → Connectors, select Spend and add the teams that should see it.

​
What Hebno reads

Reads are live. Hebno queries Pleo when a request needs it, so amounts match what finance sees in Pleo. Only what a reply used is stored with the conversation as its sources.
Excerpts a reply uses, including expense amounts and merchants, become part of the conversation. Anyone you share the conversation with can read them.

​
What Hebno writes

Every write appears first as a confirmation card. You can change any field before you select Confirm.
Confirmation card for Pleo with editable fields

A Pleo change pending confirmation. Nothing is written until you confirm.

Hebno never changes amounts, categories or receipts, approves or rejects an expense, exports to accounting, issues or freezes cards, or starts reimbursements or top-ups. For an expense that is already exported, the entry in your accounting system does not change, so a tag set after export appears in Pleo only. Writes are made through the organisation connection, with the write recorded against you in Admin → Logs → Integrations. Linking marks which Pleo tag belongs to a project, so you can ask “what have we spent on this engagement?” without naming the tag.
  1. Open the project and select Brain.
  2. Under Linked records, select Link record, then Pleo.
  3. Choose the tag group, then select the tag value your team uses for the engagement, such as Contoso pricing review.
In chats tagged to the project, Hebno filters spend questions to the linked tag, and tag cards default to it. See Linked records.

​
Use Pleo in chat

  • Attach: open the + menu, choose Sources → Pleo, and pick an expense, a tag or a team’s spend. Or type / and choose Pleo.
  • Ask: name the client, tag, team or period in your request. For example:
    What did we spend on the Contoso pricing review in October 2026, and which expenses are missing a receipt?
    Compare travel spend by team for Q3 and Q4 so far.
    Add a note to Priya Nair’s 4 November hotel expense: client workshop in Leeds, rebillable to Contoso.
  • Research runs show a Checking Pleo step, with a chip for each expense or tag it read.
  • Agents can read Pleo on a schedule, for example a Friday list of expenses missing receipts. Writes an agent proposes appear in agent approvals for review.

​
Troubleshooting