The geissweb:einvoice:generate-xml command generates the electronic invoice and credit memo XML files.
# Einzelne Rechnung (über die Entity-ID)
bin/magento geissweb:einvoice:generate-xml --invoice-id=123
# Alle Rechnungen
bin/magento geissweb:einvoice:generate-xml --all-invoices
# Neu erzeugen (vorhandene Dateien überschreiben)
bin/magento geissweb:einvoice:generate-xml --all-invoices --force
# Gutschriften
bin/magento geissweb:einvoice:generate-xml --creditmemo-id=456
bin/magento geissweb:einvoice:generate-xml --all-creditmemos
Options
| Option | Short | Meaning |
|---|---|---|
--invoice-id |
-i |
Entity ID of the invoice. |
--creditmemo-id |
-c |
Entity ID of the credit memo. |
--all-invoices |
Generate XML for all invoices. | |
--all-creditmemos |
Generate XML for all credit memos. | |
--force |
-f |
Overwrite existing XML files (otherwise skipped). |
--output-dir |
-o |
Reserved – currently not implemented; the configured directory is always used. |
Here, --invoice-id refers to the entity ID of the invoice (the internal database key), not the visible invoice number. Note the difference from the verify-amounts command, which expects the increment ID (invoice number).
Output
The files are stored in the configured storage path (default var/export/e-invoices), named according to the pattern:
- Invoice:
invoice_000000123.xml - Credit memo:
creditmemo_000000123.xml
Without --force, existing XML files are skipped. With --all-invoices/--all-creditmemos, the command shows a progress bar and, at the end, a summary (successful/errors) as well as the storage location.
After every configuration change, the affected invoices should be regenerated with --force, since existing files otherwise remain unchanged.