Tags imply cost centres. So when you assign tags to an accounting entry, it helps in allocating the correct cost centre to an accounting entry. For example, an expense of the Flight category is recorded in Pleo. This specific accounting entry is assigned the Business Trip tag. Assignment of tags helps in assessment of cost incurred for specific reasons.
Important Terminologies
- Tag Group: Tag group is like a collection of tags. For example, a tag group is a Department and it includes Sales, Marketing, and IT. Each individual value is a tag; hence, Sales, Marketing, or IT is a tag indicating a specific department.
- Tag: Tags are actual cost allocations. For example, if Projects is a tag group, Project A and Project B are individual tags. To explain a tag, we use dimensions; these are like attributes of tags. For example, each project would have a project name and project code. Project name and Project code are important attributes of each tag.
- The value mentioned for each dimension is a Dimension Value. For example, project name of Project A is Open Banking and project code is 24689.
Characteristics of Tags Managed in Pleo
- Pleo assigns IDs to tag groups and tags for correct identification.
- Attributes of a tag (dimensions) represent column headings in a table, implying they are relevant for all tags of a tag group. And tags are like rows in a table that must contain the dimension values.
- If you are using an ERP/accounting system that supports the tags capability, then the integration would send requests to the Tags API endpoints to synchronise tag groups and tags between the ERP/accounting system and Pleo.
- You can either create new tags in Pleo or you can import tags from the ERP/accounting system that you have integrated with. In addition, you can also import tags from an excel spreadsheet, enabling customers to track the types and volumes of expenses recorded in Pleo based on the tags assignment.
- You can assign a maximum of five tags to an accounting entry. An accounting entry might have tags related to projects, office locations, internal company structure.
- A user can only see non-archived tag groups.
How are Tags Different from Accounts and Categories?
Tag Groups Object
Object | Type | Description |
---|---|---|
archived | boolean | The tag group is no longer used. |
code | string | External identifier of the Tag group / Dimension used for mapping to accounting system |
companyID | string | Unique identifier of the company the Tag Group belongs to |
createdAt | string | Creation date and time. Example: 2023-08-23T03:11:48.000Z |
id | string | Unique identifier of Tag Group (generated on creation) |
metadata | string | Place for API users to store flexible data. Example: {"externalExtraId":"f302f9ec-6c17-11ee-b962-0242ac120002"} |
name | string | Projects User readable name of Tag Group |
updatedAt | string | Date and time of the last update. Example: 2023-08-23T03:11:48.000Z |
Tags Object
Object | Type | Description |
---|---|---|
archived | boolean | This Tag is no longer used |
code | string | External identifier of the Tag |
createdAt | string | Creation date and time. Example: 2023-08-23T03:11:48.000Z |
groupId | string | Unique identifier of the Tag Group this Tag belongs to |
name | string | User readable name that is used for the possible value within a tag group on an expense Example: lunch allowance |
updatedAt | string | Date and time of the last update Example: 2023-08-23T03:11:48.000Z |