-
-
Notifications
You must be signed in to change notification settings - Fork 305
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[14.0][IMP] l10n_it_fatturapa_pec: decoupling from l10n_it_sdi_channel.
- Loading branch information
Showing
20 changed files
with
631 additions
and
8 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -57,6 +57,21 @@ Configuration | |
|
||
Consultare il modulo `l10n_it_sdi_channel`. | ||
|
||
Creare un nuovo canale di tipo PEC (unico supportato per ora) e indicare: | ||
|
||
- Il server PEC da utilizzare per inviare/ricevere attraverso lo SdI | ||
- La email PEC dello SdI, inizialmente uguale a [email protected] | ||
|
||
Dopo il primo invio, lo SdI risponderà segnalando l'indirizzo da utilizzare per gli invii successivi, da inserire nella configurazione del server PEC dedicato. | ||
|
||
Nella configurazione del server smtp, sezione "PEC e fattura elettronica", selezionare la casella "Server PEC e-fattura". | ||
|
||
Indicare quindi la email da usare per l'invio e la ricezione, solitamente è uguale al nome utente di connessione (può essere diversa in casi particolari). | ||
|
||
È preferibile avere una email dedicata solo alla fatturazione elettronica, in quanto i messaggi di altro tipo non possono essere gestiti da Odoo (verrebbero marcati comunque come letti). | ||
|
||
Se si usano altri server SMTP per l'invio di email non PEC, è necessario aumentare la loro priorità rispetto a quella del server PEC. | ||
|
||
Lo stato dell'esportazione XML può essere forzato impostando 'Permettere di forzare lo stato dell'esportazione e-fattura' nelle impostazioni tecniche dell'utente. | ||
|
||
Per ogni azienda, in | ||
|
@@ -69,6 +84,21 @@ specificare l'utente che sarà utilizzato come creatore delle e-fatture fornitor | |
|
||
See `l10n_it_sdi_channel` module. | ||
|
||
Create a new PEC channel type (the only one supported right now) and indicate: | ||
|
||
- PEC server to be used for sending to/receiving from ES | ||
- ES PEC email, initially equal to [email protected] | ||
|
||
After sending the first email, ES will reply indicating the address to use for all the others, to be entered in dedicated PEC server configuration. | ||
|
||
In smtp server configuration, select 'E-invoice PEC server' in 'PEC and Electronic Invoice' section. | ||
|
||
Then specify the email to use for sending and receiving, it is usually equal to connection username (can be different in special cases). | ||
|
||
It would be better to have a dedicated email for electronic invoicing, because other kind of messages can't be managed by Odoo (they would be marked as seen). | ||
|
||
If you use other SMTP servers for non-PEC email sending, you need to increase their priority as compared to PEC server one. | ||
|
||
XML export state can ba forced setting 'Allow to force the supplier e-bill export state' in user's technical settings. | ||
|
||
For every company, in | ||
|
@@ -117,12 +147,15 @@ Contributors | |
* Sergio Corato <[email protected]> | ||
* Lorenzo Battistini <https://github.com/eLBati> | ||
* Sergio Zanchetta <https://github.com/primes2h> | ||
* Giovanni Serra <[email protected]> | ||
|
||
* `Tecnativa <https://www.tecnativa.com>`_: | ||
|
||
* Víctor Martínez | ||
|
||
* `Ooops <https://www.ooops404.com>`_: | ||
|
||
* Giovanni Serra <[email protected]> | ||
|
||
Maintainers | ||
~~~~~~~~~~~ | ||
|
||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,9 @@ | ||
<?xml version="1.0" encoding="utf-8" ?> | ||
<odoo> | ||
<data noupdate="1"> | ||
<record id="sdi_pec_first_address" model="ir.config_parameter"> | ||
<field name="key">sdi.pec.first.address</field> | ||
<field name="value">[email protected]</field> | ||
</record> | ||
</data> | ||
</odoo> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,9 @@ | ||
<?xml version="1.0" encoding="utf-8" ?> | ||
<!-- Copyright 2018 Simone Rubino - Agile Business Group | ||
License AGPL-3.0 or later (https://www.gnu.org/licenses/agpl). --> | ||
<odoo> | ||
<record id="sdi_channel_pec" model="sdi.channel"> | ||
<field name="name">PEC</field> | ||
<field name="channel_type">pec</field> | ||
</record> | ||
</odoo> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.