Configure EmaraTax Emirate or subdivision
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Required seller country subdivision/emirate.
Where to goAdmin Area → EmaraTax eInvoicing → Settings → Emirate or subdivision
Before you start
- Use the exact navigation above and confirm the intended record, tenant, customer, property, document or date range.
- Verify module activation and the stated permission instead of using another staff member’s account.
- For public, email, provider, finance, signature or destructive actions, use a controlled test record before production use.
What this guide helps you do
Required seller country subdivision/emirate. These instructions follow the supplied module’s live menus, controller actions, form fields, model validation and downstream effects.
Follow these steps
- Sign in to the staff admin area and open Admin Area → EmaraTax eInvoicing → Settings → Emirate or subdivision.
- Verify that your account meets the access rule: Administrator.
- Go to the required record or configuration and review its current values before making a change.
- Complete the displayed fields or action exactly as described in this guide.
- Save, submit, download or confirm the action using the button presented by the module.
- Reopen the source record and verify the expected status, output, notification, file or linked record.
Fields and options
FieldEmirate or subdivision
Stored optionemaratax_einvoicing_seller_country_subdivision
PurposeRequired seller country subdivision/emirate.
Category/help-centre/category/emaratax-einvoicing/
Topic/help-centre/topic/emaratax-einvoicing-seller-settings/
Rules and limits
- The controller saves the emaratax_einvoicing_seller_country_subdivision option exactly from the submitted settings form.
- Save the settings page, reopen it and validate a controlled document to confirm the value is used.
Check it worked
- The configure emaratax emirate or subdivision workflow completes without bypassing the module’s permission and validation checks.
- The saved value, generated file, status, notification or linked CRM record is visible from the same workspace.
- Any validation message remains visible until the source data or setting is corrected.
Security, privacy and operational checks
- Use least-privilege staff access and do not use another person’s account to reach a hidden action.
- Check personal, financial, identity and compliance data before sending, exporting or exposing it through a public link.
- Test configuration, email, public forms, accounting effects and provider connections with controlled records before production-wide use.
Related guides
Was this guide useful?Your response is stored only in this browser.