Search options (Page 90 of 246)

P&L is calculated at the end of the year by taking the balance of all expense and income accounts and stock differentials and then auto inserted. Only the Trial Balance and computed P&L are used during the year in a similar manner. What you want is a hierarchy of P&L accounts in the Accounts Master. You are free to change the nomenclature for the Account Classes, Account Groups and Account heads.

Since most non African FA users are not familiar with the OHADA implementation, I had to look it up and provide some links for others to evaluate and advise quickly.
Look up the FA users list and see if any are from your region willing to assist.

Alternatively, upload an excel sheet of your current OHADA accounts master and their desired classification and provide the link here to assist others to advise.

@joe: Providing a native OHADA Chart would increase the FA footprint into West and Central Africa tremendously.

What is the standard procedure to include it in the invoice? Must we edit it like here or in the repXXX file in any different way? Should it be some choice in the company setup as candidates for the sys_prefs table?

Start from a blank chart master, chart class and chart groups set of tables and manually put in whatever classification you want. You can nest the Group's Accounts as well as desired to get your OHADA CoA.

In your parlance, you mean that your "fiscal result" other than income tax is FA's native P&L account. All the others can be nested in the P&L.

From Wikipedia:

ODOO Apps supports OHADA natively and is developed on GitHub, being based on Python.
This French Article may be useful.
Will this CoA meet your needs?
OHADA Accounting Plans

See the wiki for more info.

The report stands corrected and committed into the core now as rep310.php.

MySQL Bugs #13794 TEXT cannot use empty string as default value

@notrinos: Thanks for the info.

The table 0_salary_structure can remove the type field by using the signed nature of the amount field or if it is to be a flag, then an is_deduction field can replace it.

Was this necessary:

ALTER TABLE `0_gl_trans` ADD `payslip_no` INT(11) NOT NULL DEFAULT 0;

in the update.sql?
Could it not be looked up based on transaction date and employee code?
If the core FA table changes are avoided, it will be more portable.

These lines in the README.md:

- Comment out block of codes from lines 215 to 220 of "*admin/inst_module.php*".
..
..
- Uncomment lines 215-220 of "*admin/inst_module.php*".

are no longer required after this commit on 2017-12-15.

Added to the FA24extensions repo.

If your new table 0_payroll_account is intended to have just 1 record, can it not be accommodated in the 0_sys_prefs table?

Bloomberg seems to provide USD based rates only. Will check on Google decimal digits since inverted value is available for reverse rates.

document.write is used only in lines 1438 and 1439 in includes/ui/ui_view.inc.
This affects the js_cache which you may choose to purge from the company folder.

Then if we need to suppress the barcodes in the reports, we need to disable the  'use barcode on stocks' if set in company setup temporarily! Wouldn't it be better to have a parameter in the report request form for this?

Updated the Wiki accordingly.

This happens when the "Show Pictures" is set to "Yes" in the rep303 (Stock Check Sheets) form.

@Foreign Item Codes cannot have the barcodes that we generate/provide - they must follow what the supplier provides.

Looks like FA has this facility by just fixing the Salesman Role's Permissions. See attachment.