Sander van der Heyden and Binny Gopinath Sreevas
We were planning to have a relook at
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
Earlier, I was assuming that the fund sources for all products would be the same, so consolidated transactions like
Accounting Rules:
Based on the discussion in the comments below, accounting rules shall be the same for both inter/ intra branch transactions
- Scenario 1) Disburse loan to a savings from Branch A to Branch B
Loan disbursal should: Debit Loan Portfolio and Credit a Liability account for "Branch Liability Transfer"
Savings should: Credit Savings Control and Debit a Liability account for "Branch Liability Transfer"
- Scenario 2) Transfer from savings to
...
- Loan from Branch A to Branch B
Savings withdrawal in Branch A should: Debit Savings Control
Loan ShouldControl and Credits a Liability account for "Branch Liability Transfer"
Loan repayment in Branch B should: Credit Income from interest, income from fees, loan portfolio, income from penalty and Debit the account for "Branch Liability Transfer"
- Scenario 3) Transfer from savings(pr-a) to savings(pr-b)
...
- where pr-a is a withdrawal and
...
- pr-b is a
...
- deposit from Branch A to Branch B
savings (pr-a) in Branch A : Debit pr-a' Savings Control and Credits a Liability account for "Branch Liability Transfer"
savings (b) : Credit in Branch B: Debits a Liability account for "Branch Liability Transfer" and Credit b's Savings Control
would make sense (as long as all of them are within the same branch)
Questions (Blocker in the same branch):
What happens if the fund source for two products are different? Then what we are doing currently is more appropriate!
Ex: For scenario 1)
Loan is mapped to a Bank Account and Savings is mapped to Cash. If I disburse a loan to savings, I would have to show that my Bank account has decreased (which the shown transaction would not do)
Also, such concerns may be purely developer issues and not a valid use case. Can somebody please have a look at the suggested consolidated postings and comment?
Technical Changes are quite straightforward:
In GL_journal entry
entity_type_enum = 3 (Account Transfer)
what is entity Id? = Need to have a re-look
transaction_id = link to m_account_transfer_transaction ( Here add a new convenience label a "m_account_transfer_transaction tables id" )
account_transfer_transaction_id foreign key
( Is Payment details to account transfer (needs to be passed from the account on which the transaction was made) = Need to have a relookBranch Liability Transfer account shall be defined at an organizational Level
[Conversation with @pramod : Under https://demo.openmf.org/#/accounting, lets add a new section for "Map Organizational Accounts"
Here, a user will be able to edit predefined accounting types like "Suspense account for Liability Transfer", "Suspense account for Asset Transfer" or "Teller Cash Account". Need a set of API's for the same