Understand e-Invoice render filters
Know where authorised extensions can modify data and final XML/JSON.
Exact navigationCode-backed reference → e-Invoice data and handler filters
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
Know where authorised extensions can modify data and final XML/JSON. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.
Exact step-by-step process
- Use einvoice_template_data to alter the render data before Mustache.
- Use document/item placeholder filters for scoped values.
- Use einvoice_rendered_xml or einvoice_rendered_json for final output.
- Test all view, download, email and bulk paths.
Fields, choices and supported possibilities
Action scopeKnow where authorised extensions can modify data and final XML/JSON.
Module version1.0.0
NavigationCode-backed reference → e-Invoice data and handler filters
EvidenceConfirm the stored record, status, output, email, event or log produced by the code path.
Code-backed validations and workflow rules
- before_get_einvoice_* filters are also applied by the data classes.
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.