[FIX] account_ebics - README facts checked against the code

account_ebics/README.rst

@@ -103,7 +103,8 @@ Because the connection needs a Python library and your key files on the server,
 **Odoo.sh** or on an **on-premise** installation.
 
 The EBICS test mode for uploads requires fintech 4.3.4 or higher for EBICS 2.x and fintech
-7.2.7 or higher for EBICS 3.0. SWIFT 3SKey support requires fintech 6.4 or higher.
+7.2.7 or higher for EBICS 3.0. SWIFT 3SKey support requires fintech 6.4 or higher, and the signature passphrase
+fintech 7.3.1 or higher.
 
 Fintech licence
 ---------------
@@ -170,6 +171,9 @@ Count in weeks per bank rather than days, and start the contract and the paperwo
 Configuration
 =============
 
+The menus are those of Odoo Enterprise; on Odoo Community, the application is called
+*Invoicing* instead of *Accounting*.
+
 **Who may configure.** In *Settings > Users*, add the users who maintain the EBICS
 configuration to the **EBICS Manager** group.
 
@@ -179,9 +183,8 @@ installation. A missing format can be reported on
 `GitHub <https://github.com/Noviat/account_ebics/issues>`_.
 
 A download format can carry a **Download Process Method**, run by the *Process* button of a
-downloaded file: ``camt.053``, ``camt.052``, ``camt.054``, ``cfonb120`` and ``pain.002`` (the
+downloaded file: ``camt.053``, ``camt.052``, ``camt.054`` and ``cfonb120``. Each needs the
-payment status report returned by the bank). Each needs the module of its format (see
+module of its format (see Companion modules); Odoo tells you which one when it is missing.
-Companion modules); Odoo tells you which one when it is missing.
 
 **Bank connections.** In *Accounting > Configuration > EBICS > EBICS Configuration*, create one
 connection per bank contract, with the identifiers your bank sent you.
@@ -193,13 +196,12 @@ connection per bank contract, with the identifiers your bank sent you.
 Usage
 =====
 
-The **EBICS Processing** menu of the accounting application lists the downloaded and uploaded
+The **EBICS Processing** menu, in the top bar of the Accounting application, lists the
-files, and offers manual downloads and uploads. With Odoo Enterprise it sits under
+downloaded and uploaded files and offers manual downloads and uploads.
-*Accounting > Accounting*.
 
 Downloaded files are processed into bank statements. Uploads are launched from the payment
-batch or the payment order: the file, its format and the order type come from the
+batch or the payment order, with the format set in the configuration: on the payment
-configuration, not from the person clicking.
+mode for a payment order, on the journal's payment method for a batch payment.
 
 .. image:: https://raw.githubusercontent.com/Noviat/account_ebics/19.0/account_ebics/static/description/ebics_upload.png
    :alt: Uploading a pain.001 SEPA credit transfer file over EBICS 3.0, with the test mode option

account_ebics/static/description/index.html

@@ -86,7 +86,8 @@ bank to another and is billed by the bank, separately from anything on the Odoo
 <p>Because the connection needs a Python library and your key files on the server, it runs on
 <strong>Odoo.sh</strong> or on an <strong>on-premise</strong> installation.</p>
 <p>The EBICS test mode for uploads requires fintech 4.3.4 or higher for EBICS 2.x and fintech
-7.2.7 or higher for EBICS 3.0. SWIFT 3SKey support requires fintech 6.4 or higher.</p>
+7.2.7 or higher for EBICS 3.0. SWIFT 3SKey support requires fintech 6.4 or higher, and the signature passphrase
+fintech 7.3.1 or higher.</p>
 <div class="section" id="fintech-licence">
 <h3>Fintech licence</h3>
 <p>With a fintech licence, add its parameters to the <tt class="docutils literal">[options]</tt> section of the Odoo server
@@ -150,6 +151,8 @@ the bank supports the test flag, otherwise as a real transfer of a small amount.
 </div>
 <div class="section" id="configuration">
 <h2>Configuration</h2>
+<p>The menus are those of Odoo Enterprise; on Odoo Community, the application is called
+<em>Invoicing</em> instead of <em>Accounting</em>.</p>
 <p><strong>Who may configure.</strong> In <em>Settings &gt; Users</em>, add the users who maintain the EBICS
 configuration to the <strong>EBICS Manager</strong> group.</p>
 <p><strong>File formats.</strong> In <em>Accounting &gt; Configuration &gt; EBICS &gt; EBICS File Formats</em>, check that the
@@ -157,21 +160,19 @@ formats you exchange with your banks are defined; the common ones are created at
 installation. A missing format can be reported on
 <a class="reference external" href="https://github.com/Noviat/account_ebics/issues">GitHub</a>.</p>
 <p>A download format can carry a <strong>Download Process Method</strong>, run by the <em>Process</em> button of a
-downloaded file: <tt class="docutils literal">camt.053</tt>, <tt class="docutils literal">camt.052</tt>, <tt class="docutils literal">camt.054</tt>, <tt class="docutils literal">cfonb120</tt> and <tt class="docutils literal">pain.002</tt> (the
+downloaded file: <tt class="docutils literal">camt.053</tt>, <tt class="docutils literal">camt.052</tt>, <tt class="docutils literal">camt.054</tt> and <tt class="docutils literal">cfonb120</tt>. Each needs the
-payment status report returned by the bank). Each needs the module of its format (see
+module of its format (see Companion modules); Odoo tells you which one when it is missing.</p>
-Companion modules); Odoo tells you which one when it is missing.</p>
 <p><strong>Bank connections.</strong> In <em>Accounting &gt; Configuration &gt; EBICS &gt; EBICS Configuration</em>, create one
 connection per bank contract, with the identifiers your bank sent you.</p>
 <img alt="A downloaded camt.053 statement file in Odoo, before processing" src="ebics_download.png" style="width: 100%;" />
 </div>
 <div class="section" id="usage">
 <h2>Usage</h2>
