Moneydance currently lacks the ability to force transactions up or down in the order they appear in the registers. While it may seem trivial for accounts with low transaction volume, it can dramatically improve and speed up the user experience when reconciling accounts. Furthermore, accounts with very high transaction volume can become nearly impossible to successfully reconcile without such a feature.

I believe that a good approach to implementation would be something like this:

• Add an integer value to every ledger record that is not displayed in the UI.
• Populate this field in each ledger entry in an incrementing fashion.
• Create UP and DOWN arrow button UI elements that swap this new value between the selected and adjacent transaction records above or below it, depending on which button is pressed.
• Use this value to break any sorting ties, such as numerous transaction entries sorted by date and occurring in the same account on the same date.

This will allow users to make the transactions appear in the exact same order in Moneydance as they do in whatever data source they are reconciling against, making subtotals match.

Compatibility with old files lacking this field can be handled by a simple one-time check, where the value gets tacked onto all the records in whatever order they happen to occur in the database upon import.

Obviously these implementation suggestions are just broad brainstorming; your current underlying implementations and processes will dictate those details more than I ever could. Thank you!