mirror of
https://github.com/OCA/account-reconcile.git
synced 2025-01-20 12:27:39 +02:00
[FIX] spelling
(lp:c2c-financial-addons/6.1 rev 77)
This commit is contained in:
@@ -29,7 +29,7 @@
|
|||||||
'description': """
|
'description': """
|
||||||
The goal of this module is to improve the basic bank statement, help dealing with huge volume of
|
The goal of this module is to improve the basic bank statement, help dealing with huge volume of
|
||||||
reconciliation by providing basic rules to identify the partner of a bank statement line.
|
reconciliation by providing basic rules to identify the partner of a bank statement line.
|
||||||
Each bank statement profile can have his own rules to apply respecting a sequence order.
|
Each bank statement profile can have its own rules to be applied according to a sequence order.
|
||||||
|
|
||||||
Some basic rules are provided in this module:
|
Some basic rules are provided in this module:
|
||||||
|
|
||||||
@@ -39,15 +39,15 @@
|
|||||||
3) Match from statement line reference (based on Invoice number)
|
3) Match from statement line reference (based on Invoice number)
|
||||||
|
|
||||||
You can easily override this module and add your own rules in your own one. The basic rules only
|
You can easily override this module and add your own rules in your own one. The basic rules only
|
||||||
fullfill the partner, but you can use them to complete all values of the line (in the future, we'll
|
fill in the partner, but you can use them to fill in any value of the line (in the future, we will
|
||||||
add rule to automatically match and reconcile the line).
|
add a rule to automatically match and reconcile the line).
|
||||||
|
|
||||||
It add as well a label on the bank statement line (on which the pre-define rules can match) and
|
It adds as well a label on the bank statement line (on which the pre-define rules can match) and
|
||||||
a char field on the partner called 'Bank Statement Label'. Using the pre-define rules, you'll be
|
a char field on the partner called 'Bank Statement Label'. Using the pre-define rules, you will be
|
||||||
able to match various label for a partner.
|
able to match various labels for a partner.
|
||||||
|
|
||||||
The reference of the line is always used by the reconciliation process. We're supposed to copy
|
The reference of the line is always used by the reconciliation process. We're supposed to copy
|
||||||
there (or write manually) the matching string. That can be : the order Number or an invoice number,
|
there (or write manually) the matching string. This can be: the order Number or an invoice number,
|
||||||
or anything that will be found in the invoice accounting entry part to make the match.
|
or anything that will be found in the invoice accounting entry part to make the match.
|
||||||
|
|
||||||
You can use it with our account_advanced_reconcile module to automatize the reconciliation process.
|
You can use it with our account_advanced_reconcile module to automatize the reconciliation process.
|
||||||
|
|||||||
@@ -27,13 +27,13 @@
|
|||||||
'complexity': 'normal', #easy, normal, expert
|
'complexity': 'normal', #easy, normal, expert
|
||||||
'depends': ['account_statement_ext','account_statement_base_completion'],
|
'depends': ['account_statement_ext','account_statement_base_completion'],
|
||||||
'description': """
|
'description': """
|
||||||
This module bring basic methods and fields on bank statement to deal with
|
This module brings basic methods and fields on bank statement to deal with
|
||||||
the importation of different bank and offices. A generic abstract method is defined and an
|
the importation of different bank and offices. A generic abstract method is defined and an
|
||||||
example that gives you a basic way of importing bank statement through a standard file is providen.
|
example that gives you a basic way of importing bank statement through a standard file is provided.
|
||||||
|
|
||||||
This module improves the bank statement and allow you to import your bank transactions with
|
This module improves the bank statement and allows you to import your bank transactions with
|
||||||
a standard .csv or .xls file (you'll find it in the 'datas' folder). It'll respect the profil
|
a standard .csv or .xls file (you'll find it in the 'data' folder). It respects the profile
|
||||||
you'll choose (providen by the accouhnt_statement_ext module) to pass the entries. That means,
|
(provided by the accouhnt_statement_ext module) to pass the entries. That means,
|
||||||
you'll have to choose a file format for each profile.
|
you'll have to choose a file format for each profile.
|
||||||
|
|
||||||
This module can handle a commission taken by the payment office and has the following format:
|
This module can handle a commission taken by the payment office and has the following format:
|
||||||
|
|||||||
@@ -27,32 +27,35 @@
|
|||||||
'complexity': 'normal', #easy, normal, expert
|
'complexity': 'normal', #easy, normal, expert
|
||||||
'depends': ['account'],
|
'depends': ['account'],
|
||||||
'description': """
|
'description': """
|
||||||
The goal of this module is to improve the basic bank statement, by adding various new features,
|
Improve the basic bank statement, by adding various new features,
|
||||||
and help dealing with huge volume of reconciliation through payment offices (like Paypal, Lazer,
|
and help dealing with huge volume of reconciliation through payment offices such as Paypal, Lazer,
|
||||||
Visa, Amazon,...).
|
Visa, Amazon...
|
||||||
|
|
||||||
It will be mostly used for E-commerce but can be usefule for other use cases as it introduce a
|
It is mostly used for E-commerce but can be useful for other use cases as it introduces a
|
||||||
notion of profil on the bank statement to have more control on the generated entries. It will
|
notion of profile on the bank statement to have more control on the generated entries. It serves as
|
||||||
be the base for all new features developped to improve the reconciliation process (see our other
|
a base for all new features developped to improve the reconciliation process (see our other
|
||||||
set of modules, like : account_statement_base_completion, account_statement_base_import,
|
set of modules:
|
||||||
account_advanced_reconcile).
|
|
||||||
|
* account_statement_base_completion
|
||||||
|
* account_statement_base_import
|
||||||
|
* account_advanced_reconcile
|
||||||
|
|
||||||
Features:
|
Features:
|
||||||
|
|
||||||
1) This module improves the bank statement in the way it allows you to define profiles (for each
|
1) Improve the bank statement: allows to define profiles (for each
|
||||||
Office or Bank). The bank statement will then generate the entries based on some criteria chosen
|
Office or Bank). The bank statement will then generate the entries based on some criteria chosen
|
||||||
in the selected profile. You can setup on the profile:
|
in the selected profile. You can setup on the profile:
|
||||||
|
|
||||||
- The journal to use
|
- the journal to use
|
||||||
- Choose to use balance check or not
|
- use balance check or not
|
||||||
- Account commission and Analytic account for commission
|
- account commission and Analytic account for commission
|
||||||
- Partner concerned by the profile (used in commission and optionaly on generated credit move)
|
- partner concerned by the profile (used in commission and optionaly on generated credit move)
|
||||||
- Can force a to use a specifi credit account (instead of the receivalble/payable default one)
|
- use a specific credit account (instead of the receivalble/payable default one)
|
||||||
- Force Partner on the counter-part move (e.g. 100.- debit, Partner: M.Martin; 100.- credit, Partner: HSBC)
|
- force Partner on the counter-part move (e.g. 100.- debit, Partner: M.Martin; 100.- credit, Partner: HSBC)
|
||||||
|
|
||||||
2) Adds a report on bank statement that can be used for checks remittance
|
2) Add a report on bank statement that can be used for checks remittance
|
||||||
|
|
||||||
3) When an error occurs in a bank statement confirmation, it will go through all line anyway and summarize
|
3) When an error occurs in a bank statement confirmation, go through all line anyway and summarize
|
||||||
all the erronous line in a same popup instead of raising and crashing on every step.
|
all the erronous line in a same popup instead of raising and crashing on every step.
|
||||||
|
|
||||||
4) Remove the period on the bank statement, and compute it for each line based on their date instead.
|
4) Remove the period on the bank statement, and compute it for each line based on their date instead.
|
||||||
|
|||||||
@@ -27,13 +27,15 @@
|
|||||||
'complexity': 'normal', #easy, normal, expert
|
'complexity': 'normal', #easy, normal, expert
|
||||||
'depends': ['account_statement_base_completion', 'base_transaction_id'],
|
'depends': ['account_statement_base_completion', 'base_transaction_id'],
|
||||||
'description': """
|
'description': """
|
||||||
Add a completion method based on transaction ID providen by the bank/office. This
|
Add a completion method based on transaction ID providen by the bank/office.
|
||||||
transaction ID has been recorded on the SO (by a mapping through the e-commerce connector,
|
|
||||||
or manually). Completion will look in the SO with that transaction ID to match the partner,
|
|
||||||
then it will complete the bank statement line with him the fullfill as well the reference
|
|
||||||
with the found SO name to ease the reconciliation.
|
|
||||||
|
|
||||||
So this way, the reconciliation always happend on the SO name stored in ref.
|
This transaction ID has been recorded on the SO (by a mapping
|
||||||
|
through the e-commerce connector, or manually). Completion will look
|
||||||
|
in the SO with that transaction ID to match the partner, then it
|
||||||
|
will fill in the bank statement line with it, as well as
|
||||||
|
the reference with the found SO name to ease the reconciliation.
|
||||||
|
|
||||||
|
This way, the reconciliation always happen on the SO name stored in ref.
|
||||||
|
|
||||||
""",
|
""",
|
||||||
'website': 'http://www.camptocamp.com',
|
'website': 'http://www.camptocamp.com',
|
||||||
|
|||||||
@@ -30,21 +30,19 @@
|
|||||||
This module brings generic methods and fields on bank statement to deal with
|
This module brings generic methods and fields on bank statement to deal with
|
||||||
the importation of different bank and offices that uses transactionID.
|
the importation of different bank and offices that uses transactionID.
|
||||||
|
|
||||||
This module allow you to import your bank transactions with a standard .csv or .xls file
|
This module allows you to import your bank transactions with a standard .csv or .xls file
|
||||||
(you'll find it in the 'datas' folder). It'll respect the profil
|
(you'll find samples in the 'data' folder). It respects the chosen profile
|
||||||
you'll choose (providen by the account_statement_ext module) to generate the entries.
|
(model provided by the account_statement_ext module) to generate the entries.
|
||||||
|
|
||||||
This module can handle a commission taken by the payment office and has the following format:
|
This module can handle a commission taken by the payment office and has the following format:
|
||||||
|
|
||||||
* transaction_id : the transaction ID given by the bank/office. It'll be used as reference
|
* transaction_id : the transaction ID given by the bank/office. It is used as reference
|
||||||
in the generated entries and will be useful for reconciliation process
|
in the generated entries and is useful for reconciliation process
|
||||||
* date : date of the payment
|
* date : date of the payment
|
||||||
* amount : amount paid in the currency of the journal used in the importation profil
|
* amount : amount paid in the currency of the journal used in the importation profile
|
||||||
* commission_amount : amount of the comission for each line
|
* commission_amount : amount of the comission for each line
|
||||||
* label : the comunication given by the payment office, used as communication in the
|
* label : the comunication given by the payment office, used as communication in the
|
||||||
generated entries.
|
generated entries.
|
||||||
|
|
||||||
|
|
||||||
""",
|
""",
|
||||||
'website': 'http://www.camptocamp.com',
|
'website': 'http://www.camptocamp.com',
|
||||||
'init_xml': [],
|
'init_xml': [],
|
||||||
|
|||||||
@@ -29,7 +29,7 @@
|
|||||||
'description': """
|
'description': """
|
||||||
Adds transaction id to invoice and sale models and views. On Sales order, you can specify the transaction ID
|
Adds transaction id to invoice and sale models and views. On Sales order, you can specify the transaction ID
|
||||||
used for the payment and it will be propagated to the invoice (even if made from packing).
|
used for the payment and it will be propagated to the invoice (even if made from packing).
|
||||||
This is mostely used for E-commerce handling. You can then add a mapping on that SO field to save the E-Commerce
|
This is mostly used for e-commerce handling. You can then add a mapping on that SO field to save the e-commerce
|
||||||
financial Transaction ID into the OpenERP SO field. The main purpose is to ease the reconciliation process and
|
financial Transaction ID into the OpenERP SO field. The main purpose is to ease the reconciliation process and
|
||||||
be able to find the partner when importing the bank statement.
|
be able to find the partner when importing the bank statement.
|
||||||
""",
|
""",
|
||||||
|
|||||||
Reference in New Issue
Block a user