-<p>The <strong>EBICS Processing</strong> menu of the accounting application lists the downloaded and uploaded
+<p>The <strong>EBICS Processing</strong> menu, in the top bar of the Accounting application, lists the
-files, and offers manual downloads and uploads. With Odoo Enterprise it sits under
+downloaded and uploaded files and offers manual downloads and uploads.</p>
-<em>Accounting &gt; Accounting</em>.</p>
 <p>Downloaded files are processed into bank statements. Uploads are launched from the payment
-batch or the payment order: the file, its format and the order type come from the
+batch or the payment order, with the format set in the configuration: on the payment
-configuration, not from the person clicking.</p>
+mode for a payment order, on the journal's payment method for a batch payment.</p>
 <img alt="Uploading a pain.001 SEPA credit transfer file over EBICS 3.0, with the test mode option" src="ebics_upload.png" style="width: 100%;" />
 </div>
 <div class="section" id="diagnostics">

account_ebics_batch/README.rst

@@ -22,8 +22,8 @@ Configuration
 =============
 
 The scheduled action **EBICS Batch Import** is created **inactive** at installation, with a
-daily interval. Activate it in *Settings > Technical > Scheduled Actions*, and adapt its
+daily interval. Activate it in *Settings > Technical > Automation > Scheduled Actions* (developer
-interval if needed.
+mode), and adapt its interval if needed.
 
 It calls the following method, on all confirmed connections::
 

account_ebics_batch/static/description/index.html

@@ -14,8 +14,8 @@ were entered manually.</p>
 <div class="section" id="configuration">
 <h2>Configuration</h2>
 <p>The scheduled action <strong>EBICS Batch Import</strong> is created <strong>inactive</strong> at installation, with a
-daily interval. Activate it in <em>Settings &gt; Technical &gt; Scheduled Actions</em>, and adapt its
+daily interval. Activate it in <em>Settings &gt; Technical &gt; Automation &gt; Scheduled Actions</em> (developer
-interval if needed.</p>
+mode), and adapt its interval if needed.</p>
 <p>It calls the following method, on all confirmed connections:</p>
 <pre class="literal-block">
 model._batch_import()

account_ebics_batch_payment/README.rst

@@ -24,10 +24,10 @@ This module depends on:
 Configuration
 =============
 
-On the bank journal, in the incoming and outgoing payment methods, set the **EBICS File
+On the bank journal, in the incoming and outgoing payment methods, show the optional
-Format** used for each payment method, for example pain.001 for SEPA credit transfers and
+**EBICS File Format** column and set the format of each payment method, for example
-pain.008 for direct debits. Only the formats of the journal's active EBICS connections are
+pain.001 for SEPA credit transfers and pain.008 for direct debits. The formats offered are
-offered.
+those of the journal's confirmed EBICS connection.
 
 Usage
 =====

account_ebics_batch_payment/static/description/index.html

@@ -17,10 +17,10 @@ means nothing can be altered on the way.</p>
 </div>
 <div class="section" id="configuration">
 <h2>Configuration</h2>
-<p>On the bank journal, in the incoming and outgoing payment methods, set the <strong>EBICS File
+<p>On the bank journal, in the incoming and outgoing payment methods, show the optional
-Format</strong> used for each payment method, for example pain.001 for SEPA credit transfers and
+<strong>EBICS File Format</strong> column and set the format of each payment method, for example
-pain.008 for direct debits. Only the formats of the journal's active EBICS connections are
+pain.001 for SEPA credit transfers and pain.008 for direct debits. The formats offered are
-offered.</p>
+those of the journal's confirmed EBICS connection.</p>
 </div>
 <div class="section" id="usage">
 <h2>Usage</h2>

account_ebics_oe/README.rst

@@ -4,8 +4,8 @@ EBICS - Odoo Enterprise Integration
 
 **Glue module. Install it and forget it.**
 
-On Odoo Enterprise, this module places the **EBICS Processing** menu in the Accounting
+On Odoo Enterprise, this module places the **EBICS Processing** menu in the top bar of
-application, under *Accounting > Accounting*.
+the Accounting application.
 
 It is installed automatically when both of these modules are installed:
 

account_ebics_oe/static/description/index.html

@@ -2,8 +2,8 @@
 <div class="section" id="ebics-odoo-enterprise-integration">
 <h1>EBICS - Odoo Enterprise Integration</h1>
 <p><strong>Glue module. Install it and forget it.</strong></p>
-<p>On Odoo Enterprise, this module places the <strong>EBICS Processing</strong> menu in the Accounting
+<p>On Odoo Enterprise, this module places the <strong>EBICS Processing</strong> menu in the top bar of
-application, under <em>Accounting &gt; Accounting</em>.</p>
+the Accounting application.</p>
 <p>It is installed automatically when both of these modules are installed:</p>
 <ul class="simple">
 <li><tt class="docutils literal">account_ebics</tt>;</li>