Access Data Movement between Query and Table (1 Viewer)

@ZoeMaKayla

What are your business rules regarding 3rd party payments?
Do payments need to belong to an existing customer?
Do you allow customers to pay on each other's sales (Normally when sub/contractor makes order but contractor or people that hired them) make payment?

3rd party payment can get tricky, depending on your business rules. This is something you would need to get written out before you start working on how your system will handle it. This is especially true where party A places order and party B pays on it, but its not the most recent order A has placed.

@Mark Thanks,
first the system can allow for payment without order raise and the payment can be applied to the order whenever raise.
Also, the payment on an invoice can either be once or installmental and can still keep tab on the order as against the payment
thirdly, another customer with excess in account can pay for another customer's order

@ZoeMaKayla

First is generally referred to as "prepay".

If you have a table of payments that still have value (not all applied) they you can apply payment to an order made AFTER the payment. Works the same as applying to an order made before the payment.

For the second, I normally would create child records to the customer file with "Next action". There are several ways to do this but all do the same thing; let the user know the customer has another payment due. This allows for installments as well as any other scheduled event (follow up on order, warranty expiration, scheduled service call) and can save a lot of hassle if you have more than one business process that requires scheduled actions with a customer.

You would still wait for the customer to make the payment before entering a payment transaction. This simply tells users when it SHOULD happen, not that it DID.

For the third, it works just like any other payment but is NOT limited to only orders made by that customer. This would normally have either a text "Note" as part of the junction record OR a child "Note" file; depending on business needs.

Please note, using a junction table to join otherwise unrelated records can be very useful when you have a piece of data that logically connects the two. In this case you are using the join to ALSO hold date applied and amount applied.