Understand e-Invoice output filenames and MIME types
Interpret the route-generated name and headers.
Exact navigationAdmin Area → invoice/credit note → e-Invoice → View/Download
Before you begin
- 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 covers
Interpret the route-generated name and headers. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.
Exact step-by-step process
- Generate XML and JSON test outputs.
- Confirm invoice_{id}.xml/json or credit_note_{id}.xml/json for single-record output.
- Confirm application/json for JSON and text/xml for XML.
Fields, choices and supported possibilities
Action scopeInterpret the route-generated name and headers.
Module version1.0.0
NavigationAdmin Area → invoice/credit note → e-Invoice → View/Download
EvidenceConfirm the stored record, status, output, email, event or log produced by the code path.
Code-backed validations and workflow rules
- The controller contains a TODO to use formatted sales numbers for single output; version 1.0.0 uses record type and ID.
- Download sends attachment/binary headers; View sends inline content disposition.
Expected result and verification
- 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.