My friend I would love to help you but what you are asking is not a simple question, rather asking us how to build an entire solution.
Are you familiar with relational databases at all?
Ever used FileMaker?
Your question is just rather vague...can you be more specific please? I mean there are probably a thousand different ways to achieve what you are trying to do...
You could always start with the FMP Inventory Starter Solution and build upon it. Add in payment plans, scheduling, flags for payment dates, etc.
Thank you for your reply! To answer your question, the answer is yes.
I am currently working on a speration model solution and the question I posted is just one part of it.
There are so many ways of doing the method above but I just wanted to have a brainstorm session if anyone was interested...and also wanted to know what others would do in this case..
For starters I'd use an Invoices table to record sales to each customer. A customer table to track each customer, and a payments table to record payments made by each customer. A join table between Payments and Invoices would be a very likely thing to add as it would allow a single payment to be applied to multiple invoices and also for a single payment to be applied as a partial payment of a single invoice.
Thanks guys. What I am thinking is to also add an order table to track the orders and then have an invoice table separately because some might have multiple invlices (ex: multiple payments).
How would the order table be different from invoices?
Can't customers make a single payment for multiple items/plans purchased?
Phil, yes, the customers can make a single payment.
My intention on making an order table is for the customers who want to make 3 payments on the order.
For example if a customer purchases some goods for $100 (not a monthly plan), then they can split the payment into 3 times.
Is the added table then to document the payment plan for a given customer? (I can see where that could be useful here.)
Recording the actual payments can be recorded in a payments table with links to a customer table, and a join table can link it to invoices so that one payment can apply to multiple items and also for one payment to represent a partial payment.