Understand e-Invoice output filenames and MIME types
Interpret the route-generated name and headers.
Where to goAdmin Area → invoice/credit note → e-Invoice → View/Download
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
Interpret the route-generated name and headers. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.
Follow these steps
- Generate XML and JSON test outputs.
- Verify invoice_{id}.xml/json or credit_note_{id}.xml/json for single-record output.
- Verify application/json for JSON and text/xml for XML.
Fields and options
Action scopeInterpret the route-generated name and headers.
Module version1.0.0
NavigationAdmin Area → invoice/credit note → e-Invoice → View/Download
EvidenceVerify the stored record, status, output, email, event or log produced by the code path.
Rules and limits
- 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.
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.