|
Currently MifosX has a Journal entry screen which supports both simple and compound Journal entries.
You can select any number of accounts for debit and credit and pass entries as long as the amounts are balanced.
While this would be sufficient in an Ideal world (where everybody know accounting ![]() ), In the real world, the average end user (non-accountant) might not understand enough of accounting to use this screen for carrying out the most commonly used day to day activities like entering details of bank payments and receipts.
We were earlier thinking of adding country specific abstractions, but I guess they don't add too much value to the core platform.
We are currently thinking of a new feature called "Pre-defined posting rules"
So, an accountant would pre-define a posting Rule, by selecting the following
1) The default credit account
2) The default debit account
3) The name for the posting rule (Say "Bank deposit to HDFC Bank")
(Assuming that this is a simple journal entry)
This rule could then be used by data entry operators:
a) Click on "Bank deposit to HDFC Bank"
b) In the appearing screen, enter a non-zero amount
and Voila, you are done! Based on the accounting rule selected, the appropriate debits and credits would be done automatically.
We would then want to extend this functionality to support
a) "Pre-defined posting rules" for Compound Journal entries (wherein multiple accounts would be affected)
b) "Partially" defined posting rules: wherein the accountant would select the either the "Debit" or "Credit" accountant and say that
the opposite posting (either Debit/Credit) could can have "n" number of transactions from any of "These" accounts
Here "These" is a set of accounts that the accountant pre-selects.
Now, when a data entry operator opens the entry screen, he has an option to select among a list of accounts and and add amounts for each selection and make the posting (This would be very helpful for building error proof bank/cash receipts/payments functionality etc).
We need to build both the API and a Generic UI for this functionality
|
