Skip to main content
This section describes how to implement Tags Sync between an Accounting System and Pleo. Tags Sync maps Accounting Dimensions to Tag Groups and Dimension Values to Tags in Pleo. Synchronisation is one-way, from the Accounting System into Pleo. The integration is responsible for all sync orchestration, reconciliation, and API operations. The pages in this section cover the detailed implementation requirements for each step of the sync process. For a platform-level overview of Tags Sync, including system guarantees and responsibility model, see Platform Capabilities: Tags Sync.

​
Tags Sync Execution Model

Tags Sync is a deterministic reconciliation process executed by the integration. On each sync run, the integration:
  1. retrieves selected Dimensions and Dimension Values from the Accounting System
  2. retrieves the current state of Tag Groups and Tags from Pleo
  3. reconciles Pleo to match the Accounting System state
  4. applies the required create, update, unarchive, and archive operations via the Pleo API
Each sync run must be independent, repeatable, and produce a consistent end state.

​
High-Level Process

​
Sync Steps

Tags Sync runs in three steps. Step 1 runs once on first connection to configure which Dimensions to synchronise. Steps 2 and 3 run on a recurring schedule to keep Pleo aligned with the Accounting System.

​
Step 1: Select Dimensions

The integration retrieves active Dimensions from the Accounting System and selects which ones to synchronise. On first connection, Dimensions whose code matches an existing active Tag Group in Pleo are automatically pre-selected. The selection is stored in the integration’s configuration and used as input to every subsequent sync cycle. Up to 5 Dimensions may be selected at any time. If a selected Dimension becomes inactive in the Accounting System, it is automatically deselected and its corresponding Tag Group is archived in Pleo. For the full selection rules, auto-selection logic, and deselection behaviour, see Dimension Selection.

​
Step 2: Sync Tag Groups with Dimensions

The integration reconciles selected Accounting Dimensions with Tag Groups in Pleo.

​
Outcomes

After all selected Dimensions are processed, any remaining active Tag Groups that no longer have a matching selected Dimension are archived.

​
Step 3: Sync Tags with Dimension Values

For each synchronised Dimension–Tag Group pair, the integration reconciles Dimension Values with Tags.

​
Outcomes

​
Duplicate Handling

If multiple Tags share the same code:
  • retain a single Tag
  • archive duplicate Tags
  • ensure the retained Tag has the correct current name
After all Dimension Values are processed, any remaining active Tags that no longer have a matching Dimension Value are archived.

​
Matching Model

Tag Groups and Tags are each matched to their AS counterparts using the code field. For full matching rules, see Sync Tag Groups with Dimensions and Sync Tags with Dimension Values.

​
Execution Requirements

The integration is responsible for all sync scheduling and execution behaviour. For schedule, frequency, and rate limit details, see Tags Sync Periodicity and Scheduling.

​
Processing Principles

All implementations must follow these architectural principles.

​
Expected Outcome

After implementation:
  • Pleo accurately reflects selected Accounting Dimensions
  • Tag Groups and Tags remain stable across repeated sync runs
  • outdated entities are archived automatically
  • duplicate entities are eliminated through reconciliation
  • bookkeepers always work with current Tags aligned to the Accounting System

​
What Comes Next?

Each section describes the detailed implementation requirements for that stage of the sync process.