Setup, permissions and settings

Enable invoice e-Invoice email attachments

Attach rendered XML/JSON to the normal invoice email immediately before sending.

Audience: CRM staffPermission: AdministratorModule v1.0.0
Exact navigationAdmin Area → Setup → Settings → Finance → e-Invoice
Before you begin
  • 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 covers

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.

Exact step-by-step process

  1. Select a valid default invoice template.
  2. Set Send e-Invoice as invoice email attachment to Yes.
  3. Save settings.
  4. Send a test invoice through the normal CRM email action.
  5. Verify the attachment name, MIME type and content.

Fields, choices and supported possibilities

Action scopeAttach rendered XML/JSON to the normal invoice email immediately before sending.
Module version1.0.0
NavigationAdmin Area → Setup → Settings → Finance → e-Invoice
EvidenceConfirm the stored record, status, output, email, event or log produced by the code path.

Code-backed validations and workflow rules

  • The hook runs before_invoice_sent_to_client.
  • The filename uses the formatted invoice number with slashes replaced by hyphens.

Expected result and verification

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