Bulk export and operational limitations

Bulk export invoice e-Invoices

Follow this guide to create a ZIP of eligible invoices rendered with the default invoice template. 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.

Audience: CRM staffPermission: e-Invoice: Bulk ExportModule v1.0.0
Jump to steps
Where to goAdmin Area → Utilities → Bulk Export → Export Type: Invoice
Before you start
  • Use an authorised account and confirm the source CRM record or setting is correct.
  • Follow the exact route shown above; do not force database values to imitate a completed action.

What you’ll accomplish

Create a ZIP of eligible invoices rendered with the default invoice template. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.

Follow these steps

  1. Select Invoice.
  2. Select a status.
  3. Submit.
  4. Download the generated ZIP.
  5. Check the year folders and each output file.

Fields and options to review

Action scopeCreate a ZIP of eligible invoices rendered with the default invoice template.
Module version1.0.0
NavigationAdmin Area → Utilities → Bulk Export → Export Type: Invoice
EvidenceVerify the stored record, status, output, email, event or log produced by the code path.

Rules the system enforces

  • The exporter queries invoices, loads each through invoices_model and renders the default invoice template.
  • If staff lacks standard View invoices, the normal staff invoice where-SQL is applied.

How to confirm it worked

  • The requested record, output or setting is created or updated through the supported module flow.
  • Any related status, count, email, audit/event, PDF/file or queue evidence agrees with the source action.
  • An error message is investigated rather than bypassed.

Security, privacy and operational checks

  • Apply least privilege and verify the correct customer, lead, sales document or recipient before processing.
  • Protect public tokens, recipient data, IP/browser evidence, templates and exported files according to organisational policy.
  • Test configuration changes with controlled records before production-wide use.
  • Retain or delete evidence only under an authorised retention process.