Understand e-Invoice bulk ZIP structure

This guide explains that the archive name, year subdirectories and generated file names. 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.

What you’ll accomplish

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

1. Go to the ZIP.
2. Verify files are grouped under a year derived from the sale record date when available.
3. Verify filenames use formatted sales numbers passed through slug_it plus the stored content_type extension.
4. Verify the archive name is slug(companyname)-{type}s.zip.

Fields and options to review

Rules the system enforces

• 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.

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.

Continue with related guidance