Feature Plan for version 4.6 of KMyMoney

Include below the items you think should be included in the next version For each item, add a subheader with a quick explanation


  • AlkValue
  • Budget revamp
  • Performance of the ledger
  • Reports internal structure revamp
  • Tags?
  • Schedule ids on transactions?
  • Online transfer of funds (via AqBanking)
  • Import CSV file via plugin
  • Streamline general statement interface and change OFX, QIF, HBCI and CSV plugins to use it consistently
  • Improve transaction matcher to cover more use cases
  • Improve investment support
 * Allow transaction in the investment account
 * Full support for online statement processing
  • Improve QIF importer to allow better conversion from other apps
  • Improve database backend
  • Improve treatment of transfer transactions (GUI/Dialogs with dual payees,No & Memo, Reports on transfers)
  • Data entry through Transaction Templates (with formulae)
  • Improve Business support (VAT, stocks, AR/AP)
  • Loans revamp (including different interest of arrears)


Budget revamp (Alvaro)

  • Make budgets rolling (no longer year-specific) and have 1 on the list be the default budget
  • Add assets and liabilities to budget
    • The user should enter the net variation for each account
    • The reports will have to be adjusted for this. Probably separate budgets at first
    • Variation on assets and liabilities count toward net variation
  • Advice whether budget is feasible: incomes should at least match expenses and net worth variation
  • Perhaps try to make the budget list dockable, as it won't be used much and it would be best to hide it or shrink it. Leave more room for the actual budget data

Report structure(Alvaro)

  • Port to a nested structure, to match the account hierarchy
  • Use a QAbstractModel?
  • Allow reports to have an arbitrary level of detail, with subtotals for each level

Transaction Form Updates

  • The current design should be freed from some legacy design decisions that are no longer relevant
  • View/Edit widgets are clumsy
  • Transaction type tabs could be made into a combobox
  • Investment transactions complicate the form
  • Transition auto-fill to an MVC architecture
  • Implement tags and transaction templates
  • Before starting on the above, we need requirements capture and a solid design, so that all developers understand the vision for this key piece of the code.

This page was last edited on 19 June 2011, at 08:04. Content is available under Creative Commons License SA 4.0 unless otherwise noted.