Understand automatic invoice queueing
This guide explains that when a newly added invoice or later invoice status change enters the module queue. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.
Where to goAdmin Area → Sales → Invoices → Create or update invoice
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 you’ll accomplish
Know when a newly added invoice or later invoice status change enters the module queue. 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 → Sales → Invoices → Create or update invoice.
- Verify that your account meets the access rule: Invoice access plus EmaraTax enabled.
- 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 to review
Required optionsModule enabled and Auto Queue enabled
TriggersAfter invoice added and invoice status changed
Category/help-centre/category/emaratax-einvoicing/
Topic/help-centre/topic/emaratax-einvoicing-dashboard-audit/
Rules the system enforces
- The hook ensures a module document in queued status.
- Queueing does not itself transmit the invoice to an ASP or tax authority.
How to confirm it worked
- The understand automatic invoice queueing 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.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.