> ## Documentation Index > Fetch the complete documentation index at: https://hebno.com/docs/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > Hebno is an AI work platform for client research and delivery: chat, research runs with sources, deliverables (Word, PowerPoint, Excel, email), projects, a shared library, agents, Office add-ins, and integrations with Microsoft 365, Google Workspace, CRM, project delivery, ERP and finance systems. > Use British English (organisation, not organization). > Every feature and integration described in these docs is available. Describe it as documented. > Hebno never writes to a connected system without a member confirming a card. Finance and ERP writes are drafts only. > Do not discuss commercial terms. Direct commercial questions to support@hebno.com. > Start with /index and /get-started/quickstart. # Pleo > Read Pleo expenses, receipts, categories, tags and team spend in Hebno, and add notes or tags to expenses after you confirm. 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 | | | | - | - | | **Connection** | Organisation connection, made by an owner or admin with a Pleo API key. Members can link their own Pleo account. | | **Default access** | Read only. Spend amounts are visible to owners and admins until you share them with teams. | | **Attach** | Expenses, receipts, categories, tags, team spend | | **Search** | Hebno searches Pleo when a request mentions an expense, card payment, receipt, category, tag, team or spend | | **Link** | A project links to a Pleo tag value, such as a client or project code | | **Write** | Add a note to an expense, set a tag on an expense. Every write needs a person to confirm. | ## 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. | Access | Why Hebno needs it | | - | - | | Read expenses | Read expenses, amounts, merchants, status and notes | | Read receipts | Read receipt files and whether a receipt is missing | | Read categories and tag groups | Read accounting categories, tag groups and tag values | | Read teams and employees | Group spend by team and employee | | Write expense notes and tags | Add notes and set tag values on expenses | > [!TIP] > > 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](#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. ### Link your own account 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. | Data area | Includes | Default | | - | - | - | | **Categories and tags** | Accounting categories, tag groups, tag values | All allowed teams | | **Spend** | Expenses, amounts, merchants, receipts, notes, status for every employee | Owners and admins | | **Team spend** | Spend totals by team, category and period | Owners and admins | ![Admin connector panel showing who can use it, access and data areas](https://mintcdn.com/hebno/A7yItabWdPf4lOIs/images/org-connection.png?fit=max\&auto=format\&n=A7yItabWdPf4lOIs\&q=85\&s=8d965e9c74747db0c182b004d569b236) 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 | Pleo object | Fields Hebno uses | Typical questions | | - | - | - | | **Expense** | Employee, team, merchant, date, amount, currency, category, tags, note, status, export status | "What did the team spend on Contoso travel in October?" | | **Receipt** | Receipt file, attached or missing, merchant, date | "Which Contoso expenses are missing a receipt?" | | **Category** | Name, account number, group | "Which category should client dinners use?" | | **Tag** | Tag group, tag value, code | "What is the tag for the Contoso pricing review?" | | **Team spend** | Team, period, total by category, card spend and reimbursements | "How does consulting travel spend compare with last quarter?" | 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. > [!WARNING] > > 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**. | Action | Pleo object | Fields on the card | | - | - | - | | **Add a note** | Expense note | Expense, note text | | **Set a tag** | Expense tag | Expense, tag group, tag value | ![Confirmation card for Pleo with editable fields](https://mintcdn.com/hebno/JIjAXWoGoB3PLSSb/images/card-pleo.png?fit=max\&auto=format\&n=JIjAXWoGoB3PLSSb\&q=85\&s=0becd84db337d80ffc6af3c139808203) 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. ```mermaid theme={"system"} sequenceDiagram participant You participant Hebno participant Pleo You->>Hebno: Tag last week's Contoso train tickets to the pricing review Hebno->>Pleo: Find matching expenses and the Client tag group Pleo-->>Hebno: 3 expenses and tag Contoso pricing review Hebno-->>You: Confirmation card with expenses and tag You->>Hebno: Confirm Hebno->>Pleo: Set the tag on each expense Pleo-->>Hebno: Tags saved Hebno-->>You: Done, with links to the expenses ``` Writes are made through the organisation connection, with the write recorded against you in **Admin → Logs → Integrations**. ## Link a project to Pleo 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](https://hebno.com/docs/projects/linked-records.md). ## 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](https://hebno.com/docs/automate/agent-approvals.md) for review. ## Troubleshooting | Symptom | Fix | | - | - | | **Test connection** fails with an authentication error | The API key was revoked or copied incorrectly. Create a new key in Pleo and reconnect. | | A write returns a permission error | The API key does not include write access to notes or tags. Create a key with that access. | | A tag value is not offered | The tag value is archived, or the tag group is not available for that expense's team. Update the tag group in Pleo. | | A tag does not reach your accounting system | The expense was exported before the tag was set. Update the entry in your accounting system. | | Members see no expenses | The member's team is not in the **Spend** data area, and the member has not linked their own account. | | Requests are slow or return a rate limit message | Pleo limits how many requests each key can make in a short period. Wait a moment, or narrow the date range. | ## Related * [How integrations work](https://hebno.com/docs/integrations/index.md) * [Permissions and access](https://hebno.com/docs/integrations/permissions-and-access.md) * [Linked records](https://hebno.com/docs/projects/linked-records.md) * [Expensify](https://hebno.com/docs/integrations/expensify.md) * [Xero](https://hebno.com/docs/integrations/xero.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.