Validate an XML e-Invoice template
Pass Mustache rendering and DOMDocument XML parsing before save.
Exact navigationAdmin Area → Setup → Settings → Finance → e-Invoice → Template → Validate
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
Pass Mustache rendering and DOMDocument XML parsing before save. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.
Exact step-by-step process
- Choose XML.
- Enter one well-formed XML document using supported placeholders.
- Select Validate.
- Correct the first reported XML parser error.
- Save after success.
Fields, choices and supported possibilities
Action scopePass Mustache rendering and DOMDocument XML parsing before save.
Module version1.0.0
NavigationAdmin Area → Setup → Settings → Finance → e-Invoice → Template → Validate
EvidenceConfirm the stored record, status, output, email, event or log produced by the code path.
Code-backed validations and workflow rules
- Validation first renders Mustache with empty data.
- XML parsing uses DOMDocument with internal errors and reports the first available error.
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.