[IMP] : Update Description for modules
bzr revid: cha@tinyerp.com-20120712095425-l1i8o33okp2tzfjx
This commit is contained in:
parent
4db49fc84d
commit
66b80419e0
|
@ -29,14 +29,14 @@ Accounting and Financial Management.
|
|||
|
||||
Financial and accounting module that covers:
|
||||
--------------------------------------------
|
||||
General accountings
|
||||
Cost/Analytic accounting
|
||||
Third party accounting
|
||||
Taxes management
|
||||
Budgets
|
||||
Customer and Supplier Invoices
|
||||
Bank statements
|
||||
Reconciliation process by partner
|
||||
* General accountings
|
||||
* Cost/Analytic accounting
|
||||
* Third party accounting
|
||||
* Taxes management
|
||||
* Budgets
|
||||
* Customer and Supplier Invoices
|
||||
* Bank statements
|
||||
* Reconciliation process by partner
|
||||
|
||||
Creates a dashboard for accountants that includes:
|
||||
--------------------------------------------------
|
||||
|
|
|
@ -27,13 +27,15 @@
|
|||
This module supports the Anglo-Saxon accounting methodology by changing the accounting logic with stock transactions.
|
||||
=====================================================================================================================
|
||||
|
||||
The difference between the Anglo-Saxon accounting countries
|
||||
and the Rhine or also called Continental accounting countries is the moment of taking the Cost of Goods Sold versus Cost of Sales.
|
||||
Anglo-Saxons accounting does take the cost when sales invoice is created, Continental accounting will take the cost at the moment the goods are shipped.
|
||||
The difference between the Anglo-Saxon accounting countries and the Rhine or also called
|
||||
Continental accounting countries is the moment of taking the Cost of Goods Sold versus
|
||||
Cost of Sales. Anglo-Saxons accounting does take the cost when sales invoice is created,
|
||||
Continental accounting will take the cost at the moment the goods are shipped.
|
||||
|
||||
This module will add this functionality by using a interim account, to store the value of shipped goods and will contra book this interim account
|
||||
when the invoice is created to transfer this amount to the debtor or creditor account.
|
||||
Secondly, price differences between actual purchase price and fixed product standard price are booked on a separate account.""",
|
||||
This module will add this functionality by using a interim account, to store the value of
|
||||
shipped goods and will contra book this interim account when the invoice is created to
|
||||
transfer this amount to the debtor or creditor account. Secondly, price differences between
|
||||
actual purchase price and fixed product standard price are booked on a separate account.""",
|
||||
"images": ["images/account_anglo_saxon.jpeg"],
|
||||
"depends": ["product", "purchase"],
|
||||
"category": "Hidden/Dependency",
|
||||
|
|
|
@ -29,7 +29,7 @@
|
|||
Module that extends the standard account_bank_statement_line object for improved e-banking support.
|
||||
===================================================================================================
|
||||
|
||||
Adds
|
||||
This module adds:
|
||||
- valuta date
|
||||
- batch payments
|
||||
- traceability of changes to bank statement lines
|
||||
|
|
|
@ -28,8 +28,8 @@
|
|||
This module allows accountants to manage analytic and crossovered budgets.
|
||||
==========================================================================
|
||||
|
||||
Once the Budgets are defined (in Invoicing/Budgets/Budgets),
|
||||
the Project Managers can set the planned amount on each Analytic Account.
|
||||
Once the Budgets are defined (in Invoicing/Budgets/Budgets), the Project Managers
|
||||
can set the planned amount on each Analytic Account.
|
||||
|
||||
The accountant has the possibility to see the total of amount planned for each
|
||||
Budget in order to ensure the total planned is not greater/lower than what he planned
|
||||
|
|
|
@ -28,7 +28,8 @@
|
|||
Allows cancelling accounting entries.
|
||||
=====================================
|
||||
|
||||
This module adds 'Allow Cancelling Entries' field on form view of account journal. If set to true it allows user to cancel entries & invoices.
|
||||
This module adds 'Allow Cancelling Entries' field on form view of account journal.
|
||||
If set to true it allows user to cancel entries & invoices.
|
||||
""",
|
||||
'website': 'http://www.openerp.com',
|
||||
"images" : ["images/account_cancel.jpeg"],
|
||||
|
|
|
@ -40,17 +40,18 @@ Supported are CODA flat files in V2 format from Belgian bank accounts.
|
|||
* Support for 'parsing only' CODA Bank Accounts (defined as type='info' in the CODA Bank Account configuration records).
|
||||
* Multi-language CODA parsing, parsing configuration data provided for EN, NL, FR.
|
||||
|
||||
The machine readable CODA Files are parsed and stored in human readable format in CODA Bank Statements.
|
||||
Also Bank Statements are generated containing a subset of the CODA information (only those transaction lines
|
||||
that are required for the creation of the Financial Accounting records).
|
||||
The CODA Bank Statement is a 'read-only' object, hence remaining a reliable representation of the original CODA file
|
||||
whereas the Bank Statement will get modified as required by accounting business processes.
|
||||
The machine readable CODA Files are parsed and stored in human readable format in
|
||||
CODA Bank Statements. Also Bank Statements are generated containing a subset of
|
||||
the CODA information (only those transaction lines that are required for the creation
|
||||
of the Financial Accounting records). The CODA Bank Statement is a 'read-only'
|
||||
object, hence remaining a reliable representation of the original CODA file whereas
|
||||
the Bank Statement will get modified as required by accounting business processes.
|
||||
|
||||
CODA Bank Accounts configured as type 'Info' will only generate CODA Bank Statements.
|
||||
|
||||
A removal of one object in the CODA processing results in the removal of the associated objects.
|
||||
The removal of a CODA File containing multiple Bank Statements will also remove those associated
|
||||
statements.
|
||||
A removal of one object in the CODA processing results in the removal of the associated
|
||||
objects. The removal of a CODA File containing multiple Bank Statements will also
|
||||
remove those associated statements.
|
||||
|
||||
The following reconciliation logic has been implemented in the CODA processing:
|
||||
|
||||
|
@ -59,8 +60,9 @@ The following reconciliation logic has been implemented in the CODA processing:
|
|||
3) When the previous step doesn't find a match, the transaction counterparty is located via the Bank Account Number configured on the OpenERP Customer and Supplier records.
|
||||
4) In case the previous steps are not successful, the transaction is generated by using the 'Default Account for Unrecognized Movement' field of the CODA File Import wizard in order to allow further manual processing.
|
||||
|
||||
In stead of a manual adjustment of the generated Bank Statements, you can also re-import the CODA
|
||||
after updating the OpenERP database with the information that was missing to allow automatic reconciliation.
|
||||
In stead of a manual adjustment of the generated Bank Statements, you can also
|
||||
re-import the CODA after updating the OpenERP database with the information that
|
||||
was missing to allow automatic reconciliation.
|
||||
|
||||
Remark on CODA V1 support:
|
||||
In some cases a transaction code, transaction category or structured communication code has been given a new or clearer description in CODA V2.
|
||||
|
|
|
@ -36,7 +36,7 @@ Project Management module tracks multi-level projects, tasks, work done on tasks
|
|||
It is able to render planning, order tasks.
|
||||
|
||||
Dashboard for project management that includes:
|
||||
--------------------------------------------
|
||||
-----------------------------------------------
|
||||
* List of My Open Tasks
|
||||
* Graph of My Remaining Hours by Project
|
||||
""",
|
||||
|
|
Loading…
Reference in New Issue