Is it possible to make Reports Aged Receivables by due date, because custom report made by Issue date is not usseful regarding prediction cash flow and domestic tax regulative ( Republic of Serbia ).
Thank you in advance.
I am confused, because the: Reports → Aged Receivables produces exactly what you ask for, i.e. by due date
I also point out that an aged receivables report, in Manager or any other accounting system, is not a predictive report and has nothing to do with cash flow. It is a presentation of how late your customers are in paying their invoices.
No. It works by Issue date…
You are right it is by issue date. So +90 days is from issue date not due date. It indeed would be helpful to have a report that generates overdue invoices based on due date.
As far as I know, the column [Current] in the [Aged Receivables] report represents the invoices within the due date term, the column 1-30 days etc. represents the invoices which are older then the due date, but not older then 30 days and so forth.
Ofcourse all based on the issue date.
It doesn’t matter the number of days ( 30+ or anything ), the point is that report need to be based on the due date… For example, a tax regulative in the Republic of Serbia demands to make report with unpaid invoices from 60+ days based on due date…
Thanks for the explanation.
IFRS requires aging of receivables by due date. However, if there’s regulation somewhere that requires aging by issue date then I think this should be considered as an idea.
@Ivan_Raonic please provide a link to the reference resource that where this is required:
This is not an accountant issue although tax issue…
https://www.narodnaskupstinars.net/?q=la/akti/usvojeni-zakoni/zakon-o-porezu-na-dobit-0
" Corporate income tax law
That’s an index page of the entire Serbian tax laws. That’s not particularly useful to this discussion.
I quote Corporate Tax law, and YES, everything I wrote is important, and it is not for debate, already calling for creators of this software to create the mentioned report…
If you would like any change to the software to occur I suggest you stop and think briefly.
- You have not contracted the software developer to do any task
- You are not in a position to dictate a change will occur just because you feel it is a good idea
- Changes to the software occur continuously, but none are dictated by community forum users
- There is currently 233 good enhancement listed in the “ideas” section of the forum. Your idea will not be added unless it is at least as beneficial to the software product.
- The software developer has given higher priority to true legal requirements in a jurisdiction (as opposed to typical approach)
Then you are making zero contribution to increase the chance it is ever implemented
As you have zero authority that is counter productive. A far more poductive approach is to
- demonstrate how the enhancement would improve the software for a high proportion of users
- Identify specific paragraphs of legislation which dictate a particular accounting treatment in your jurisdiction.
2 Likes
I don’t know that for sure and in order for you to show me that you need to have the patience to get your point accross.
You can start by:
Please understand that nobody else will read your country’s entire tax laws to further your idea. That’s something you will have to do yourself, unfortunately.
What R U talking about? I gave suggestions to software creators to make this statement…
The developper will have to have detailed official information on the requirement, not what your interpretation of the tax law is - however good that is. He will not read through the whole of the tax laws to find it
You will have to supply a link to the particular paragraphs of the tax laws that define the official requirement to have any chance of this idea progressing beyond a wish
Please use the official tax authorities website Tax system This is in English and as you were asked please provide a link and copy relevant text that states:
Thank you.
I’m confused. The accounts receivables report is broken down by invoice due date and always has been.
Who claims it’s by issue date, can you demonstrate using the screenshots?
@Lubos see post 7 in this topic.
Which would mean that the “due” date should be the starting point when counting for Aged receivables but Manager (rightly so) uses the issue date and counts back to it.
I think this statement is not right,
Manager counts the ageing days from the due date in Aged Receivables and Unpaid invoices
Means
Now