Review excluded or replaced fields in the Payments export
No custom-field join is implemented for payments.
Where to goAdmin Area → Utilities → CSV Export → Payments → Download
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
No custom-field join is implemented for payments 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 → Utilities → CSV Export → Payments → Download.
- 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
Review excluded or replaced fieldsNo custom-field join is implemented for payments
Category/help-centre/category/csv-export-manager/
Topic/help-centre/topic/csv-export-manager-payments/
Rules and limits
- No custom-field join is implemented for payments
- Reconcile a controlled row against the source CRM record before distributing the export.
Check it worked
- The review excluded or replaced fields in the payments export 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.