Britixo CRMBritixo CRMEnterprise Help Centre
Ctrl K
Placeholders and rendering

Use e-Invoice custom-field placeholders

Include supported custom fields added by the data helper. 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 → 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

Include supported custom fields added by the data helper. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.

Follow these steps

  1. Create/populate the relevant CRM custom fields.
  2. Check generated placeholder names in the template reference/data helper.
  3. Insert them in the template.
  4. Validate output against records with and without values.

Fields and options to review

Action scopeInclude supported custom fields added by the data helper.
Module version1.0.0
NavigationAdmin Area → Setup → Settings → Finance → e-Invoice → Template
EvidenceVerify the stored record, status, output, email, event or log produced by the code path.

Rules the system enforces

  • The data classes add custom-field values for supported document/items through their shared helper.

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.
e-Invoice module overviewUse e-Invoice customer and primary-contact placeholdersUnderstand e-Invoice render filtersUnderstand e-Invoice XML and JSON post-processingGenerate and export an e-invoiceSend an invoice to a customer