Skip to Content
Menu
v 17.0 Third Party
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies Purchase (purchase)
Invoicing (account)
Discuss (mail)
Inventory (stock)
Lines of code 73
Technical Name fal_so_analytic_account_transfer_to_po
LicenseOPL-1
Websitehttps://cluedoo.com/shop/lic-clu-set-aap-0001-transfer-analytic-account-from-sales-to-purchase-667
You bought this module and need support? Click here!
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies Purchase (purchase)
Invoicing (account)
Discuss (mail)
Inventory (stock)
Lines of code 73
Technical Name fal_so_analytic_account_transfer_to_po
LicenseOPL-1
Websitehttps://cluedoo.com/shop/lic-clu-set-aap-0001-transfer-analytic-account-from-sales-to-purchase-667

STORY BEHIND THE FEATURES

ODOO BEHAVIOR

Odoo Standard proposes the notion of analytic account but consider that it's relevant on some accounting transaction (customer invoice, vendor bills) but not on all the accounting transaction.

CLUEDOO BEHAVIOR

Cluedoo considers that all the documents which will generate a journal entry should have the possibility to record an analytic account. So, Cluedoo extend the choice of analytic account to

MODULE+

A Cluedoo best practice when you use analytic account on P&L is to fill this analytic account dimension for 100% of journal items of the P&L. By adding this field on all the documents, Cluedoo gives the possibility to make consistent analytic accounting.

BUSINESS CASE

If you buy machines dedicated to a project, it's important to allocate each depreciation related to this machine on the project in order to track your project margin.

CLUEDOO RECOMMENDATION

Installation on 100% of the databases from the beginning. We recommend to use analytic account for all the integration.

Related module: Default analytic account on product.

OUR FEATURES AS SOLUTION

Analytic Account for Journal Entry from Various Sources

Automatically fill analytic account in journal entry from Sales, Purchase, and Bank Statement

Common Analytic Account

Share analytic account with other company

HOW TO USE THIS MODULE ?

Dependencies

Analytic Account Tag

Base Setup Configuration

1

Sales to Purchase transaction

Create a sale order with MTO and buy product so that the purchase order is  also created.
Set the analytic account on sale order, when purchase order is created, analytic account on purchase order line and on journal item is also automatically filled.





2

From Bank Statement

Create bank statement, we can apply analytic account to lines by clicking Apply to line.
Then reconcile the statement, and it will create journal items with analytic account automatically filled.

Analytic tag is not available from v16 onwards.




3

Common Analytic Account

On Cluedoo configuration panel, we can activate Common Analytic Account.
After activating the feature, we can use analytic account from other company.

Not available from v16 onwards.



Odoo Proprietary License v1.0

This software and associated files (the "Software") may only be used (executed,
modified, executed after modifications) if you have purchased a valid license
from the authors, typically via Odoo Apps, or if you have received a written
agreement from the authors of the Software (see the COPYRIGHT file).

You may develop Odoo modules that use the Software as a library (typically
by depending on it, importing it and using its resources), but without copying
any source code or material from the Software. You may distribute those
modules under the license of your choice, provided that this license is
compatible with the terms of the Odoo Proprietary License (For example:
LGPL, MIT, or proprietary licenses similar to this one).

It is forbidden to publish, distribute, sublicense, or sell copies of the Software
or modified copies of the Software.

The above copyright notice and this permission notice must be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,
DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
DEALINGS IN THE SOFTWARE.

Please log in to comment on this module

  • The author can leave a single reply to each comment.
  • This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
  • If you want to start a discussion with the author or have a question related to your purchase, please use the support page.