Skip to main content
This page describes when Tax Sync runs, how it is triggered, and the constraints integrations must respect when scheduling sync operations.

​
Sync Schedule

The integration is responsible for defining and owning the sync schedule. Pleo does not trigger syncs automatically. The recommended schedule is:
  • On connect: run an initial sync immediately after the integration is connected and authorised
  • Recurring: run a sync every 15 minutes
This ensures Pleo Tax Codes are populated from the outset and remain continuously up to date.

​
Ad Hoc Tax Sync (Optional)

If technically possible, integrations should support user-triggered sync. Ad hoc sync allows users to trigger a Tax Sync at any moment. This is useful when:
  • New tax codes have been added to the Accounting System and the bookkeeper wants them reflected in Pleo immediately.
  • A user suspects Tax Codes are out of date and wants to force a refresh.
Ad hoc sync follows the same reconciliation process as scheduled sync.

​
Pleo API Rate Limit

The integration should target a maximum of 500 requests per minute to avoid errors under load, even if the Pleo API rate limit is higher. Integrations should:
  • Monitor request volume during sync cycles.
  • Implement throttling if tax code volumes are high.
  • Avoid unnecessary repeated requests within a single sync cycle.

​
What Comes Next?