Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Contents from David email.

A Payment applied to a BillingAccount should still be applied to an
Invoice. If a Payment comes in before the Invoice, then the Invoice should
be "applied" to the Payment when it comes in, or as they come in.There still seems to be some confusion about BillingAccounts. This has
been discussed before, so I'm not sure how to put it best...

A BillingAccount is essentially nothing. Just forget that it exists in
relation to regular Invoice and Payment processes. With or without a
BillingAccount those operate and flow the same.

...

I haven't reviewed the implementation of all of these things in detail
to verify they are working like this, other than review here and there
of commits and work done. If anything is assuming that Payments
assigned to a BillingAccount are never assigned to Invoices, then that needs
to be corrected. I'm not sure what that would even mean because in order
for books to balance and for Payments and Invoices to be "closed", they
have to be assigned.

Credit Limit:

A field on a BillingAccount entity records the value of Line of Credit issued to a Party billingAccount. If a Payment is received before Invoice or is a Customer Deposit, such payment can be applied to a BillingAccount.When a Payment is applied to a BillingAccount there should be a record there, but if the
PaymentApplication record(s) doesn't have the invoiceId field populated
it should not be considered applied to an Invoice and therefore "consumed".