Template editor and validation

Create an e-Invoice template

Follow this guide to add a new module template stored in the core templates table with type einvoice. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.

Audience: CRM staffPermission: AdministratorModule v1.0.0
Jump to steps
Where to goAdmin Area → Setup → Settings → Finance → e-Invoice → New Template
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 you’ll accomplish

Add a new module template stored in the core templates table with type einvoice. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.

Follow these steps

  1. Select New Template.
  2. Enter Name.
  3. Select XML or JSON.
  4. Enter valid Mustache content.
  5. Select Validate.
  6. Resolve all errors.
  7. Save.

Fields and options to review

Action scopeAdd a new module template stored in the core templates table with type einvoice.
Module version1.0.0
NavigationAdmin Area → Setup → Settings → Finance → e-Invoice → New Template
EvidenceVerify the stored record, status, output, email, event or log produced by the code path.

Rules the system enforces

  • Successful create stores addedfrom, type einvoice, content and content_type.

How to confirm 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.