Placeholders and rendering

Use credit-note e-Invoice placeholders

Map all supplied credit-note identity, status, totals, currency and address fields. 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 → Credit Note placeholders
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

Map all supplied credit-note identity, status, totals, currency and address fields. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.

Follow these steps

  1. Insert credit-note ID, number, date and status.
  2. Insert subtotal, tax, adjustment, discount and total.
  3. Insert currency code.
  4. Insert billing/shipping address and country values.
  5. Validate with representative credit notes.

Fields and options to review

Credit-note placeholdersCREDIT_NOTE_ID, CREDIT_NOTE_NUMBER, CREDIT_NOTE_DATE, CREDIT_NOTE_STATUS, CREDIT_NOTE_SUBTOTAL, CREDIT_NOTE_TOTAL_TAX, CREDIT_NOTE_ADJUSTMENT, CREDIT_NOTE_DISCOUNT_TOTAL, CREDIT_NOTE_TOTAL, CURRENCY_CODE and all supplied billing/shipping fields.

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.