Export payments to CSV
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Follow this guide to create a payments CSV using the selected period and the module’s exact joins, exclusions and formatting.
Where to goAdmin Area → Utilities → CSV Export → Export Type → Payments
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
Create a payments CSV using the selected period and the module’s exact joins, exclusions and formatting. 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 → Export Type → Payments.
- 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
Date filter columninvoicepaymentrecords.daterecorded
IncludedPayment records joined to invoice, currency and payment mode
Excluded/changedNo custom-field join is implemented for payments
Derived valuesFormatted invoice number, base currency fallback and gateway display name
Category/help-centre/category/csv-export-manager/
Topic/help-centre/topic/csv-export-manager-payments/
Rules and limits
- The exporter filters invoicepaymentrecords.daterecorded when a period is selected.
- Rows are streamed in batches and headings are generated from the final field list.
Check it worked
- The export payments to csv 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.