The odoo fixed asset using a Gregorian calendar for posting asset depreciation for instance the depreciation posted on the last day of the month. In Ethiopia, we have a different calendar system so we wanted to post the depreciation on the last month of the Ethiopian calendar like august 7. The current enterprise version of odoo didn't allow the period definition, so are there other alternatives to achieve this functionality?
Related
i just installed odoo 11 CE and managed to get the accounting features by activating in the user settings. However the most important functions to create fiscal periods and to close a fiscal year properly seems to be completely missing.
If this is the case and this is only available in the enterprise version the CE version becomes pretty much useless for accounting.
Thanks for any hint
Peter
Peter,
In odoo 11 (and I think since odoo 9) there are not Fiscal Periods anymore. The way to act is to create Date Ranges, that are multi propose ranges to use anywhere.
Conceptually there is not a closing of the fiscal year, but you can filter all your data by Date Ranges and make all your reporting based on this new model.
This seems to be a more flexible and powerful tool, but here is the bad news. One basic thing I think Odoo has missed out is the functionality of close a period or, in other words, to prevent of creating journal entries to the users when they are in a period. You have to use locking dates. This functionality is half implemented but it is very blocking. After the locking date, you cannot register payments because they are creating journal entries after the blocking date. I have searched a lot and I have found this PR in the OCA related with a set of functionalities to solve all this scenario.
Hope it helps to give you a scope of the functionality and limitations.
Cheers,
Pere
You can specify the fiscal year end in Odoo by entering the Fiscal year last day, and specifying locking status as below:
After this, there is no need to make a 'physical closure' for the fiscal year.
In Odoo there is no need to do a specific year end closing entry in
order to close out income statement accounts. The reports are created
in real-time, meaning that the Income statement corresponds directly
with the year-end date you specify in Odoo.
Reference:
https://www.odoo.com/documentation/user/11.0/accounting/others/adviser/fiscalyear.html
From Odoo 11, closing of fiscal years happen automatically at designated year end i.e balances of P&L accounts are zeroed out and the net is carried forward in the Balance sheet. All you need to do is to decide how to allocate the current year earning.
I am working on a export functionality and one of the requirments is to display accounting period in YYYYPPP format.
Can anyone please explain what is YYYYPPP format
It is about time information where YYYY is the fiscal year and PPP is the period of that fiscal year. For example, 2017001 represents the first period in fiscal year 2017.
Often used in Analysis Budget Management tools like SAP. The standard format for entering periods is YYYYPPP or YYYY then PPP.
I have a report that, according to users, started miscalculating dates in one field in November 2015. After some digging around, I found that one of the tables the field referenced seemed to have an end date on 2015-10-31.
The "D" field seems to represent the day of the week, with Sunday being day 1 and Saturday being 7.
Is there a way to extend the calendar so that it ends further into the future, for example 2049-12-31?
Our calendar table, for a variety of reasons, goes the the end of the current year. We have written a query that adds a new year to this table. This query takes care of most of the fields in that table. It does not touch the holiday field. That is updated manually through a web page.
We send ourselves reminders. Starting in March, we send monthly reminders that we should think about adding another year. After ensuring that the database segment has space, and that none of the definitions, such as fiscal periods, have changed, we run the query that adds a year.
Later in the year we start mailing ourselves reminders about the holidays. Then we check to see if HR has declared them, and if so, update the records accordingly.
This meets our business requirements. Yours will be different of course.
I have got multiple entries in each week. I would like to see the most recent entry in the current week and the most recent entry the previous week.
Any help is much appreciated.
Your question is very vague.
Query #1:
For the most recent entry this week (including today), try max([DateFieldGoesHere]).
Query #2:
For the most recent entry in the previous week, it depends on how the week is defined.
If your week starts "7 days from now", then you can do a WHERE clause with a datediff of 7 days.
If you week starts on Sunday, then your WHERE will have to take that into consideration.
The datediff functions available to you will depend on the technologies you are using.
My problem is that I need to calculate a running total that works like a YTD.
The "year" in question is not a calendar year, it is an academic period.
TOTALYTD(..."28-02") nearly does the trick, however on leap years the 29th of Feb bleeds in to the next year's window.
I've tried CALCULATE(MyMeasure, DATESBETWEEN(...,...)) and this doesn't seem to work or I am just using the functions incorrectly.
To summerise, I need an expression that works exactly like TOTALYTD() but does not have the leap yer problem.
Thanks!
Unfortunately, I also experienced the same problem.
I created a dates table with a check to see if the year is a leap year.
Then I created this Dax Formula: Year End = IF(MAX( Dates[LeapYear] )=0,"02/28","02/29")
This worked perfectly, but if I add this to the TOTALYTD built-in formula like this Sales YTD = TOTALYTD( [Sales], Dates[Date], ALL( Dates[Date] ), [Year End]), it does not allow it - which is stupid - hopefully, they will allow this in the future.
I then found this answer, which answers your question but also doesn't because Power BI does not cater for it yet.
"You will need to write custom YTD measures instead" as per OwenAuger