Status Tracking

E-Invoice status is stored directly on the invoice (and optionally on the credit memo) so you can track generation results and download the generated files.

Status Values

StatusDescriptionNext Steps
pendingWaiting for generationWill be processed by queue/cron
generatedSuccessfully createdDownload available
errorGeneration failedCheck error message
disabledE-invoicing skippedManual trigger available

Where You See It (Admin)

Invoice View

On Sales >Invoices > View, the extension adds an E-Invoice Information section that shows:

  • Status + error message (if any)
  • Format + file type information
  • Generated timestamp
  • Validation results (after validation)
  • Actions (generate/download/validate/view XML)

Credit Memo View

If credit memo generation is enabled, the extension also adds an E-Invoice Information section on Sales >Credit Memos > View with status, format, timestamp, and download actions.

Admin Actions

Invoice Actions (single invoice)

  • Generate E-Invoice
  • Download PDF (hybrid formats)
  • Download XML
  • Validate E-Invoice
  • View XML Content

Mass Actions (invoice/credit memo grids)

  • Sales >Invoices: Generate E-Invoice and Download E-Invoices (ZIP)
  • Sales >Credit Memos: Generate E-Invoice

Status Persistence

The module stores status, format, generated file references, timestamp, and error details on the sales document so Admin UI, downloads, and API responses stay consistent.

Audit Trail

All status changes are logged:

  • Generation attempts (success/failure)
  • File paths created
  • Validation results
  • Error messages

Check Magento logs for the full audit trail:

  • var/log/system.log
  • var/log/exception.log

API Access

If enabled in configuration, invoice and credit memo API responses include:

GET /rest/V1/invoices/{id} Response includes: - extension_attributes.einvoice_xml - extension_attributes.einvoice_pdf

Notes:

  • einvoice_pdf is base64-encoded PDF content (hybrid formats).
  • einvoice_xml is the XML string (not base64).

Found an issue with this documentation? Let us know