OdooWiki OCA HUB

Account Invoice Export Job

account_invoice_export_job folder_open OCA/edi open_in_new
Invoicing Management License: AGPL-3

This module enables the use of the queue_job module with account_invoice_export

auto_awesome What this module does

AI-generated from the code · Odoo 18.0

Automatically sends customer invoices to the eBill/transmit method in the background using the job queue, so users don't have to wait and failed exports can be retried.

This module makes invoice exporting to an electronic transmission method (eBill) run as a background job instead of blocking the user. It builds on the account_invoice_export and queue_job modules.

When an invoice is exported, the export action is automatically delayed and placed in a dedicated job channel called invoice_export. Because of this, the user can keep working while the system sends the invoice in the background.

  • The export is queued automatically; no manual step is needed.
  • Failed jobs are retried automatically following a retry pattern (after 1, 2, 3 and 5 attempts with increasing delays).
  • If sending fails, an error message template is available that shows the transmission method name and the failed job's identifier.

The module extends the account.move model and hooks into its export method. It also registers a job function for _job_export_invoice on account.move and creates the invoice_export job channel. No new menus or screens are added; the change happens behind the scenes when invoices are exported.

Models and fields (1)
  • account.move · extends an existing model

Text generated by AI (DeepSeek) from reading the Odoo 18.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub

Availability by version

Reviewed: 2026-11-03
Confirmed (verified in repository and branch) Estimated (unverified) No information

Confirmation status: 2 confirmed, 7 with no information of 9 versions.

terminal Installation and usage

No verified information

Installation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.

info

Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.