Implementation
- Tax Sync Workflow Guide: workflow context and sequencing
- How to Fetch and Match Tax Codes: API usage and step-by-step instructions
Tax Codes: Data Mapping
Map the following datapoints from AS tax codes to Pleo Tax Codes API fields.| Pleo Tax Codes API Field | AS Tax Code Datapoint |
|---|---|
code | The identifier of the tax code in the AS. Used for matching. |
name | Name of the tax code |
rate | Rate of the tax code as a decimal (for example: 0.20 for 20%) |
type: reverse | Use only for reverse taxes |
type: inclusive | Use for all other taxes |
archived: false | Use when creating new active Tax Codes or unarchiving existing Tax Codes |
archived: true | Use when archiving Tax Codes that no longer have a matching active tax code in the AS, or that were previously synced but have since been deleted, archived, or deactivated |
Matching Field
Tax Codes are matched to their AS counterparts using thecode field on both ends.
Matching is case insensitive. The code field is the stable identifier used to track a tax code across sync runs, even if its name or rate changes.
Tax Code Type Mapping
| AS Tax Code | Pleo type |
|---|---|
| Reverse tax | reverse |
| All other taxes | inclusive |
exclusive appears as a valid enum value in the API spec, it is not currently supported. Attempting to create a Tax Code with type: exclusive returns a 400 BAD_REQUEST error. Do not use this value.