Configure EmaraTax Payment means type code
Payment means code; default 30.
Exact navigationAdmin Area → EmaraTax eInvoicing → Settings → Payment means type code
Before you begin
- Use the exact navigation above and confirm the intended record, tenant, customer, property, document or date range.
- Confirm 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 covers
Payment means code; default 30. These instructions follow the supplied module’s live menus, controller actions, form fields, model validation and downstream effects.
Exact step-by-step process
- Sign in to the staff admin area and open Admin Area → EmaraTax eInvoicing → Settings → Payment means type code.
- Confirm that your account meets the access rule: Administrator.
- Open 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, choices and supported possibilities
FieldPayment means type code
Stored optionemaratax_einvoicing_payment_means_type_code
PurposePayment means code; default 30.
Category/help-centre/category/emaratax-einvoicing/
Topic/help-centre/topic/emaratax-einvoicing-seller-settings/
Code-backed validations and workflow rules
- The controller saves the emaratax_einvoicing_payment_means_type_code option exactly from the submitted settings form.
- Save the settings page, reopen it and validate a controlled document to confirm the value is used.
Expected result and verification
- The configure emaratax payment means type code 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.
- Review 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.