Enable invoice e-Invoice email attachments
Attach rendered XML/JSON to the normal invoice email immediately before sending. 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.
Where to goAdmin Area → Setup → Settings → Finance → e-Invoice
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
Attach rendered XML/JSON to the normal invoice email immediately before sending. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.
Follow these steps
- Select a valid default invoice template.
- Set Send e-Invoice as invoice email attachment to Yes.
- Save settings.
- Send a test invoice through the normal CRM email action.
- Check the attachment name, MIME type and content.
Fields and options to review
Action scopeAttach rendered XML/JSON to the normal invoice email immediately before sending.
Module version1.0.0
NavigationAdmin Area → Setup → Settings → Finance → e-Invoice
EvidenceVerify the stored record, status, output, email, event or log produced by the code path.
Rules the system enforces
- The hook runs before_invoice_sent_to_client.
- The filename uses the formatted invoice number with slashes replaced by hyphens.
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.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.