Default mapping and payload
New ISV workspaces receive a ready UAE mapping and schema-complete payload automatically. This removes manual mapping setup from the normal onboarding path.
Generated workspace resources
| Resource | Where to find it | Behavior |
|---|---|---|
| Default GETS Mapping | Integration engine | Protected system mapping for UAE invoicing |
| Default UAE GETS Payload | Payload Manager | Complete payload with every registered UAE tax-invoice field |
| Automatically assign new Sources | Default mapping Source panel | Enabled by default for newly created ISV workspaces |
The default is resolved by workspace and environment. Creating additional mappings does not disable it.
Source assignment
When single, branch, or bulk onboarding creates a new Source, Complyance attempts to assign that Source to the designated default mapping.
Successful onboarding returns:
{
"readyForInvoicing": true,
"mappingReadiness": {
"status": "READY",
"templateId": "default-gets-WORKSPACE_ID"
}
}When action is required, readyForInvoicing is false and mappingReadiness.code is one of:
| Code | Meaning |
|---|---|
CONNECT_MAPPING_NOT_CONFIGURED | No designated default exists for the environment |
CONNECT_MAPPING_INELIGIBLE | The designated mapping is not ready for assignment |
CONNECT_MAPPING_CONFLICT | The Source conflicts with an existing mapping assignment |
CONNECT_MAPPING_LINK_FAILED | The mapping was found but Source assignment failed |
Automatic-assignment toggle
The toggle controls future onboarding only:
- On: newly created Sources are assigned automatically.
- Off: newly created Sources are onboarded without automatic assignment.
- Existing assignments are never removed by changing the toggle.
Protected fields and custom fields
Core, regional, and UAE fields in the system default are visible but read-only. You can add, edit, and remove custom fields without changing the protected seeded mappings.
The system default itself cannot be renamed, deleted, or have its generated country and payload replaced.
Create an editable mapping
Use Duplicate mapping when you need to change standard field mappings. The copy receives new workspace-scoped identifiers, remains separate from the default, and can be edited normally. The original default stays unchanged.
After validating the copy, explicitly select it as the designated default for the required environment. Existing Source assignments are not overwritten automatically.
Existing custom-mapping workspaces
Existing ISV workspaces that already use a custom designated mapping are preserved. Complyance does not replace their mapping, enable automatic assignment unexpectedly, or change existing Source links.