In a general manner, the chart templates should not be set to noupdate, that way, if a new company starts in an existing database, it starts with an up-to-date chart of accounts. For instance, if the chart of template is not updated from 12.0 to 13.0, the `default_pos_receivable_account_id` is not added in the chart template, and when a new company is created, the default pos receivable account is not set on the company. Besides, the field `res.company``account_default_pos_receivable_account_id` is not displayed on any form view, whether or not the full accounting is installed, so we must especially pay attention this default account is well set from start, as the user as no opportunity to correct this by himself. In addition, in upgrade scripts, the default pos receivable account on the chart template is used to correctly set the pos receivable account on the company and on the pos payment methods, so it must be well set for the upgrade script to do its job correctly. Technically, it means, without this revision, the fields: - `account.chart.template``default_pos_receivable_account_id`, - `res.company``account_default_pos_receivable_account_id`, - `pos.payment.method``receivable_account_id` were not filled properly on upgrade, causing critical issues in the accounting entries on pos session closing. Related to #52786 Related to odoo/upgrade@ccfd2371ef closes odoo/odoo#52870 X-original-commit: 3258ba015ff75b7c176d83a44261d24ebfcc26de Signed-off-by: Denis Ledoux (dle) <dle@odoo.com>
19 lines
904 B
XML
19 lines
904 B
XML
<?xml version="1.0" encoding="UTF-8"?>
|
|
<odoo>
|
|
<!-- Chart of Accounts Template -->
|
|
<record id="account_chart_template_lithuania" model="account.chart.template">
|
|
<field name="name">Lithuania - Accounting</field>
|
|
<field name="code_digits">1</field>
|
|
<field name="currency_id" ref="base.EUR"/>
|
|
<!-- Anglo-Saxon Accounting is used for reporting cost of good sold
|
|
when products are sold/delivered.-->
|
|
<field name="use_anglo_saxon" eval="True"/>
|
|
<!-- Languages for which the translations of templates could be
|
|
copied in the final object when generating them from templates -->
|
|
<field name="spoken_languages" eval="'lt_LT'"/>
|
|
<field name="bank_account_code_prefix">271</field>
|
|
<field name="cash_account_code_prefix">272</field>
|
|
<field name="transfer_account_code_prefix">273</field>
|
|
</record>
|
|
</odoo>
|