Use e-Invoice custom-field placeholders
Include supported custom fields added by the data helper.
Exact navigationAdmin Area → Setup → Settings → Finance → e-Invoice → Template
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
Include supported custom fields added by the data helper. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.
Exact step-by-step process
- Create/populate the relevant CRM custom fields.
- Review generated placeholder names in the template reference/data helper.
- Insert them in the template.
- Validate output against records with and without values.
Fields, choices and supported possibilities
Action scopeInclude supported custom fields added by the data helper.
Module version1.0.0
NavigationAdmin Area → Setup → Settings → Finance → e-Invoice → Template
EvidenceConfirm the stored record, status, output, email, event or log produced by the code path.
Code-backed validations and workflow rules
- The data classes add custom-field values for supported document/items through their shared helper.
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.