diff --git a/account_ebics/README.rst b/account_ebics/README.rst index c483521..39423ae 100644 --- a/account_ebics/README.rst +++ b/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 `_. 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 -payment status report returned by the bank). Each needs the module of its format (see -Companion modules); Odoo tells you which one when it is missing. +downloaded file: ``camt.053``, ``camt.052``, ``camt.054`` and ``cfonb120``. Each needs the +module of its format (see 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 -files, and offers manual downloads and uploads. With Odoo Enterprise it sits under -*Accounting > Accounting*. +The **EBICS Processing** menu, in the top bar of the Accounting application, lists the +downloaded and uploaded files and offers manual downloads and uploads. 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 -configuration, not from the person clicking. +batch or the payment order, with the format set in the configuration: on the payment +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 diff --git a/account_ebics/static/description/index.html b/account_ebics/static/description/index.html index 5e6995e..0b71bbf 100644 --- a/account_ebics/static/description/index.html +++ b/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

Because the connection needs a Python library and your key files on the server, it runs on 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

With a fintech licence, add its parameters to the [options] section of the Odoo server @@ -150,6 +151,8 @@ the bank supports the test flag, otherwise as a real transfer of a small amount.

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.

File formats. In Accounting > Configuration > EBICS > EBICS File Formats, 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 GitHub.

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 -payment status report returned by the bank). Each needs the module of its format (see -Companion modules); Odoo tells you which one when it is missing.

+downloaded file: camt.053, camt.052, camt.054 and cfonb120. Each needs the +module of its format (see 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.

A downloaded camt.053 statement file in Odoo, before processing

Usage

-

The EBICS Processing menu of the accounting application lists the downloaded and uploaded -files, and offers manual downloads and uploads. With Odoo Enterprise it sits under -Accounting > Accounting.

+

The EBICS Processing menu, in the top bar of the Accounting application, lists the +downloaded and uploaded files and offers manual downloads and uploads.

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 -configuration, not from the person clicking.

+batch or the payment order, with the format set in the configuration: on the payment +mode for a payment order, on the journal's payment method for a batch payment.

Uploading a pain.001 SEPA credit transfer file over EBICS 3.0, with the test mode option