I have the proposed modificatins to implement a real accounts receivable module finished except for the collections part which I am working on ATM and a SECA to apply avaliable credits automatically (not really sure if I want to do this or maybe have it configurable). All the code however is in a single file called BillingAccountWorker.java and it really needs refactored because there are services, helper methods and worker methods all in the same file. I have not done this because I hope this will eventually be adopted and the methods stuck in the Ofbiz classes.
It all works without changing any of the Ofbiz code, but two Ofbiz services are overridded with others that make small modifications to existing Ofbiz services. The basic premise is that every billing account transaction is backed by either a Payment and/or Invoice and the sum of the billing account is the sum of these entities. There is the odd case of a Payment made on an order (payment in advance), but that is all handled. OrderPaymentPreference is no longer used for billing accounts. All the UI work has been done using Opentaps. However, all that needs done there is to change the main-decorator (I think). All the UI widgets and such are in org.ofbiz.accounting.ar and in a separate hot-deploy folder. If anyone is chomping at the bit to see this, I can put up a Jira entry and upload it, or I want wait and do it after the collections piece is done. The big question for me is, are there any users who need real accounts receivable? This is not your typical need for most web based sales. It is more appropriate for organizations that do a significant part of their business using net x terms. I offer it early because I could certainly use help testing and fine tuning it. Skip
