Understand e-Invoice bulk ZIP structure
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
This guide explains that the archive name, year subdirectories and generated file names.
Where to goAdmin Area → Utilities → Bulk Export → Download ZIP
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 this guide helps you do
Know the archive name, year subdirectories and generated file names. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.
Follow these steps
- Go to the ZIP.
- Verify files are grouped under a year derived from the sale record date when available.
- Verify filenames use formatted sales numbers passed through slug_it plus the stored content_type extension.
- Verify the archive name is slug(companyname)-{type}s.zip.
Fields and options
Action scopeKnow the archive name, year subdirectories and generated file names.
Module version1.0.0
NavigationAdmin Area → Utilities → Bulk Export → Download ZIP
EvidenceVerify the stored record, status, output, email, event or log produced by the code path.
Rules and limits
- Only values and transitions exposed by the supplied module code are supported.
- Server-side validation remains authoritative even when browser controls appear to accept a value.
Check 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.
Related guides
Was this guide useful?Your response is stored only in this browser.