Hi
I am missing one rather important sorting possibility, namely to have the possibility to have the newest entry on the ledger at the last line, regardless which date the invoice, bill or such like has. This allows with one glance to check the correctness of my typing.

As I am not obliged to enter my data every day, just about a month before tax return date, I assemble usually a pile of 20 cm to record, absolutely in no data order.

In Quicken I could do this very simply by a possibility to «sort after newest entry». I have filed a wish at https://bugs.kde.org/show_bug.cgi?id=280465 and hope, some of you who would like such a feature too (or who just want to support me) can make such a comment?

Many thanks to all.

I think this may not be as hard as you think. As you have discovered, the manual does not really describe how to use the sort control dialog, but it is fairly easy. When you have the ledger displayed, right click on the header row. This brings up a dialog to control sorting. If you want to sort on entry order, first click to unset the "Use default" check box in the upper left. That will activate the dialog. At that point, the right column lists the active sort order of ledger columns from top to bottom. The list on the left is the other ledger columns which are not being used to sort. Click on "Entry order" in the left column to select it, and then click the right arrow between the two lists to move it to the active list. By default, it starts at the bottom, so click on it again to select it, and then click the up arrow to the right of the list to make it the first item in the sort order. Click OK and see if that does what you want.

Well, what do I have to say? Thanks you very much, that has been the solution. I have now in the right panel only the «Entry order» listed and I got exactly what I need for entering my next 200 bookings.

This will certainly speed up the entries and their control by about factor 1000.

Thanks again. I will now try do delete my bug report.

As you hopefully saw, you have (correctly) closed the bug (perhaps the state could have been "Works for me" rather than "Resolved" but you don't want to delete it. That way, if anybody else has the same problem, and searches to see if there is already a bug, they should find this one and see the solution.

Thanks again.