Placeholders and rendering

Use e-Invoice line-item and tax placeholders

Render repeating items and their taxes through Mustache sections. 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 → Line Items / Taxes
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

Render repeating items and their taxes through Mustache sections. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.

Follow these steps

  1. Go to the line-item section using the structure shown by the template reference.
  2. Insert item ID/order/name/description/quantity/unit/unit price/total.
  3. Inside each item, iterate taxes and insert name/rate/total.
  4. Close each Mustache section correctly.
  5. Validate with documents containing multiple items and taxes.

Fields and options to review

Item fieldsLINE_ITEM_ID, LINE_ITEM_ORDER, LINE_ITEM_NAME, LINE_ITEM_DESCRIPTION, LINE_ITEM_QUANTITY_NUMBER, LINE_ITEM_QUANTITY_UNIT, LINE_ITEM_UNIT_PRICE, LINE_ITEM_TOTAL.
Tax fieldsTAX_NAME, TAX_RATE, TAX_TOTAL.

Rules the system enforces

  • Only values and transitions exposed by the supplied module code are supported.
  • Server-side validation remains authoritative even when browser controls appear to accept a value.

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.