ITA - Fattura elettronica - Emissione - Scissione Pagamenti
Italiano
Modulo tecnico di integrazione tra l10n_it_split_payment e l10n_it_fatturapa_out
English
Technical module for integrating l10n_it_split_payment and l10n_it_fatturapa_out
auto_awesome What this module does
AI-generated from the code · Odoo 16.0Adds split payment support to Italian electronic invoice (FatturaPA) XML export, so the total amount sent to the tax authority includes the split-payment amount.
This is a technical bridge module that connects two existing Italian localization features: split payment and electronic invoice export. It does not add any new menu, screen or button.
When a user exports customer invoices to the Italian FatturaPA XML format, the module changes how the invoice total is calculated for the file. If the invoice is flagged as split payment, the split-payment amount is added to the total that is written into the electronic invoice.
- It extends the electronic invoice export wizard (
wizard.export.fatturapa) and overrides the method that computes the invoice total (getImportoTotale). - The rule is automatic: no user action is needed beyond marking the invoice as split payment and running the usual export.
- It only affects invoices where the split payment flag is set; other invoices are exported exactly as before.
Because it is an auto-install module, it is installed automatically when both the FatturaPA export and split payment modules are present. It touches the invoice export wizard and, indirectly, the invoice data used by that wizard.
Models and fields (1)
- wizard.export.fatturapa · extends an existing model
Text generated by AI (DeepSeek) from reading the Odoo 16.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-03Confirmation status: 2 confirmed, 7 with no information of 9 versions.
Sources · Odoo 14.0
Confirmed on 2026-11-03 in branch 14.0 of OCA/l10n-italy.
terminal Installation and usage
No verified informationInstallation 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.
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.