[EMAIL PROTECTED] wrote:
Jacopo
As the man with the plan,
uhm... me? :-)
I wanted to throw this new plan past you. I have
dug pretty deeply into the existing payment/billing account stuff and it
all seems a bit arcane to me and mostly because it looks like payments are
meant to be made from the company to a vendor and from a customer to the
company, all with the same screens.
I want to create a really easy to use AR payment system. The user enters a
payment and can then either apply the payment to individual invoices (and a
store credit if too much is received) or he can apply it to the billing
account, in which case we automatically apply it to the oldest invoices
first and then to a credit if too much is received.
I'd suggest the following subtasks:
a) implement a new service to automatically apply the payments
associated to a billing account to the older open invoices associated to
the same account; the new service will have one mandatory parameter
"billingAccountId" (and maybe one optional parameter "paymentId") and it
will:
- select the open invoices associated to the billing account and sort
them by date (older first)
- iterate on the list and for each of them call the service
capturePaymentsByInvoice passing in the invoice id and billingAccountId
(this is the service that is invoked when you click on the "capture"
link near the invoice in the billingaccoun-invoices screen)
b) the new service can be invoked by a new link ("apply payments to
invoices") at the top of the billing account->invoices screen or (maybe
in your custom application) triggered every time you associate a payment
to a billing account.
This should cover your requirements but it is also generic enough to be
a good fit for OFBiz.
What do you think?
Jacopo
Is this too simplistic for some reason I am missing? Do others have AR
needs outside this that would justify a more complicated transaction set?
Skip
