Understand e-Invoice XML and JSON post-processing | Pixie CRM Help Centre Canonical: https://pixiecrm.com/help-centre/understand-e-invoice-xml-and-json-post-processing Publisher: Pixie Technologies LLC Placeholders and rendering Understand e-Invoice XML and JSON post-processing 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 the final transformations made after Mustache rendering. Audience: CRM staff; Permission: Staff login; Module v1.0.0; Where to goAutomatic e-Invoice rendering 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 the final transformations made after Mustache rendering. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow. Follow these steps - Validate the template. - Generate test output. - For XML, confirm a UTF-8 declaration is added when absent. - For JSON, confirm trailing commas immediately before } or ] are repeatedly removed. Fields and options Action scopeKnow the final transformations made after Mustache rendering. Module version1.0.0 NavigationAutomatic e-Invoice rendering EvidenceVerify the stored record, status, output, email, event or log produced by the code path. Rules and limits - Final output then passes through the format-specific rendered filter. 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. Related guides e-Invoice module overview (https://pixiecrm.com/help-centre/e-invoice-module-overview)Understand e-Invoice render filters (https://pixiecrm.com/help-centre/understand-e-invoice-render-filters)Understand e-Invoice render error output (https://pixiecrm.com/help-centre/understand-e-invoice-render-error-output)Generate and export an e-invoice (https://pixiecrm.com/help-centre/generate-and-export-an-e-invoice)Send an invoice to a customer (https://pixiecrm.com/help-centre/send-an-invoice-to-a-customer)