Template editor and validation

Edit an e-Invoice template

Follow this guide to update an existing template after validating the changed content. 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 → Templates → Edit
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

Update an existing template after validating the changed content. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.

Follow these steps

  1. Go to the template.
  2. Change name, type or content.
  3. Select Validate.
  4. Save the validated update.
  5. Retest invoice/credit-note output using this template.

Fields and options to review

Action scopeUpdate an existing template after validating the changed content.
Module version1.0.0
NavigationAdmin Area → Setup → Settings → Finance → e-Invoice → Templates → Edit
EvidenceVerify the stored record, status, output, email, event or log produced by the code path.

Rules the system enforces

  • Opening an existing template returns 404 if it is missing or its type is not einvoice.

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.