Automated Payments

[awardsguy]

We've got a cpouple of banks and colleges that have different people paying bills. The name badge person wants to pay for badges, the sign person pays for signs, the promiiotional products people pay for that stuff, but there are also some people that are in a different dept that also occastionally want to order some of the above stuff.

What I'm wondering is if we can ***ociate more than one credit card on file (maybe an option to ***ociate a credit card with a person in the company rather than one credit card per company as it is in the autobilling function)?

[awardsguy]

Is this a viable idea?

[nielsnorby]

Why don't you duplicate the customer record and create one for each credit card

i.e.
1. XYZ Company - Nametag
2. XYZ Comapny - Plaques
3. XYZ Company - Promo Items

Then you can have a credit card ***ociated with each one and keep it clean and simple

[M. David Matney]

Sounds to me like Niels' idea is a good solution. The billing for a single customer is designed to be static. If you have multiple departments that handle billing separate, they should be setup as separate customers, since in essence they are treated as separate customers.