Customer work, connected.

Help & supportMyAccount
Placeholders and rendering

Understand e-Invoice render filters

Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.

This guide explains that where authorised extensions can modify data and final XML/JSON.

Audience: Developers and system integratorsPermission: Staff loginModule v1.0.0
Jump to steps
Where to goCode-backed reference → e-Invoice data and handler filters
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 this guide helps you do

Know where authorised extensions can modify data and final XML/JSON. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.

Follow these steps

  1. Use einvoice_template_data to alter the render data before Mustache.
  2. Use document/item placeholder filters for scoped values.
  3. Use einvoice_rendered_xml or einvoice_rendered_json for final output.
  4. Test all view, download, email and bulk paths.

Fields and options

Action scopeKnow where authorised extensions can modify data and final XML/JSON.
Module version1.0.0
NavigationCode-backed reference → e-Invoice data and handler filters
EvidenceVerify the stored record, status, output, email, event or log produced by the code path.

Rules and limits

  • before_get_einvoice_* filters are also applied by the data classes.

Check 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.

Search the platform, integrations and practical Help Centre guides.

Press Esc to close.Browse every page