e-Invoice module overview
Understand template creation, output, email attachment and bulk-export flows implemented in version 1.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
Understand template creation, output, email attachment and bulk-export flows implemented in version 1.0.0. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.
Exact step-by-step process
- Create and validate an XML or JSON e-Invoice template.
- Set the default invoice and/or credit-note template.
- Use the e-Invoice menu on a sales record to view/download output.
- Optionally enable email attachments.
- Grant Bulk Export and use Utilities → Bulk Export where appropriate.
Fields, choices and supported possibilities
Action scopeUnderstand template creation, output, email attachment and bulk-export flows implemented in version 1.0.0.
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
- 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.
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.