Hi Scott,
Scott Gray wrote:
Hi Jacopo
I decided to have a look at this stuff and it doesn't make sense to me
why we have the billingAccountId on PaymentApplication rather than on
Payment itself?
I agree with you that having the billingAccountId in the Payment entity
would have made things simpler. I did not design this, it was already
there when I've refactored/fixed the billing account processes.
However, having the billingAccountId in the PaymentApplication improve
the flexibility: I could receive a Payment and use one part of it to pay
an invoice (not associated to a billing account) and use the remaining
to 'fill' a billing account.
Jacopo
It seems like the logic is pretty much the same
except we're doing it in a roundabout sort of way by creating a
PaymentApplication with null invoiceId just to maintain the link.
Thanks
Scott
