> I think what you want to try is this:
>
> > <bean id = "financialRules"
> > class="org.mifos.accounts.financial.util.helpers.FinancialRules"
> > abstract="false" factory-method="getInstance">
> >   <property name="actionToDebitAccount">
> >     <map>
> >       <entry key="FEEPOSTING" value="11201"/>
> >     </map>
> >   </property>
> >   <property name="actionToCreditAccount">
> >     <map>
> >       <entry key="FEEPOSTING" value="31300"/>
> >       <entry key="MISCFEEPOSTING" value="31304"/>
> >     </map>
> >   </property>
>
> We only allow 1 type per entry key but then when you create your fees in 
> Mifos, you can select any GL under 31300 > as the account it goes to.  You 
> should try what I said above to see if it will work.  You can continue to set 
> Misc Fee > to be 31304 and that will go to the right account.

OK.  So I have re-deployed (and re-configured) keeping the above in
mind.

I tried adding the custom chart of accounts below thinking I would see
them in the drop down list of MIFOS when creating a fee from the admin
interface.

<GLAccount code="31301" name="Fees" />
<GLAccount code="31302" name="Processing Fees" />
<GLAccount code="31303" name="Training Fees" />
<GLAccount code="31304" name="Service Fees" />
<GLAccount code="31305" name="Other Fees" />

But I still see only the ones that were there in the default chart of
accounts. I have tried dropping and re-creating the database with my
own custom configuration to no avail.

I am almost there but still don't get fully how to customize the chart
of accounts.

Any help would be very appreciated.

Thank you,

--
GH

------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Mifos-users mailing list
Mifos-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mifos-users

Reply via email to